Re: [Talk-us] [Imports] Integrating our open source data into OSM

2017-11-10 Thread Rihards 
On 2017.11.10. 00:11, Sean Lindsey wrote:
> It seems that it's going to be hard to come up with a mass import
> solution that every one can agree on. I would suggest that you take
> name, address, phone number, website and category then try and
> re-geocode the data, but it seems there is opposition to this method as
> well.
> 
> Another approach - as a way of keeping OSM and this data separate - is
> having this POI data be a "secondary resource" that OSM users could "opt
> in" to adding into their mapping set, but not be inherently owned or in
> OSM's primary data set. For example, by loading up an OSM database you
> could be linked to us or someone who creates a derivative of our data
> suitable for importing into OSM maps. Thereby OSM does not feel
> responsible for this resource but it still becomes available for people
> to import and use via us or someone else. In this case we would want to
> work with someone in order to create an OSM import-friendly version of
> this data. We have a ton of indicators that tell us the quality and
> freshness of this data and potentially we can rework in into something
> more usable.

as opposed to some other data (public transportation timetables and
similar), this information belongs in osm - the concern is not about it
being there, the concern is about licensing and accuracy, both being
discussed and clarified.
accuracy issue can be handled by a layer that looks for features in this
dataset that cannot be matched to existing osm features. sort of map
notes, although flooding notes with this might not be feasible.
osm community response, after a survey, could be to add the entity, add
it with corrections (location etc) or reject it as not existing on the
ground - it might be useful to get a feedback loop for those.

feedback amount will vary a lot. i'd expect smaller towns and the like
not to get much feedback at all. suggesting a layer like this to be
used. any pois without any feedback in 6 months to be imported (split in
smaller sections and all other usual precautions).
this would not be a blanked import and would be expected to be "better
than before".

> Thoughts?
> 
> On Thu, Nov 9, 2017 at 1:09 AM, Rory McCann  > wrote:
> 
> Hi Sean,
> 
> On 09/11/17 07:14, Sean Lindsey wrote:
> > Thanks for all the feedback, we have put together some blogs to help
> > people figure out how to play with the data, to give people an idea of
> > what it is and how it was put together.
> >
> > https://blog.cybo.com/
> 
> So that website says:
> 
> OmniPlaces is formed from billions of records (literally), from
> tens of thousands of sources (literally)
> 
> 
> Trying to figure out the licence for tens of thousands of datasets is
> practically impossible Licence issues are often a problem with
> imports, and I think this could be a show-stopper for this.
> 
> On 09/11/17 05:54, Jo wrote:
> 
> If the addresses are in the data as well, we don't really need
> to use
> the lat/lon coordinates.
> 
> 
> Not necessarily, depends where the addresses came from. If you had
> lots of lat/longs, and geocoded the, and threw away the lat/longs
> then you don't have a clean dataset.
> 
> -- 
> Rory
> 
> 
> 
> ___
> Imports mailing list
> impo...@openstreetmap.org 
> https://lists.openstreetmap.org/listinfo/imports
> 
> 
> 
> 
> 
> -- 
> Sean Lindsey
> Cybo Company
> LinkedIn 
> 541-912-2505 
> 
> 
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
> 


-- 
 Rihards

___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] [Imports] Integrating our open source data into OSM

2017-11-09 Thread Sean Lindsey 
It seems that it's going to be hard to come up with a mass import solution
that every one can agree on. I would suggest that you take name, address,
phone number, website and category then try and re-geocode the data, but it
seems there is opposition to this method as well.

Another approach - as a way of keeping OSM and this data separate - is
having this POI data be a "secondary resource" that OSM users could "opt
in" to adding into their mapping set, but not be inherently owned or in
OSM's primary data set. For example, by loading up an OSM database you
could be linked to us or someone who creates a derivative of our data
suitable for importing into OSM maps. Thereby OSM does not feel responsible
for this resource but it still becomes available for people to import and
use via us or someone else. In this case we would want to work with someone
in order to create an OSM import-friendly version of this data. We have a
ton of indicators that tell us the quality and freshness of this data and
potentially we can rework in into something more usable.

Thoughts?

On Thu, Nov 9, 2017 at 1:09 AM, Rory McCann  wrote:

> Hi Sean,
>
> On 09/11/17 07:14, Sean Lindsey wrote:
> > Thanks for all the feedback, we have put together some blogs to help
> > people figure out how to play with the data, to give people an idea of
> > what it is and how it was put together.
> >
> > https://blog.cybo.com/
>
> So that website says:
>
> OmniPlaces is formed from billions of records (literally), from tens of
>> thousands of sources (literally)
>>
>
> Trying to figure out the licence for tens of thousands of datasets is
> practically impossible Licence issues are often a problem with
> imports, and I think this could be a show-stopper for this.
>
> On 09/11/17 05:54, Jo wrote:
>
>> If the addresses are in the data as well, we don't really need to use
>> the lat/lon coordinates.
>>
>
> Not necessarily, depends where the addresses came from. If you had lots of
> lat/longs, and geocoded the, and threw away the lat/longs then you don't
> have a clean dataset.
>
> --
> Rory
>
>
>
> ___
> Imports mailing list
> impo...@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/imports
>



