Hi,
> The general rule in OSM is that multiple values for a tag must be
> separated by a semicolon. [..]
Another general rule in OSM is that OSM only maps features that are
_currently there_. Why should we bother with old city names. They are
replaced and thus obsolete. There is no Leningrad any
Simon Ward writes:
> On Tue, Jan 27, 2009 at 04:36:08PM -0500, Matthias Julius wrote:
>> That's actually error prone if someone enters a semicolon who doesn't
>> know about the rule. I think that should better be reversed or '\;'
>> be used as separator because this is much less likely to appear
[Moved to dev; followups to dev]
On Tue, Jan 27, 2009 at 10:58:25PM +, Ævar Arnfjörð Bjarmason wrote:
> > I think multiple keys with the same name should be allowed for a
> > node/way/relation. AFAIK it's only the editors that don't currently let
> > you do this.
>
> Yes, the API and data fo
On Tue, Jan 27, 2009 at 10:24 PM, Simon Ward wrote:
> On Tue, Jan 27, 2009 at 04:36:08PM -0500, Matthias Julius wrote:
>> > This doesn't account for multiple names in the same language, though. I
>> > can also imagine a place having several old names over time, while
>> > old_name=* really only a
On Tue, Jan 27, 2009 at 04:36:08PM -0500, Matthias Julius wrote:
> > This doesn’t account for multiple names in the same language, though. I
> > can also imagine a place having several old names over time, while
> > old_name=* really only allows for one.
>
> IMHO there really needs to be a well d
Simon Ward writes:
> On Tue, Jan 27, 2009 at 02:50:37PM -0500, Russ Nelson wrote:
>>
>> On Jan 27, 2009, at 2:08 PM, Manfred Podzkiewitz wrote:
>>
>> > Hello, i have a question about the handling of unoffical, or ethnic,
>> > or
>> > historic names of towns and villages.
>> The TIGER import i
Andy Allan wrote:
> On Tue, Jan 27, 2009 at 7:50 PM, Russ Nelson wrote:
>> On Jan 27, 2009, at 2:08 PM, Manfred Podzkiewitz wrote:
>>
>>> Hello, i have a question about the handling of unoffical, or ethnic,
>>> or
>>> historic names of towns and villages.
>> The TIGER import in the USA uses name_1
Le 27 janv. 09 à 21:02, Simon Ward a écrit :
> This doesn’t account for multiple names in the same language,
> though. I
> can also imagine a place having several old names over time, while
> old_name=* really only allows for one.
The general rule in OSM is that multiple values for a tag must
On Tue, 2009-01-27 at 19:57 +, Andy Allan wrote:
> On Tue, Jan 27, 2009 at 7:50 PM, Russ Nelson wrote:
> >
> > On Jan 27, 2009, at 2:08 PM, Manfred Podzkiewitz wrote:
> >
> >> Hello, i have a question about the handling of unoffical, or ethnic,
> >> or
> >> historic names of towns and villages
On Tue, Jan 27, 2009 at 02:50:37PM -0500, Russ Nelson wrote:
>
> On Jan 27, 2009, at 2:08 PM, Manfred Podzkiewitz wrote:
>
> > Hello, i have a question about the handling of unoffical, or ethnic,
> > or
> > historic names of towns and villages.
> The TIGER import in the USA uses name_1 for alte
On Tue, Jan 27, 2009 at 7:50 PM, Russ Nelson wrote:
>
> On Jan 27, 2009, at 2:08 PM, Manfred Podzkiewitz wrote:
>
>> Hello, i have a question about the handling of unoffical, or ethnic,
>> or
>> historic names of towns and villages.
> The TIGER import in the USA uses name_1 for alternate names. P
On Jan 27, 2009, at 2:08 PM, Manfred Podzkiewitz wrote:
> Hello, i have a question about the handling of unoffical, or ethnic,
> or
> historic names of towns and villages.
The TIGER import in the USA uses name_1 for alternate names. Perhaps
we should view all tags starting with "name" as pot
Hello, i have a question about the handling of unoffical, or ethnic, or
historic names of towns and villages. Did you ever have searched for
"Krung Thep", which is the new offical name of the capital of Thailand?
I think, this town is better known to you as "Bangkok".
So, how do we handle historic
13 matches
Mail list logo
