1 / 8

Henning Schulzrinne Hannes Tschofenig Martin Thomson Vishal Singh

Dynamic Feature Extensions to the Presence Information Data Format Location Object (PIDF-LO) draft-singh-geopriv-pidf-lo-dynamic-05. Henning Schulzrinne Hannes Tschofenig Martin Thomson Vishal Singh. Background (reminder). Provide information about movement of target

maylin
Download Presentation

Henning Schulzrinne Hannes Tschofenig Martin Thomson Vishal Singh

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. Dynamic Feature Extensions to the Presence Information Data Format Location Object (PIDF-LO)draft-singh-geopriv-pidf-lo-dynamic-05 Henning Schulzrinne Hannes Tschofenig Martin Thomson Vishal Singh IETF - GEOPRIV

  2. Background (reminder) • Provide information about movement of target • Speed: “traveling at 10 m/s” • Acceleration: “accelerating at 3 m/s2” • Heading: “target is heading north-east” • Orientation: “target is pointing east” IETF - GEOPRIV

  3. Current version: orientation <?xml version="1.0" encoding="UTF-8"?> <dyn:Dynamic”> <dyn:orientation> <gml:DirectionVector> <gml:horizontalAngle uom="urn:ogc:def:uom:EPSG::9102”>90</ gml:horizontalAngle> <gml:verticalAngle uom="urn:ogc:def:uom:EPSG::9102"> 5</gml:verticalAngle> </gml:DirectionVector> </dyn:orientation> … next slide … </dyn:Dynamic> IETF - GEOPRIV

  4. Speed, heading, acceleration <dyn:speed uom="urn:ietf:params:ns:geopriv:dynamic:uom#mps”>3.2<dyn:speed> <dyn:heading> <gml:DirectionVector> <gml:horizontalAngle uom="urn:ogc:def:uom:EPSG::9102"> 180</gml:horizontalAngle> <gml:verticalAngle uom="urn:ogc:def:uom:EPSG::9202"> 0</gml:verticalAngle> </gml:DirectionVector> </dyn:heading> <dyn:acceleration uom="urn:ietf:params:ns:geopriv:dynamic:uom#mps2"> 0</dyn:acceleration> Really no need to specify units - makes receiver implementation difficult Seems too complicated for common use cases IETF - GEOPRIV

  5. Simple alternative • Avoid units • No vertical orientation • Not GML, but compatible • GeoRSS is not GML <Dynamic xmlns="...dynamic"> <orientation>90</orientation> <speed>3.2</speed> <heading>44</heading> <acceleration>0</acceleration> </Dynamic> IETF - GEOPRIV

  6. GML <MovingObject> <element name="MovingObjectStatus" type="gml:MovingObjectStatusType" substitutionGroup="gml:TimeSlice"/> <complexType name="MovingObjectStatusType"> <complexContent> <extension base="gml:AbstractTimeSliceType"> <sequence> <element ref="gml:position"/> <element name="speed" type="gml:MeasureType”> <element name="bearing" type="gml:DirectionPropertyType”/> <element name="acceleration" type="gml:MeasureType”/> <element name="elevation" type="gml:MeasureType”/> <element ref="gml:status”/> </sequence> </extension> </complexContent> </complexType> duplicates PIDF-LO information – not optional! IETF - GEOPRIV

  7. <MovingObject> example <gml:MovingObjectStatus> <gml:validTime><gml:TimeInstant> <gml:timePosition>2005-11-28T14:00:00</gml:timePosition> </gml:TimeInstant></gml:validTIme> <gml:location><gml:Point> <gml:pos>140.1 -34.9</gml:pos> </gml:Point></gml:location> <gml:speed uom="#kph">23.</gml:speed> <gml:bearing> <gml:CompassPoint>ESE</gml:CompassPoint> </gml:bearing> </gml:MovingObjectStatus> Not all that helpful IETF - GEOPRIV

  8. Next steps • Gone around the GML circle a few times • Finally, decide on one • <Dynamic>, simplified • and avoid push-back on GML faithful  IETF - GEOPRIV

More Related