-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generalized files at different tolerances have the same output #4
Comments
I also tested with a fresh, custom extract and see the same problem. Also looks like issues with other generalized layers.
|
So there are two issues raised here, one of which isn't an issue but a symptom of the other, namely:
The problem is that the generalized tables, loaded from the extracts we produce using the mapping found in https://github.com/mapzen/chef-mapzen_odes/blob/master/files/default/mapping.json, are empty. From the imposm3 documentation regarding the mapping:
I've been running tests this morning to try and get the generalized tables for waterareas and landusages to populate any data without any success. @migurski , and thoughts on what you think the mapping should look like? Do we even want to produce the generalized data? There was never any conscious decision made to do so, they just happened to be included in the default imposm3 mapping. |
As for the roads generalized tables, there are indeed differences in the geojson output depending on what location extract you're looking at between gen0 and gen1. So presumably for Prague, the available data simply happens to pass the threshold in both cases, making them the same. But if you look at SF Bay for example, you'll find differences. |
From the IMPOSM spec, https://imposm.org/docs/imposm/latest/database_schema.html#generalized-tables
the layers gen0 (tolerance 200m) and gen1 (tolerance 50m) should be different, but have the same output for both shapefiles and geojsons.
To reproduce:
A user alerted us about this through email support.
The text was updated successfully, but these errors were encountered: