[Talk-us] Coolidge Corner, Brookline, MA has wrong zip code

[Bill Ricker]

I'll note that we've seen other Nominatum issues in Greater Boston, e.g.
County for a point near Somerville/Charles town boundary.

OSM used MassGIS not Tiger in Mass. for initial import. It was better than
Tiger back then but has different problems. I mention this because USA
rules of thumb only partially apply here.

Both Suffolk and Norfolk Co have multipoly and/or relations, so Nominatum
convex hull geo search can easily get confused if the data isn't perfect.
Brookline is one of Norfolk's two exclaves. Of course, zip boundaries cross
government admin boundaries at the USPS convenience, and aren't well
published. Nominatum does best effort ? So we may need to add Zip to some
points or admin poly?

CC-ing the Mass. Talk Group ...


On Dec 4, 2017 9:59 AM, "Marc Gemis" <marc.gemis at gmail.com> wrote:

> If you fill in "Coolidge Corner, Brookline, MA" on the nominatim
> website, and run that query:
> http://nominatim.openstreetmap.org/search.php?q=Coolidge+Corner%2C+
> Brookline%2C+MA&polygon_geojson=1&viewbox=
> Then click details, you end on the page
> http://nominatim.openstreetmap.org/details.php?place_id=498867
>
> There you see how the address is computed. The postal code is computed
> a bit different than the other data. From the table you see there is
> no boundary or so defined in OSM with the postal code  (there is no
> "details >").
> This means the postal code comes from either an external source that
> was imported by Nominatim or an as part of an address node. But when I
> click on the address node details for "Coolidge Corner, Brookline, MA"
> or Allston, I do not see a postal code at all.
>
> So I think
>
> 1) whatever you changed is not reflected in the OSM database
> 2) the postal code is coming from an import (most likely Tiger data)
> in the Nominatim database.
>
> hope this make sense
> m.
>
> On Mon, Dec 4, 2017 at 2:42 AM, Andre Robatino
> <robatino at fedoraproject.org> wrote:
> > Nominatum's top result for "Coolidge Corner, Brookline, MA" still has
> 02446
> > (as it did immediately after I read your reply), but the other results
> still
> > have 02118. Shouldn't it have been copied to all the mirrors by now?
> >
> > BTW, I was wondering if it would make sense to use a list of specific
> > addresses as a sanity check on edits. Someone could register address(es)
> > they are familiar with, such as their own, and they would be notified
> > automatically if any of the associated data (such as county or zip code)
> > changed. If the change is wrong, they could log in and flag the error,
> and
> > the mistake could be traced back to the offending edit. If this existed,
> I
> > could have used it both for the zip code error, and for the wrong county
> > error that I reported in July, in
> > https://lists.openstreetmap.org/pipermail/talk-us/2017-July/017529.html
> .
> >
> > On 11/19/2017 02:57 PM, Clifford Snow wrote:
> >
> > Nominatim should return the correct results now.
> >
> > Problem that Max Erickson discovered was an incomplete edit in Boston
> that
> > caused the problem. By adding a tag to the Boston node to describe the
> > feature, resulted in Nominatim returning the correct results.
> >
> > Clifford
> >
> > On Sun, Nov 19, 2017 at 11:34 AM, Clifford Snow <clifford at snowandsnow.us
> >
> > wrote:
> >>
> >> I just asked about nominatim on the IRC
> >>
> >> On Sun, Nov 19, 2017 at 11:30 AM, Max Erickson <maxerickson at gmail.com>
> >> wrote:
> >>>
> >>> Nominatim calculates 02118:
> >>>
> >>> http://nominatim.openstreetmap.org/details.php?place_id=498867
> >>>
> >>> Most of the data seems to have the correct addr:postcode:
> >>>
> >>> http://overpass-turbo.eu/s/t5e
> >>>
> >>> (The query includes postal_code but there aren't any in the data)
> >>>
> >>> So what is Nominatim looking at to come up with the calculated value?
> >>> I think the next thing to check would be boundaries enclosing
> >>> Brookline, not sure if that is how nominatim works though.
> >
> >
> >
> > _______________________________________________
> > Talk-us mailing list
> > Talk-us at openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/talk-us
> >
>
> _______________________________________________
> Talk-us mailing list
> Talk-us at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20171205/fe6eff0e/attachment.html>