Bug in Philippines relations?

Avatar
  • updated
  • Not a bug

Hello, I think there is a bug in relation tree generation. Bangsamoro, Bicol Region, Cagayan Valley, etc. are part of Philippines (443174), not Philippines maritime boundary (2850940), yet OSM Boundaries database says otherwise. Which variables do you use to map them?


(2) Philippines | Relation: ‪Philippines‬ (‪443174‬) | OpenStreetMap

(2) Philippines maritime boundary | Relation: ‪Philippines maritime boundary‬ (‪2850940‬) | OpenStreetMap

Dataset Version: 2023-09-04

Pinned replies
Avatar
Magnus
  • Answer
  • Not a bug

It's not a bug in our end. This is how the data looks. We only present the data, we do not create it.

Please refer to the (not to thorough) documentation to read how the tree and its hierarchy is built.

The tree is based on the administrative levels of the boundaries. Boundaries fitting inside another boundaries is placed as a child to the outer one, and that's how the tree is built. Each level in the tree is sorted on the administrative level and then on the name.

Avatar
Magnus

There are no such immediate plans. Long-term we would like for it to be possible to use multiple variants of the tree, but it's not something we are working on at the moment. The honest truth is that there aren't much development of the site at all. There are plans to spend more time on it in the future though, but currently we lack the manpower, and funds.

Avatar
Yukha Dharmeswara

Thank you for your clarification! Is there any plan to refine it? Such as prioritize boundary=administrative as parent when there are more than 1 candidate on same admin_level.

That being said, I will try to find way to "fix" it from OSM side. Thank you.

Avatar
Magnus
  • Answer
  • Not a bug

It's not a bug in our end. This is how the data looks. We only present the data, we do not create it.

Please refer to the (not to thorough) documentation to read how the tree and its hierarchy is built.

The tree is based on the administrative levels of the boundaries. Boundaries fitting inside another boundaries is placed as a child to the outer one, and that's how the tree is built. Each level in the tree is sorted on the administrative level and then on the name.