topic Re: Leveraging R&H API in Roads and Highways Questions

Leveraging R&H API

deleted-user-UxcAu2PHrDQp — Tue, 18 Jul 2017 12:38:35 GMT

For those that have FME and Roads & Highways, Iowa DOT developed custom FME transformers and web service (called SkyFire) that combines multiple R&H web services making it easy for end users to transform location data. Our old LRS had an API my team developed called JetFire (see attached documentation, soon to be retired)

Example SkyFire API call

https://fme.iowadot.gov/fmedatastreaming/SkyFire/...

If you have FME and want to know more, email me and I can share what we have.

If you have done similar things with ESRI workflow manager I would like to see what you have done. Looking to stand up a similar geoprocessing service on our ArcGIS Server stack. Might be good to pull together a webinar to show how organizations are leveraging R&H services to do cool things.

Re: Leveraging R&H API

ScottFierro2 — Tue, 18 Jul 2017 12:52:16 GMT

Eric, we'd be interested in seeing what you have done. Didn't notice your email in profile. Could you please shoot me a message at some point to discuss; scott.fierro@dot.ohio.gov Thanks

Re: Leveraging R&H API

deleted-user-UxcAu2PHrDQp — Tue, 18 Jul 2017 14:28:58 GMT

Sure will once I get a list of those interested. Funny you cant see my email in the profile, I will check that eric.abrams@iowadot.us.

Re: Leveraging R&H API

Anonymous User — Wed, 19 Jul 2017 15:20:29 GMT

Thanks for sharing this Eric. This is good stuff. I'd also like to make the case for geoprocessing (GP) services for these kinds of solutions. The biggest benefit is that you have a COTS client with the Web AppBuilder Geoprocessing widget that you can deploy without writing any code. Using a WAB application, people could execute these functions from their phone or any other device. If authored correctly geoprocessing services can have very good performance and can access all of your GIS data. Check out this (very simple) GP service I made for doing offsets with MassDOT data: Execute Task (FindMassDOTOffset). As you can see this GP service performs pretty well. To get the best performance with GP services check out the help doc here: Performance tips for geoprocessing services—Documentation | ArcGIS Enterprise.

Re: Leveraging R&H API

deleted-user-UxcAu2PHrDQp — Wed, 19 Jul 2017 17:08:53 GMT

We started with a GP service but had performance issues. We did not take the time to do a deep dive on why it was slow; could of been our ignorance. After you and I talked last week, the challenge is on to create a complex GP service and see if we can get the same or similar results. GP services gives us a better integration with Web App Builder, which is needed. But there are some special things our service does that a GP service may not be able to accomplish, stay tuned. We will hit you up for a starting sample.