-
-
Notifications
You must be signed in to change notification settings - Fork 471
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
missing outer polygon(s) when diff update deletes a multipolygon relation #67
Comments
Yes, this is a long standing bug in the diff import code. It has been reported as https://trac.openstreetmap.org/ticket/4525 However, as no one has done such an assessment or come up with a better way in the last 10 month, I will likely just go ahead and commit it soon and we will just have to live with the consequences to performance it entails. |
I doubt it will have a big consequences on performances. Deleting relations is not something that happens so much. |
Well, I have now committed the patch, which I believe should fix this. If anyone does notice a significant drop in performance (or other issues), please report. |
On 08/29/2013 12:09 PM, cquest wrote:
|
I posted my comment a bit too quickly... i was just too impatient. The patch seems ok, sorry. I'm just wondering now how to recover the lost polygons... |
When a multipolygon is deleted by diff updates, its polygon is correctly deleted from planet_osm_polygon, but if the outer member ways are still there in the DB, their polygons are not recreated and thus missing after the update because they were not created because of the multipolygon.
It looks like delete_rels query may set pending back true on members to workaround this, but I'm not familiar enough with osm2pgsql code to offer a patch.
The text was updated successfully, but these errors were encountered: