| snippet:
|
A point feature of the Mileposts on state owned roads in New Mexico.
Use: For determining where a MilePost exists on NM roads.
Guidance: MilePost as opposed... |
| summary:
|
A point feature of the Mileposts on state owned roads in New Mexico.
Use: For determining where a MilePost exists on NM roads.
Guidance: MilePost as opposed... |
| accessInformation:
|
NMDOT, Roadway Inventory, GIS Support |
| thumbnail:
|
|
| maxScale:
|
5000 |
| typeKeywords:
|
[] |
| description:
|
<DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">Fields / Coding / Description</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">Measure: </SPAN><SPAN>The actual measure of the MilePost as it relates to the MilePoint.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">Milepost: </SPAN><SPAN>The number appearing on the MilePost sign.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">Longitude: </SPAN><SPAN>The as collected longitude of the Milepost.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">Latitude: </SPAN><SPAN>The as collected latitude of the Milepost.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">Route/Milepost: </SPAN><SPAN>The RouteID combined with the Milepost number.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">MilePost_5: </SPAN><SPAN>The Mileposts in 5 mile increments for mapping</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">MilePost_10: </SPAN><SPAN>The Mileposts in 10 mile increments for mapping</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">MilePost_25: </SPAN><SPAN>The Mileposts in 25 mile increments for mapping</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">MilePost_50: </SPAN><SPAN>The Mileposts in 50 mile increments for mapping</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Source: </SPAN></SPAN><SPAN><SPAN>LiDAR asset collection in 2013</SPAN></SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Updated: </SPAN></SPAN><SPAN><SPAN>The measure field is updated using Esri Roads and Highways event behavior. Other fields including the Longitude/Latitude are not changed.</SPAN></SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-weight:bold;">Update Procedure: </SPAN><SPAN>Updated only when a new statewide data collection takes place, currently scheduled for late 2024.</SPAN></P><P><SPAN STYLE="font-weight:bold;">Quality: </SPAN><SPAN>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.</SPAN></P><P><SPAN STYLE="font-weight:bold;">Connected Systems</SPAN><SPAN>: None</SPAN></P><P><SPAN STYLE="font-weight:bold;">Non-Connected Systems: </SPAN><SPAN>Unknown.</SPAN></P></DIV></DIV></DIV> |
| licenseInfo:
|
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>None however, the Mile</SPAN><SPAN STYLE="font-weight:bold;">Post</SPAN><SPAN> and Mile</SPAN><SPAN STYLE="font-weight:bold;">Point</SPAN><SPAN> of a route often times do not match due to numereous issues such as road realignments, road exchanges, or inaccuracies when the MilePost was placed in the ground. An example is US285 where the last MilePost number is 408 but, the MilePoint is 412. </SPAN></P></DIV></DIV></DIV> |
| catalogPath:
|
|
| title:
|
SDE.Milepost |
| type:
|
|
| url:
|
|
| tags:
|
["Mileposts","LRS","NMDOT","Roadway Inventory"] |
| culture:
|
en-US |
| name:
|
|
| guid:
|
|
| minScale:
|
150000000 |
| spatialReference:
|
|