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.