If an enclave then it will share borders so would have to be in a relation.
If an island it's highly likely to have other admin_levels or even be an
exclave.
-------------
I'd recommend
* adding maritime=yes to all required ways that don't have them.
* adding boundary=administrative relations to ways the require them
* removing admin_level & boundary=administrative from ways which have
them in relations
This should be adequate for OSM-Carto to render boundaries as desired.
however on GitHub, Matthijs claims "there is no way to express that in
CartoCSS".
This is not a good enough reason to add & use duplicated tags on ways.
It's been agreed they are redundant.
If Overpass can perform the required API call, why can't CartoCSS be
coded to do it?:
http://overpass-turbo.eu/s/x7H <http://overpass-turbo.eu/s/wWg>
rel"admin_level"="2"
<https://github.com/gravitystorm/openstreetmap-carto/pull/%7B%7Bbbox%7D%7D>;
way(r)["maritime"="yes"];
out geom;
DaveF
On 18/03/2018 22:23, Kevin Kenny wrote:
On Sun, Mar 18, 2018 at 12:11 PM, Andrew Hain
<[email protected]> wrote:
I agree entirely with Dave on this. Consider this a request to consider
systematically removing the admin_level tag from ways or making it a
discardable tag only for ways.
I hope that you mean 'ways that are also part of a
boundary=administrative relation.' It's easy to imagine an
administrative region whose border is a single way (it's an island, or
it's an enclave entirely surrounded by another administrative region.
If you mean by this statement that 'an administrative region must
always be a relation,' please make that explicit.
_______________________________________________
Tagging mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tagging
_______________________________________________
Tagging mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tagging
