Hello, I perfectly understand the need to create SUMO networks from your own preprocessed data. While we have the turn:lanes thing on our todo-list there is no telling when we'll get around to it and unless you want to send us a patch (which would be great) your solution is understandable. However, I stand by my recommendation of using Netconvert to create the .net.xml file. The common way to create .net.xml from custom input data is to create/generate the so-called plain-xml files .nod.xml, .edg.xml and .con.xml (and optionally .tll.xml) and built the network from these with Netconvert. The advantage of this approach is that you are insulated from any changes in the .net.xml format and do not need to hunt for special attributes. The mechanism for defining custom junction shapes in a .nod.xml file is documented in the wiki and you should be able to define any other kind of customization as needed this way (if not, let me know about any constraints you encounter). The reason I'm stressing this point is that I already encountered much grief by people who generated their own .net.xml files directly.
regards, Jakob 2017-06-05 21:27 GMT+02:00 Fabien Rohrer <[email protected]>: > Thank you Jakob, your help is very precious as usual. > customShape="true" was the point I was looking for since too much time. By > the way, it's not documented in the wiki: > http://sumo.dlr.de/wiki/Networks/SUMO_Road_Networks# > Junctions_and_Right-of-Way > > If you give me a reason why the recommended approaches do not work for you > > I may be able to make yet another recommendation. > > > I'm working on the Webots simulator where we also have an OSM -> Webots > road network converter with constraints slightly different than netedit. > Typically, the OSM "turn:lanes" info is not covered by SUMO. Moreover, the > users are supposed to edit our Webots network before adding *optionally* > the SUMO "layer". In a first approach, we have done this in the other > direction (OSM -netconvert-> SUMO -> Webots network), but the data synch > was a total mess. The solution to export sumo.net.xml from our network > seems to offer a much better workflow for our users. > My solution is almost working, hopefully this week, with only ~300 simple > lines of Python, because I think that our network contains all the > information required by SUMO and more. > > I would be very interesting to have your comments on this project. > > > Sincerely, > > -- > Fabien Rohrer > Software Developer > Cyberbotics Sàrl <http://www.cyberbotics.com/> > PSE C - EPFL > 1015 Lausanne > Switzerland > -- > > 2017-06-05 17:43 GMT+02:00 Jakob Erdmann <[email protected]>: > > > Please excuse my fast typing. I strongly recommend **against** building > > .net.xml files with something other than netconvert. > > > > > > 2017-06-05 17:33 GMT+02:00 Jakob Erdmann <[email protected]>: > > > >> Hello, > >> I suspect you are exporting the data incorrectly and did not set the > >> <junction> attribute customShape="true". > >> I strongly recommend building .net.xml files with something other than > >> netconvert (http://sumo.dlr.de/wiki/FAQ#I_made_changes_to_the_.net.xml- > >> file_but_it_did_not_work_as_expected._Why.3F) > >> If you give me a reason why the recommended approaches do not work for > >> you I may be able to make yet another recommendation. > >> > >> regards, > >> Jakob > >> > >> > >> > >> 2017-06-05 9:24 GMT+02:00 Fabien Rohrer <[email protected] > >: > >> > >>> Hi, > >>> > >>> I'm writing a script exporting sumo.net.xml files, and I have issues > with > >>> the junction.shape field. I think that I'm exporting the data > correctly, > >>> but strangely, netedit seems to simply not taking this field into > account > >>> and recreates automatically its own shapes (which doesn't fit my > goals). > >>> > >>> Is there a way to get rid of this automatic computation and use the raw > >>> data inside sumo.net.xml? > >>> > >>> Sincerely, > >>> -- > >>> Fabien Rohrer > >>> Software Developer > >>> Cyberbotics Sàrl <http://www.cyberbotics.com/> > >>> PSE C - EPFL > >>> 1015 Lausanne > >>> Switzerland > >>> -- > >>> ------------------------------------------------------------ > >>> ------------------ > >>> Check out the vibrant tech community on one of the world's most > >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >>> _______________________________________________ > >>> sumo-user mailing list > >>> [email protected] > >>> https://lists.sourceforge.net/lists/listinfo/sumo-user > >>> > >> > >> > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > sumo-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sumo-user > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ sumo-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sumo-user
