1 / 5

LRMS Rev C

LRMS Rev C. The Location Reference Message Specification (LRMS) Rev B (MDI) is a Counterpart to SAE J2374 Both documents cover similar content - Spatial Data Interoperability Protocols for ITS.

kimama
Download Presentation

LRMS Rev C

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. LRMS Rev C • The Location Reference Message Specification (LRMS) Rev B (MDI) is a Counterpart to SAE J2374 • Both documents cover similar content - Spatial Data Interoperability Protocols for ITS. • Documents reflect consensus of thought related to how Location data will be formatted for system wide (ITS) communication. • Consensus is an evolving process, as is ITS. This revision may not be last and it must also undergo review - your comments are sought! • SAE J2374 was recently balloted and accepted, now it is time to take continued improvements of thought on how LRMS will function and include them with improvements from J2374 into a new LRMS Rev C.

  2. Major Recent Changes • The need to transfer limited sets of spatial data has been identified as important. (Emergency Management/Incident Management is one service area where this is apparent.) • Transfer is different from “Reference” in that reference assumes both parties have spatial data to look up the reference within. “Transfer” refers to providing the base data a receiver will use for subsequent lookups of location references. • This provides a means for systems to adapt to situations where they may not have been able to function previously, due to data incompatibilities. This new capability improves the overall value and usefulness of ITS systems. • The Geometry profile was identified as a profile that might also accommodate transfer of spatial data. • Geometry profile was evaluated and revised to accommodate transfers of simple transportation relevant spatial data.

  3. Geometry Profile Changes • Profile changes were made with backward compatibility for in mind for SAE J2374 users. (Many/most changes corrected minor errors in the Rev B document.) • Changes were made to create consistency between Geometry Profile in SAE and Point/Link Id profile (now renamed Geometry profile) in LRMS. • The only major record change was the the “Point/Point with offset” record which was redundant with the “Chain/Chain with offset” record. A true Point id based record was added in its place.

  4. Geometry Profile - New Records • New record added to Geometry Profile to allow users to define spatial data in terms of primitives. Primitives are definable in terms of nodes or points (nodes are considered to exist on the transportation network, points can exist off of the transportation network). • Primitive-set objects include: • Point/Node - a “point” with latitude and longitude • Link - A connection between 2 nodes • Chain - A series of Links • Transition - A series of Links between 2 important chains (typically ramps or “turns”) • Area/polygon -A series of node/points to define an object that is non-linear • New record was added to Geometry Profile to allow users to define “custom” attributes types for data. • New record added to Geometry Profile to allow users to define index tables for attribute values. • (Record already existed to allow users to define nodes at a geographic coordinate.)

  5. Conclusion • Entire Rev C is in internal review. • Send mail to johnl@pop.usit.net to request a review copy.

More Related