Road Closure solution enhancements

[Joshua-Young]

Just some observations I have had since using the new road closure solution these past months.

1. Need a way to edit multiple attributes of different features at the same time
2. Support for honor 24-hour clock format when editing and having the seconds default to zero
   1. I use a 24-hour clock and it is supported everywhere except when editing the closure attributes
   2. When I pick a date the time is automatically filled in with the current time down to the seconds. It would save time for the seconds to always be zero.
3. A status field with values like "Under Review", "Public", and "Complete"
   1. This would allow filtering the public map to show only closures that are about to happen or are in progress without having to rely on dynamic date filters which currently do not play well with related record popups
4. A way to copy and paste closure locations and attributes for closures that happen over multiple days, but update the automatically

[ScottOppmann · Accepted solution]

Thanks for the feedback @Joshua-Young .    We are working on a minor update to the Road Closures solution for early 2025 and will likely move to a configuration of the new Web Editor in this update.   

Moving to the Web Editor will add support for reoccurring events (copy/paste) you describe in #4.  We're also working with the Web Editor team to add support for bulk attribute updates described in #1.  

We'll explore updates to the editing form to address #2.  Finally, want to think through #3 a bit more.  Currently, we are using the date/time to display / age closures in our Community Maps aggregated feed.  Reduces need to maintain another attribute that reflects the status of the closure - maintenance of that attribute would worry me.   

Thanks again for the note and enhancement requests.  

[Joshua-Young]

The #3 request is because I have having trouble using dynamic date filters to limit what the public sees. I cannot find a way to set a dynamic date filter on the view definition and when I set a dynamic date filter in the web map the related records popup elements stop working. I have a support case submitted for this issue. My current work around is to use an arcade expression to change the transparency based on the current date. The problem with this is a user can still open a popup of a closure that is not visible on the map.

I would like our public layer to start showing closures within 2 weeks of the closure starting and stop showing after the closure day is over.

[ChrisFox]

@Joshua-Young, I would recommend not changing the behavior/settings in the solution's public view as we use this for aggregation as part of the Community Maps program. You are welcome to create your own view off of the Road Closures service and modify the filter/visible fields however you would like. In addition, you can add an additional field to the source service to store a status field and you could use this to filter on your own view. This will not impact the solution or the contribution to the Community Maps program.

[Joshua-Young]

@Chris I have not set any filters on the view itself. I have been playing around with the filtering in the web map. I did have to add additional fields to the view to get distributed collaboration working correctly between ArcGIS Enterprise and ArcGIS Online. If the edit tracking fields and GlobalID are not in the view, then distributed collaboration will not sync between the two platforms.

I too would like to avoid adding a status field to the source service, but I have not found a reliable way to only show closures that are about to happen or are in progress using the built-in date filter options available through the new map viewer.