Am 18.08.2014 16:04, schrieb fly:
> Hey
>
> On the English wiki page [1] "comma" is the proposed separator for
> several values of addr:housenumber.
>
> This contradicts our rule of using "semi-colon" as separator of values
> and I do not have a clue why.
>
> I propose to deprecate "comma" and u
Am 24.08.2014 17:10, schrieb Friedrich Volkmann:
> On 24.08.2014 13:31, Christian Quest wrote:
>> In that case, how should application resolve housenumbers ?
>> What tagging do you propose to allow it ?
>
> I wrote down some thoughts here:
> http://wiki.openstreetmap.org/wiki/Proposed_Features/Mul
Martin Koppenhoefer wrote on 24.08.2014 22:50:
>> Il giorno 24/ago/2014, alle ore 14:03, Dan S ha
>> scritto:
>> On the other hand, if you see an object tagged
>> addr:housenumber=265-269
>> addr:interpolation=odd
>> then we can be quite confident that the mapper intended you to
>> interpret t
> Il giorno 24/ago/2014, alle ore 14:03, Dan S ha
> scritto:
>
> On the other hand, if you see an object tagged
>
> addr:housenumber=265-269
> addr:interpolation=odd
>
> then we can be quite confident that the mapper intended you to
> interpret this as "265" and "267" and "269".
Yes, but
> Il giorno 24/ago/2014, alle ore 12:24, Friedrich Volkmann ha
> scritto:
>
> The housenumber belongs on the building or building part, not the
> entrance(s).
In Germany house numbers belong mostly to the whole site, if necessary numbers
can also be assigned to staircases or individual buil
On 24.08.2014 13:31, Christian Quest wrote:
> In that case, how should application resolve housenumbers ?
> What tagging do you propose to allow it ?
I wrote down some thoughts here:
http://wiki.openstreetmap.org/wiki/Proposed_Features/Multiple_addresses
...although I do now prefer addr2:* instead
Hi Christian,
As I've already mentioned, in the other thread we discussed a
disambiguation. I would suggest that if you find only
addr:housenumber=265-269
then you can't really assume any interpolation, and I would argue that
even transforming it to "265" and "269" is going beyond what the dat
In that case, how should application resolve housenumbers ?
What tagging do you propose to allow it ?
I'm working on the BANO project who aims to create a nationwide address
database, using in part OSM data.
I already have to deal with this kind of addr:housenumber=*
For the moment, 265-269 is tr
2014-08-24 11:24 GMT+01:00 Friedrich Volkmann :
> On 18.08.2014 22:36, Janko Mihelić wrote:
>> What happens when the same entrance has two housenumbers, each from its own
>> street? I'm sure this exists somewhere.
>
> The housenumber belongs on the building or building part, not the
> entrance(s).
2014-08-24 11:05 GMT+01:00 Friedrich Volkmann :
> On 20.08.2014 10:18, Holger Jeromin wrote:
>> Andreas Labres wrote on 20.08.2014 04:10:
>>> On 19.08.14 23:17, fly wrote:
but 265-267 is wrong
>>
>> Read as "tagging 265-267 alone is wrong".
>>
>>> Disagree. addr:housenumber is the official num
On 18.08.2014 22:36, Janko Mihelić wrote:
> What happens when the same entrance has two housenumbers, each from its own
> street? I'm sure this exists somewhere.
The housenumber belongs on the building or building part, not the
entrance(s). When a building (part) has two equivalent addresses, use
On 20.08.2014 10:18, Holger Jeromin wrote:
> Andreas Labres wrote on 20.08.2014 04:10:
>> On 19.08.14 23:17, fly wrote:
>>> but 265-267 is wrong
>
> Read as "tagging 265-267 alone is wrong".
>
>> Disagree. addr:housenumber is the official number given to that building.
>> And if
>> it's "265-267
On 19/08/2014 22:17, fly wrote:
but 265-267 is wrong as 266 is not included. Either tag 265;267 or add
addr:interpolation=odd
I'm not clear with this example, do numbers 265 and 267 exist as
separate units inside the building?
In the UK, house numbers like 265-267 do exist where there is only
Am 20.08.2014 10:18, schrieb Holger Jeromin:
> Andreas Labres wrote on 20.08.2014 04:10:
>> On 19.08.14 23:17, fly wrote:
>>> but 265-267 is wrong
>
> Read as "tagging 265-267 alone is wrong".
+1
>> Disagree. addr:housenumber is the official number given to that building.
>> And if
>> it's "265
Andreas Labres wrote on 20.08.2014 04:10:
> On 19.08.14 23:17, fly wrote:
>> but 265-267 is wrong
Read as "tagging 265-267 alone is wrong".
> Disagree. addr:housenumber is the official number given to that building. And
> if
> it's "265-267", then addr:housenumber=265-267 is the only correct
>
On 19.08.14 23:17, fly wrote:
> but 265-267 is wrong
Disagree. addr:housenumber is the official number given to that building. And if
it's "265-267", then addr:housenumber=265-267 is the only correct implementation
of this.
This is not a listing, this is a label only.
/al
__
Am 19.08.2014 12:17, schrieb Andreas Labres:
> On 18.08.14 16:04, fly wrote:
>> On the English wiki page [1] "comma" is the proposed separator for
>> several values of addr:housenumber.
>> This contradicts our rule of using "semi-colon" as separator of values
>> and I do not have a clue why.
>
> I
On 18.08.14 16:04, fly wrote:
> On the English wiki page [1] "comma" is the proposed separator for
> several values of addr:housenumber.
> This contradicts our rule of using "semi-colon" as separator of values
> and I do not have a clue why.
I would not at all put different housenumbers into one t
What happens when the same entrance has two housenumbers, each from its own
street? I'm sure this exists somewhere.
2014-08-18 21:29 GMT+02:00 Martin Koppenhoefer :
>
>
> > Il giorno 18/ago/2014, alle ore 16:04, fly
> ha scritto:
> >
> > I propose to deprecate "comma" and use "semi-colon" inste
> Il giorno 18/ago/2014, alle ore 16:04, fly ha
> scritto:
>
> I propose to deprecate "comma" and use "semi-colon" instead to harmonize
> our data structure and allow QA software to find problematic values.
+1
Cheers,
Martin
___
Tagging mailing li
2014-08-18 15:04 GMT+01:00 fly :
> Hey
>
> On the English wiki page [1] "comma" is the proposed separator for
> several values of addr:housenumber.
>
> This contradicts our rule of using "semi-colon" as separator of values
> and I do not have a clue why.
Probably led by what users are already doin
I believe comma is used instead of semi-colon because the key
addr:housenumber frequently gets rendered, and comma is the common
separator symbol for end users.
2014-08-18 11:04 GMT-03:00 fly :
> Hey
>
> On the English wiki page [1] "comma" is the proposed separator for
> several values of addr:
Hey
On the English wiki page [1] "comma" is the proposed separator for
several values of addr:housenumber.
This contradicts our rule of using "semi-colon" as separator of values
and I do not have a clue why.
I propose to deprecate "comma" and use "semi-colon" instead to harmonize
our data struct
23 matches
Mail list logo
