Hacker News new | ask | show | jobs
by missosoup 2268 days ago
It would violate the ToS.
2 comments

Which part of the ToS (that isn't getting violated already)?

The real problem with this approach is that you will never know when real time is conflicting with historical unless you're calling the API constantly anyway

Google's ToS says you're not allowed to do any computation on your own?

I mean, I'm not disputing it, I just hadn't realized we were already there.

Section 3.2.3 of the Google Maps ToS

> (c) No Creating Content From Google Maps Content. Customer will not create content based on Google Maps Content.

> (d) No Re-Creating Google Products or Features. Customer will not use the Services to create a product or service with features that are substantially similar to or that re-create the features of another Google product or service.

https://cloud.google.com/maps-platform/terms/

For the use case described in the article it sounds just fine. The content part is a big vague. If read very broadly it would be super prohibitive. Perhaps it is?
i don't see how using this is different from using the directions api for the purpose in the article?