I'm not a lawyer either and I don't want to get myself into more trouble than necessary, but as far as I know, as long as it is a non-commercial editor, using the API should be OK. I'll try to find out what exactly are the exact limitations on using the API.
Regarding other sources of data, we are definitely going to use all available data sources. I don't see a reason not to use other types of data. Trying to solve the problem using computer vision alone is way too ambitious. The only problem with using different sources of data is probably making sure the sources are well aligned/registered (which is not a trivial problem). -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Anthony Sent: Sunday, February 06, 2011 12:15 PM To: Ido Omer Cc: Steve Bennett; [email protected] Subject: Re: [OSM-talk] (magical?) road detector On Sun, Feb 6, 2011 at 2:40 PM, Ido Omer <[email protected]> wrote: > Hi Steve, > > What we currently exposed is a web service that given two points finds > the best road between them (or at least what it considers as best, > which can be really bad sometimes) We are not stopping people from > using this service in their editors and achieve part of the functionality you > suggested (we really hope this will happen). What are the restrictions on the use of the API? Are we allowed to store results? Compare them with other data (LIDAR, parcel data, USGS imagery)? Access it by bot without human intervention? Even without the source code, I can think of a lot of neat things that can be done with the API. But I'm not sure they're consistent with the intent for which the service was released. _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