-- 
Sean Lindsey
Cybo Company
LinkedIn 
541-912-2505 <(541)%20912-2505>
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] [Imports] Integrating our open source data into OSM

2017-11-08 Thread Sean Lindsey 
Thanks for all the feedback, we have put together some blogs to help people
figure out how to play with the data, to give people an idea of what it is
and how it was put together.

https://blog.cybo.com/

I assumed the set we released was not yet ready for OSM but with some
guidance I may be able to go back through and derive something that's more
useful for you and likely others interested in working with the data. Most
of our records/POIs are from several different sources, which means the way
a record is compiled could influence how useful it is.

On Wed, Nov 8, 2017 at 8:54 PM, Jo  wrote:

>  If the addresses are in the data as well, we don't really need to use the
> lat/lon coordinates. The best way to use this kind of data, is to use it as
> one of several sources. So a direct import is out of the question, but
> using it as a shortcut and combining with what we already have plus aerial
> imagery plus possibly an extra lookup in other sources could be considered.
>
> Of course, we don't want to be a front end for SEO techniques, so maybe
> the data needs to be pruned from overly commercial information and
> descriptions, before it is useful to us.
>
> I'm downloading it too, but it takes a while. I can probably figure out a
> way to convert it into something usable (at a technical level).
>
> Polyglot
>
> 2017-11-09 2:53 GMT+01:00 Brian May :
>
>> Its critical to know where the lat/longs came from. For example, if they
>> came from Google Maps - then its a no go, because Google's licensing is
>> incompatible with OSM. Their geocodes are not public domain, etc. Same
>> thing applies to many / most other commercial geocoding services. If you
>> don't know how the lat/longs were derived, then that is probably a show
>> stopper as well.
>>
>> Brian
>>
>>
>> On 11/8/2017 1:53 PM, Sean Lindsey wrote:
>>
>> We have open sourced our US POI data, it may not be ready for a direct
>> import into OSM, but we'd be willing to try to get it there.
>>
>> Its a national directory of 59 million US businesses, that has been
>> updated as of this summer. And should be getting another refresh shortly.
>>
>> What process is there to discuss and work to integrate this data?
>>
>> The data is available under a creative commons attribution license at
>> https://omniplaces.cybo.com/
>>
>> I would be willing to waive and/or clarify certain aspects of the licence
>> if needed however.
>> * I asked this same question in help.openstreetmap.org
>> ,
>> and was referred to these mailing lists
>>
>> Regards,
>> --
>> Sean Lindsey
>> Cybo Company
>> LinkedIn 
>> 541-912-2505 <(541)%20912-2505>
>>
>>
>> ___
>> Talk-us mailing 
>> listTalk-us@openstreetmap.orghttps://lists.openstreetmap.org/listinfo/talk-us
>>
>>
>>
>> ___
>> Imports mailing list
>> impo...@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/imports
>>
>>
>


-- 
Sean Lindsey
Cybo Company
LinkedIn 
541-912-2505
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] [Imports] Integrating our open source data into OSM

2017-11-08 Thread Mike Thompson 
I downloaded data for one of the states (Colorado) to attempt checkout its
quality.  It appears to be in JSON (not GeoJSON).  Is there an easy way to
get the data into something like QGIS so it can be visualized on a map?



On Wed, Nov 8, 2017 at 6:53 PM, Brian May  wrote:

> Its critical to know where the lat/longs came from. For example, if they
> came from Google Maps - then its a no go, because Google's licensing is
> incompatible with OSM. Their geocodes are not public domain, etc. Same
> thing applies to many / most other commercial geocoding services. If you
> don't know how the lat/longs were derived, then that is probably a show
> stopper as well.
>
> Brian
>
>
> On 11/8/2017 1:53 PM, Sean Lindsey wrote:
>
> We have open sourced our US POI data, it may not be ready for a direct
> import into OSM, but we'd be willing to try to get it there.
>
> Its a national directory of 59 million US businesses, that has been
> updated as of this summer. And should be getting another refresh shortly.
>
> What process is there to discuss and work to integrate this data?
>
> The data is available under a creative commons attribution license at
> https://omniplaces.cybo.com/
>
> I would be willing to waive and/or clarify certain aspects of the licence
> if needed however.
> * I asked this same question in help.openstreetmap.org
> ,
> and was referred to these mailing lists
>
> Regards,
> --
> Sean Lindsey
> Cybo Company
> LinkedIn 
> 541-912-2505 <(541)%20912-2505>
>
>
> ___
> Talk-us mailing 
> listTalk-us@openstreetmap.orghttps://lists.openstreetmap.org/listinfo/talk-us
>
>
>
> ___
> Imports mailing list
> impo...@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/imports
>
>
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us