1 / 0

Location Tranformation http:// tools.ietf.org/html/draft-marshall-geopriv-location-transform-00

Location Tranformation http:// tools.ietf.org/html/draft-marshall-geopriv-location-transform-00. Document Authors: Roger Marshall, Robins George, James Polk IETF80 – Prague 3/28/2011. Status.

hyman
Télécharger la présentation

Location Tranformation http:// tools.ietf.org/html/draft-marshall-geopriv-location-transform-00

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Location Tranformationhttp://tools.ietf.org/html/draft-marshall-geopriv-location-transform-00

    Document Authors: Roger Marshall, Robins George, James Polk IETF80 – Prague 3/28/2011
  2. Status Goal, to describe a standard (protocol) mechanism useful in exchanging one form of location for another Combines parts of earlier drafts and garnered support inprevious IETF face-to-face mtgs. draft-george-geopriv-address-translation draft-polk-ecrit-losts-transformations-urn
  3. History Promotes use of LoST for a discovery process Location & Service URN as inputs e.g., Anytown, Country + urn:service:transform.location (tbd) One issue is that this makesdiscovery have to be location based Are there other ideas?
  4. A Few Examples Consider a protocol that could: Take Civic Location as input, and returns a geodetic transformation (lat/lon) (yes, this is simple geocoding – but in a standard way, over the Internet) Given a lat/lon based on NAD83, this mechanism could be used to return a “transformed” WGS84 lat/lon (handy, since hundreds of datums exist worldwide)
  5. A Few More… Examples, continued: Input: Geo Position AND base layer constraint (e.g., parcel polygon layer), returns the “associated” civic location (reverse geocoding with specific layer flexibility) Given a municipal survey (real estate) description as input, it returns a complete WGS84 Geo Polygon Input: Postal Civic form of address, Output: Dispatch ready address format
  6. Many Transformations of Location a) Converting between (Civic) Location types b) Converting between (Geo) Datums 123 Main Street Seattle, WA … 123 Main St. Ballard, WA Postal Address Dispatch Address Location Transformation Request Location Transformation Response Service NAD83 (x,y) WGS84 (x,y)’
  7. Civic, Geo and Geo data layer in PIDF-LO MESSAGE sip:transform@domain.com SIP/2.0 Via: SIP/2.0/TCP transform1.domain.com;branch=z1pG2bK996sdkfse Max-Forwards: 70 From: sip:transform1@domain.com;tag=49553 To: sip:transform@domain.com Call-ID: addm86asid59@1.2.3.4 Geolocation: <cid:thatsvr@domain.com> ;routing-allowed=yes Supported: geolocation Accept: application/pidf+xml, application/common-alerting-protocol+xml CSeq: 1 MESSAGE Content-Type: multipart/mixed; boundary=boundary1 Content-Length: ... -- set of points PIDF-LO ! discrete --polygon PIDF-LO ! Data layer
  8. Additional Ideas Many applications are possible Additional examples? Location specific – e.g., not meant to be a unit conversion tool
  9. Next Steps? Protocol framework is currently missing, to be supplied soon in subsequent revision Ideas on protocol structure, RelaxNG, etc. Some initial comments received, more welcome
More Related