hi, > ... > Reservation-boundary might cross a first admin boundary, so two admin=3's might cross/hit oneself. You need to establish for these "meta-state" situation "a" distinction-term - or create a seperate boundary system - or make-up the admin-levels by adding more levels (f.e. 40-49) - like in protected_areas. And even reservations might hit eachother(?).
This "protected_areas"-key is, where you have to act in any way different than usually - where you have to take care, change your behavior (no photo), because of named *local* policies. A Reservation is located in state(s), which give or takes sovereignty (domestic dependent nation). A reservation is no province - but it might become one ... and doesn't mean the distribution area of an ethnic group. With these class=24 you have a clear seperate key. Question is, if one level is enought: With a use of Relations, you can too combine scattered tribal lands and too seperate zones within one level - so OSM don´t has to stand by with a long number of levels, what is to be avoided (I heard), &if you think of possible global ideas. zone example: <http://www.openstreetmap.org/browse/relation/1749699> best, tshrub _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
