Copyright © 2002-2008 Open Geospatial Consortium, Inc. All Rights Reserved.
147
1.4.7 Route Instructions List ADT
Route Instructions List ADT contains a list of travel instructions consisting of turn-by- turn directions and advisories along the route, ordered in sequence of their occurrence,
and formatted for presentation to the user. Route Instructions List ADT is generated by the Route Service and “presented” to a subscriber via the Presentation Service.
1.4.8 Route ADT
The Route ADT is actually two ADTs: Route Summary and Route Geometry. Route Summary contains the route’s overall characteristics, such as its start point, waypoints,
end point, transportation type, total distance, travel time, and bounding box. Route Geometry contains a list of geographic positions along the route, ordered in the sequence
of planned travel, starting with the position of the route’s origin and ending with the position of the route’s destination. The geometry includes the positions of all nodes along
the route, including waypoints. The geometry also includes intermediate points needed to describe the geometric shape of the route segments between each node in the route. These
two ADTs are generated by the Route Service and “presented” to a subscriber as routing information, e.g. as a route displayed over a map, via the Presentation Service, or they are
used directly by an application to guide a mobile subscriber to their destination.
1.5 Service Requirements
1.5.1 Directory Service requirements 1.5.1.1 General
The definition of requestresponse pairs defined below will encompass the requirements for both Pinpoint and Proximity Directory Services. The two usages of the Directory
Service will be affected by selecting the appropriate optional parameters in the XML schema.
1.5.1.2 Request Requirements
The parameters of the combined PinpointProximity request must include: Directory Type: e.g., White Pages, Yellow Pages, Green Pages, etc.
The Pinpoint query will use parameters that will uniquely identify the Point of Interest. At least one of the following options may be used to identify the target location:
Point of Interest Name, identifying a specific location – e.g., Red Dragon Chinese Restaurant;
Copyright © 2002-2008 Open Geospatial Consortium, Inc. All Rights Reserved.
148 Point of Interest Point, identifying an exact location coordinate of the Point of
Interest; Point of Interest Address, identifying the street address of the Point of Interest.
The Proximity query will use parameters that will identify a shortlist of candidate locations by distance from a location that may itself be specified by a Pinpoint query,
e.g., “Give me the taxi rank nearest to the Red Dragon Chinese Restaurant”.
This may involve a combination of Proximity parameters to spatially constrain the search:
Proximity Type: type of proximity algorithm – e.g., Linear Distance, Bounding Polygon;
Source Location – point for determining proximity possibly a POI; Proximity Minimum Distance;
Proximity Maximum Distance; Proximity WithinBoundary, a polygon for Bounding Polygon search;
It will also involve a combination of parameters to constrain the result of the search: Maximum Number of elements to be returned: e.g., nearest 5 restaurants.
Sort criteria attribute to sort on; ascendingdescending. Other parameters may be used to constrain the search, resulting in a shortlist of Points of
Interest: List of Point of Interest PlaceProductService types identifying a group of locations
with some common attribute - e.g., Restaurants, Restaurants.Asian, Restaurants.Asian.Chinese, Restaurants.Asian.Chinese.Seafood;
Formal Categorisation in the form of a Name Reference System, e.g., NAICS, NACE, UPC, specifying the properties appropriate to that Name Reference System;
List of one or more keywords; Partial street address, such as State, City or Suburb.
The XML Request will comprise a Header Block and a Method Block, according to the Request and Response Encoding Requirements.
Kategori