<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20241230</CreaDate>
<CreaTime>11393700</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="FALSE">FunctionalSystem</itemName>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Meter (1.000000)</csUnits>
<projcsn Sync="TRUE">NAD_1983_UTM_Zone_15N</projcsn>
<peXml Sync="TRUE">&lt;ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.3.0'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_UTM_Zone_15N&amp;quot;,GEOGCS[&amp;quot;GCS_North_American_1983&amp;quot;,DATUM[&amp;quot;D_North_American_1983&amp;quot;,SPHEROID[&amp;quot;GRS_1980&amp;quot;,6378137.0,298.257222101]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Transverse_Mercator&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,500000.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-93.0],PARAMETER[&amp;quot;Scale_Factor&amp;quot;,0.9996],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,0.0],UNIT[&amp;quot;Meter&amp;quot;,1.0],AUTHORITY[&amp;quot;EPSG&amp;quot;,26915]]&lt;/WKT&gt;&lt;XOrigin&gt;-5120900&lt;/XOrigin&gt;&lt;YOrigin&gt;-9998100&lt;/YOrigin&gt;&lt;XYScale&gt;10000&lt;/XYScale&gt;&lt;ZOrigin&gt;-100000&lt;/ZOrigin&gt;&lt;ZScale&gt;10000&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;16093472.18694436&lt;/MScale&gt;&lt;XYTolerance&gt;0.001&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.001&lt;/ZTolerance&gt;&lt;MTolerance&gt;6.2136994949494902e-07&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;26915&lt;/WKID&gt;&lt;LatestWKID&gt;26915&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<SyncDate>20250511</SyncDate>
<SyncTime>18110300</SyncTime>
<ModDate>20260630</ModDate>
<ModTime>12352100</ModTime>
<ArcGISProfile>ISO19139</ArcGISProfile>
</Esri>
<mdLang>
<languageCode value="eng"/>
<countryCode value="USA"/>
</mdLang>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdHrLvName>dataset</mdHrLvName>
<mdContact>
<role>
<RoleCd value="002"/>
</role>
<rpOrgName>Louisiana Department of Transportation</rpOrgName>
<rpPosName>Enterprise GIS Unit</rpPosName>
<rpCntInfo>
<cntAddress addressType="">
<eMailAdd>DOTDGIS@LA.GOV</eMailAdd>
</cntAddress>
<cntPhone>
<voiceNum tddtty="">225-379-1232</voiceNum>
</cntPhone>
</rpCntInfo>
</mdContact>
<distInfo>
<distFormat>
<formatName>File Geodatabase Feature Class</formatName>
<formatVer>ArcGIS Pro 3.3.4 - Enterprise 11.3.0.5236</formatVer>
<formatSpec>This is a dynamic LRS Event dataset registered to the parent LRSID_Routes Network. Geometry generation depends on active Route ID and Measure values linked to the parent LRS Network.</formatSpec>
</distFormat>
</distInfo>
<dataIdInfo>
<envirDesc>Esri ArcGIS 13.3.7.52636</envirDesc>
<dataLang>
<languageCode value="eng"/>
<countryCode value="USA"/>
</dataLang>
<idCitation>
<resTitle Sync="FALSE">Functional System</resTitle>
<presForm>
<PresFormCd value="005"/>
</presForm>
<date>
<createDate>2025-04-15T00:00:00</createDate>
</date>
<citRespParty>
<displayName>Louisiana Department of Transportation</displayName>
<rpOrgName>Louisiana Department of Transportation</rpOrgName>
<rpCntInfo>
<cntAddress addressType="physical">
<delPoint>1201 Capitol Access Road</delPoint>
<city>Baton Rouge</city>
<adminArea>LA</adminArea>
<postCode>70802</postCode>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum tddtty="">225-379-1232</voiceNum>
</cntPhone>
</rpCntInfo>
</citRespParty>
</idCitation>
<spatRpType>
<SpatRepTypCd value="001"/>
</spatRpType>
<idCredit>Louisiana Department of Transportation and Development</idCredit>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;There are no use limitations of this data as provided by the Louisiana Department of Transportation and Development (LADOTD). The data was created and is maintained for internal planning usage of the Department. The data has been processed successfully on computers at the LADOTD and has been developed from the best available sources to ensure accuracy and reliability; however, the entire risk as to the quality and performance of the data is assumed by the user. The data herein, including but not limited to geographic data, tabular data, analytical data, electronic data structures or files, are provided "as is" without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. In no event shall the LADOTD be liable for direct, indirect, incidental, consequential or specific damages of any kind, including, but not limited to, loss of anticipated profits or benefits arising out of use of or reliance on the data. The user should refer to the accompanying metadata notes for a description of the data and data development procedures. The data may not be suitable for all high-precision measurement applications such as property transfers or other uses that might require highly accurate measurements of the earth's surface. Distribution of the data is intended for informational purposes and should not be considered authoritative for navigational, engineering, legal or other site-specific uses. The data is provided free to use in any product or publication, however no warranty, expressed or implied is made with regard to the accuracy of data or the spatial accuracy, and LADOTD accepts no liability for any damages or misrepresentation caused by inaccuracies in the data or as a result of changes to the data caused by system transfers or other transformations or conversions, nor is there responsibility assumed to maintain the data in any manner or form. &lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<idPoC>
<rpOrgName>Louisiana Department of Transportation</rpOrgName>
<rpPosName>Enterprise GIS Unit</rpPosName>
<role>
<RoleCd value="002"/>
</role>
<rpCntInfo>
<cntAddress addressType="physical">
<delPoint>1201 Capitol Access Road</delPoint>
<city>Baton Rouge</city>
<adminArea>LA</adminArea>
<postCode>70802</postCode>
<eMailAdd>DOTDGIS@LA.GOV</eMailAdd>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum tddtty="">225-379-1232</voiceNum>
</cntPhone>
<cntHours>8am - 4:30pm Mon-Fri (Central)</cntHours>
</rpCntInfo>
</idPoC>
<resMaint>
<maintCont>
<rpOrgName>Louisiana Department of Transportation</rpOrgName>
<rpPosName>Enterprise GIS Unit</rpPosName>
<role>
<RoleCd value="002"/>
</role>
<rpCntInfo>
<cntAddress addressType="">
<eMailAdd>DOTDGIS@LA.GOV</eMailAdd>
</cntAddress>
<cntPhone>
<voiceNum tddtty="">225-379-1232</voiceNum>
</cntPhone>
</rpCntInfo>
</maintCont>
</resMaint>
<idPurp>Classification of roadways based on their role within the transportation network.</idPurp>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;Functional System classifies roads based on their role within the transportation network. Higher classifications prioritize regional mobility by limiting direct access and connections, while lower classifications prioritize property access. Together, the classifications form a connected network of roadways ranging from major corridors to local streets. Functional System is a required data element submission to the Federal Highway Administration (FHWA) for the Highway Performance Monitoring System (HPMS) and is required to be submitted for all public roadways.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<searchKeys>
<keyword>Open Data</keyword>
<keyword>Transportation</keyword>
<keyword>Roads and Highways</keyword>
<keyword>LRS</keyword>
<keyword>FunctionalSystem</keyword>
</searchKeys>
<tpCat>
<TopicCatCd value="015"/>
</tpCat>
<tpCat>
<TopicCatCd value="018"/>
</tpCat>
</dataIdInfo>
<mdMaint>
<maintCont>
<rpOrgName>Louisiana Department of Transportation</rpOrgName>
<role>
<RoleCd value="002"/>
</role>
<rpPosName>Enterprise GIS Unit</rpPosName>
<rpCntInfo>
<cntAddress addressType="">
<eMailAdd>DOTDGIS@LA.GOV</eMailAdd>
</cntAddress>
<cntPhone>
<voiceNum tddtty="">225-379-1232</voiceNum>
</cntPhone>
</rpCntInfo>
</maintCont>
</mdMaint>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
</dqInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="">
<geoObjTyp>
<GeoObjTypCd value="002"/>
</geoObjTyp>
<geoObjCnt>0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<refSysInfo>
<RefSystem dimension="">
<refSysID>
<identCode code="26915"/>
<idCodeSpace>EPSG</idCodeSpace>
<idVersion>6.11(3.0.1)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<eainfo>
<detailed Name="">
<enttyp>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">0</enttypc>
<enttypds>Louisiana Department of Transportation and Development</enttypds>
</enttyp>
<attr>
<attrlabl Sync="TRUE">OBJECTID</attrlabl>
<attalias Sync="TRUE">OBJECTID</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="FALSE">Internal feature number.
System-generated unique identifier for each individual record or feature within the dataset.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape</attrlabl>
<attalias Sync="TRUE">Shape</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="FALSE">Feature geometry.
System-generated field that stores the geographic geometry and coordinate paths defining the feature.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Coordinates defining the features.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">FromDate</attrlabl>
<attalias Sync="TRUE">FromDate</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>In Esri's Roads and Highways, the FromDate field is a temporal date-and-time attribute that defines the exact date and time when an LRS feature (such as a route, centerline, or event) officially became operational or active
Together with the ToDate field, FromDate facilitates time awareness and time slicing. It dictates how geographic and attribute data are queried, edited, and visualized over time:</attrdef>
<attrdefs>LRS Network properties</attrdefs>
<attrdomv>
<udom>Marks the beginning of a feature’s lifespan in the database</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">ToDate</attrlabl>
<attalias Sync="TRUE">ToDate</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>In Esri's Roads and Highways, the ToDate field is a temporal date-and-time attribute that defines the exact date and time when an LRS feature (such as a route, centerline, or event) officially ceased to be operational, active, or valid.
The ToDate field acts as the closing boundary for a feature's lifecycle within the Linear Referencing System (LRS)</attrdef>
<attrdefs>LRS Network properties (https://doc.esri.com/en/arcgis-pro/latest/help/production/roads-highways/view-lrs-network-properties.html)</attrdefs>
<attrdomv>
<udom>Marks the end of a feature’s active lifespan.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">EventID</attrlabl>
<attalias Sync="TRUE">EventID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">38</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>In Esri's Roads and Highways, the EventID field is a system-enforced, alphanumeric identifier that uniquely distinguishes a specific logical asset or business attribute (such as a speed limit, pavement condition, or sign) across its entire temporal lifecycle.
The EventID represents the asset, not just the individual database row. When a route undergoes a realignment or an asset attribute changes, Roads and Highways executes a time slice. This retires the old row (populating ToDate) and creates a new row (populating FromDate). Both rows will retain the exact same EventID so that the asset's history remains fully traceable over time.</attrdef>
<attrdefs>https://doc.esri.com/en/arcgis-pro/latest/help/production/location-referencing-pipelines/external-event-registration.html</attrdefs>
<attrdomv>
<udom>A unique, system-generated alphanumeric identifier (typically a GUID or UUID) assigned to each distinct event or record.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">RouteID</attrlabl>
<attalias Sync="TRUE">RouteID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>In Esri's Roads and Highways, the RouteID field is a system-enforced, unique identifier that binds all the architectural elements of the Linear Referencing System (LRS) together. It maps a linear feature (the route) directly to its underlying geometry (centerlines) and its overlaid business assets (events).
The RouteID uniquely distinguishes a specific travel path or roadway entity within a given LRS Network.</attrdef>
<attrdefs>https://doc.esri.com/en/arcgis-pro/latest/help/data/linear-referencing/introduction-to-routes-and-route-feature-classes.html</attrdefs>
<attrdomv>
<udom>A unique, system-generated alphanumeric identifier that establishes the unique identity of a linear route within the network.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">FromMeasure</attrlabl>
<attalias Sync="TRUE">FromMeasure</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>In Esri's Roads and Highways, the FromMeasure field (internally mapped during event configuration as the measure_field parameter) is a numeric attribute that defines the exact linear starting distance along a route where an LRS asset, point of interest, or business event begins.
By definition, the value in FromMeasure must be less than or equal to the value in the ToMeasure field for monotonically increasing routes, preserving the topological integrity of the travel corridor.
For Line Events: It marks the strict beginning boundary of a linear asset segment (e.g., the starting point of a speed limit zone, paving material, or construction project).
For Point Events: It serves as the single, definitive location measure indicating exactly where a distinct point asset resides along the route (e.g., an individual highway sign, culvert, or accident location).
Dataset unit of measure = miles</attrdef>
<attrdefs>Esri ArcGIS Location Referencing system schemas, tool references, and workflow guides for ArcGIS Pro 3.3+ and Enterprise 11.3</attrdefs>
<attrdomv>
<udom>A numeric value indicating the starting location or measure of a linear event or segment along a specific route.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">ToMeasure</attrlabl>
<attalias Sync="TRUE">ToMeasure</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>In Esri's Roads and Highways, the ToMeasure field (internally mapped during event configuration as the to_measure_field parameter) is a numeric attribute that defines the exact linear ending distance along a route where a line asset, restriction, or business event concludes.
In standard increasing routes, the value in ToMeasure must be strictly greater than the value in FromMeasure to ensure topological validity along the corridor.
While mandatory for line events, this field is completely omitted or left blank (&lt;Null&gt;) for point events, as points exist exclusively at a single measure (FromMeasure).
Dataset unit of measure = miles</attrdef>
<attrdefs>Esri Create LRS Event Tool Reference, ArcGIS Pro Events Data Model Guide</attrdefs>
<attrdomv>
<udom>A numeric value indicating the ending location or measure of a linear event or segment along a specific route.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">DataSource</attrlabl>
<attalias Sync="TRUE">DataSource</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>An authoritative resource—such as a file, dataset, system, or document—used to create, compile, or derive the spatial features or descriptive attribute values within the dataset.</attrdef>
<attrdefs>International Organization for Standardization (ISO) Technical Specification 19139:2007, Geographic Information — Metadata — XML Schema Implementation</attrdefs>
<attrdomv>
<udom>An alphanumeric text string identifying the specific origin, agency, system, or vendor that provided or collected the segment or event data.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">DataYear</attrlabl>
<attalias Sync="TRUE">DataYear</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The specific calendar year or discrete time position that reflects when the geographic phenomena or descriptive attribute values actually existed in the real world.</attrdef>
<attrdefs>International Organization for Standardization (ISO) Technical Specification 19139:2007, Geographic Information — Metadata — XML Schema Implementation</attrdefs>
<attrdomv>
<rdom>
<rdommin>1900</rdommin>
<rdommax>2100</rdommax>
</rdom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">HPMSDataItem</attrlabl>
<attalias Sync="TRUE">HPMSDataItem</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>A specific, standardized roadway performance or inventory attribute required for annual federal reporting, structurally mapped as a linear referencing event layer and classified within the metadata using schema descriptors.</attrdef>
<attrdefs>Federal Highway Administration (FHWA) Highway Performance Monitoring System (HPMS) Field Manual</attrdefs>
<attrdomv>
<udom>An alphanumeric string or code designating the specific federal Highway Performance Monitoring System (HPMS) data element or narrative requirement mapped to the LRS segment.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">LocError</attrlabl>
<attalias Sync="TRUE">LocError</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>In Esri's Roads and Highways, the LocError (Location Error) field is a system-populated text attribute within an LRS Event table that flags and describes the data quality or spatial status of an event feature.
The LocError field serves as an automated quality control tracker. When you create, append, or modify LRS event data using ArcGIS Pro tools or web apps like the ArcGIS Event Editor, the system automatically validates the asset's measure locations against the underlying route.
Any string value other than No Error signals a structural problem with that asset row. Features with location errors may not render spatially on your map (dynamic segmentation fails) or may behave unpredictably during route adjustments.
The LocError field is explicitly system-managed and read-only within clients like the ArcGIS Event Editor. You cannot manually type into it; rather, it updates itself when you fix the underlying measure or date problem and refresh or reconcile your layers</attrdef>
<attrdefs> Esri Location Errors Analysis Guide, ArcGIS Event Editor Frequently Asked Questions</attrdefs>
<attrdomv>
<udom>A descriptive alphanumeric text string or numeric value detailing a specific linear referencing system (LRS) alignment issue, event orphan status, or spatial mismatch.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">FromReferentMethod</attrlabl>
<attalias Sync="TRUE">FromReferentMethod</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>In Esri's Roads and Highways, the FromReferentMethod field is a system-managed attribute within an LRS Event table that identifies the specific engineering or linear method used to capture and calculate the starting location of an asset.
When a cartographic or real-world realignment changes the length of a highway, standard measures shift. By storing how the feature was originally located via FromReferentMethod, the LRS can automatically recalculate the exact point on the new map using offsets from physical markers (like intersections or signs) rather than breaking the data link.
This field uses a pre-configured Geodatabase Coded Value Domain named dReferentMethod. This domain is automatically generated by Roads and Highways. The system populates it when edits are committed using the ArcGIS Event Editor or ArcGIS Pro tools.
Different rows in the exact same event table can use completely distinct linear referencing methods.</attrdef>
<attrdefs>Esri Storing Referent and Offset Information Reference Guide, Esri Enable Referent Fields Tool Reference, sri View LRS Event Properties Documentation</attrdefs>
<attrdomv>
<codesetd>
<codesetn>dReferentMethod</codesetn>
<codesets>LaDOTD</codesets>
</codesetd>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">FromReferentLocation</attrlabl>
<attalias Sync="TRUE">FromReferentLocation</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>In Esri's Roads and Highways, the FromReferentLocation field is a system-managed text attribute within an LRS Event table that stores the unique name, ID, or description of the specific physical asset or landmark feature from which the event's starting position is derived.
Instead of defining an event's start using only a raw, shifting route measure, this field permanently logs the name or primary key of the physical reference feature. Common examples include intersection names (e.g., "Main St &amp; 5th Ave"), reference marker post IDs (e.g., "MP 42"), or asset IDs (e.g., "Sign_94021").
If a highway is physically realigned or shortened, its linear measures shift. Because the system preserves the exact real-world anchor name in the FromReferentLocation field, the LRS software can dynamically recalculate the correct coordinates and new FromMeasure values without breaking or corrupting the asset's relational location.
For Point Events: This field captures the sole reference anchor for the point feature.
For Line Events: This field captures the starting anchor of the linear segment, while a companion field called ToReferentLocation captures the ending anchor.</attrdef>
<attrdefs>Esri Storing Referent and Offset Information Reference Guide, ArcGIS Pro Events Data Model Specifications, Esri Enable Referent Fields Tool Parameter Reference</attrdefs>
<attrdomv>
<udom> A text description or structured string identifying the starting referent landmark and its associated spatial offset used to locate the beginning of a linear event.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">FromReferentOffset</attrlabl>
<attalias Sync="TRUE">FromReferentOffset</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>In Esri's Roads and Highways, the FromReferentOffset field is a system-managed numeric attribute within an LRS Event table that stores the precise linear distance from a known physical landmark (FromReferentLocation) to the actual starting point of an LRS event or asset.
Assets are rarely positioned perfectly on top of intersections or mile markers. This field captures how far before or after that reference landmark the asset begins. For example, if a speed limit change occurs 500 feet past Mile Marker 42, the offset field stores that 500 unit value.
The values can be positive or negative numbers. A positive offset indicates a distance moving forward in the direction of increasing route measures, while a negative offset indicates a distance moving backward against the direction of calibration.
When real-world construction or map alignments change the underlying route lengths, raw measures shift. Because the system retains the fixed landmark name and this specific offset distance, the Roads and Highways software can run its structural equations to reposition the asset and calculate its new FromMeasure automatically.
For Point Events: This field stores the single offset value required to locate the point asset relative to its anchor.
For Line Events: This field establishes the starting point's offset, while a companion field named ToReferentOffset maps the terminating boundary offset.</attrdef>
<attrdefs>Esri Storing Referent and Offset Information Reference Guide, ArcGIS Pro Events Data Model Specifications, Esri Enable Referent Fields Tool Parameter Reference</attrdefs>
<attrdomv>
<udom>A numeric value representing the precise displacement or distance from the designated starting referent landmark to the actual beginning of the linear event.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">ToReferentMethod</attrlabl>
<attalias Sync="TRUE">ToReferentMethod</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>In Esri's Roads and Highways, the ToReferentMethod field is a system-managed attribute within an LRS Line Event table that identifies the specific engineering or linear referencing method used to capture and calculate the ending (terminal) location of a linear asset.
This field is only utilized for Line Events (such as pavement condition segments or speed limit zones). It is omitted or left blank (&lt;Null&gt;) for Point Events, as points do not possess an ending boundary.
By capturing how the end of an asset was originally located (e.g., via an intersection, engineering station, or mile marker), the LRS can dynamically recalculate the ending position (ToMeasure) if the underlying road network undergoes a physical or cartographic realignment.
This field is controlled by the same pre-configured Geodatabase Coded Value Domain named dReferentMethod that governs the starting method. The values are automatically maintained when edits are made via the ArcGIS Event Editor or ArcGIS Pro tools.</attrdef>
<attrdefs>Esri Storing Referent and Offset Information Reference Guide, ArcGIS Pro Events Data Model Specifications, Esri Enable Referent Fields Tool Parameter Reference</attrdefs>
<attrdomv>
<codesetd>
<codesetn>dReferentMethod</codesetn>
<codesets>LaDOTD</codesets>
</codesetd>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">ToReferentLocation</attrlabl>
<attalias Sync="TRUE">ToReferentLocation</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>In Esri's Roads and Highways, the ToReferentLocation field is a system-managed text attribute within an LRS Line Event table that stores the unique name, ID, or description of the specific physical asset or landmark feature from which the event's ending (terminal) position is derived.
This field is strictly mandatory for Line Events (e.g., a specific pavement project segment or functional classification zone). It is omitted or left blank (&lt;Null&gt;) for Point Events, as point features have no terminal boundary.
It records the permanent identity of the physical asset or landmark that defines where the asset stops. Common entries include a terminal intersection name (e.g., "State Route 12 &amp; County Rd 4"), a reference post ID (e.g., "MP 47.5"), or an engineering structure asset key.
If the physical road network is shortened, lengthened, or re-calibrated, raw measures change. Because the system holds the immutable text string of the ending landmark in ToReferentLocation, the LRS software can dynamically re-compute the new ending coordinate and update the ToMeasure field automatically without losing or corrupting the feature's relational endpoint.</attrdef>
<attrdefs>Esri Enable Referent Fields Tool Parameter Reference, Storing referent and offset information for event locations, Esri LRS Events Data Model Guide</attrdefs>
<attrdomv>
<udom>A text description or structured string identifying the ending referent landmark and its associated spatial offset used to locate the termination of a linear event.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">ToReferentOffset</attrlabl>
<attalias Sync="TRUE">ToReferentOffset</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>In Esri's Roads and Highways, the ToReferentOffset field is a system-managed numeric attribute within an LRS Line Event table that stores the precise linear distance from a known physical terminal landmark (ToReferentLocation) to the actual ending point of the LRS line event.
Much like its partner field, this is used strictly for Line Events to establish where the linear segment physically terminates relative to a real-world object. It is omitted or left blank (&lt;Null&gt;) for Point Events.
Linear assets rarely stop perfectly on top of an intersection or milepost. This field logs that exact gap. For example, if a lane restriction ends 300 feet before an upcoming intersection landmark, this field captures that exact relative value.
This field accepts both positive and negative values. A positive offset shifts the calculated endpoint forward (in the direction of increasing route measures), while a negative offset shifts the endpoint backward (against the direction of route calibration).
When real-world roadway realignments alter underlying route lengths, raw measure positions shift. Because the system preserves the fixed terminal landmark name and this specific offset distance, the Roads and Highways software can rerun its structural equations to reposition the asset and calculate its new ToMeasure automatically.</attrdef>
<attrdefs>Esri Enable Referent Fields Tool Parameter Reference, Esri Storing Referent and Offset Information Reference Guide, Esri LRS Events Data Model Guide</attrdefs>
<attrdomv>
<udom> A numeric value representing the precise displacement or distance from the designated ending referent landmark to the actual termination point of the linear event.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">created_user</attrlabl>
<attalias Sync="TRUE">created_user</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>A system-generated audit field maintained by Editor Tracking that automatically records the database user name or portal identity of the individual or automated process that created the record.</attrdef>
<attrdefs>ArcGIS Pro Documentation: Introduction to Editor Tracking</attrdefs>
<attrdomv>
<udom>An alphanumeric text string indicating the unique login name or account identity of the user who originally created the record or event segment.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">created_date</attrlabl>
<attalias Sync="TRUE">created_date</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>A system-generated audit field maintained by Editor Tracking that automatically logs the coordinated universal time (UTC) date and timestamp indicating exactly when the record was originally created in the geodatabase.</attrdef>
<attrdefs> ArcGIS Pro Documentation: Introduction to Editor Tracking</attrdefs>
<attrdomv>
<udom>A temporal value recording the exact calendar date and time when the specific feature, route, or event record was originally created in the geodatabase.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">last_edited_user</attrlabl>
<attalias Sync="TRUE">last_edited_user</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>A system-generated audit field maintained by Editor Tracking that automatically overwrites and records the database username or portal identity of the individual or automated process that most recently modified the record.</attrdef>
<attrdefs> ArcGIS Pro Documentation: Introduction to Editor Tracking</attrdefs>
<attrdomv>
<udom>An alphanumeric text string indicating the unique login name or account identity of the user who performed the most recent modification to the record or event segment.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">GlobalID</attrlabl>
<attalias Sync="TRUE">GlobalID</attalias>
<attrtype Sync="TRUE">GlobalID</attrtype>
<attwidth Sync="TRUE">38</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>A system-managed, globally unique identifier (GUID) automatically assigned to each record upon creation to maintain an unalterable identity across distributed enterprise geodatabases, replication workflows, and branch-versioned feature services.</attrdef>
<attrdefs> ArcGIS Pro Documentation: ArcGIS Field Data Types - GlobalIDs</attrdefs>
<attrdomv>
<udom>A system-assigned, globally unique alphanumeric identifier used to establish an un-duplicable identity for each individual record or feature in the geodatabase.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">last_edited_date</attrlabl>
<attalias Sync="TRUE">last_edited_date</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>A system-generated audit field maintained by Editor Tracking that automatically overwrites and logs the coordinated universal time (UTC) date and timestamp indicating exactly when the record was most recently modified in the geodatabase.</attrdef>
<attrdefs>ArcGIS Pro Documentation: Introduction to Editor Tracking</attrdefs>
<attrdomv>
<udom>A temporal value recording the exact calendar date and time when the specific feature, route, or event record was most recently modified in the geodatabase.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape_Length</attrlabl>
<attalias Sync="TRUE">Shape_Length</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Length of feature in internal units.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
</detailed>
</eainfo>
</metadata>
