Maarten Deen wrote:
> http://tweakers.net/nieuws/70621/dienstregeling-de-lijn-vanaf-2011-in-googl
> e-maps.html
>
> Tja...
Wel grappig dat dezelfde problemen als bij ons opduiken:
* wie is aansprakelijk voor verkeerde informatie
* hoe visualiseer je de routes
En dat eerste probleem zal ons noo
On Fri, Nov 5, 2010 at 2:14 PM, Ben Laenen wrote:
>
>
>
>
> 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, tha
http://tweakers.net/nieuws/70621/dienstregeling-de-lijn-vanaf-2011-in-google-maps.html
Tja...
Maarten
___
Talk-be mailing list
Talk-be@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-be
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
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 acce
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
