[Feature request]: Flexible Train ID naming and coloring

[hamishpf]

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for an issue that matches the one I want to file, without success.

Request type

Request for a new component

Functionality

Problem

Current program only permits SBB train ID names

Users would like to create Train IDs for other traintypes (DB's ICE, SNCF TGV, etc and for potentially other networks)

Proposed solution

In addition to the options, the menu box has a custom name field that permits free text (e.g. upt to 5 characters) and custom colors

Link to design proposal file

No response

[aiAdrian]

I haven’t reviewed this in detail yet, but I’d like to add the following hint:
DATA_MODEL_JSON.md

https://github.com/OpenRailAssociation/netzgrafik-editor-frontend/blob/main/documentation/DATA_MODEL_JSON.md

netzgrafikColors: Represents the user defined colors which can be used in the Netzgrafik.

I think we should combine this request with a “Netzgrafik Color Editing” functionality. This would allow each user to define their own colors. Currently, the color is stored in the metadata, and this works — you can manually edit the JSON data and then have the category and color. However, this process needs to be much more user-friendly.

[emersion]

Indeed. The current data model supports custom train categories and colors just fine, we're just missing any kind of UI to edit these. From the OSRD side, we're passing SNCF categories and colors and NGE works well.

[germannp]

Would be great, if these colors and labels could be customized; we have used these traintypes and colors to visualize different networks, locomotive types and whatnot in the past.

[hamishpf]

I haven’t reviewed this in detail yet, but I’d like to add the following hint: DATA_MODEL_JSON.md

https://github.com/OpenRailAssociation/netzgrafik-editor-frontend/blob/main/documentation/DATA_MODEL_JSON.md

netzgrafikColors: Represents the user defined colors which can be used in the Netzgrafik.

I think we should combine this request with a “Netzgrafik Color Editing” functionality. This would allow each user to define their own colors. Currently, the color is stored in the metadata, and this works — you can manually edit the JSON data and then have the category and color. However, this process needs to be much more user-friendly.

Thank you. I hadn't considered customizing it through the meta data. I think a UI to do this would still be a nice to have. Though I'm happy to close this as its probably low priority.

[hamishpf]

@emersion would you mind detailing how I can customize the colors, I've not figured it out?

here are the steps I've taken

1. export a json file from the Netgraph view
2. Edit the meta data (example below)

"trainrunCategories": [
{
"id": 0,
"name": "Express",
"order": 0,
"colorRef": "Exp",
"shortName": "Exp",
"fachCategory": "HaltezeitIPV",
[... truncated....]
},

(I've highlighed the edited values. 

3. Change the : ColorRefType[] defaults. <--- This is where I'm getting stuck. Should I add updated information in the [meta data](https://github.com/OpenRailAssociation/netzgrafik-editor-frontend/blob/main/documentation/DATA_MODEL_JSON.md#metadata)? Or should ColorRefType and Color ref values (#xxxxxx) be also edited elsewhere. 

(Apologies if this is a newbie question)

[aiAdrian]

We should definitely add a user interface to the network graphics editor. This would address a frequently expressed user request. While changes to the JSON data (metadata) are generally possible, they carry risks. Errors can lead to system malfunctions because they are not safeguarded by appropriate logic in the code. In particular, updating the metadata can cause instability.

Therefore, I propose including this in the planning and introducing a new subsection under “Edit” where metadata such as colors and train categories can be adjusted. Optionally, we should also explore whether clock frequencies and similar parameters can be modified. This is certainly more complex and should therefore be considered an option for now.

I strongly recommend adding the user interface as soon as possible to improve usability and at the same time strengthen the user base.