I don't completely understand numberOfStops, so it's possible I have not used the tag properly.

The idea behind numberOfStops is that it serves as a placeholder for the number of stations (nodes) that are not explicitly defined. This means we don’t have to draw or specify every station where a train will stop. Instead, we can simply provide a number indicating that the train stops at n stations, without defining where they are or how long the train stays there. The stopping times and travel times are combined for that edge, or the stopping times are already integrated. This helps long‑term planners work more quickly without dealing with details that are not important at this stage of planning.

The last commit add a few events that seemed missing. There's a couple that are not useful for osrd (as we deactivated the features), but should probably be emitted for other potential users that may want to use the event system too. There are a few that correspond to niche features enabled in osrd, and for which the osrd behavior is currently bugged. Finally I have not added any to visibleTrainrunsSetLabel, as the behavior already seems propagated somehow?

Could you share an overview of what OSRD uses? It might be helpful to have a short document with links in the technical documentation folder. I think it would be important to provide an overview of the components OSRD relies on, and which application uses which layer or interface (API).

API documentation would be really helpful -> https://github.com/OpenRailAssociation/netzgrafik-editor-frontend/tree/main/documentation/technical (if the documentation is somewhere else -> please share / link it)

As OSRD is directly listening to every "operation" events, you can consider that OSRD reacts to every operation.emit you can find in the code of NGE. See our listener.

Such documentation would be difficult to provide, and more important, difficult to maintain. For instance, I tried to note everything here, a long time ago, but I fear that this is not up to date anymore.

To add some information to Louis's answer, we have only disabled a couple of actions in the fork. For example, I think the action of turning a node into a non node stop or vice versa is disabled in osrd currently (as osrd lack a model for non node stop). We have also disabled the file import (as it's done in osrd interface instead), and we have disabled the save filter actions as we don't store them. I may forget a thing or two, but the differences are intentionally kept minimal. Everything else we use!

I don't completely understand numberOfStops, so it's possible I have not used the tag properly.

The idea behind numberOfStops is that it serves as a placeholder for the number of stations (nodes) that are not explicitly defined. This means we don’t have to draw or specify every station where a train will stop. Instead, we can simply provide a number indicating that the train stops at n stations, without defining where they are or how long the train stays there. The stopping times and travel times are combined for that edge, or the stopping times are already integrated. This helps long‑term planners work more quickly without dealing with details that are not important at this stage of planning.

Thanks for the explanation!

Yep, if you are curious, here are all the things we do differently when we use NGE for OSRD: main...osrd-project:netzgrafik-editor-frontend:standalone