Here you will find documentation, including diagrams to help you understand the appropriate content for an OpenLS XML request and response. These documents will also help you understand the appropriate values for the Java XML Bindings, any .NET bindings you produce, or any other language bindings you create for the XML.
When looking at the top level for a schema the places you should start are the Elements with request or response postfixed on the name. These are the requests and responses to the web service and usually contain the other elements and types.
Here are the different schemas
| Document | Description |
|---|---|
| Directory Service | The directory service is a POI lookup service. It allows searching for POIs based on various criteria such as name, type, proximity to a location, and location. It also allows for returning various kinds of information about found POIs, such as name, telephone number, address, type, and location (lat-lon). |
| Location Utility Service | The location utility service is the geocoder and reverse geocoder service. It enables searching for the location of an address, given various kinds of input data or for determining an approximate address based on a location (lat-lon). A deCarta proprietary extension enables “freeform” address specification for geocoding. |
| Presentation Service | The presentation service draws maps, in several possible graphical formats. You can specify the location and extent of the mapped area, the size of the map image, and various kinds of overlays such as POI icons and text labels. deCarta proprietary extensions to the specification make it easy to enable common mapping application features such as pan, zoom, and click to re-center. Other deCarta extensions include using multiple configurations, using an address to specify the center of the map (saves you a geocoding step), and forcing the map to include enough area to show specified icons at their location. |
| Route Service | The route service calculates routes and can return driving directions, overview maps and maps of individual maneuvers, route summary information (time, distance), and so on. A deCarta extension makes it easy to correlate maneuver instructions with maneuver maps. |
| Traffic Service | A description of the Traffic Service |
| RUOK Service | A simple service to test if the DDS Server is up and running. |
For a Route Service the following are not implemented:
For the ADT Schema the following are not implemented:
For the GML Schema the only elements which are implemented are:
There are no elements implemented from xlinks
The only element implemented from UOM is DistanceUnitType