The change is due to https://github.com/eclipse/sumo/issues/5531 You have to possibilities for modelling this dual-track layout:
1) the way it is done in the original osm with two separate <way> elements 2) with a way that has attribute oneway="no" and that doesn't have the tag railway:bidirectional=regular I'm honestly not sure how oneway="no" with railway:bidirectional is supposed to be interpreted. To me the osm wiki implies that railway:bidirectional describes capabilities of a single track. On the other hand, oneway describes whether there are lanes in both directions for regular ways. A compromise could be to create two tracks that both can be used in either direction (4 sumo edges) but this isn't implemented yet. regards, Jakob Am Fr., 3. Mai 2019 um 18:39 Uhr schrieb Lara CODECA <[email protected] >: > Dear All, > > I just noticed that something changed with the conversion of the railways > in netconvert. > > With netconvert 1.2.0, and OSM single rail taggeg with double directions > generates the two separated rails. > The exact same OSM and netcfg files with v1_2_0+0163-d480773dd2 generates > a single rail. > > All the files are available at > (1.2.0) https://github.com/lcodeca/MoSTScenario/releases/tag/v0.6 > (devel) https://github.com/lcodeca/MoSTScenario > > Was this change wanted? If so, what is the correct way to fix the scenario? > > Thank you for your time! > > All the Best, > Lara > > -- > Lara CODECA > Postdoc > Tel : 04.93.00.81.51 > > EURECOM > Campus SophiaTech > http://www.eurecom.fr/ > _______________________________________________ > sumo-user mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://www.eclipse.org/mailman/listinfo/sumo-user >
_______________________________________________ sumo-user mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
