You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: attila.asztalos[at]gmail.com [Submitted to the original trac issue database at 11.10am, Tuesday, 17th May 2011]
Nominatim does not seem to update parent information related to streets after a "suburb" type polygon (enclosing said streets) gets created. Case in point: http://www.openstreetmap.org/browse/way/106764291
Nominatim seems to have indexed said polygon (now 6 weeks old), acknowledged it as a suburb type entity, but it only assigned it as parent to the one street that has been edited since the polygon exists. The remaining (enclosed) streets that have remained untouched still do not have said suburb as their parent (and still come up as belonging to an old node type suburb that has lost the "suburb" attribute at the same time as the new polygon got created - but that's a different bug, #2727).
The text was updated successfully, but these errors were encountered:
Reporter: attila.asztalos[at]gmail.com
[Submitted to the original trac issue database at 11.10am, Tuesday, 17th May 2011]
Nominatim does not seem to update parent information related to streets after a "suburb" type polygon (enclosing said streets) gets created. Case in point: http://www.openstreetmap.org/browse/way/106764291
Nominatim seems to have indexed said polygon (now 6 weeks old), acknowledged it as a suburb type entity, but it only assigned it as parent to the one street that has been edited since the polygon exists. The remaining (enclosed) streets that have remained untouched still do not have said suburb as their parent (and still come up as belonging to an old node type suburb that has lost the "suburb" attribute at the same time as the new polygon got created - but that's a different bug, #2727).
The text was updated successfully, but these errors were encountered: