-
Notifications
You must be signed in to change notification settings - Fork 4
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
handle emtpy role as deprecated, too #28
Comments
There are currently so many empty roles that I didn't want to clog that category with those cases. Yes, they are wrong, but "not as wrong" as the other cases, so I see a lower priority for them. |
Do you know the order of magnitude of such cases (or affected % of total MPs)? In my limited personal experience, I have actually only relatively rarely seen such cases in comparison to old-style MPs (and for me, most often I saw inner ways with missing roles, like this example – which actually is a somewhat more severe error). |
PS: here's a simple overpass query to find multipolygons with empty role members for manual fixing: |
As I see here https://taginfo.openstreetmap.org/relations showing the ["empy role"] percent
|
sorry .. the affected % of total MPs : |
Thx, totally didn't think about just looking it up on taginfo. 😆 So, in absolute numbers it's about 6 times more empty role members than members where the role is anything other than "outer", "inner", or empty. |
yes, many Long tail - errors :) and there are some interesting combinations:
Side note: according the wiki:
So the type=boundary roles should be accepted as a valid
maybe this is not as important ( related to osm2pgsql change), but good cases for OSM Changeset Analyzers , osm-compare rules for detecting similar error types as early as possible. |
I think we should probably re-tag those as type=boundary. |
JOSM does this automatically for some years now. Hopefully not many left... Regarding this ticket - Did you check if the number of multipolygons with empty roles as outer differs a lot from these where roles are wrong or inner is empty? I very seldom find empty roles, but I found a large number of polygons in east Europe, which have all empty roles. Maybe fixing these will reduce the number of empty outers as well? Anyway showing the number of affected multipolygons instead of the number of affected roles would anyway be better :-) |
I fixed a lot of these in central Europe using the overpass query above and in most cases missing outer role also indicates other issues. So I agree, that role blank should be handled as error similar to any other role not outer/inner in the tests and statistics. Most often cases:
|
Maybe the Wrong role case should also include empty roles which are deprecated according to the wiki (since at least mid 2011):
The text was updated successfully, but these errors were encountered: