The One Fatal Flaw in Mashups

In the mashup ecosystem, let’s get one thing straight. The data owner is ultimately in control, because a mashup developer is reliant on data owners to keep the supply of data flowing.

Sure the presentation is important, but if you rely on data sources you don’t have control over you run the risk of losing out. Better to get permission from your sources before you are blocked from getting the data. One should never base your business model on free data unless you have secured access to it.

This entry was posted in GIS and tagged . Bookmark the permalink. Both comments and trackbacks are currently closed.

5 Comments

  1. Posted March 2, 2006 at 12:10 pm | Permalink

    Excellent point and something that needs to be considered. Funny, just yesterday I bounced a similar question off an exec at GlobeXplorer.. here’s what he replied… “Most mashups are using web service image and street data that is licensed for personal and/or internal business use only, and not for resale. Aside from that, all our customers pay for the premium data services we provide, even sites that appear to end users as “free”. Much like TeleAtlas and Navteq data supplied from various web services into other sites, including mashups. We’ve been doing this for seven years now, and growing very fast”. Food for thought… Glenn (GISuser.com)

  2. Posted March 2, 2006 at 12:58 pm | Permalink

    I thought you were going to say, “what is called a mashup has long been known as ‘doin GIS”

    I like your point though too…

  3. Posted March 2, 2006 at 5:31 pm | Permalink

    James,

    Spot on.. there is no such thing as “free” data somebody is covering the costs of the content somewhere is the mash-up chain, and this may or may not be sustainable !

    ed

  4. Posted March 2, 2006 at 9:53 pm | Permalink

    Since I don’t have a nickel for every great “mashup” idea someone came to me with, I’ve had to improvise by repeating the mantra to would-be spatial capitalists “the devil is in the data.”

  5. Posted March 6, 2006 at 4:53 pm | Permalink

    A real world example of this:

    Yahoo recently decided to roll back their geocoding support on their API considerably, which had a negative impact on my batch geocoding tool (which is a mashup of sorts.)

    Luckily I figured out a workaround which so my service was not disabled, though its not quite as sweet as it once was.

    My advice to anyone who’s venturing into mashups: tread lightly and always have a backup plan.

    -Phillip

One Trackback

  1. [...] The one fatal flaw in mashups: “ [...]

  • License

  • Disclaimer

    The information in this weblog is provided "AS IS" with no warranties, and confers no rights.

    This weblog does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion and probably incorrect.

  • Meta