On Wed, Aug 19, 2015 at 1:32 PM, Scott Blanks <[email protected]> wrote:
> Hi all, > > I'm following up from a post I sent to the list a couple weks back. I > work at the LightHouse for the Blind in San Francisco. We have data we > hope to upload to OSM, and I had planned to share examples of the data > much sooner than today. Nonetheless, here is a glimpse at the the type > of information we have. I can attach an Excel doc if that's easier, > but for now I'll just post the raw data below. After taking a look at > this, I'd appreciate hearing from anyone about whether this is an > appropriate type of POI to upload to OSM. Keep in mind our goal is to > make this data available particularly to blind travelers, as it > contains key details that our community needs when traversing the > city. > I think the answer to this question hinges entirely on factors outside of OSM: namely will there be an app that speaks this data to blind users, and will that app gain traction? If nobody is listening, the data maintenance will be poor, and like other efforts right in San Francisco, fade away quickly: http://legacy.ski.org/Rehab/WCrandall/introts.html So at this point I would not focus on the question of good or bad data. Rather look at the user community, and what assistive apps they're using now, and if this data can flow *through OSM* into those apps (or devices or teaching materials or whatever is in use now). ----- I'd say that as it stands now the data is not a good candidate for OSM. And that the transfers data is redundant, and should not be imported. OSM has better ways of handling that data. By and large the lat/long should be used to confirm during conflation, and not be used as the actual location of the feature. The date revised is important, and appears to be blank in your sample data.
_______________________________________________ Imports-us mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports-us
