[OSM-talk-be] Format of is_in tags in Belgium
List, Long story short: I've noticed that there are many, many is_in tags in Belgium which do not conform to the generally accepted OSM standard. (Note that I'm not debating here whether an is_in tag should or should not be used within OSM - I'm just interested in the is_in tags which are already there in the data). There are three main things which I've noticed, and I refer you to http://wiki.openstreetmap.org/wiki/Key:is_in for the currently 'accepted' standard. 1. Entities should be separated by semi-colons ;. There are many, many is_in tags with entities separated by commas ,. I'm not sure if this is something to do with automatic imports... 2. It is recommended that entities be written in ascending order of size. For example, the is_in tag for Ieper would be something along these lines: Ieper;West-Vlaanderen;Vlaanderen;Belgium;Europe. (Different [local] language versions of these names are perfectly acceptable. For example: Ieper;West-Flanders;West-Vlaanderen;Flanders;Vlaanderen;Belgium;Belgie;Belgique;Europe). 3. The is_in:country tag should have the name of the country, in English, in full. No abbreviations. I saw (and corrected) one example where the is_in:country tag had a value of BE. BE should go in the is_in:country_code tag. If have seen examples of the above 'problems' in both the flanders region and the walloon region, which is why I send this to the main mailing list - I thought at first that it might just be one person doing this in a local area, but it seems the practice is widespread. I'm not suggesting go all out and hunt them down: just, if you come across an is_in tag, check to see if it is up to standard! Cheers Tim ___ Talk-be mailing list Talk-be@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-be
Re: [OSM-talk-be] Format of is_in tags in Belgium
Tim Francois wrote: 2. It is recommended that entities be written in ascending order of size. For example, the is_in tag for Ieper would be something along these lines: Ieper;West-Vlaanderen;Vlaanderen;Belgium;Europe. (Different [local] language versions of these names are perfectly acceptable. For example: Ieper;West-Flanders;West-Vlaanderen;Flanders;Vlaanderen;Belgium;Belgie;Bel gique;Europe). This originates from an old German import (I think from Geonames). Their import script couldn't handle the different translations. It was noted at the time, but they never cleaned it up. Anyway, for my part all the is_in tags may be deleted anyway. Once the boundaries are there, you can derive your is_in information from them. Greetings Ben ___ Talk-be mailing list Talk-be@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-be
Re: [OSM-talk-be] Format of is_in tags in Belgium
hit send a bit too soon... Tim Francois wrote: 1. Entities should be separated by semi-colons ;. There are many, many is_in tags with entities separated by commas ,. I'm not sure if this is something to do with automatic imports... This has its origin also a long time ago. The first definition of the is_in key had comma-separated values. Only later it was replaced with a semicolon, to be consistent with other multi-value tags. But just no-one cares about the is_in tag anyway, so does it really matter? Ben ___ Talk-be mailing list Talk-be@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-be
Re: [OSM-talk-be] Format of is_in tags in Belgium
On Fri, Nov 5, 2010 at 2:14 PM, Ben Laenen benlae...@gmail.com wrote: snip But just no-one cares about the is_in tag anyway, so does it really matter? I know that was a flippant comment, but it's not true - there are many projects which still use the is_in tags. As I said in my original message though, that's not my point: my point is, if it's in the OSM database, and if it's not being deleted, there's no harm in fixing it up if you come across one. Thanks for the info though - I had a suspicion that the is_in tags may have been imported and/or the wiki changed since the inception of the is_in tags! Tim ___ Talk-be mailing list Talk-be@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-be
