B. ROSEN, M. THOMSON, D. STANLEY, G. BAJKO, A . THOMSON, S. MCCANN

draft-thomson-geopriv-relative-location-00

This draft

Combines two previous drafts on how to represent interior location (the “Stanley” draft on offset from a civic and the “Thomson” draft on offset from a geo)

Extends a PIDF-LO to have an offset represented by a geoshape

Also defines a “map” element for a floorplan, database or other secondary reference data to enable display of “you are here” or “go there”, etc.

Defines TLV representations for the offset shapes

Example

<presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" xmlns:gml="http://www.opengis.net/gml" xmlns:gs="http://www.opengis.net/pidflo/1.0" entity="pres:ness@example.com"> <dm:device id="nesspc-1">

<gp:geopriv> <gp:location-info> <ca:civicAddress xml:lang="en-AU"> <ca:country>AU</ca:country> <ca:A1>NSW</ca:A1> <ca:A3>Wollongong</ca:A3> <ca:A4>North Wollongong</ca:A4> <ca:RD>Flinders</ca:RD> <ca:STS>Street</ca:STS> <ca:HNO>123</ca:HNO> <ca:INT N="Door" R="A">Front</ca:INT> </ca:civicAddress>

<gp:relative-location> <gp:shape> <gml:Point xmlns:gml="http://www.opengis.net/gml" srsName="--TBD--"> <gml:pos>100 50</gml:pos> </gml:Point> </gp:shape> </gp:relative-location> </gp:location-info> <gp:usage-rules/> <gp:method>GPS</gp:method> </gp:geopriv> <dm:deviceID>mac:1234567890ab</dm:deviceID> <dm:timestamp>2007-06-22T20:57:29Z</dm:timestamp> </dm:device> </presence>

The reference point

Is a location information (that is, a geo or civic, as we currently define it)

There is some author disagreement on how to represent the reference

The offset

Defined geoshapes Point Circle/Sphere Ellipse/Ellipsoid Polygon/Prism

Contained in a <relative-offset> element in <geopriv>

CRS is an (optional) angle in degrees from North, units of meters and uses the reference as the datum

The “Map”

URI to some object: could be an image, could be a data structure

MIME type to know what the object isCan include Angle, Scale and Offset to define

map CRS

TLVs

TLV definitions for the shapes that define the offset are provided in the draft

New registry for the types that are explicitly non conflicting with 4776 (CAtypes)

Could combine the reference using 4776 types with the offset using these types to get a relative offset, but this draft doesn’t define the details of how you do that

Open Issue: Representing the Reference

The current draft just has the reference as a civicAddress or gml in <location-info>

The offset is a new <relative-offset> in <location-info>

This means if you don’t understand <relative-offset> you take the reference as the location

Some authors think this is wrong and if you don’t understand the extension, you should get no location

If the offset can be very large, this could be a problem