News:

MyKidsDiary.in :: Capture your kids magical moment and create your Online Private Diary for your kids

Main Menu

Billable Transactions in Virtual Earths

Started by thiruvasagamani, Jan 24, 2009, 07:04 PM

Previous topic - Next topic

thiruvasagamani

Billable Transactions

The Virtual Earth Platform includes the MapPoint Web Service, the Virtual Earth map control, and the Virtual Earth Web Services.
MapPoint Web Service

The MapPoint Web Service (MWS) methods that cause billable transactions to be accrued include Find, FindAddress, FindById, FindByProperty, FindNearby, FindNearRoute, FindPolygon, GetLocationInfo, ParseAddress, GetMap, GetLineDriveMap, CalculateRoute, and CalculateSimpleRoute.
Virtual Earth map control

Certain Virtual Earth (VE) map control requests made after the VEMap.SetClientToken Method is called with a valid token are included in your transaction reports. The following Virtual Earth map control features count as billable transactions and appear in your Virtual Earth Platform Reports.

Map navigation (VE: Load Standard Map) – Transactions are counted any time new map tiles are requested from Virtual Earth. Virtual Earth Platform bills per map view, which is calculated based on the assumption that a map view is multiple tile transactions. This includes VEMap.LoadMap, VEMap.ZoomIn, VEMap.ZoomOut, VEMap.Pan, VEMap.SetMapView, and many other methods that cause the map to move. A single Billable Transaction shall equate to eight (8) Virtual Earth image tiles being fetched from Microsoft servers.

Traffic requests (VE: Load Traffic Map) – If traffic is turned on, you are charged double for every tile that includes traffic information. Virtual Earth Platform bills per map view, which is calculated based on the assumption that a map view is multiple tile transactions. A single Billable Transaction shall equate to eight (8) Virtual Earth image tiles being fetched from Microsoft servers.

VE: Geocode – Any time Virtual Earth map control makes a where-only request for a find result, one transaction is counted. This includes where-only requests from the VEMap.Find method as well as the VEMap.GetDirections method.

VE: ReverseGeocode - Each request made using the VEMap.FindLocations method counts as one transaction.

VE: CalculateRoute – If you make a request for a route using the new VEMap.GetDirections method, one transaction per returned route is counted. Use of the deprecated GetRoute method is not counted.

Source : MSDN
Thiruvasakamani Karnan