Bing Traffic API: The Bing Traffic API provides information about traffic incidents and issues, such as construction sites and traffic congestion. Traffic incident information is currently available for the United States and Canada. Users can also get information about traffic issues that met the criteria specified in the URL request, such as map area, incident type and severity. The API uses RESTful calls and responses are formatted in XML and JSON.
deCarta MapSearch Engine API: deCarta is a location based services provider. The Map Search Engine API gives developers the ability to implement local search on their web sites and applications. The API can search address and point of interest data sourced from content partners. Developers can also overlay their own searchable content onto the map. MapSearch Engine is “white label”, allowing customers to unitize their own UI, branding and content. The API uses RESTful calls and responses are formatted in XML, JSON, JSONP and XHTML.
- Programmable Web
Bonus: 40 real estate APIs
- +skipcody
by Adena Schutzberg on 02/22 at 07:09 AM |
Comments |
Greg Sterling reports, but did not get official confirmation from either organization, Nokia tech will power the Bing Maps infrastructure. There have been many rumors regarding NAVTEQ in recent weeks from folks outside the industry, but Greg's on the inside, so I think this is worth sharing.
However my lunch companion argued unequivocally that Nokia Maps would effectively replace almost everything that Microsoft had developed over the past several years in terms of the Bing Maps infrastructure. This was shocking because Microsoft has invested hundreds of millions of dollars (if not billions) in creating a viable competitor to Google Maps. Most recently the company has been promoting its roll out of new hi-resolution aerial imagery on a global basis.
I said I couldn’t believe Microsoft would agree to swap in Navteq for the guts of its own system. Yet my lunch guest argued that Microsoft’s role would mostly center on the Bing Maps UI — ironically not unlike Yahoo’s relationship to Microsoft search results — everything else would be powered by Nokia.
And there was another very interesting remark. He asserted that Google’s unwillingness to agree to a co-mingling of Google Maps and Nokia Maps or substitution of Nokia Maps on the back end was one of the sticking points that prevented Nokia and Google from coming to terms.
Search Engine Land via @atanas
The gory details of how Nokia's mapping portfolio would work in the new Microsoft/Nokia deal announced earlier this year was not completely clear (APB coverage).
by Adena Schutzberg on 05/16 at 04:08 AM |
Comments |
