Dear development team and SUMO users the last SUMO conference confirmed again that there is still a limited number of realistic SUMO traffic scenarios. An important step towards realistic traffic networks has been made by releasing netedit. A big thank you for this!
As netedit is in active development, I'd like to share some suggestions for improvements (but maybe you have more or better ideas). In my opinion, the most critical editing issue is the capability to model realistic complex intersections, as they can impact heavily the overall network performance. Below are some ideas on how to improve the editing of intersection topology, connectivity and traffic lights. Please bear in mind that I am using version 0.25, so some of the issues may already be addressed (or some features are already implemented and I just could not figure out how to use them). Anyway I hope I give some useful hints! Best wishes, Joerg ############ Improving topological and connection editing: 1.1 deleting of junctions should be less destructive: when deleting a junction, then the incoming and outgoing edges should not be deleted. Instead a dummy node (with a default junction type) should be created at the border of the junction which has been deleted. 1.2 deleting a single lane from edge (for example the possibility to remove the footpath is fundamental) 1.3 creating/deleting pedestrian crossings 1.4 creating a new node in an existing edge by splitting the edge. 1.5 The centers of junctions should be visible as a circle with a fixed radius (i.e. 20 pixel). Ideally the circle should not be filled, such that lane/edge endings remain visible. The desired effect would be this: when zooming into complex intersections, the size of the nodes remains constant, while edges and lanes become enlarge on the screen. In this way, it is possible to spot, select and edit nodes and short edges/lanes in complex intersections. 1.6 Cycle through ambiguous selection: during selection, when clicking on several overlapping objects, it should be able to cycle through this objects (for example with SHIFT-click as with xfig). For this purpose it would be helpful to highlight the current selected object for example by making it brighter (in this way objects preserves color and remain recognizable). 1.7 semi-transparent lanes/edges/junctions such that shapes are easier recognizable if covert. This would also help to match shapes to a background image 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. 1.9 Complex intersections as subnets : placement (translation and rotation) and merge a subnet into current net. Make subnet loadable from file or from a library. Note: A convenient way of merging a (sub)net would be useful not only to import intersections, but in general, for instance if several people edited different parts of the network and want to join them (I know it is possible to merge (but not place) different networks with netconvert). Improving TLS editing: 2.1 including multiple junction TLS : why not creating TLS for junctions which are already part of the selection (in blu)? or allow to add junctions to be controlled with CTRL - click while running the TLS tool 2.3 TLS link selection: before generating the phases of the TLS program, one should be able to select or deselect those connections of the controlled junction(s) which ought to be controlled (become a TLS link). Maybe to decide whether a certain turn is controlled by a TLS is in fact a connection property. 2.4 Edit TLS types 2.5 Edit min/max TLS green phases of dynamic traffic lights (while keeping total cycle length constant) Other (minor urgent) suggestions: 3.1 input/output file specification given at command line does not seem to work, except for net.xml as input. It would also be very useful, if the network is exported to a format/destination specified at the command line, once netedit is closed. 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. 3.3 create a roundabout in current network by selecting edges 3.4 aboard action on right click: when a specific tool is selected, it would be good to aboard on right click as in most CAD applications. The context menu is shown only if no action/tool is selected (actually the context menu should show all tool options for a specific object). 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. -- 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
