Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
The SAE J2266 standard, formally known as the Location Referencing Message Specification (LRMS), provides a structured framework for encoding location references within Intelligent Transportation Systems (ITS). Published in 2019 and stabilized due to the lack of identified active users, this specification remains a valuable reference for engineers working with transportation data exchange, particularly in legacy systems and V2X communications. It defines a comprehensive set of data frames and elements to represent locations on transportation networks, supporting methods such as linear referencing, geographic coordinates, grid systems, and pre-coded locations.
LRMS addresses the need for standardization in location referencing across diverse ITS applications. The standard specifies common data concepts to ensure interoperability, regardless of the underlying location method. Its structure uses modular data frames and data elements that can be combined to create location references tailored to specific use cases. The 2019 stabilization notice (SAE J2266 JUN2019) indicates the document is no longer subject to periodic reviews, but it remains available for continued use.
🔍 Stabilization Note: As declared by the SAE V2X Core Technical Committee, this document is stabilized and will not be updated. Users are responsible for verifying continued suitability and references.
The LRMS supports multiple location referencing methods to accommodate a variety of ITS scenarios. Below is a summary of the primary methods and their associated data frames:
| Method | Description | Key Data Frames |
|---|---|---|
| Linear Reference | Location along a linear element (e.g., road) using offset from a reference point. | LinearReference:frame, LinkLocation:frame, AddressPoint:frame |
| Geographic Coordinate | Absolute location using latitude/longitude with horizontal datum. | GeographicCoordinate:frame, GeoLocation:frame, GeoLocationDelta:frame |
| Grid Location | Location relative to a defined grid system, including offsets and zoom levels. | Grid:frame, GridPoint:frame, GridArray:frame, PublicGridUSNG:frame |
| Route Location | Location referenced to a hierarchical route network (e.g., administrative area + road + offset). | RouteLocation:frame, StreetInfo:frame, AdminAreaGroup:frame |
| Pre-Coded Location | Fixed location identifiers assigned by an authority (e.g., point of interest codes). | PreCoded:frame, IdType:frame |
| Spatial Object | Geometric shapes (point, line, polygon) defining an area or segment. | SpatialObject:frame, Geometry:frame, Polygon:frame |
Each method is encapsulated through dedicated data frames (e.g., LocationReference:frame as a container) and associated data elements for attributes like direction, altitude, and datum.
The LRMS design is modular and extensible, allowing engineers to combine methods as needed. This flexibility is critical for bridging legacy systems that rely on linear referencing with modern geographic coordinate systems. However, the stabilization status means that no further enhancements will be made; users must ensure that the specification meets their current and future requirements.
⚠️ Common Pitfall: Avoid assuming a single location referencing method is sufficient for all applications. For example, on-road ITS may favor linear referencing, while mapping and routing often require geographic coordinates. The standard provides multiple methods to allow the best fit for the context.
No. The standard was stabilized in June 2019. It is no longer subject to periodic reviews, but the document is available for reference and use. Engineers should verify that other standards or newer technologies do not supersede their requirements.
The choice depends on the nature of the location data and the application context. Use linear referencing for highway segments, geographic coordinates for absolute mapping, grid methods for localized precision (e.g., construction zones), and route location for hierarchy-aware addressing. The LRMS documentation outlines guidelines for each method.
Mandatory elements vary per method. For instance, a geographic coordinate requires horizontal datum and latitude/longitude; a linear reference needs a link identifier and offset. The LocationReference:frame serves as a top-level container aggregating relevant frames and elements.
LRMS provides the location referencing foundation for V2X messages that involve positioning (e.g., basic safety messages, event notifications). It ensures that location data from different sources can be interpreted consistently, supporting interoperability across V2X implementations.