Re: [sumo-user] Conflict using netdiff when multiple members edit networ

[Jakob Erdmann <namdre.sumo@xxxxxxxxx>]

You can set the default prefix for edges junctions etc. as netedit options (--node-prefix, --edge-prefix).

Conceivably you could have every team member use a distinct prefix to avoid ID collisions.

To fix the existing patch files you could probably do a search and replace to change the default prefix with a member-specific prefix.

Instead of setting multiple options  you could in theory also set a global prefix with option --prefix but this global prefix currently doesn't work in netedit: https://github.com/eclipse/sumo/issues/12024

Patch files are the recommended way to work on a network as team. Another possible method is distributing the work between "spotters" and "fixer" with multiple people spotting the problems and one person fixing them.

Am Fr., 11. Nov. 2022 um 10:47 Uhr schrieb Yunhe Zhao <bleuclair0104@xxxxxxxxx>:

Hi all,

I'm currently working on a semi-large project within a 5 people group, and when we wanted to edit the network simultaneously on different areas and then merge using netdiff.py, we came across this problem: 

When more than one of us create new edges and nodes, the automatically assigned names of these edges and nodes are the same (for example both J0). This resulted in unexpected long-distance edges between different junctions in the merged network. Please see picture below the selected edges.

Does anyone know how to resolve this conflict without having to change the names manually? 

Also are there any other good ways to contribute to a network as a team?

Best,

Yunhe

_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user