On Wed, Dec 27, 2017 at 4:13 PM, Greg Morgan <[email protected]> wrote:
> Daminan and Ilya, > > Thank you very much for this kind of effort. I tend to not map business > POIs any more. I'll add the address to a building polygon but not the > business information because of volatility. I spent too much time after > the sub-prime rate debacle cleaning up failed companies. I don't want to > maintain more of the same. Oh! But this is genius. There is a ref:walmart > in the data. You all can update the information as needed. There is no > way that I can keep this kind of data accurate. Moreover, there was a > bunch of SEO spam that was added in my area. It wasn't even useful and was > deleted. This project looks like a wonderful collaboration by working with > the community. All the new information added to these POIs is similar to > what I do with KeepRight corrections or OSM Inspector corrections. > > What I really like is that you have the addr:city, addr:country, and > addr:postcode tags set. Sometimes that is hard to come by. I see no > problem with the addr:full tag being used. I found that the SEO spammers > or even new mappers will try to shove the address in to addr:housenumber or > addr:street. If we can get the address code from balrog-kun or emacsen, > then we can come back later to expand addr:full to the other missing street > components. I wouldn't let addr:full be a show stopper. addr:full is a > perfectly valid tag in its own right. > > http://ksmapper.blogspot.com/2011/05/main-attraction.html > > balrog-kun > https://lists.openstreetmap.org/pipermail/talk-us/2010-July/003760.html > balrog-kun is/was one of my heroes. I did not have to manually make all those name expansions!!! Here is his code that operated on the western part of the US. https://trac.openstreetmap.org/browser/applications/utils/import/tiger2osm/expand/expand.py > > > Serge Wroclawski (emacsen) > https://groups.google.com/forum/#!topic/mappingdc/rB0U0aWmFwY > https://github.com/emacsen/tiger-expansion > > > On Mon, Dec 18, 2017 at 11:00 AM, Damian Rollison <[email protected]> > wrote: > > > > Hello to everyone on this thread, and thank you for the encouraging > comments and helpful suggestions! I'm glad to see how active you all are in > ensuring the OSM dataset is maintained at the highest quality. > > > > As you know, Ilya has kindly offered his help in working through the > import process with the OSM community. We'll be consulting with Ilya to > take those suggestions we can act upon and use them to improve the data. > > > > Assuming we are able to establish a relatively smooth and timely process > with this import, we have many thousands of brand-sourced POIs we would > like to add to OSM, both in the US and internationally. It's our job to > represent store locations as accurately and thoroughly as possible, so I > hope the community will find our contributions valuable. > > > > Looking forward to a great relationship, > > Damian > > > > > > > > On Mon, Dec 18, 2017 at 5:07 AM, Mike N <[email protected]> wrote: > >> > >> On 12/16/2017 8:01 AM, Ilya Zverev wrote: > >> > >>> OSM Conflator works only with nodes, except when it updates tags on > >>> polygons. If you like mapping building outlines, please do a challenge > >>> for MapRoulette after this import. Brandify doesn't have building > outlines. > >> > >> > >> A post-import MapRoulette challenge would make sense. A natural > progression when adding SuperCenter store detail is to add the POIs as > separate nodes. It should be no problem when adding them first except > that the address would logically belong to the building unless the embedded > stores have their own unit/suite number. > >> > >>> > >>> De-abbreviating street names and distinguishing "Fourth Street of Oaks" > >>> from "4, Street of Oaks" is a very complex task, and unrelated to the > >>> importing subject. I thought the street address from the source data > >>> would be better added to some tag on an object, but without touching > >>> addr:street and addr:housenumber. And addr:full looks good for this. > >>> There is no rules for this tag, and city and country are usually > >>> geocoded, so the value can help when searching. > >> > >> > >> The nearby OpenStreetMap road name could help since it's already in > the proper form. But there are also many US or state Highways that > haven't been set to a usable address name: for example the street and post > office address would be "Highway 244" but the nearby US244 only has a ref > but no name, or it is named "United States Highway 244". > >> > >> > >> > >> _______________________________________________ > >> Imports mailing list > >> [email protected] > >> https://lists.openstreetmap.org/listinfo/imports > > > > > > > > > > -- > > > > Damian Rollison > > > > VP Product > > > > Awarded "Best Dashboard For Managing Local Campaigns" > > > > Direct: 406.282.0773 <(406)%20282-0773> | Office: 888.377.2767 > <(888)%20377-2767> > > > > > > > > > > Confidentiality Notice: This communication, including any attachments, > is only for the use of the intended recipient and may contain confidential > and/or privileged information. If any reader of this communication is not > the intended recipient, then any use, disclosure or copying is strictly > prohibited and may be unlawful. If you have received this communication in > error, then please immediately notify the sender by return email, and > delete this communication and all copies from your system. > > > > _______________________________________________ > > Imports mailing list > > [email protected] > > https://lists.openstreetmap.org/listinfo/imports > > >
_______________________________________________ Imports mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports
