New view for viewing and managing district network routes
District network routing facilities are used to specify and store a definition of a route, or vertex/edge path, in a the district network model.
A route is defined by its starting, ending and in-between waypoints which are always in a specific order (i.e. a List).
Routes are resolved into concrete paths, which means a fully baked continuous path of vertices and edges that passes through the requested waypoints. Concrete routes are calculated using the Apros solver TH process model calculation level components. There is a shortest-path algorithm for this in Apros SCL modules already.
Task list:
-
Add new Routes view -
Allow definition of a new route by clicking through waypoints -
List routes as root level nodes in the Routes view tree -
List waypoints in Routes view under the corresponding route -
Allow committing a route (writes it to the database) - Now by pressing Enter on keyboard when the route is done
-
Support renaming of routes from Routes view - Rename Route in context menu or F2
-
Support deletion of routes from Routes view - Discard Route in context menu
-
Allow user to calculate route and select the corresponding elements on the district network diagram - Select Route on Diagram in context menu
-
More intuitive route tool initiation and route committing -
Visualize found shortest route on diagram during route definition - This is needed to avoid the need to perform "select on diagram while the route has not yet been committed which again causes users to create fully baked routes with tons of waypoints instead of just the end points and actually using route finding to do the rest.
-
Visualize selected waypoints on the diagram (perhaps as "badges" like google maps)
Scrapped tasks:
Allow reordering of waypoints in Routes view
Edited by Tuukka Lehtonen