-
Notifications
You must be signed in to change notification settings - Fork 2
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
use of isced:level and addr:full #4
Comments
cc. @dannykath |
Hey @govvin, sorry for my late response, I checked your comments and I have some comments:
According to schema, we have considerated 3 levels : Initial, primary and secondary.
I think we can fix this one run a query using overpass for initial level, primary and secondary and change the data for avoid this issue 👍
According to data of INEI , the political division has 4 levels : Department, province, district and populated center and in openstreetmap does not exist populated center, and this was the reason because we use
I don’t have enough information about the 👉 |
Where street-level information is not available, you may use |
This is great!! @govvin thanks !! I will change the documentation about this ☝️ |
In the the proposal page for
isced:level=xxx
key, the values for levels are supposed to be numeric.In this import, you have these values as
primary
orsecondary
, where they should be as1
or2
, respectively. Also note that kindergartens may also be tagged asisced:level = 0
I'm curious about your use of
addr:full
with a value that duplicates theaddr:subdistrict
key and theaddr:district
that duplicatesaddr:province
Based on the image above, the field value should have been justaddr:full = Titihue, Huancane
In the following case:
The value could be
addr:full = Azangaro, Chupa, Caminocoya
, or often in the format<housenumber> <street address> <neighbourhood> <town> <zipcode> <country>
I'm familiar with these keys because I have a similar import in the pipeline, and appreciate the value of these imports add to the map, and their importance to the community. I'm curious with your use case.
The text was updated successfully, but these errors were encountered: