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.
Copyright © 2002-2008 Open Geospatial Consortium, Inc. All Rights Reserved.
149
1.5.1.3 Response Requirements
The parameters of the combined ProximityPinpoint response include the required elements of the Point of Interest ADT.
The XML Response will comprise a Header Block and a Method Block, according to the Request and Response Encoding Requirements.
1.5.2 Gateway service requirements
The Gateway Service should support the following requirements: Use Case
Priority
Client requests a single mobile terminal’s immediate location.
1
Client requests single mobile terminal’s periodic location 2
Client requests multiple mobiles’ immediate location 2
Client requests single mobile terminal’s triggered location 3
Client request multiple mobiles’ periodic location 3
Client requests multiple mobiles’ triggered location 3
1.5.3 Location Utility service requirements
1.5.3.1 Geocode Service
The following requirements must be supported by the Geocoder Service: Given an Address ADT, must be capable of using an address matching Geocoding
algorithm to determine a position for the specified address. Must be capable of performing geocoding using an incomplete address and return the
complete set of address information i.e., a normalized address. Must be able to indicate the number of matches in the response possibly zero for a
particular address supplied in the geocoding request. Must be capable of processing one or more addresses in a single geocoding request.
Copyright © 2002-2008 Open Geospatial Consortium, Inc. All Rights Reserved.
150 May provide information on the quality of the result using a ‘match code’.
1.5.3.2 Reverse Geocode Service
The following requirements must be supported by the Reverse Geocoder Service: Given a Position ADT, must be able to return one or more locations i.e., Address
ADTs with associated Point geometries, and optionally, the ranges of these locations from the given position, as it is defined in the Position ADT.
The form of the returned addresses must be based upon the user’s preference, as stated in the request. The user should be able to specify a preference of StreetAddress,
StreetIntersection, or PositionOfInterest Place andor PostalCode. If not specified, the service should default to StreetAddress.
Must be capable of returning all location information of a preferred type within an area of interest AOI ADT – a Circle, Polygon or Box.
Must be able to indicate the number of matches in the response possibly zero for a given request.
1.5.4 Presentation Service
The main purpose of the Presentation Service is the portrayal of maps, and the portrayal of ADTs as map overlays. The act of portrayal is taking the information from the other
OpenLS Core Services ADTs, adding style and producing output that is easily understood by a user.
DESCRIPTION Must
Should May
Accept output Parameters
Support context parameters
Accept a list of ADT’s
