I agree. In the USA, the five-digit postal code was introduced in 1963 and
called a "ZIP code," for "Zone" (first digit), "Improvement" (second and third
digits), "Plan" (fourth and fifth digits). In 1983, nine-digit codes were
introduced by adding a hyphen after the five digits and four more
On Mon, Jan 13, 2020 at 6:34 PM Joseph Eisenberg
wrote:
> In the USA a postal code is not actually an area, but a set of
> addresses. Often they are all in one area, but sometimes the area is
> not clearly defined. This is partially why postal codes are usually
> just added to the POI directly in
In the USA a postal code is not actually an area, but a set of
addresses. Often they are all in one area, but sometimes the area is
not clearly defined. This is partially why postal codes are usually
just added to the POI directly in the USA. Trying to make a sensible
set of areas or boundaries wil
On Sun, Jan 12, 2020 at 11:49 AM Mateusz Konieczny
wrote:
>
>
>
> 12 Jan 2020, 18:39 by snusmumriken.map...@runbox.com:
>
> On Sun, 2020-01-12 at 08:35 -0600, Paul Johnson wrote:
>
>
>
> On Sun, Jan 12, 2020 at 1:47 AM Snusmumriken <
> snusmumriken.map...@runbox.com> wrote:
> > On Sat, 2020-01-11
On Sun, 2020-01-12 at 22:53 +0100, Martin Koppenhoefer wrote:
> On 12. Jan 2020, at 08:47, Snusmumriken <
> > snusmumriken.map...@runbox.com> wrote:
> >
> > Not saying that OSM should do it, just that it doesn't differ that
> > much
> > from postcode areas, where a certain authority has designated
sent from a phone
> On 12. Jan 2020, at 08:47, Snusmumriken
> wrote:
>
> Not saying that OSM should do it, just that it doesn't differ that much
> from postcode areas, where a certain authority has designated a certain
> number to a certain area, although there is no ground-truth that could
>
On Sun, 2020-01-12 at 21:00 +, Jóhannes Birgir Jensson wrote:
> So you suggest that we help routers to blacklist these areas,
Wow, you're putting words in my mouth that is the exact opposite of
what I wrote a couple of e-mails back. That is really dishonest.
___
So you suggest that we help routers to blacklist these areas, which means
living there will become even worse as various services depending on our data
stop delivering there?
These no-go areas are very much based on estimates. Personally if we are
marking hazards then my country can pretty much
On Sun, 2020-01-12 at 18:46 +0100, Mateusz Konieczny wrote:
> > I understand that it would politically sensitive, but from a data-
> > model
> > point of view it doesn't really differ from postcode areas (under
> > the
> > assumption that there's an authority that designates some areas as
> > high
12 Jan 2020, 18:46 by matkoni...@tutanota.com:
>
>
>
> 12 Jan 2020, 18:39 by snusmumriken.map...@runbox.com:
>
>> I understand that it would politically sensitive, but from a data-model
>> point of view it doesn't really differ from postcode areas (under the
>> assumption that there's an autho
12 Jan 2020, 18:39 by snusmumriken.map...@runbox.com:
> On Sun, 2020-01-12 at 08:35 -0600, Paul Johnson wrote:
>
>>
>>
>> On Sun, Jan 12, 2020 at 1:47 AM Snusmumriken <
>> snusmumriken.map...@runbox.com> wrote:
>> > On Sat, 2020-01-11 at 21:22 +0100, Martin Trautmann via talk wrote:
>> > > On 2
On Sun, 2020-01-12 at 08:35 -0600, Paul Johnson wrote:
>
>
> On Sun, Jan 12, 2020 at 1:47 AM Snusmumriken <
> snusmumriken.map...@runbox.com> wrote:
> > On Sat, 2020-01-11 at 21:22 +0100, Martin Trautmann via talk wrote:
> > > On 20-01-02 12:23, pangoSE wrote:
> > >
> > > > A map cannot solve a
On Sun, Jan 12, 2020 at 1:47 AM Snusmumriken
wrote:
> On Sat, 2020-01-11 at 21:22 +0100, Martin Trautmann via talk wrote:
> > On 20-01-02 12:23, pangoSE wrote:
> >
> > > A map cannot solve a lack of general awareness when visiting a
> > > new/unknown place. Going to the mountains to hike can also
On Sat, 2020-01-11 at 21:22 +0100, Martin Trautmann via talk wrote:
> On 20-01-02 12:23, pangoSE wrote:
>
> > A map cannot solve a lack of general awareness when visiting a
> > new/unknown place. Going to the mountains to hike can also be
> > dangerous
> > if you are not well prepared. This is of
On Sat, Jan 11, 2020 at 2:25 PM Martin Trautmann via talk <
talk@openstreetmap.org> wrote:
> On 20-01-02 12:23, pangoSE wrote:
>
> > A map cannot solve a lack of general awareness when visiting a
> > new/unknown place. Going to the mountains to hike can also be dangerous
> > if you are not well pr
On 11/01/2020 20:22, Martin Trautmann via talk wrote:
But a good map is for people who do NOT know this area.
People who know about neither need a map nor a warning.
Which those with more accurate, regularly updated data, such a emergency
services & governmental authorities, can provide by ov
> On Jan 11, 2020, at 12:22 PM, Martin Trautmann via talk
>
> and
> On 20-01-02 12:23, pangoSE wrote what they wrote.
To be clear, the hazards I'm hazily identifying are naturally-occurring or are
human-made real-life hazards that can cause you real harm if you approach them
and are not caref
On 20-01-02 12:23, pangoSE wrote:
> A map cannot solve a lack of general awareness when visiting a
> new/unknown place. Going to the mountains to hike can also be dangerous
> if you are not well prepared. This is of course not marked on the map!
I agree that I don't know any non-subjective way ho
On 2020-01-01 15:28, Rory McCann wrote:
This topic has come up before, and unfortunately when you think about
it, there is no objective way to define a "no go area". It's all
subjective. So it doesn't belong in OSM.
People do live in many of these areas, so software that didn't route
in/throu
This topic has come up before, and unfortunately when you think about
it, there is no objective way to define a "no go area". It's all
subjective. So it doesn't belong in OSM.
People do live in many of these areas, so software that didn't route
in/through these areas would be pretty bad for pe
20 matches
Mail list logo
