-
Notifications
You must be signed in to change notification settings - Fork 117
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
This "Object tagged twice as way and relation" seems like a false positive #598
Comments
Please do not mark as false positive because it lost the marker. Can you point me the object, or wait it will be back. About the return as false positive it is a know bug. We are currently addressing it. |
Yes, there is something wrong. |
* frodrigo/master: Fix fallback coord on geocoding fails #591 Contains in place of Intersects in analyser_osmosis_double_tagging #598 Avoid duplicate in analyser_merge_geodesie #560 Avoid duplicate issues in analyser_osmosis_building_overlaps #560 Avoid duplicate issues in Analyser_Merge #560 Avoid duplicate issues in Highway_Lanes #360 Avoid duplicated issues in analyser_osmosis_relation_associatedStreet #560 Avoid duplicate issues in analyser_osmosis_relation_public_transport #560 Base subclass on node index #560 Avoid duplicate error from analyser_osmosis_boundary_intersect #560 Avoid duplicate issues in analyser_osmosis_powerline #560
Done. |
Thanks a lot. |
This issue seems to be back again: "Object tagged twice as way and relation" is reported for all cases where a simple way is enclosed by a multipolygon of the same type, e.g. a way tagged leisure=track within a multipolygon tagged leisure=track. Example: https://www.openstreetmap.org/relation/4493595 |
There is two unrelated tracks Check made with ST_Contains Use relation_shape from https://github.com/osm-fr/osmose-backend/blob/master/osmosis/CreateFunctions.sql#L127 |
http://osmose.openstreetmap.fr/en/error/31550558886
http://osmose.openstreetmap.fr/en/map/#item=4080&zoom=17&lat=51.097&lon=3.448011&level=1%2C2%2C3&tags=&fixable=
I don't understand that the object would be tagged twice as a way (707832083) and relation (9843260). The only thing I see is that the 'outer' member of the relation shares some nodes with the way.... Or am I missing something?
This seems like a false positive. I've tried marking it as such, but it comes back.
The text was updated successfully, but these errors were encountered: