On 2014-07-19 08:00, Paul Johnson wrote :
I don't see how that's the case, the reason being that the Supreme
Court has clearly ruled that tribes are above the state but
semi-dependant on the fed, as far as the law is concerned.
Furthermore, the state may still intervene, but has the option not to
in situations where it would otherwise be obligated, in tribal
regions. This makes a state not dissimilar to a county relative to
the tribe, particularly in cases like the Navajo and Iroquois, whose
jurisdiction crosses state boundaries.
On Sat, Jul 19, 2014 at 12:56 AM, Paul Norman penor...@mac.com
mailto:penor...@mac.com wrote:
On 2014-07-18 10:53 PM, Paul Johnson wrote:
I should add that I do not intend on changing state
boundaries, just mapping indian nations where I know the
boundaries to lie on the ground, as higher than state, lower
than the country, inside the US only, if that wasn't clear on
the admin level argument. It would still be possible to
render a map without such excluded territory at a state level,
since, in practice, there's a LOT of overlap in
responsibilities and jurisdiction.
What you're proposing badly breaks admin hierarchies - hence the
need to carve the bits out of the states if you wanted to go that
route.
Your solution would be to use another type of boundaries than
administrative, if not administered.
But beware that the Boundary key specifications
http://wiki.openstreetmap.org/wiki/Boundary look like changing every day.
Lately, I was looking for other types than administrative and they were
removed.
And now they're back.
At the same time, some page stated that type=multipolygon is deprecated
for boundaries.
I can't find that statement any more.
This raised an issue with overpass API, for which, to be considered an
area, an element must
http://wiki.openstreetmap.org/wiki/Overpass_API/Areas
* have a tag /admin_level/ and a tag /name/,
* have a tag /type/ with value /multipolygon/ and a tag /name/,
* have a tag /postal_code/, or
* have a tag /addr:postcode/.
Obviously, e.g. a national park has no admin_level and if it can't be a
multipolygon, it can't be an area.
Same for some touristic region which I tagged for the renderer.
But note that this spec has changed too, only for those who can read
overpass.
I think that linguistic boundaries are badly missing.
Based on the fundamental OSM rule that people do the same thing
different ways, I could use user_defined.
But I really prefer OSM to be predictable.
And there's is a contradictory boundary rule that what was correct one
day is decreed invalid the day after.
So, I would appreciate someone to notify me that all the targets have
stopped moving ;-)
André.
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
