Finally, let's save the last query as a view without ordering the results. This way, we can ease our future work by having shorter, and thus, more manageable chunks of code. We can easily create a view from QGIS's DB Manager by prefixing the query with CREATE VIEW AS and the view's name. However, before creating a view, let's talk about naming conventions. If we work with a PostGIS database extensively, we will definitely end up with different kinds of tables like the following:

• Original tables holding raw spatial data for our analyses, which shouldn't be modified or dropped accidentally
• Tables holding final or partial results of our analyses
• Views and materialized views holding queries, and speeding up our work

To distinguish between the different types of data, we should apply a naming convention. A good example would be prefixing different kinds of data with some abbreviations. This practice can help pgAdmin or other graphical interfaces to visually group and organize different kinds of data. We can name our views as vw_viewname or vwViewName, our temporal or final results as res_tableName or resTableName, and so on. It shouldn't really matter (although PostgreSQL will drop camel cases by default) as long as we keep to our rules, and name our tables consistently. Now as I'm naming my view vw_quiethouses, the query saving the view looks like the following:

    CREATE VIEW spatial.vw_quiethouses AS WITH main_roads AS (
     SELECT ST_Collect(geom) AS geom FROM spatial.roads r
     WHERE r.fclass LIKE 'primary%' OR r.fclass LIKE 'motorway%'),
    industrial_areas AS (
     SELECT ST_Collect(geom) AS geom FROM spatial.landuse l
     WHERE l.fclass = 'industrial' OR l.fclass = 'quarry')
    SELECT h.*, hwd.dist_road, hwd.dist_ind
     FROM spatial.houses h, main_roads mr, industrial_areas ia,
     LATERAL (SELECT ST_Distance(h.geom, mr.geom) AS dist_road,
     ST_Distance(h.geom, ia.geom) AS dist_ind) AS hwd
     WHERE hwd.dist_road > 200 AND hwd.dist_ind > 500;