Some more thoughts and visions ...
We got four implementation platforms to fulfill the route builder's desires:
- Mike's RW Toos;
- Ruth's map visualisation;
- Various batch mode tools from the likes of Jim and me;
- Last, not least, the route editor with the various display modes through which you cycle using the space bar.
We cannot modify the route editor, of course. We can only remember what it can do and not duplicate that. But complement it where desired, e.g., to show track properties in tunnels, too.
The most attractive field of development seems to me the integration of the complex/abstract stuff such batch tools to with the user friendly stuff by Mike and Ruth. E.g., it would be cool if RW Tools would read CSV tables and perform what it does already interactively for each of the lines in the table. E.g., swap assets.
Ruth's tool could take a list of missing assets, generated by RW Tools or my blueprint checker, and mark their locations on the map. Or it could just take a list of icons or colours and coordinates (tile number plus place on tile) specifying where to plot them (as a blob in the case of colours). This would be used for missing assets, or for marking fishy junctions, signals with some link flaw, distants that are really close to the stop signal they announce, harsh gradient changes, track segments with some property marked for a suspicious short length, e.g., under 1 m, other fishy spots in the track work. The idea is that if some analysis tool outputs a list of spots, then it is easy to show that graphically.
Colour-coding track is not as simply to implement. However, if the lines of a CSV contain some ID of the track ribbon plus colour, then it would be easy to implement in the map drawing.
Ideas for colour coding are, using red for bad and green or blue or black for fine, and yellow for medium:
- Deceleration do stop at the signal based on distance to distant, line speed and gradient;
- Curve radius;
- Centrifugal force based on line speed, radius and superelevation.
All these would help quality assurance in route building.
In addition, showing track links as arcs or tags could be helpful. The most useful representation appear to be 5-cornered tags (rectangle with adjoining triangle) pointing in the direction for which the track link is valid, bearing the number of the link. All links of the same signal share the same colour, colours for different signals are assigned randomly.
Showing markers and various track properties as simple track colouring might provide a swift alternative to the route editor and a foundation for route documentation in user manuals. On the other hand, it is not as much of an enrichment as showing something not visualised otherwise.