Several new features in the Bing Spatial Data Services and the Bing Maps Account Center are added, announced Bing Maps team. The new features includes:
Bing Spatial Data Services provide a REST interface that allows you to geocode or reverse-geocode your own POI data sources in batch-mode, manage these data sources and query your own or some public POI data sources that Bing Maps provides in a spatial context. In this release the following features are added:
- Incremental Upload – now you can set the parameter ‘loadOperation’ in the Data Source Management API to ‘incremental’.
- New Query Options support wildcard Searches through filter criteria. “For example, let’s say you have a “Store Manager” field in your data source. You can look for said manager by last name, “%Smith” or first name “John%” so you get all the Smiths or Johns within a region,” explains Bing Maps team.
- Traffic Incidents for North America are now available as a public POI data source and can be accessed through the Query API. Now the traffic incidents you see on Bing Maps are available to you in your applications via a spatial query.
- Find Near Route additional spatialFilter allows you to search for POI along a route. In other words, it allows you to spatially query the points you’ve uploaded into SDS within a 1 mile buffer of your route.
Bing Maps Account Center lets you find information for development with Bing Maps, and also manage your account. It contains links to interactive and traditional SDKs, a facility to generate Bing Maps Keys, a web user interface to manage your own POI data sources and a reporting service through which you can retrieve statistics about your Bing Maps usage.
In this release the following features are added:
- “Additional data validation has been introduced for the upload of your own POI data sources.
- Before it was already possible to add and edit records in a data source that you uploaded through the portal. You can now also download and delete data sources.
- Image capturing adds now additional security during the generation of Bing Maps Keys.
- Additional reports have been added to provide more details on the use of specific Bing Maps Keys,” informed the Maps team.
Also, Bing Maps Token Service will end on on March 30, 2012, and the current Bing Maps Platform customers using the service should move to Bing Maps Keys in due time. “The upgrade will apply only to the following Bing Maps Platform API’s: Bing Maps AJAX Control v6.3 (and earlier versions), Bing Maps SOAP Services, and Bing Maps Silverlight Control,” the bing maps team notes.
Adding further, the team explains that the use of Bing Maps Keys also brings a series of other benefits when compared to the Bing Maps Token Service including:
- Improved performance in accessing the Bing Maps Platform (i.e. the elimination of the requirement to call the Token Service prior to calling the Bing Maps API’s).
- Unlike Bing Maps Tokens, Bing Maps Keys do not expire.
- Enhanced management and reporting of your Bing Maps Platform usage (i.e. you can assign a unique Bing Maps Key to each of your applications to separately track the Bing Maps usage for each of your applications).
The team explains, if your Bing Maps application is calling or referencing any of the following Bing Maps Platform URL’s (HTTP or HTTPS) you are very likely using the Bing Maps Token Service”: http://s.mappoint.net/mappoint-30/GetClientToken; http://common.virtualearth.net/find-30/common.asmx; http://findv3.mappoint.net/Find-30/Common.asmx.
Also, they can go to the View My Bing Maps API Usage section of the Bing Maps Account Center, which provides a Legacy (MWS + Token) Usage Report by Category report. They can also access the Transaction Usage by Category report, available in the View Usage section of the Bing Maps Customer Services Site.