Hello Jakob, thanks for the lightning fast reply and thanks for the hints. I'm sure once all the tickets you have created are implemented we'll have a powerful net editor!
Just some quick answers to your remarks. On 08/06/16 12:59, Jakob Erdmann wrote: > 1.8 if possible, the edge/lane endings should automatically coincide > with junction boundaries (the junction shape). In this way,complex > intersections would look cleaner and also the connections between lanes > would be more clearly visible and editable. > Probably the computation of junction shapes itself is challenging. > Still, even small junctions (with a single ingoing/outgoing edge) should > have a minimum extension, such that edges can be better added and > connections can be easily modified. > > This should already work. Also, if junction shapes are very small, a > circle is drawn instead to make it selectable. Since connections are > currently modified by clicking lanes there should be no problem. > (However this might become an issue when editing connection attributes > in the future). Maybe you can describe the current editing issue in more > detail? Well, yes, technically connections can be visualized and edited in the way it's implemented now. Still, I think it is useful if one can actually see all possible connections within a junction at once (for checking, deletion and maybe editing in the future). > 3.2 save plain xml does not work properly when changing the directory > for example from /mydir1/mynet.edg.xml to /mydir2/mynet.edg.xml. > The given directory is not properly applied to the path of the nod, > con and the other xml files. > > I could not reproduce this. All plain xml files are saved in the same > directory on my side. Can you describe the symptoms in more detail? > OK, I checked this: The described problem only occurs if I give an --output-prefix argument at command line. Without this, saving works, as expected. Best would be if netedit copied the command-line --output-prefix (if given) as default directory and filename in the "save plain xml" dialog. The current version seems to use the directory from netfile path as default directory, and does not suggest any filename. > > 3.3 create a roundabout in current network by selecting edges > > Not sure how your idea would work but it might be covered by this: > http://sumo.dlr.de/trac.wsgi/ticket/2303 OK, this ticket describes another good way of creating a roundabout: My idea was: - to manually edit a complete roundabout (by modifying/creating ordinary edges, possibly on a background map) - to create the actual roundabout by selecting those edges which constitute the roundabout. In any case, it would be good to actually see some indication of rounabouts. I'm sure it would brake dependencies of existing roundabouts if I modified its edges. So it would be good to have some control on what is going on with roundabouts. An alternative approach is of course to detect all roundabouts automatically once net editing is done. > 3.5 wizards (this would be feature for professional usage): Subnets > (from library) with configurable parameters (for example diameters or > number of lanes of a roundabout) Once configured, such subnets could > then be merged and connected to the rest of the net > > This might be nice but possible the subnet-feature along with a library > of subnetworks would provide most of that functionality already > (changing lane numbers is quite simple already and getting a > configurable-width roundabout is already a ticket). > However, it could be worthwhile to add wizards for accessing netgenerate > functionality from netedit: > http://sumo.dlr.de/trac.wsgi/ticket/2393 > OK, I agree that with the sub-networks feature, such a wizard could be emulated in a 2 Step process. Thanks again for considering these issues. Will keep on testing and suggesting... Best wishes, Joerg -- Joerg Schweizer University of Bologna DICAM - Transportation Group Viale Risorgimento, 2, I-40136 Bologna, Italy Tel: +39 051 209 3338, Fax: +39 051 209 3337 5x1000 AI GIOVANI RICERCATORI DELL'UNIVERSITÀ DI BOLOGNA Codice Fiscale: 80007010376 ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ sumo-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sumo-user
