Skip to content
This repository has been archived by the owner on Apr 2, 2020. It is now read-only.

Inconsistent admin_level on relation and label_node #3

Open
Noki opened this issue Mar 17, 2017 · 0 comments
Open

Inconsistent admin_level on relation and label_node #3

Noki opened this issue Mar 17, 2017 · 0 comments

Comments

@Noki
Copy link

Noki commented Mar 17, 2017

Hi!

We're currently play around with openstreetmap data and found quite some inconsistencies between administrative areas and the corresponding label nodes. The inconsistencies make it really hard to automatically build a trustworthy hierachie.

We found 53 relations where the admin_level of the relation and the area differs.

In my opinion areas and corresponding label nodes should always have the same admin_level and whenever there are multiple administrative levels there should be a relation for each one of them, even if they cover exactly the same area (correct my when I'm wrong).

From what I can see most of the time the correct admin_level is at the area.

I tried to write a challenge for it but I could not get the data selection working with the Overpass API.

Here is what I was trying to do:

RELATION MUST HAVE boundary=administrative AND admin_level IN (2 ...11) AND has(lable_node)
CHECK: relation->admin_level <> label_node->admin_level

Maybe someone could help with this one. Here is a list of affected relations: https://docs.google.com/spreadsheets/d/1yu1-3F8VYF8hA4ZuE_P_bIyuFpz_XZAbWRjlrDd8sdU/edit#gid=0

Best Regards
Tobias

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant