| ArcGIS REST Services Directory |
| Home > services > Mileposts (FeatureServer) > All Layers and Tables | | API Reference |
Fields / Coding / Description
Measure: The actual measure of the MilePost as it relates to the MilePoint.
Milepost: The number appearing on the MilePost sign.
Longitude: The as collected longitude of the Milepost.
Latitude: The as collected latitude of the Milepost.
Route/Milepost: The RouteID combined with the Milepost number.
MilePost_5: The Mileposts in 5 mile increments for mapping
MilePost_10: The Mileposts in 10 mile increments for mapping
MilePost_25: The Mileposts in 25 mile increments for mapping
MilePost_50: The Mileposts in 50 mile increments for mapping
Source: LiDAR asset collection in 2013
Updated: The measure field is updated using Esri Roads and Highways event behavior. Other fields including the Longitude/Latitude are not changed.
Update Procedure: Updated only when a new statewide data collection takes place, currently scheduled for late 2024.
Quality: Fair, the data is from 2013 and not updated. Also note that mileposts often remain in the field even after roads have been exchanged or partially exchanged between governmental entities. This results in odd looking data with inconsitent Route/MilePost data.
Connected Systems: None
Non-Connected Systems: Unknown.
Fields / Coding / Description
Measure: The actual measure of the MilePost as it relates to the MilePoint.
Milepost: The number appearing on the MilePost sign.
Longitude: The as collected longitude of the Milepost.
Latitude: The as collected latitude of the Milepost.
Route/Milepost: The RouteID combined with the Milepost number.
MilePost_5: The Mileposts in 5 mile increments for mapping
MilePost_10: The Mileposts in 10 mile increments for mapping
MilePost_25: The Mileposts in 25 mile increments for mapping
MilePost_50: The Mileposts in 50 mile increments for mapping
Source: LiDAR asset collection in 2013
Updated: The measure field is updated using Esri Roads and Highways event behavior. Other fields including the Longitude/Latitude are not changed.
Update Procedure: Updated only when a new statewide data collection takes place, currently scheduled for late 2024.
Quality: Fair, the data is from 2013 and not updated. Also note that mileposts often remain in the field even after roads have been exchanged or partially exchanged between governmental entities. This results in odd looking data with inconsitent Route/MilePost data.
Connected Systems: None
Non-Connected Systems: Unknown.
Fields / Coding / Description
Measure: The actual measure of the MilePost as it relates to the MilePoint.
Milepost: The number appearing on the MilePost sign.
Longitude: The as collected longitude of the Milepost.
Latitude: The as collected latitude of the Milepost.
Route/Milepost: The RouteID combined with the Milepost number.
MilePost_5: The Mileposts in 5 mile increments for mapping
MilePost_10: The Mileposts in 10 mile increments for mapping
MilePost_25: The Mileposts in 25 mile increments for mapping
MilePost_50: The Mileposts in 50 mile increments for mapping
Source: LiDAR asset collection in 2013
Updated: The measure field is updated using Esri Roads and Highways event behavior. Other fields including the Longitude/Latitude are not changed.
Update Procedure: Updated only when a new statewide data collection takes place, currently scheduled for late 2024.
Quality: Fair, the data is from 2013 and not updated. Also note that mileposts often remain in the field even after roads have been exchanged or partially exchanged between governmental entities. This results in odd looking data with inconsitent Route/MilePost data.
Connected Systems: None
Non-Connected Systems: Unknown.
Fields / Coding / Description
Measure: The actual measure of the MilePost as it relates to the MilePoint.
Milepost: The number appearing on the MilePost sign.
Longitude: The as collected longitude of the Milepost.
Latitude: The as collected latitude of the Milepost.
Route/Milepost: The RouteID combined with the Milepost number.
MilePost_5: The Mileposts in 5 mile increments for mapping
MilePost_10: The Mileposts in 10 mile increments for mapping
MilePost_25: The Mileposts in 25 mile increments for mapping
MilePost_50: The Mileposts in 50 mile increments for mapping
Source: LiDAR asset collection in 2013
Updated: The measure field is updated using Esri Roads and Highways event behavior. Other fields including the Longitude/Latitude are not changed.
Update Procedure: Updated only when a new statewide data collection takes place, currently scheduled for late 2024.
Quality: Fair, the data is from 2013 and not updated. Also note that mileposts often remain in the field even after roads have been exchanged or partially exchanged between governmental entities. This results in odd looking data with inconsitent Route/MilePost data.
Connected Systems: None
Non-Connected Systems: Unknown.