Location errors allow you to determine data quality issues with LRS events. When events are created or edited using ArcGIS Pro feature creation or feature editing tools, or created by adding a row in an event layer's attribute table, the status of the event feature is indicated in the location error field.
When an event is created accurately using the attribute table or any other method, the result is a No Error value for the location error field. Any status other than the No Error value indicates a problem that should be resolved; otherwise, unexpected behavior may occur when performing other LRS operations. The list of possible statuses depends on the event creation or event editing method in use.
For statuses that occur while using specific methods, refer to event creation using feature creation, event editing using feature edits, event creation using the attribute table, and event editing using the attribute table.
Note:
The complete list of statuses also includes location errors that can occur when referent offset values are in use or after the Translate Event Measures tool has been run.
The following table provides the complete list of statuses:
| Location error | Description |
|---|---|
| Different From Route And To Route Line IDs | The starting route and the ending route have different line IDs. This is applicable to events associated with line networks. |
| From Referent Location Not Found | The event's starting referent location was not found. |
| From And To Referent Locations Not Found | The event's starting and ending referent locations were not found. |
From Route Line Order Not Lower Than To Route Line Order | The starting route does not have a lower line order than the ending route. This is applicable to events associated with line networks. |
| Invalid Dates | The event's start date is before the event's end date. |
Invalid Length Field Value | The event's length field value is invalid. This is applicable to referent offset events using the length field. For example, if the route is 1000 feet long, but the referent offset is set to 1500 using length as the referent method, the result is an invalid length. |
| Invalid Route Line ID | The route does not have a valid line ID. This is applicable to events associated with line networks. |
| Invalid Route Line Order | The route does not have a valid line order. This is applicable to events associated with line networks. |
Invalid Location Route ID | The route location's route ID is invalid (NULL, empty, or invalid value). |
| Invalid Location Measure | At least one of the route location's measure values is invalid. |
| Invalid Referent Method | The event's referent method is invalid or does not exist in the dReferentMethod domain. |
Measure Extent Out Of Route Measure Range | The route location's shape was not found because the start measure and the end measure are outside the route measures. |
Multi Match | Multiple matching routes were found. This error can occur after running the Translate Event Measures tool. |
| Multiple Route Locations Found | More than one point location was found. Measures may not be unique along the routes. This error can occur after running the Translate Event Measures tool. |
No Error: Conflict Prevention Bypassed | The event was correctly located but was appended using the Append Events tool with the Append even if there are conflict prevention locks parameter checked. |
No Match | No matches were found in the target network for an event associated with a route in the source network. This error can occur after running the Translate Event Measures tool. |
Parent Event Not Found | The parent event could not be found. This is applicable to referent offset events. |
Parent Event Measure Location Not Found | The parent event's measure value is invalid. This is applicable to referent offset events. |
| Partial Match For The From Measure And To Measure | The start and end measures are outside the route measure range. This error can occur after running the Translate Event Measures tool. |
| Partial Match For The From Measure | The start measure is outside the route measure range. |
| Partial Match For The To Measure | The end measure is outside the route measure range. This error can occur after running the Translate Event Measures tool. |
Partial Multi Match For The From Measure | Multiple matches were found for the start measure. This error can occur after running the Translate Event Measures tool. |
Partial Multi Match For The From And To Measure | Multiple matches were found for the start and end measures. This error can occur after running the Translate Event Measures tool. |
Partial Multi Match For The To Measure | Multiple matches were found for the end measure. This error can occur after running the Translate Event Measures tool. |
| Route Measures Null | The route does not have m-values, or the m-values are null. |
Route Location Not Found | The route location's shape was not found. The route has no m-values, or the route location's measures don't exist on the route. |
| Route Not Found | The route does not exist. This may be due to the route not existing in the network or the route and event having different time ranges that do not overlap. |
| Route Shape Empty | The route does not have a shape, or the shape is empty. |
| Route Not M Aware | The route is not an m-aware polyline. |
| To Referent Location Not Found | The event's ending referent location was not found. |
XY Location Invalid | The event's xy location was not found on the route. |
Zero Length Extent | The start measure is equal to the end measure. |