Share via

MapPoint Location Server Web Service Class Library

  • Article

Microsoft® MapPoint® Location Server Web Service is a set of Web services with a Simple Object Access Protocol (SOAP) API that you can use to provide location-based services to your enterprise users and customers.

MapPoint Location Server Web Service consists of the following five Web services:

Location service

The Location service is introduced with MapPoint Location Server. This service contains methods that you can use to locate the geographic position of a user carrying a locatable device such as a cell phone or pager. This service also provides methods for managing the personal preferences of users, such as culture, visibility settings, and contact lists.

Common service

The Common service contains classes, methods, and properties that are common to the Find, Route, and Render services, or are basic utility functions.

Find service

With the Find service, you can locate addresses, geographic entities, latitude and longitude coordinates, and points of interest from MapPoint data, as well as parse addresses and return location information for a specified latitude and longitude coordinate.

Render service

With the Render service, you can render maps of routes and found locations, place Pushpins (using the MapPoint stock set of icons or your own icons that we host for you), set the map size and map view, select points on a map, get location information about points on a map, pan and zoom a rendered map, and create clickable maps.

Route service

With the route service, you can generate routes, driving directions, and calculated route representations based on locations or waypoints (used to render a highlighted route on a map), set segment and route preferences, and generate map views of segments and directions.

Remarks

Ensure that you resolve type name conflicts when using both MapPoint Location Server Web Service and the MapPoint Location Server management API and MapPoint Web Service in an application. Type name conflicts can occur in the following scenarios:

  • An application that uses both MapPoint Location Server Web Service and MapPoint Web Service as Web references.
  • An application that uses MapPoint Location Server Web Service as a Web Reference and the MapPoint Location Server data types as assembly references.
  • An application that uses the MapPoint Location Server data types as an assembly reference and MapPoint Web Service as a Web reference.

These conflicts occur because MapPoint Location Server and MapPoint Web Service use the same Web services and types. To resolve type name conflicts, do the following:

  • If you are developing a MapPoint Location Server Web Service application, always use the consolidated MapPoint Location Service WSDL instead of importing each service separately from corresponding WSDL documents.
  • If you are developing a server-side application using the MapPoint Location Server management API, use the proxy classes that are available in the Microsoft.MapPoint.LocationServer.Types.dll assembly under the Microsoft.MapPoint.LocationServer.Types.MapPointService namespace.

Important  Sensitive user information (name, phone number, alias, and so on) that is used for the Pushpin.Label property when invoking MapPoint Location Server Web Service to render maps with pushpins (for example, with the RenderServiceSoap.GetMap method) is forwarded to MapPoint Web Service (MapPoint Location Server Web Service internally invokes MapPoint Web Service). In some cases, this can be considered a potential privacy violation.