On 26/08/2020 07.12, pangoSE wrote:
I rest my case. Thanks for the examples. Could you help update the wikipage
about POIs to reflect this?
By "the wikipage", do you mean
https://wiki.openstreetmap.org/wiki/Points_of_interest? It isn't
immediately obvious where this information would be adde
Hi
Matthew Woehlke skrev: (25 augusti 2020 15:25:19
CEST)
>On 24/08/2020 16.25, pangoSE wrote:
>> Martin Koppenhoefer skrev: (24 augusti 2020 02:16:27 CEST)
>>> Also useful when the POI is approximately placed (e.g. in a
>>> neighbouring building, happens quite often, at least as long as most
>>
On 24/08/2020 16.25, pangoSE wrote:
Martin Koppenhoefer skrev: (24 augusti 2020 02:16:27 CEST)
Also useful when the POI is approximately placed (e.g. in a
neighbouring building, happens quite often, at least as long as most
POIs are not yet mapped)
Really? Can you link to an example? I have n
Martin Koppenhoefer skrev: (25 augusti 2020 09:18:08
CEST)
>
>
>sent from a phone
>
>> On 25. Aug 2020, at 02:07, pangoSE wrote:
>>
>> What I mean is that its a bad idea to keep the exact same data in
>multiple places and thinking about it postal addresses follows land
>plots and legal bounda
sent from a phone
> On 25. Aug 2020, at 02:07, pangoSE wrote:
>
> What I mean is that its a bad idea to keep the exact same data in multiple
> places and thinking about it postal addresses follows land plots and legal
> boundaries and not POIs.
it is often not the exact same data. Housenum
Hi
Andrew Harvey skrev: (25 augusti 2020 00:39:55 CEST)
>On Tue, 25 Aug 2020 at 06:27, pangoSE wrote:
>
>> The POI IMO cannot logically have an adress itself, its a human
>symbol for
>> designating something of interest within a feature like a building,
>park or
>> whatever. Adresses are special
On Tue, 25 Aug 2020 at 06:27, pangoSE wrote:
> The POI IMO cannot logically have an adress itself, its a human symbol for
> designating something of interest within a feature like a building, park or
> whatever. Adresses are specialized designations used by the state and
> postal service. You can
Hi Martin
Martin Koppenhoefer skrev: (24 augusti 2020 02:16:27
CEST)
>
>
>sent from a phone
>
>> On 23. Aug 2020, at 23:20, pangoSE wrote:
>>
>> This collides with one feature one element does it not?
>
>
>it does not. An address is not (necessarily) a feature, it can also be
>a property
Hmm
sent from a phone
> On 23. Aug 2020, at 23:20, pangoSE wrote:
>
> This collides with one feature one element does it not?
it does not. An address is not (necessarily) a feature, it can also be a
property
> Can you give an example of what you mean by stable?
if you move the POI or the b
Martin Koppenhoefer skrev: (23 augusti 2020 19:15:04
CEST)
>
>
>sent from a phone
>
>> On 23. Aug 2020, at 18:53, Thibault Molleman
> wrote:
>>
>> Should that entrance node also have the
>> addr:housenumber=15
>> tag or is it assumed based on it being placed on the building's way?
>
>
>The ad
sent from a phone
> On 23. Aug 2020, at 18:53, Thibault Molleman
> wrote:
>
> Should that entrance node also have the
> addr:housenumber=15
> tag or is it assumed based on it being placed on the building's way?
The addr:housenumber ideally should be added to the object to which it applies
Hi,
You probably meant 5, not 15. I think it's OK to repeat the address on that
entrance node.
Jo
On Sun, Aug 23, 2020 at 6:53 PM Thibault Molleman <
thibaultmolle...@gmail.com> wrote:
> Update on my example I gave. We changed it to
> addr:housename=Residentie Den Oude Post
> addr:housenumber=1
Update on my example I gave. We changed it to
addr:housename=Residentie Den Oude Post
addr:housenumber=14
addr:street=Kasteelstraat
addr:unit=1A;2A;3A
A more complex example:
https://www.openstreetmap.org/way/699214532
So this is Kasteelstraat 5
The bank that's located on the bottom floor is on
sent from a phone
> On 23. Aug 2020, at 10:17, Jo wrote:
>
> The house number is not 12 and it is not 14, it actually is 12-14, because 2
> buildings were torn down and a single building was built instead of it. This
> also happens when people or companies acquire 2 adjacent buildings, they
Am 19.08.2020 um 10:46 schrieb Sarah Hoffmann:
> ...
> We'd also need a new tag to indicate the interpolation steps odd/even/all.
> It's not really
> a good idea to reuse addr:interpolation because on a building outline it
> becomes ambigious:
> you'd have to check for the presence of other tags
Hi, I changed it. I also added a url which has some additional background
information for the whole street.
I don't think we should drop hyphens in house numbers. The house number is
not 12 and it is not 14, it actually is 12-14, because 2 buildings were
torn down and a single building was built i
I think the old building at that location used to be split in 2 (thus the 2
housenumbers).
So Kasteelstraat 12 does not exist anymore.
I only just now realized I mapped this wrong (was one of my first things I
mapped a couple years ago).
By your photo, it looks like you could even put a building
On Sun, 23 Aug 2020 at 05:55, Thibault Molleman
wrote:
> This is a simple example: https://photos.app.goo.gl/wEQiB4X6BA3doK7T7
> one building, one unit/flat on each floor.
> mailbox at the front for all 3 units.
>
> https://www.openstreetmap.org/way/675768351
>
> currently mapped as:
> addr:house
This is a simple example: https://photos.app.goo.gl/wEQiB4X6BA3doK7T7
one building, one unit/flat on each floor.
mailbox at the front for all 3 units.
https://www.openstreetmap.org/way/675768351
currently mapped as:
addr:housenumber=1A;2A;3A
addr:street=Kasteelstraat
On Sat, 22 Aug 2020 at 19:13
sent from a phone
> On 22. Aug 2020, at 09:25, Thibault Molleman
> wrote:
>
> So what's the consensus on an apartment building (way) that has mailboxes for
> each person who has an apartment there.
> I've just been tagging those as:
> addr:housenumber = A1;A2;A3;A4;A5;A6;A7;A8;A9;A10;A11
a
A lot of those types of apartment buildings in my area (and i assume other
places in Belgium as well) don't have a "building housenumber", only the
individual flat housenumbers.
Making a node for every single flat just looks bad on the map. And I agree
that it just makes more sense to put it on th
Aug 22, 2020, 11:43 by andrew.harv...@gmail.com:
> On Sat, 22 Aug 2020 at 17:25, Thibault Molleman <>
> thibaultmolle...@gmail.com> > wrote:
>
>> So what's the consensus on an apartment building (way) that has mailboxes
>> for each person who has an apartment there.
>> I've just been tagging
hyphen denotes (or not... Or both... I don't care) a range.
>>
>> LeTopographeFou
>> De:>> >> tagging@openstreetmap.org
>> Envoyé:>> 20 août 2020 6:35 PM
>> À:>> >> andrew.harv...@gmail.com
>> Répondre à:>> >>
On Sat, 22 Aug 2020 at 17:25, Thibault Molleman
wrote:
> So what's the consensus on an apartment building (way) that has mailboxes
> for each person who has an apartment there.
> I've just been tagging those as:
> addr:housenumber = A1;A2;A3;A4;A5;A6;A7;A8;A9;A10;A11
>
Could you use https://wiki
épondre à:* tagging@openstreetmap.org
> *Cc:* matkoni...@tutanota.com; tagging@openstreetmap.org
> *Objet:* Re: [Tagging] We should stop using hyphens to denote address
> ranges
>
>
>
>
> Aug 20, 2020, 15:50 by andrew.harv...@gmail.com:
>
>
> And it may be useful to have tag
hould stop using hyphens to denote address ranges Aug 20, 2020, 15:50 by andrew.harv...@gmail.com:And it may be useful to have tag to mark "yes this is actually a single housenumber despitethat includes hyphen or something else that suggests range" I would assume that to be the default,
Aug 20, 2020, 15:50 by andrew.harv...@gmail.com:
>>>
>>>
>> And it may be useful to have tag to mark "yes this is actually a single
>> housenumber despite
>> that includes hyphen or something else that suggests range"
>>
>
> I would assume that to be the default, when there are multiple addr
>
>
> And it may be useful to have tag to mark "yes this is actually a single
> housenumber despite
> that includes hyphen or something else that suggests range"
>
I would assume that to be the default, when there are multiple addresses
best to mark them all out individually or use a linear way wi
sent from a phone
> On 20. Aug 2020, at 15:29, Mateusz Konieczny via Tagging
> wrote:
>
> And it may be useful to have tag to mark "yes this is actually a single
> housenumber despite
> that includes hyphen or something else that suggests range"
referring to addresses or to housenumbers,
Aug 19, 2020, 10:46 by lon...@denofr.de:
> On Tue, Aug 18, 2020 at 11:29:50PM +0200, Colin Smale wrote:
>
>> I think you misunderstand hyphenated addresses in Queens. The second
>> part of the hyphenation is not a flat/apartment number. As an example,
>> the Dunkin Donuts at the corner of 31st
On Tue, Aug 18, 2020 at 11:29:50PM +0200, Colin Smale wrote:
> I think you misunderstand hyphenated addresses in Queens. The second
> part of the hyphenation is not a flat/apartment number. As an example,
> the Dunkin Donuts at the corner of 31st St and 36th Ave has an address
> of 31-02 36th Ave,
Two dots are used in some circles to indicate inclusive range. eg 21..27.
Best, Peter Elderson
Op wo 19 aug. 2020 om 00:25 schreef Tod Fitch :
>
> On Aug 18, 2020, at 2:29 PM, Colin Smale wrote:
>
>
> Maybe we should use a different character to indicate a range, such as a
> slash?
>
>
>
> In
18 Aug 2020, 23:29 by colin.sm...@xs4all.nl:
>
> On 2020-08-18 22:39, Clay Smalley wrote:
>
>
>> If you
>>
>> On Tue, Aug 18, 2020 at 12:51 PM Colin Smale <>> colin.sm...@xs4all.nl>> >
>> wrote:
>>
>>>
>>> On 2020-08-18 20:55, Clay Smalley wrote:
>>>
>>>
On Tue, Aug 18, 2020 at 11:26 AM C
On Wed, Aug 19, 2020 at 9:28 AM Graeme Fitzpatrick
wrote:
> On Wed, 19 Aug 2020 at 05:51, Colin Smale wrote:
>
>>
>>
>> On the other hand using the "1-5" notation to indicate a range is pretty
>>> well understood in the UK at least. What it is missing is the
>>> "interpolation" value (even, odd,
> On Aug 18, 2020, at 2:29 PM, Colin Smale wrote:
>
>
> Maybe we should use a different character to indicate a range, such as a
> slash?
>
In the United States it is not too uncommon for infill housing in urban areas
to have fractional street numbers. So you can see addresses like “123 1/2
On Wed, 19 Aug 2020 at 04:26, Colin Smale wrote:
> There are two use cases here: one is "what is the address of this building
> (or whatever)" and the other is the reverse situation: "where can I find
> number XXX". As long as we have tagging that is potentially ambiguous we
> won't be able to co
On Wed, 19 Aug 2020 at 05:51, Colin Smale wrote:
>
>
> On the other hand using the "1-5" notation to indicate a range is pretty
>> well understood in the UK at least. What it is missing is the
>> "interpolation" value (even, odd, all).
>> So let us sort this mess out by defining:
>> 1) that a hyp
On 2020-08-18 22:39, Clay Smalley wrote:
> If you
>
> On Tue, Aug 18, 2020 at 12:51 PM Colin Smale wrote:
>
> On 2020-08-18 20:55, Clay Smalley wrote:
>
> On Tue, Aug 18, 2020 at 11:26 AM Colin Smale wrote:
> There are two use cases here: one is "what is the address of this building
> (o
If you
On Tue, Aug 18, 2020 at 12:51 PM Colin Smale wrote:
> On 2020-08-18 20:55, Clay Smalley wrote:
>
> On Tue, Aug 18, 2020 at 11:26 AM Colin Smale
> wrote:
>
>> There are two use cases here: one is "what is the address of this
>> building (or whatever)" and the other is the reverse situatio
On 2020-08-18 20:55, Clay Smalley wrote:
> On Tue, Aug 18, 2020 at 11:26 AM Colin Smale wrote:
>
>> There are two use cases here: one is "what is the address of this building
>> (or whatever)" and the other is the reverse situation: "where can I find
>> number XXX". As long as we have tagging
On Tue, Aug 18, 2020 at 11:26 AM Colin Smale wrote:
> There are two use cases here: one is "what is the address of this building
> (or whatever)" and the other is the reverse situation: "where can I find
> number XXX". As long as we have tagging that is potentially ambiguous we
> won't be able to
On 2020-08-18 16:10, Martin Koppenhoefer wrote:
> sent from a phone
>
>> On 18. Aug 2020, at 05:34, Paul White wrote:
>>
>> I wanted to raise a concern about tagging house numbers on a building using
>> a hyphen to denote the address range (e.g 33-55 Main Street).
> It's their address, and I
sent from a phone
> On 18. Aug 2020, at 05:34, Paul White wrote:
>
> I wanted to raise a concern about tagging house numbers on a building using a
> hyphen to denote the address range (e.g 33-55 Main Street).
I am not sure for buildings, but for addresses I use this all the time, because
t
On Mon, 17 Aug 2020 at 23:32, Paul White wrote:
> I wanted to raise a concern about tagging house numbers on a building using a
> hyphen to denote the address range (e.g 33-55 Main Street).
Let's keep in mind there are also buildings in London and possibly
elsewhere which have a _single_ entranc
On Tue, 18 Aug 2020 at 19:15, Simon Poole wrote:
> The correct ways to model a range of house numbers is to use an address
> interpolation or explicitly list the numbers (using comma or semi-colons as
> delimitiers), anything else is woefully underspecified, not to mention
> other issues, for exa
The correct ways to model a range of house numbers is to use an address
interpolation or explicitly list the numbers (using comma or semi-colons
as delimitiers), anything else is woefully underspecified, not to
mention other issues, for example hyphens being used to delimit building
and apartment/u
Aug 18, 2020, 07:09 by andrew.harv...@gmail.com:
> > Data consumers see these hyphenated house numbers as one address, as well.
>
> Is that a problem? An address range can be considered a single address.
>
> > Create an address node for each housenumber and place each node somewhere
> > on the
> Data consumers see these hyphenated house numbers as one address, as well.
Is that a problem? An address range can be considered a single address.
> Create an address node for each housenumber and place each node somewhere
on the building outline (or inside the building)
I don't think that's a
Hello,
I wanted to raise a concern about tagging house numbers on a building using
a hyphen to denote the address range (e.g 33-55 Main Street). This is a bad
idea because some areas in the United States and possibly elsewhere use
hyphenated street numbers for individual dwellings.[1] Data consume
49 matches
Mail list logo
