topic Re: LRS functionality in AGOL – Locating Features/Querying LRM user stories in Roads and Highways User Group (RHUG) Questions

LRS functionality in AGOL – Locating Features/Querying LRM user stories

RyanKoschatzky — Wed, 14 Apr 2021 19:22:11 GMT

Post your user stories for Reference M Value, Referencing Data and Integration of XY. List any current issues with not having this functionality.

See https://community.esri.com/t5/roads-and-highways-user-group/rh-user-group-march-2021-pdf/m-p/1040723 for definitions

Re: LRS functionality in AGOL – Locating Features/Querying LRM user stories

KyleGonterwitz — Thu, 15 Apr 2021 15:33:57 GMT

Pavement Condition Index and PM2 (pavement performance measures) for MPOs could be easily collected and referenced over time on the same routes for pavement lifecycle analysis and management across DOT and MPO jurisdictions.

Re: LRS functionality in AGOL – Locating Features/Querying LRM user stories

KyleGonterwitz — Wed, 14 Apr 2021 19:57:12 GMT

Cities and Counties could easily calculate impacts to traffic improvements by comparing before and after crash rates along the routes when traffic safety countermeasures are applied.

Re: LRS functionality in AGOL – Locating Features/Querying LRM user stories

KyleGonterwitz — Wed, 14 Apr 2021 20:06:27 GMT

In the meeting the question about impedances comes up, one answer to that question (and it was discussed in the meeting) and the solution this discussion topic proposes is to close the gap between State DOT Linear reference systems and non-State DOT organization transportation and logistics management.

Re: LRS functionality in AGOL – Locating Features/Querying LRM user stories

ErinLesh1 — Fri, 16 Apr 2021 11:54:38 GMT

NCDOT Divisions frequently use Go!NC (AGOL) to view and interact with data on a web map, which is easier than learning ArcMap and/or Pro. For resurfacing estimations, the want to click on routes on a web map and have it return the route measures. They are currently stuck using our "hatch" map as a workaround. NCDOT Divisions also find it helpful to have maps for resurfacing contracts which are done 3-5 times a year or more. The maps are currently done mostly by hand and they show sections to be resurfaced with a to/from and based on intersection or milepost description. They want a tool to more seamlessly create these maps.

Re: LRS functionality in AGOL – Locating Features/Querying LRM user stories

SarahWray — Thu, 13 May 2021 17:36:52 GMT

NCDOT uses Survey123 to collect disaster assessment details. The lat/long of the damaged infrastructure is recorded but the route/milepost data, if entered, is done by hand. This information is integrated with the agency's ERP which then produces reports for FEMA and FHWA reimbursement purposes. Newer reporting requirements from the federal agencies require detailed route information to support the financial justification. Having this functionality in the field will allow for quicker and more accurate location details which will decrease the amount of time needed to produce the reimbursement reports thereby allowing for NCDOT to recoup funds sooner.