-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Change "all" views to tables loaded via Flex style #337
Conversation
… moving code into shop_helper. Need to add more tests on original to help find the cause of the problem with this change.
2aa1c80
to
43e0d6f
Compare
Rebased and force pushed after #338. |
Problem is in the FAILED TEST: sql/shop_combined_point_osm_type_subtype_count.sql - See tmp/shop_combined_point_osm_type_subtype_count.diff
docker exec -it pgosm /bin/bash -c "cat /app/tests/tmp/shop_combined_point_osm_type_subtype_count.diff "
FAILED TEST: sql/shop_polygon_osm_type_subtype_count.sql - See tmp/shop_polygon_osm_type_subtype_count.diff
docker exec -it pgosm /bin/bash -c "cat /app/tests/tmp/shop_polygon_osm_type_subtype_count.diff " |
Cleaned up shops, started on POIs. |
Unsure why I'm getting this error
|
The error in #337 (comment) is quite unexpected. I believe I'm doing everything the same as the The { column = 'geom', type = 'point', projection = srid, not_null = true}, It fails adding rows on both polygons and lines (confirmed by commenting out the polygon portion...) which use these lines respectively. geom = object:as_polygon():centroid() and geom = object:as_linestring():centroid() The the error is |
Problem wasn't the |
* Add shop tests (#338) Add tests for shop point/polygon counts. Includes moving test docs to main docs page, and overall improvements to the examples. * Change "all" views to tables loaded via Flex style (#337) * Changing vbuilding_all view to building_combined_point table * Create PK, move helper into style folder * Starting to convert vshop_all. Current version has test errors due to moving code into shop_helper. Need to add more tests on original to help find the cause of the problem with this change. * Fix loading of shop polygons. Reset shop_polygon test output to actual. * Add detailed POI tests * Restructure POI loading in prep to migrate all view * Moving from vpoi_all mat view to poi_combined_point table * still failing on poi_combined_point * Fixed import problem by setting up ID column properly * Cleanup RE #320 (#340) * Remove refresh of MV that no longer exists. Make comments on new tables more consistent * Add missing comments. Install PgDD extension
Closes #320
The views have turned into tables and are not always created.
vbuilding_all
-->building_combined_point
vshop_all
-->shop_combined_point
vpoi_all
-->poi_combined_point
place_combined_point
table #339Pros / Cons / Inter-tangled
Enables loading combined point table w/out requiring load of full polygon data. This can be considerable size savings when larger polygons are involved in the source data but being simplified before loading to Postgres.
vbuilding_all and vshop_all were views doing combining, probably wasn't good for general querying performance beyond small regional data. New table structure is only points, and fully indexed.
Requires duplicating a bit of logic. The negative impact is minimized by moving common logic into new helper methods. E.g.
building
andbuilding_combined_point
leverage common logic inbuilding_helper
.Increased data size with
layerset=everything
with more data materialized to tables. Because of additional overhead not loading indefault
. However, this opens the opportunity to consider loading more_combined_points
layers into lightweight layersets. Going to consider adding aplace_combined_point
layer option. Some of those polygons are huge, and if all you need is a centroid.Additional Change Notes
Layerset: Basic
building_polygon
building_combined_point
poi_combined_point
Layerset: Everything
building_combined_point
poi_combined_point
shop_combined_point
Layerset: Minimal
poi
topoi_combined_point