-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Paul!
Well it's not *wrong* if you tag the admin_boundary on the way, rather than the relation. I'd advise that you use the relation, rather than the way tags, so I'm not sure *why* you've done it. There are downsides to using the boundary tags, Be careful of reading too much into the wiki, the wiki is not definitive, and is often wrong and ignored. OSM is more anarchistic than a wiki allows. :) You mentioned on the changeset that you wanted to render country borders, but not in the sea. Many people don't like the maritime borders, so you're not alone in that. There are other solutions, such as re-ordering your rendering to draw sea on top of the land, or processing the lines in postgis to remove the boundaries which aren't on the land (ST_Intersection), or using Paul Norman's OSMBorder which tells you if it's maritime or not. The downside to tagging the ways is that now the boundary is entered into OSM twice! ways and relation. We mostly use the relation, so the ways might get out of sync. Or someone who hasn't read this email will not know why there are boundary tags, and will remove the tags, and you'll have redo your work. Just please don't break our relations! We've spent ages mapping it all, and it could be easy for someone new to come in and accidentally break something. :) Just adding admin tags to the way won't do that. (BTW it's "Ireland" not "Eire" ;) ) [1] https://github.com/pnorman/osmborder On 10/04/17 22:18, Paul Oldham wrote: > Hi folks > > We at The Hug are coming to the end of rendering a set of tiles > for Ireland and we came across an odd issue when rendering the > border. We tried to use boundary=administrative plus admin_level=2 > as per the wiki[1][2] but when we rendered using that combination > we realized that there was a problem in that about 75% was so > tagged and the rest wasn't. > > Some sections were missing both tags, some were missing one. > > So I worked my way through all along the border to ensure the > entire border had boundary=administrative plus admin_level=2 so it > was both consistent and tied up with the tagging mandated by the > wiki. That both helped us and, I thought, was making the OSM data > more consistent. > > I also found that the much of border had a tag > boundary_type=nation. We weren't clear where that came from as it's > not mentioned in the wiki but we were faced with either taking it > out of lots of sections or adding it to less. Preferring to be > constructive rather than destructive we opted for the latter. > > I've since had a comment from user SK53 saying that "We're a bit > puzzled by these edits"[3] (I'm not sure who "we" is in this > context?) and they said: > >> At the very least you need to discuss this with the Irish OSM >> community at the talk-ie mailing list. > > So here I am. I think my questions are: > > 1. Are you happy with what I've done? > > 2. If not then can you explain why some of the border was not > previously tagged boundary=administrative plus admin_level=2 so > that I'm clear why it was done that way? > > 3. Does anyone know what the story is behind the > boundary_type=nation tagging? > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJY9KplAAoJEOrWdmeZivv2xzsIAI5BqMVrMuAS+j0KGAdE7W1+ pTMK0ti/TlPbNxDAvVsnf38ETfafDAvOtAjhzhXRdQbosshPYhN0vc367sDuBgC+ L9G/dw4Qd27t8LzKO5+gYkGOrKKsXZjQD6fFefl/jZT/aLNvEp/M07DS/JCpON4H PrOF/mh3kTbxCUurnIDpJEvU9vC8bSqP5jk7iR/58dYFoOvfA363TaNtQoFYMy5H 0WAvfyK2xsA3U1FzFZS8dN7i+kLLCpBPaGUyHTWrbI3XowCFmVzFQbfrFpzXyQ0m 1dYNSAzkxhMLMcRBBo+AcVelG0IigoXxnae/zx0JObTfMdrcHUNN3OGSVaCR/Lk= =f0Ue -----END PGP SIGNATURE----- _______________________________________________ Talk-ie mailing list Talk-ie@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-ie
