LRS functionality in AGOL – Support Field Operations user stories

501
2
04-14-2021 12:22 PM
RyanKoschatzky
Occasional Contributor III

Post your user stories for Connect R&H with Survey 123, ArcCollector and Workforce Tools. 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.

2 Replies
MichaelO_Neil
New Contributor

At NYSDOT, multiple field data collection efforts are underway using Collector & Survey 123.  Integration between those apps and R&H would allow for the simplification of a complex workflow. 

Currently, all editing takes place within a transactional geodatabase which is then replicated via python script into a data warehouse.  The script locates the recently edited assets on the LRS and, ultimately, populates a Route ID and Measure.  From there, the data is then made available as a map service for ingestion into NYSDOT’s new maintenance management system.

A key aspect of this workflow is that each asset is collected with a route identifier, ex. I-90, in order to validate the route location generated using the linear referencing toolbox (Locate features on Routes).

At the time when this workflow was developed (late 2019), the geometry to measure operation within the R&H API had bugs and deficiencies which prevented its use.  Specifically, the search tolerance was not being enforced which resulted in inaccurate results being returned.  Also, there was no indication as to which returned route location was the closest.  These issues have since been addressed at 10.8, but we have yet to test them since we are currently using 10.7.1.

A significant issue going forward is that the existing process has worked well for asset updates on the network but is lacking when it comes to, conversely, network updates on the assets.  Any future integration that would assist in tackling this issue would be happily welcomed.

MunroKevin
New Contributor II

At INDOT we manage a large number of roadside assets off the linear referencing system using a combination of mobile and web based editing. Critical to these inventories is to have a human readable unique key be DB generated (on create) for every record and to offer a record ‘retirement’ method instead of offering a record ‘delete’ method.

Workflows like the corridor sign replacement require a-spatial lists of data ordered by combinations of route/direction/side/measure/administrative unit. To do this:

A one time effort is required to associate each asset to its reporting route_id and use geometry2measure to interpret a measure.

Event data containing minimum fields like the unique key of the asset and it’s route/measure/from_date be loaded as an event into R&H.

Regularly, FME is used on a frequency to:

Compare differences between event records and non LRS assets to communicate:

  1. Need for retirement or end dating in either repository when mismatches in lists are evident. Theis can trigger a manual exploration/evaluation or trigger direct event and/or asset update.
  2. Data for inserts into the event layer when new inventory has been collected or retired.
  3. Data for updates to the event layer when changes in location have been detected in the last and current geometry.

Finally,

FME is used to; on a frequency, join asset inventories with linear referenced records to create directionally ordered lists of assets for use in the field for inventory completeness checks, sign orders and work orders.

Using FME rather than an ESRI solution is IMHO more flexible and tailorable to the individual and ever moving requirements of these integrations.

0 Kudos