[postgis-users] Google Directions -> PostGIS

[Travis Kirstine]

I don't think this would be permitted based on Google's terms of service,
for example:

Section 10.1.3 *Restrictions against Data Export or Copying.*

(b) *No Pre-Fetching, Caching, or Storage of Content.* You must not
pre-fetch, cache, or store any Content, except that you may store: (i)
limited amounts of Content for the purpose of improving the performance of
your Maps API Implementation if you do so temporarily (and in no event for
more than 30 calendar days), securely, and in a manner that does not permit
use of the Content outside of the Service; and (ii) any content identifier
or key that the Maps APIs Documentation specifically permits you to store.
For example, you must not use the Content to create an independent database
of "places" or other local listings information.



On 16 May 2013 11:01, James David Smith <james.david.smith at gmail.com> wrote:

> Hi there,
>
> This isn't so much a question as such, more a request for opinions and
> advice. I was wondering whether anyone had any experience with using the
> Google API for getting driving directions/routing - but then storing the
> results in a PostgreSQL/PostGIS database. I was thinking that my workflow
> might go something like this:
>
> 1) Take table of trip_ids, start points, end points, travel modes and
> start times from the database
> 2) Export them as a CSV
> 3) Import the CSV to R
> 4) Use R to loop through the data and send queries off to the Google API.
> 5) The results are a series of polylines each with the geometry as a
> polyline, the length of the stage, the time of the stage etc. As a JSON
> file. If I could break this apart in it's constiuent parts, could I then
> store it back in my PostGIS database?
>
> I guess the hardest bit I can see about this process, is converting the
> google encoded polyline to a PostGIS polyline I think. Any thoughts on that?
>
> Once this is all done I then want to use the routes with another layer to
> calculate someones exposure to X over each journey.
>
> Any general thoughts about this process would be welcome.
>
> Thanks
>
> James
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20130516/a8662d47/attachment.html>