chore: bugfixes and notes after merging
This commit is contained in:
@@ -4,7 +4,7 @@
|
||||
DO
|
||||
$$
|
||||
BEGIN
|
||||
DROP TABLE IF EXISTS osm_boundary_polygon CASCADE;
|
||||
DROP TABLE IF EXISTS osm_boundary_polygon_nuts CASCADE;
|
||||
EXCEPTION
|
||||
WHEN wrong_object_type THEN
|
||||
END;
|
||||
@@ -12,8 +12,8 @@ $$ LANGUAGE plpgsql;
|
||||
|
||||
-- etldoc: osm_border_linestring -> osm_border_linestring_gen_z13
|
||||
-- etldoc: osm_border_linestring_adm -> osm_border_linestring_gen_z13
|
||||
DROP MATERIALIZED VIEW IF EXISTS osm_boundary_polygon CASCADE;
|
||||
CREATE MATERIALIZED VIEW osm_boundary_polygon AS
|
||||
DROP MATERIALIZED VIEW IF EXISTS osm_boundary_polygon_nuts CASCADE;
|
||||
CREATE MATERIALIZED VIEW osm_boundary_polygon_nuts AS
|
||||
(
|
||||
SELECT r.osm_id as relation_id,
|
||||
r.name,
|
||||
@@ -33,7 +33,7 @@ FROM (
|
||||
) as p
|
||||
LEFT JOIN osm_administrative_relation as r on r.osm_id = p.relation_id
|
||||
) /* DELAY_MATERIALIZED_VIEW_CREATION */ ;
|
||||
CREATE INDEX IF NOT EXISTS osm_boundary_polygon_idx ON osm_boundary_polygon USING gist (geometry);
|
||||
CREATE INDEX IF NOT EXISTS osm_boundary_polygon_idx ON osm_boundary_polygon_nuts USING gist (geometry);
|
||||
|
||||
|
||||
-- etldoc: osm_border_linestring -> osm_border_linestring_gen_z13
|
||||
@@ -117,7 +117,7 @@ FROM (
|
||||
FROM osm_administrative_boundary as b
|
||||
INNER JOIN osm_administrative_member as m
|
||||
ON b.osm_id = m.boundary_id
|
||||
INNER JOIN osm_boundary_polygon as r
|
||||
INNER JOIN osm_boundary_polygon_nuts as r
|
||||
ON m.relation_id = r.relation_id
|
||||
) as g
|
||||
GROUP BY osm_id, geometry
|
||||
|
||||
Reference in New Issue
Block a user