This is a request to add an enhancement to the Directions widget and this option to carry through to any instant app, web map, experience builder app needing this capability from directions widget.
The request is to add the ability for the app creator/configurer to place a specific barrier (such as a road closure) in the directions widget and have the ability to disable the Edit button on the directions widget so the end user cannot change the barrier. Or disable just the ability to perform a barrier edit.
Use case: The City of Greenville, SC wanted to provide an interactive map to the citizens ahead of a major road/bridge closure that is scheduled to occur. We wanted to be able to provide the user with an app so that they can pre-plan their route before the closure to find a route that best fits their routine ahead of time using the Esri street network service (we do not have a custom route network to use).
The directions widget (tried on Web Map and Experience Builder) does a great job allowing the user to enter a To:From: addresses and add a barrier. However, there doesn't appear to be a way for us, the City GIS analysts building the app, to set a barrier in the widget that cannot be deleted by end users. We need a way to add a "permanent" barrier that the citizens cannot accidentally delete.
Yes, we know the routing for citizens will take credits, but the "preplanning" app only needs to be available prior to the closure. Once the closure happens, citizens can use their favorite mapping applications outside of Esri.
This ability would be used by us in many situations to allow citizens to preplan routes ahead of known closures - especially for our large special events and races that close several downtown streets several times a year.
I spoke to some Esri Javascript developers at the Dev Summit. They indicated it was a great use case and asked me to submit the idea here and an enhancement request through support.
Thanks,
Thank you for posting your idea here, @CarmenDurham. This makes sense to me. We will consider this functionality for a future release.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.