You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After some pained troubleshooting, we've identified the following enhancements for deployments in order to make troubleshooting and finding deployments a little easier:
show routerId so user knows if this is a 'test' feed or main production feed
we should look for outlier stops and report them as a validation warning
the deployment screen should show a preview of the OSM extract area as a map. (maybe even allow adjustment on the fly?)
there doesn't seem to be any rhyme or reason to how the deployment listings are sorted. I would have it default to deployment data (most recent first), with maybe an option to sort by name
maybe also allow sorting by any of the columns in the main feed source list. e.g. if you want all of the deployable feeds on top
it would also be handy to have some indication of when the feed was last updated in that list
if feeds are removed from the deployment because they are expired, there should be a warning for the user
option to use cached OSM file and/or bundle (skip downloading)
notify the user when the deployment to server completes or fails
The text was updated successfully, but these errors were encountered:
After some pained troubleshooting, we've identified the following enhancements for deployments in order to make troubleshooting and finding deployments a little easier:
The text was updated successfully, but these errors were encountered: