The Latest News On The API Economy
Searching: No Search Term , Filtered By Category: "Environment", Category: "Mapping", Category: "Energy", Category: "New York City"
Over two years after Google originally announced the end of the Google Earth API, Google will finally sunset the API today. January 11, 2017 is the official sunset date that many had hoped Google would continue to delay. The popular API is based on the outdated NPAPI plugin framework.
This article is part of a 10-part series about interesting APIs that were added to our directory during 2016. Mapping and Location APIs are covered in this segment. The APIs were chosen by our researchers, by popularity according to website traffic, and by mentions on social media.
This article is part of a 10-part series about interesting APIs that were added to our directory during 2016. Health and Environment APIs are covered in this segment. The APIs were chosen by our researchers, by popularity according to website traffic, and by mentions on social media.
This is the introduction to our series What is The Green Button API initiative and How It Took OAuth To An Entirely New Level. This article will help you understand what the Green Button API Initiative is and how it came about. Green Button is part of the Obama Administration's My Data initiatives.
This is part 2 of our series on the Green Button API initiative. This article examines the architectural underpinnings, including the requirements and standards behind the initiative. The Green Button technology is based on existing standards that were assembled to meet the identified requirements.
This is part 3 of our series on the U.S. government's Green Button API initiative. In this part, we will describe the building blocks of Green Button technology and how they respond to the project requirements with respect to authorization of access to data provided to third parties.
This is part 4 of our series What is The Green Button API initiative and How It Took OAuth To An Entirely New Level. In this part we explain the structure of Green Buttons’ scope parameters and illustrate the data exchanges and protocol used to implement Green Button’s scope negotiation.
This is part 5 of our series What is The Green Button API initiative and How It Took OAuth To An Entirely New Level. Here, we look at how Green Button data, due to its regularly renewed nature needed to adopt a pseudo PUSH model that was consistent with the OAuth resource data exchange model.
This is the conclusion to our series What is The Green Button API initiative and How It Took OAuth To An Entirely New Level. It provides a set of references for enriched additional information for the reader about technologies and choices made in the design of the Green Button architecture.
Earlier this year, Google requested map data from the Korean government. In response, Korean tech companies Naver and Kakao have increased free limits to their respective maps APIs beyond what Google offers. The government is expected to respond next month but the competition has already started.
MapQuest is inviting developers to take its MapQuest Static Map v5 API for a spin while in beta testing. The refreshed API has a handful of new features that should appeal to developers who rely on MapQuest's mapping tools. The beta is being offered for free through the end of 2016.
TomTom has added another API to its mapping and navigation solutions portfolio: Traffic Stats API. Traffic Stats collects data from over 450 million connected devices in order to provide historical traffic data. The data collected includes speed, route, travel time, segment, and more.
Google is opening up Maps to new ride-sharing partners, meaning the search giant just effectively created the first ride-hailing price comparison feature. The surprise here is that Uber, previously the only ride-sharing partner on Google Maps, allowed this.
Geocoding involves converting a description of a physical address into coordinates that represent that location on a map to perform spatial analysis. This tutorial on the Google Maps APIs blog describes the two approaches to geocoding with Google Maps APIs, and when to use them.
Google today said it is putting the Google Places API for iOS 2.0 and the Google Maps SDK for iOS 2.0 into separate CocoaPods. The idea here is to reduce the app size for developers who need Places data, but not Maps data. Google says the change heralds big savings in app binaries.
After continued developer requests, Google has added marker clustering to Google Maps SDK for iOS Utility Library. The feature allows users to populate maps with a large number of markers while keeping the map clean and readable. As zoom levels adjust, markers aggregate and slit out accordingly.
Google implemented a number of changes to its Maps API Standard Plan. Apps created on or after June 22nd will be subject to a host of new rules surrounding access and limits. Active domains utilizing the APIs prior to June 22nd are grandfathered in to differing degrees depending on implementation.
Google Maps API is the most popular tool for building location-based services. Now, the Google Maps Operations team is leveraging their experience to collaborate with Udacity and create a free course that teaches students how to integrate maps and location features into websites.
The Google Maps API team maintains many Google Maps APIs and SDKs. Manually tracking updates across the various sets of Release Notes presents a challenge for developers. Google now offers auto-updates to Maps Release Notes via RSS feeds. RSS feeds for all Maps and Places APIs are available.