Slashdot Mirror


Google Claims a TOS Violation On RouteBuilder For Using the Map API (medium.com)

New submitter acm writes: RouteBuilder has been using the Google Maps API to help people share their routes (bicycling, hiking, etc) for a decade. Last week, Google sent an email demanding Routebuilder stop using the API: "In particular,your application violates clause 10.4(c), which does not allow developers to create a wrapper — an application that re-implements or duplicates the Google Maps website or mobile app, or any of the Google Maps APIs." Why did it take the Google Maps Team 10 years to decide they don't want pedometer-type sites to use their API?

4 of 130 comments (clear)

  1. because by jemmyw · · Score: 5, Insightful

    because they're about to launch their own pedometer type site?

  2. Smallest violin by CaligarisDesk · · Score: 5, Interesting
    I'm sure someone could reimplement it using open street maps, but here's why it won't happen: From routebuilder's FAQ:

    I'm building a website that would benefit from some of the features of RouteBuilder. Will you give me the source code for free? I'm sorry, I'm not interested in giving away the source code behind this website for free. However, I am open to selling a license to use it.

  3. Re:Important 3rd party API lesson by Wycliffe · · Score: 5, Interesting

    That's a nice sounding ideology but the reality is that even if you start with a good 100% accurate street map, chances are you'll never be able to keep up with the updates on your own as governments build and change roads. That's of course, assuming you even have the resources to create one to begin with.

    Since this is a one man operation, I really doubt your suggestion is at all practical.

    "Always have a backup plan" is not the same as "don't use third party software". I work for a company that uses google for our maps. We can also switch over to an alternative api with a click of a button. We do it occasionally for testing and I believe there might have been a problem 4-5 years ago where we ran the alternate for certain failover conditions but for the most part it has never been activated on our live servers but it's there just in case. We also use several commercial apis and on several occasions have switched vendors and then switched back for pricing reasons. Not only does this protect us from cases where the third party is no longer available but it also helps with pricing negotiations as even if we prefer one vendor over another they know that if they try to raise our rates that we are not locked into their platform.

  4. RouteBuilder does not have a commercial licence by Frosty+Piss · · Score: 5, Informative

    RouteBuilder is not Open Source, the site says:

    Q: I'm building a website that would benefit from some of the features of RouteBuilder. Will you give me the source code for free?

    A: I'm sorry, I'm not interested in giving away the source code behind this website for free. However, I am open to selling a license to use it.

    Free use of Google Maps in applications comes with limits on how you can use it, and how many times you can hit the Google server for free. More than likely RouteBuilder exceeded these limits and Google asked RouteBuilder to purchase a licence, which they declined to do.

    This is not news.

    --
    If you want news from today, you have to come back tomorrow.