Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance. Project price only 1 $
You can buy this project and download/modify it how often you want.
This is the abstract type that all other abstract types will extendLocation can be one of four things: Position, POI, Address or Point. Each of those types has been defined in the XLS namespace with this in condiseration. QoP as defined by LIF.The Position ADT. Normally used to represent an observation/calculated position for a mobile terminal, but can be any position used by the platform. Contains Point with optional Shape, QoP, Speed, Direction and Time. Also has levelOfConfidence attribute.Point of Interest is a place, product or service with a fixed position, typically identified by name rather than by address and characterized by type, that may be used as a reference point or a target in a location based service request. We need to look more closely at this choice block (it's too restrictive). Since we don't have a getCapabilities, there is really no way that a client can discover the information a Directory Service could possibly return. Also, clients have no way to specify which of these information types they want returned (ReferenceSystem, POIInfoList, Point, and/or Address), like we do for GeoCode. Plus, when a Directory Service has two or more of these types, with the choice block there is no way for the a client to receive the full information set. Do we want to change this to a sequence block and/or change POIAttributeList and/or Point to optional? Also, we need to examine the role of POI in this form since it may not return a Point or Address and therefore may not have sufficient info to be used in location services that require a position of some sort.
[MM] 17/3/03. Made the change from a choice block to a sequence block. Made the elements optional inside the sequence block
The POI ADT. Primarily generated in the responses from Directory Services. Can also be used as a filter in the request to a Directory Service for nearest/within distance conditions. One or more formal name classifications and/or one or more name/value pairs.List of other information available about the POI in name/value pairs.POI Information defined as a Name/Value pairFormal name reference system. Three are defined here (NACE, NAICS and SIC), but any others may be defined and added to this schema.The Area of Interest (AOI) ADT. Can be a Circle, Polygon or Point.
The AddressType is the Address_ADT for OpenLS and it supports the concepts of the OGC Geocoder document 01-026r1
with some modifications which resulted in both simplifications and improved handling capability. The definition is also
broad enough to handle some of the more obscure occurrences of street addressing as well as handling the
case of when all you have is an un-parsed string representing the complete address. We could generalize this even
further to handle non-street addressing schemes found in other industries, such as the Municipal Survey Addressing
schemes that are used by Municipalities to address the lots on which a building may be placed but that is probably a
future requirement outside the scope of OLS1.
ISO 3166 Alpha-2 Country Codes
A set of precise and complete data elements that cannot be subdivided and that describe the physical location of a place.Structured street address.The location on a street.
The AbstractStreetLocatorType is an abstract type for describing the location on a street within an AddressType.
We do this because the components of a location on a street vary greatly throughout the world.
So that the schema can accommodate this variation we create derived types such as the
BuildingLocatorType which has the components for an apartment or suite or floor within a building.
An addressable place; normally a location on a street: number, subdivision name and/or building name.A type of AbstractStreetLocatorTypeThe data elements that make up the name of a street. There are two valid methods for encoding this information: 1). Use the structured elements and attributes. 2). The element value may contain a simplified string (e.g. 43 West 83rd. Street).
An example: The direction for a street (e.g., North), placed before the official name.The street type (e.g., Rd or Ave) specified before the official name
The name for a street (e.g., Main).
The street type (e.g., Rd or Ave) specified after the official nameThe direction for a street (e.g., North), placed after the official name.Structured Street Name.The Address ADT. An address that is either a “Free Form Address” or a “Street Address” or an “Intersection Address”, with 0 or more “place” elements and an optional “postalCode” element. It also has two optional attributes, the “addressee” and the “phone number”, and one required attribute, the “country”.Defines an addressAn unstructured free form address.The classification for the hierarchy a level of which is defined to be one of five different types: CountrySubDivision, CountrySecondarySubdivision, Municipality, or MunicipalitySubdivision.Place represents a hierarchical set of geographic regions/placenames: country subdivision, country secondary subdivision, municipality, and municipality subdivision.
The NamedPlaceType defines a named place within an AddressType.
A named place has a classification (such as country, country subdivision, or municipality).
A zipcode or international postal code as defined by the governing postal authority.
The AbstractPostalCodeType is an abstract type for postal code within an AddressType.
We do this because the components of a postal code vary greatly throughout the world.
So that the schema can accommodate this variation we create derived types such as the
USZipCodeType which has the components for a US zipcode
These types don't fit well with ADTs, rather with Location Utility. Should move them. Also, GeocodingQOSType should be renamed GeocodeMatchCodeType, for consistency, or the element GeocodeMatchCode should be renamed GeocodingQOS.Provides information on the quality of the match operation (accuracy and match code).Quality of service typeThis is the score (probability) assocaited with the match functionDescribes the type of match made by the function, example zip+4Map data embeded into the xml (if map data is binary then it is base64 encoded) The Data can be found at this URLlat/long WGS84 point to center the map onA ratio of distance. For example 1:5000 would be expressed as 5000, it's always expressed per 1 pixel of the displayDots per Inch of the display device.This defines the area that will be required to be displayedThe orientation of the map, clockwise degrees from north.The Spatial Reference System that the data with be projected to in EPSG:XXXX format (getCapabilites provides the list of SRS's supported).Abstract type which specifies a route's overall characteristics.Estimated time to travel the complete route. Expressed as a duration as defined by W3C. reference URL: http://www.w3c.org/TR/xmlschema-2/Total distance covered by the route.Rectangular area bounding the complete route.Base element which represents a route's overall characteristics.Defines the characteristics of a segment along a route.Distance along the segment.Estimated time to travel the complete route, Expressed as a duration as defined by W3C. reference URL: http://www.w3c.org/TR/xmlschema-2Rectangular area bounding the segment.Name of segment, e.g.: street name, or the name of the public transit line. When the name is unknown, this should be an empty string. When not specified, the name is assumed to be the same as the previous segment.Base element which represents the information about the segment of the route between the current maneuver and the next.Abstract type representing a location to be visited along a route.A location to be visited along a route.Specifies a route's overall characteristics.A route's overall characteristics.Rectangular bounding area.Defines the characteristics of a segment along a route.Information about the segment of the route between this maneuver and the next.Defines a location to be visited along a route.Specifies whether the traveler plans to stop at the waypoint, or simply pass through it. Starting point of the route.Intermediate waypoint along the route.Ending point of the route (i.e. the destination)Defines a list of waypoints along a route.List of waypoints along a route.A list of route instructions.Defines a list of route instructions.Mime type describing the encoding.Specifies the language in which the instructions are given.Defines a single turn-by-turn route instruction or advisory formatted for presentation.Specifies the duration needed to execute those instructions. Duration is expressed as defined in the W3C defintion. Reference URL: http://www.w3c.org/TR/xmlschema-2/Allows the route instruction to be matched with a RouteMapType. For example "maneuver 1"A turn-by-turn route instruction or advisory formatted for presentation.A reference to a route stored at the Route Determination Service server.Defines a reference to a route stored at the Route Determination Service server.Uniquely identifies the service which holds the route.Uniquely identifies the route store at the service.Defines the geometry of a route.Geometry of a route.
