- 1 From 30.000 feet
- 2 Usage Description
- 3 Edit Modes
- 3.1 Common modes
- 3.2 Network specific modes
- 3.2.1 Create Edges
- 3.2.2 Edit connections
- 3.2.3 Prohibitions
- 3.2.4 Traffic Lights
- 3.2.5 Additionals
- 3.2.6 Crossings
- 3.2.7 TAZ (Traffic Analysis Zones)
- 3.2.8 Shapes
- 3.3 Demand specific modes
- 4 NETEDIT elements
- 4.1 Network Elements
- 4.2 Additional elements
- 4.2.1 Move and references
- 4.2.2 Parameters
- 4.2.3 Additional sets
- 4.2.4 Help dialogs
- 4.2.5 Additional types
- 18.104.22.168 Stopping Places
- 22.214.171.124 Detectors
- 126.96.36.199 Route Probe
- 188.8.131.52 Calibrator
- 184.108.40.206 Rerouter
- 220.127.116.11 Vaporizer
- 18.104.22.168 Variable Speed Signs
- 4.3 Route elements
- 5 Popup-Menu Functions
- 6 Usage Examples
- 6.1 Reducing the extent of the network
- 6.2 Specifying the complete geometry of an edge including endpoints
- 6.3 Setting connection attributes
- 6.4 Converting an intersection into a roundabout
- 6.5 Correcting road access permissions
- 6.6 Changing all traffic lights to right_on_red
- 6.7 Adapting Visualization Settings to help editing complicated intersections
- 6.8 Creating bidirectional railway tracks
- 7 Planned Features
From 30.000 feet
NETEDIT is a graphical network editor for SUMO.
- Purpose: create and modify SUMO networks
- System: portable (Linux/Windows is tested); opens a window
- Input (optional): road network definitions to import
- Output: A generated SUMO-road network; optionally also other outputs
- Programming Language: c++
NETEDIT is a visual network editor. It can be used to create networks from scratch and to modify all aspects of existing networks. With a powerful selection and highlighting interface it can also be used to debug network attributes. NETEDIT is built on top of NETCONVERT. As a general rule of thumb, anything NETCONVERT can do, NETEDIT can do as well. NETEDIT has unlimited undo/redo capabilities and thus allows editing mistakes to be quickly corrected. Editing commands are generally issued with a left-click (according to the current edit mode). The user interface closely follows that of SUMO-GUI. Additional keyboard hotkeys are documented in the Help menu.
NETEDIT is a GUI-Application and inputs are chosen via menus. The following input formats are supported:
- SUMO-net files
- NETCONVERT-configuration files
- SUMO-net files
- plain-xml files
|New Network||Ctrl + N||Create a new network|
|Open Network||Ctrl + O||Open an existing network|
|Open configuration||Ctrl + T||Open an existing SUMO configuration|
|Import foreign network||Ctrl + F||Import a foreign network|
|Reload||Ctrl + R||Reload network|
|Save network||Ctrl + S||Save network|
|Save network as||Ctrl + Shift + S||Save network in another file|
|Save plain XML||Ctrl + L||Save network as plain XML|
|Save joined junctions||Ctrl + J||Save joined junctions of network|
|Load additionals and shapes||Ctrl + A||Load a file with additionals|
|Save additionals and shapes||Ctrl + Shift + A||Save additionals in a file|
|Load demand elements||Ctrl + D||Load a file with shapes|
|Save demand elements||Ctrl + Shift + D||Save demand elements in a file|
|Load TLS Programs||Ctrl + K||Load a file with shapes|
|Save TLS Programs||Ctrl + Shift + K||Save Point Of Interest in a file|
|Close||Ctrl + W||Close network|
|Undo||Ctrl + Z||Undo the last change|
|Redo||Ctrl + Y||Redo the last change|
|Network||F3||Change to Network supermode (default )|
|Demand||F4||Change to Demand supermode(implies recomputing)|
|Common modes shortcuts||Key||Description|
|Delete||D||Change to mode "Delete"|
|Inspect||I||Change to mode "Inspect"|
|Select||S||Change to mode "Select"|
|Move||M||Change to mode "Move"|
|Network mode shortcuts||Key||Description|
|Create Edge||E||Change to mode "Create Edge"|
|Connection||C||Change to mode "Connection"|
|Prohibition||W||Change to mode "Prohibition"|
|Traffic light||T||Change to mode "Traffic light"|
|Additional||A||Change to mode "Additional"|
|Crossing||R||Change to mode "Crossing"|
|POI-Poly||P||Change to mode "POI-Poly"|
|Demand mode shortcuts||Key||Description|
|Create Route||R||Change to mode "Create Routes"|
|Create Vehicle||V||Change to mode "Create Vehicles"|
|Create Vehicle Type||T||Change to mode "Create Vehicle Type"|
|Create Stop||A||Change to mode "Create Stops"|
|Compute Junction||F5||Compute junctions of the network|
|Clean Junction||F6||Clean junctions of the network|
|Join selected Junctions||F7||Join selected junctions of the network|
|Options||F10||Open options dialog|
|Locate Junctions||Shift + j||Open dialog to locate junctions|
|Locate Edges||Shift + e||Open dialog to locate edges|
|Locate TLS||Shift + t||Open dialog to locate Traffic Lights|
|Online documentation||F1||Open the online documentation in the web browser|
|About||F2||Open the about dialog|
|Text edition shortcuts||Key||Description|
|Cut||Ctrl + X||Cut selected text of a text field|
|Copy||Ctrl + C||Copy selected text of a text field|
|Paste||Ctrl + V||Paste previously cut/copied text in a text field|
|Select all text||Ctrl + A||Select all text in a text field|
In addition to these hotkeys, all hotkeys for moving and zooming in SUMO-GUI are supported.
- <Button-Left>: Execute mode specific action
- <Button-Right>: Open context-menu
- <Button-Right-Drag>: Change zoom
- <Button-Left-Drag>: Move the view around (panning)
- in 'Move'-mode pointing at an edge: move or create geometry points
- in 'Move'-mode pointing at a junction: move the junction
- in 'Move'-mode pointing at a selected object: move all selected junctions and edges including geometry. If both junctions of an edge are selected, move the whole geometry. Otherwise, move only the geometry near the cursor
- in 'Create Edge'-mode: clear the currently selected source junction
- in 'Select'-mode: clear the current selection; cancel rectangle selection
- in 'Connect'-mode: deselect current lane and cancel all changes
- in 'Traffic Light'-mode: revert changes to current traffic light
- when editing a junction shape: abort editing the current junction shape
- <DELETE>: delete all currently selected items
- in 'Select'-mode: hold <SHIFT> and drag the mouse for rectangle selection
- in 'Select'-mode: <SHIFT>-left-click selects lanes instead of edges
- in 'Inspect'-mode: <SHIFT>-left-click inspects lanes instead of edges
- in 'Delete'-mode: <SHIFT>-left-click deletes lanes instead of edges
- in 'Create Edge'-mode, allow moving the view without defining junctions
- in 'Create Additional'-mode, allow moving the view without adding additionals
- in 'POI-Poly'-mode, allow moving the view without adding POIs
- in 'Inspect'-mode: confirm attribute changes
- in 'Connect'-mode: deselect current lane and save all changes
- in 'Traffic Light'-mode: save changes to current traffic light
- in 'TAZ'-mode: save changes to current traffic light
- when editing a junction shape: save the current junction shape
Processing Menu Options
- Compute Junctions (F5): recomputes the geometry and logic of all junctions. This is triggered automatically when entering modes which require this information (Connect, Traffic Lights).
- Clean Junctions (F6): removes all junctions that do not have any adjacent edges (These junctions are not included when saving the network. They are kept in the editor until cleaned for potential reuse).
- Join Selected Junctions (F7): joins the selected junctions into a single junction (See joining junctions).
- Options (F10): inspect and set all options. These are the same options that NETCONVERT accepts on the commandline or in a configuration.
It is also possible to load POIs and Polygons using the menu File->Load Shapes.
When activating the background grid via the visualization settings dialog or via the show grid option in Create Edge Mode, all clicks that create or move objects will snap to the nearest grid point. The resolution of the grid can be customized in the Background-Tab of the visualization settings dialog.
The main network elements that are used to represent a road network in SUMO are edges, lanes, junctions, connections, traffic lights. Additional infrastructure elements such as bus stops, detectors and variable speed signs are kept in separate files and loaded at the start of the simulation.
In SUMO the terms node and junction and intersection are used interchangeably (in NETEDIT the term junction is used throughout).
NETEDIT is controlled via various editing modes. This serves to reduce the number of clicks. For example, in Delete mode a click on any object deletes it. Edit modes are divided into two large sets (Supermodes), but with certain common modes. Supermode Network is specific to create and edit elements related to infrastructure, and Supermode Demand is specific to create and edit elements related to road traffic. Between both modes can be toggled either using the F3 and F4 keys or through the buttons located at the top of the window.
Inspect and modify attributes of edges, lanes, junctions, connections and additional network items (i.e. bus stops). Modifications have to be confirmed by hitting <Enter> (except for Boolean attributes). If the entered value is not appropriate for the modified attribute, the value will turn red to indicate the problem.
When inspecting an element that is selected along with multiple elements of the same type this mode behaves differently:
- Only non-unique attributes are listed (i.e. lane-width but not lane-ID)
- If the elements differ in their attributes, the whole range of occurring values is shown
- All selected elements of the same type are modified at the same time when setting a new value
When inspecting an edge, the extra buttons set Edge ... as Template and Copy ... into edge ... appear in the inspection frame. These can be used to set default attributes for #Create_Edges and to copy attributes between edges.
The following (non-unique) attributes are set/copied:
When copying attributes from one edge to another, lane-specific attributes will be copied as well.
The Delete mode is used to remove an element of your network. The following is possible:
- Delete junctions (and all adjoining edges)
- Delete edges
- Delete geometry points of an edge
- Delete a lane (when option selection edges is disabled)
- Delete connections (available, when show connections is enabled)
- Delete crossings
- Delete additionals
The delete frame own a list of elements that is filled automatically with the childs of the current element under the cursor. This list of child elements can be marked using Control + left-Click, and every child can be centered, inspected or removed individually with a right click over an element.
Additionally, the delete frame has a list of options to avoid undesirable deletes:
- Force deletion of additionals: Used to avoid undesirable deletion of additionals.
- Delete only geometry points: Used to remove only geometry points
Select network objects according to various criteria. Selected objects can be moved or deleted together. It is also possible to set attributes for all selected junctions (or all edges) at the same time using inspect mode.
Methods for selecting
- the selection status of objects is toggled by left-clicking. When the select edges check-box is unset, lanes, rather than edges will be selected/deselected.
- by rectangle-selection via shift+leftClick+drag (When the checkbox auto-select junctions is enabled, junctions of selected edges will be selected automatically)
- by matching object attributes (see below)
- by loading a saved selection
- by inverting an existing selection
The Modification Mode changes how a new group selection is applied to the existing selection. A new group selection can be:
- a loaded selection
- a rectangle selection
- a match-attribute-selection
The modification modes have the following functions
- add: both selections are added together (in set theory this would be called union)
- remove: all elements from the new selection are removed from the old selection. (in set-theory subtraction)
- keep: only elements common to both selections are kept. (in set theory intersection)
- replace: the existing selection is replaced by the new selection
The 'Match Attribute' controls allow to specify a set of objects by matching their attributes agains a given expression. When combining this set with the current selection, the Modificatiton Mode is also applied.
- Select an object type from the first input box
- Select an attribute from the second input box
- Enter a 'match expression' in the third input box and press <return>
- The empty expression matches all objects
- For numerical attributes the match expression must consist of a comparison operator ('<', '>', '=') and a number.
- the attribute matches if the comparison between its attribute and the given number by the given operator evaluates to 'true'
- For string attributes the match expression must consist of a comparison operator (, '=', '!', '^') and a string.
- (no operator) matches if string is a substring of that object'ts attribute.
- '=' matches if string is an exact match.
- '!' matches if string is not a substring.
- '^' matches if string is not an exact match.
- For attributes allow and disallow, the attribute value all is shown in #Inspect-mode when all classes are allowed (or disallowed). In this case an edge (or lane) will also be selected when using any vClass as match string (and edge with attribute disallow="all" will also match when filtering for disallow with string passenger). However, for technical reasons the match string =all will not match this edge (all is expanded to all private emergency passenger bus ... custom1 custom2).
Move junctions by dragging with the left mouse button. Dragging edges creates or moves geometry points. Dragging a junction on top of another junction joins them into a single junction.
By default, the junction shape is updated while moving. However the final shape after saving or activating full recomputation (F5) may be slightly different.
Moving Object Selections
- When selecting neighboring edges and dragging one of them, the neighboring edge will receive the same shape modifications
- When selecting an edge and its junctions and dragging any part of the selection, all parts including edge geometry will be moved in parallel
- When selecting an edge an one if its junctions:
- When dragging the junction, only the junction will move
- When dragging the edge, the edge will move locally and the junction will move in parallel
Network specific modes
This mode creates edges (lanes) and implicitly junctions. The edge attributes will be taken from the current #Edge_template. If no template is set, default options such as default.lanenumber will be used.
Creating a chain of edges
Creating two-way roads
Connections establish the possible directions that can be taken by a vehicle when it arrives at a junction.
Connection shapes depend of the Junction shapes. If a Junction shape is too small, the Junction takes a bubble as shape and the connections take a line as shape
As the rest of elements of netedit, connections can be inspected and modified using inspected mode. Note that the option show connections must be enabled. All parameters can be modified excepting From, To, fromLane and toLane.
The connection coloring is done as in SUMO-GUI with the exception of traffic-light connections which are brown in inspect-mode.
When a new junction is created, or their edges are modified, a set of new connections is automatically created. But NETEDIT allows also to customize the connections of a lane using the connection mode. When a source lane is selected in connection mode all outgoing lanes at the junction are colored according the the categories below:
|Legend||Meaning||Result of left-click|
|Source||The source lane for editing connections||Nothing|
|Target||The lane is already connected from the source lane.||Remove connection|
|Possible Target||The lane is not yet connected.||Add connection (with shift-click, set pass="true")|
|Target (pass)||The lane already connected and this connection is forcibly set to have priority (attribute pass="true")||Remove connection|
|Conflict||The lane is not yet connected. Adding a connection would be unusual for some reason (see below)||Print reason for conflict in status bar. (with ctrl-click add connection, with ctr+shift+click create connection with pass="true")|
To deselect the source edge or cancel the declared connections press <ESC> or click the Cancel-Button. To confirm the change press <ENTER> or click the OK-Button.
- double connection. Usually each lane only has one predecessor from the same edge. A counter-example would be a zipper node. May also be useful to model bus bays.
- Incompatible permissions: The source and target lanes have no allowed vehicle class in common
- Connection from sidewalk: Lane-to-lane connections for pedestrians are usually not defined by the user. Instead, the connectivity is modeled with pedestrian crossings.
This mode shows right of way-rules for any selected connection using a color code. To select another connection, cancel the current one with <ESC>.
Set junctions to be controlled or uncontrolled by a traffic light. Edit all aspects of static or actuated signal plans. Visualizes a signal phase by coloring the controlled lane-to-lane connections according to the signal state. Editing signal states can be accomplished in either of the following ways:
- right-clicking on any controlled lane and picking a new state (color).
- right-clicking on any of the incoming lanes to change all controlled connections from that edge
- If the lane is currently selected, all connections from selected lanes incoming to the traffic light will be changed as well
- If the edge is currently selected, all connections from selected edges incoming to the traffic light will be changed as well
- If the check-box apply change to all phases is activated, all phases of the current plan will be affected
You can also change the state by editing the phase table directly.
Add additional elements to the net. Additionals can be placed over a lane or in an empty place of the map. See #Additional_elements for more information. They are saved to a separate file (additional-file) and are loaded separately when running the simulation
Add pedestrian crossings for use with pedestrian simulation. Crossings are define relative a junction and edges at this junction. Their width can be customized and they can either be configured as priotized (zebra stripes) or unprioritzed (vehicles have right of way).
Crossings are added using the following steps:
- activate crossing mode (R)
- select a junction
- select edges that shall be crossed
- click Create Crossing
Internally, crossing works as edges, and therefore they appear in the net.xml as edges with different functions (crossing or walkingarea)
... previous element of net.xml ... <edge id=":0_c0" function="'''crossing'''" crossingEdges="3 7"> <lane id=":0_c0_0" index="0" allow="pedestrian" speed="1.00" length="13.10" width="3.00" shape="43.45,56.55 43.45,43.45"/> </edge> ... ... <edge id=":0_w1" function="walkingarea"> <lane id=":0_w1_0" index="0" allow="pedestrian" speed="1.00" length="13.10" width="3.00" shape="44.95,43.45 41.95,43.45 41.95,56.55 44.95,56.55"/> </edge> ... further elements of net.xml...
TAZ (Traffic Analysis Zones)
This mode allows creating and editing TAZ. (Shortcut Z). TAZs are composed of a closed polygon and a list of edges associated with certain weights for the inputs (Sources) and outputs (Sinks) (Similar to a Flow Network).
The creation of TAZs requiere two steps:
1) Creation of the polygon (similar to a polygon shape): Press Start drawing button (or alternatively press ENTER key) and click over the view with the mouse left button to add vertices. Press Shift + mouse left button to remove the last created vertex. To finish creating polygon, press Stop drawing button (or alternatively press ENTER key again). To abort the creation of the polygon press Abort drawing button (or alternatively press ESC key)
2) Definition of Edges and its inputs (sources) and outputs (sinks): A single click over a TAZ open the editing fields for TAZEdges in side menu. If the checkbox Membership is enabled (Toogle) box, a click over an edge will add it to the list of edges vinculated to the TAZ, (Or will be removed from the list if it was previously selected). Edge will will be added to the list with the input/output values given in the New source/New sink text fields. (note: A TAZ Edge always has a Source and a Sink).
Selecting and editing TAZ Edges: If checkbox membership is changed to "keep", then TAZ Edges can be selected individually and their values changed. A multiple selection using a rectangle is possible with shift + right. Statistics of selected TAZEdges can be observed in "Selection Statistics"
Saving and discarding changes: All changes in TAZEdges has to be saved using button "Save Changes", or in the same way can be also discarded using "cancel changes" button.
This mode allows the creation of Polygons and POIs (Points of Interest) through Polygon mode (hotkey ‘P’). These objects are used for visualization and can also be accessed via TraCI. In the polygon frame you can select the type of shape to edit (Polygons or Point Of Interest), and the corresponding parameters for each one.
One polygon is composed of mainly an exterior line called “shape”. In order to create a shape, you have to click on the button “start drawing” (or enter key), and click on the View above each of the points that will form the shape. To end the edition, you have to click on “stop drawing”. A right click on View will remove the last point created and the button “abort drawing” (or ESC key) will cancel the process of the creation of the shape. If you want to create a closed shape, you have to activate the option “closed shape” before starting to draw. The shape of the polygon can be opened or closed with the contextual menu or through the Inspector mode.
The points of a shape can be edited in the Move mode by clicking on the outline to create a new point or above an already existing one in order to modify its position. If a point moves to the same position of an adjacent point, they fuse together, and if the final point moves to the position of the initial point, the polygon gets closed. If the polygon has the option “block shape” activated, it won’t be editable, but only moved as a set.
Besides, the contextual menu offers several options, like the aforementioned open or close shape, simplify the shape, erase a vertex of the shape and establish a vertex of the shape as the initial one.
The Points Of Interest (POIs) are the locations in the map used to mark several elements relevant to the simulation, which don’t interact with the rest of elements (monuments, special buildings, etc.). As default, they are represented as a colored point, but can also be depicted using an image.
Demand specific modes
New route over the current infrastructure can be created using this mode. Routes are created clicking over consecutive edges (marked with different colors) and pressing "create route" button or Enter key. Route creation can be aborted using "abort creation" button or pressing ESC key. Note that Routes can be created between edges that aren't connected thought a connection.
Vehicles, flows and trips can be created using this mode. The term "vehicle" includes three different elements: Vehicles, flows (both placed over a Route) and Trips (placed over a "from" edge). Also every vehicle need to be a "Vehicle Type", therefore both parameters has to be selected in both list of left frame.
Vehicle Type mode
Vehicle types can be created and edited using Vehicle Type mode. A vehicle Type isn't a visual element that can be observed in the view, but is an "abstract" element that have a big influence in other elements (for example, vehicles). Every simulation has always three default vehicle types for Vehicles, Bikes and pedestrians. This default vehicle type can be edited but not deleted, and only is written in XML if one of their default value is modified. Due a Vehicle Type has a big number of parameters, only the most relevant parameters can be edited in left frame. To edit advanced parameters, use the Vehicle Type Dialog opened thought "Open attribute editor" button.
Stops used by all type of vehicles (Vehicles, Flows and Trips) can be created using StopFrame. Stops is an special type of demand elements, because it always depend of either a route or a vehicle (i.e. It can be writted in XML within the definition of either a route or a vehicle). Before creating a new Stop, their demand element parent has to be selected and the stop type (placed over a Lane or over a stopping Place). To create it, simply click over a lane or over a stopping place.
This elements comprise the road network and can be created and modified with NETEDIT.
Junctions, (also referred to as Nodes), represent intersections. A SUMO junction is equivalent to a Vertex in graph theory.
In the SUMO-context, edges represent roads or streets. Note that edges are unidirectional. It's equivalent to a edge in a graph theory.
Each SUMO edge is composed of a set of lanes (At least one).
Connections describe how incoming and outgoing edges of junctions are connected (for example to prohibit left-turns at some junctions).
A traffic light program defines the phases of a traffic light.
Additionals are elements which do not belong to the network, but may be used to influence the simulation or generate specific outputs. Additionals are defined in an additional-file and can be loaded in NETEDIT. Additionals are created in the Additionals editing mode (shortcut key: a). Once this mode is selected, the first step is to choose what kind of additional should be created in the comboBox "additional element". Once selected and if required, the parameters of the additional can be changed. Finally, with a click over a Lane/junction/edge (If the additional should be set over an element of the network), or over an empty area (if the item is independent of the network) the additional will be created.
Move and references
Additionals can be moved, but the freedom of movement depends of their relation with the network. Additionals that must be located over a lane can only move along the lane, and additionals that are located on a map can be moved in any direction. The movement also depends if the item is locked or not (symbolized by a lock icon on the item). The movement can be blocked during the creation of the element. The corresponding parameter can be changed within the inspector mode. Certain additionals have a length contingent to the length of the lane. To create a bus stop by choosing a reference point, which marks the initial position of this additional element, three types of references for the length can be selected. E.g. for a bus stop with the length 20 in the point 50 of the lane it will be the following:
- Reference left will create a new bus stop with startPos = 30 and endPos = 50.
- Reference right will create a new bus stop with startPos = 50 and endPos = 70.
- Reference center will create a new bus stop with startPos = 40 and endPos = 60.
Some additional types cannot be moved, therefore show a different icon:
There are two types of parameters for each additional: User-defined-parameters and NETEDIT-parameters. The first mentioned parameters can be of type int, float, bool string, or list and each has a default value. In the case of type list the user can add or remove values using the add or remove row buttons. In the case of the characteristic parameters of NETEDIT, this is the option to block the movement of an element, and in the case of the elements have a length, the user is allowed to change the length and reference.
Additional sets are additionals that comprise or contain another additionals (called childs) (For example, detectorE3 contains a list of detEntry and detExit). Additional sets are inserted in the same way as an Additional, but the insertion of an additional child is different. Before the insertion of an additional child in the map, the ID of the additionalSet parent must be selected in the list of IDs placed on the left frame. In this list the IDs of the additional sets only appear when they can be parents of the additional child (Referring to the given example: if the user wants to insert a detEntry, than only IDs of detectorE3 will appear in the list on the left frame). Additional sets and their childs are graphically connected by a yellow line.
With the help buttons placed in the left frame, users can obtain information about additional and editor parameters (Full name, type and description).
This section describes the different types of additional objects which are supported
Stopping places are sections of lanes, in which vehicles can stop during a certain time defined by the user.
Bus stops are positions of a lane in which vehicles ("busses") stop for a pre-given time. Every Bus stop has an unique ID assigned automatically by NETEDIT, a length and a list of bus lines defined by the user.
Charging stations define a surface over a lane in which the vehicles equipped with a battery are charged. Charging stations own an unique-ID generated by NETEDIT, a length, a charging power defined in W, a charging efficiency, a switch for enable or disable charge in transit, and a charge delay.
Detectors are additionals wich save information about vehicles that passed over a certain position on the lane.
Induction Loops Detectors (E1)
A E1 detector owns a ID parameter generated by NETEDIT, a position at a certain lane, a freq attribute which describes the period over which collected values shall be aggregated, a list of VTypes that will be detected, and a file attribute which tells the simulation to which file the detector shall write his results to.
Lane Area Detectors (E2)
Most of the E2 detectors' attributes have the same meaning as for E1 induction loops, including automatic ID and position at a certain lane. As a real detector has a certain length, "length" must be supplied as a further parameter. It may be a negative number which let the detector be extended, upstream to the given start position. The optional parameter "cont" lets the detector continue over the current lane onto this lane's predecessors when the detector's length plus his position is larger than the place available on the lane.
Multi-Entry Multi-Exit Detectors (E3)
Childs of an AdditionalSet Multi-Entry Multi-Exit Detectors E3. These additionals have only the attributes ID of a lane in which it is placed and positioned over a lane.
Instant Induction Loops Detectors (E1Instant)
A E1 detector owns a ID parameter generated by NETEDIT, a position at a certain lane, a freq attribute which describes the period over which collected values shall be aggregated, a list of VTypes that will be detected and a file attribute which tells the simulation to which file the detector shall write his results to.
RouteProbe detectors are meant to determine the route distribution for all vehicles that passed an edge in a given interval. Their real-world equivalent would be a police stop with questionnaire or a look into the database of navigation providers such as TomTom.
A calibrator generates a flow of vehicles during a certain time, and allows dynamic adaption of traffic flows and speeds. A calibrator can be used to modify a simulation scenario based on induction loop measurements. It will remove vehicles in excess of the specified flow and will insert new vehicles if the normal traffic demand of the simulation does not reach the specified number of vehsPerHour. Furthermore, the defined edge speed will be adjusted to the specified speed similar of the operation of a variable speed sign. Calibrators will also remove vehicles if the traffic on their lane is jammend beyond the specified flow and speed. This ensures that invalid jams do not grow upstream past a calibrator. A double click over the calibrator icon opens the values editor.
A rerouter changes the route of a vehicle as soon as the vehicle moves onto a specified edge.
A double click over the rerouter icon opens the values editor. Rerouter's values are divided in intervals, and every interval contains a list of closing streets, closing lanes, assignations of new destinations and assignations of new routes:
vaporizers remove all vehicles as soon as they move onto a specified edge.
Variable Speed Signs
A Variable Speed Signal modifies the speed of a set of lanes during a certain time defined by user. A double click over the Variable Speed Signal icon opens the values editor.
Edge and Lane
- Split edge here: Split an edge into two differentes edges connected with a junction.
- Split edge in both directions here: Is similar to Split edge here, but generate splitted edges in both directions.
- Reverse edge: Reverse the direction of an edge. If the ID of the start and end junctions of edge are respectively A and B, afer this operation start and end junction will be B and A.
- Add reverse direction: If don't exist, add a revere edge between two junctions
- Set geometry endpoint here: Create an geometry end point. It's usefull to mark the start and the end of an road
- Restore geometry endpoint: Restore a geometry endpoint to a normal edge
- Straighten edge: Allow to restore the visual shape of an edge
- Duplicate lane: duplicate a lane of an edge
Restricted lanes for particulars vehicle class (VClass) can be easily added in inspect mode. Currently netedit supports sidewalks (where only vehicles with VClass="pedestrian" are allowed), bike lanes (where only vehicles with VClass="bike" are allowed), and bus lanes (where only vehicle with VClass="bus" are allowed). Note that only one type of restricted lane is allowed in every edge (For example, an edge can own two restricted lane, one for buses and another for bikes, but not two or more different restricted lanes for buses.
There are two ways to add a restricted lane, either transforming a existent lane or adding a new restricted lane
A restricted lane can be transformed in a normal lane with the option revert transformation, or can be removed with the option Remove restricted lane
- Set custom shape: Allows drawing a custom junction shape via a #Modifiable Poly (see below). The junction shape determines where the incoming edges end and the outgoing edges start. If the automatic generation of shapes does not give a satisfying result it often helps to draw a custom shape instead. The shape is a polygon defined by a sequence of (x,y,z) geometry points.
- Set custom shape: Allows drawing a custom connection shape via a #Modifiable Poly (see below). The shape is confirmed with <Enter>.
- Set custom shape: Allows drawing a custom crossing shape via a #Modifiable Poly (see below). The shape is confirmed with <Enter>.
- Set custom shape: Apply this shape to the current junction
- Discard custom shape: Abort editing the current junction shape
- Simplify shape: Replace the current shape by a rectangle
- Remove geometry point: Remove the closest geometry point from the shape
- The new shape is confirmed with the <Enter> key and discarded with <Esc>.
The green polygon outline allows adding and moving geometry points by left-clicking anywhere on the outline and dragging.
- inner/lane position: Additionals that are placed over an edge or lane haven two different mouse position. Inner position is the position of the mouse with respect to the length of the additional, and lane position if the position of the mouse with respect to the length of lane
- Position in view and number of childs: shows the number of childs that own an Additionals, and their position in view
- show parameters: show all parameters of additional.
Reducing the extent of the network
- switch to selection mode
- enable the auto-select junctions checkbox in the top menu bar
- select the portion of the network you wish to keep (i.e. by holding <SHIFT> and performing a rectangle-selection)
- invert the selection with the Invert button
- delete the inverted selection using the <DELETE> key
Adapting additional objects to a reduced network
- load the additional file when cutting and then save the reduced additional file or
- open the reduced network and load the original additional file. All objects outside the reduced network will be discarded with a warning.
Specifying the complete geometry of an edge including endpoints
By default, the geometry of an edge starts with the position of the source junction and ends at the position of the destination junction. However, this sometimes leads to undesired junction shapes when dealing with roads that have a large green median strip or when modeling edges that meet at a sharp angle such as highway ramps. Also, when edges in opposite directions have unequal number of lanes (i.e. due to added left-turn lanes) and the road shapes do not line up. The solution is to define an edge geometry with custom endpoints. Below are three alternative methods of accomplishing this.
Using 'Set geometry endpoint'
- switch to move mode
- shift-click near the start or the end of the edge to create/remove a custom geometry endpoint (marked with 'S' at the start and 'E' and the end.
- once create these special geometry points can be moved around like normal geometry points
Afterwards, you will have to recompute the junction shape to see how it looks (F5). If you want to modify the edge and it's reverse edge at once this works almost the same way:
- switch to select mode
- select both edges
- switch to move mode
- create/move geometry points for that edge
- create new geometry points where the endpoints of the edge should be
- switch to select mode
- deselect both edges
- right-click on the new endpoints and select Set geometry endpoint here twice (once for each edge)
Entering the Position manually
- switch to inspect mode
- click on the edge that shall be modified
- enter new values for attributes shapeStart or shapeEnd
Using 'Join Selected Junctions'
- create new junctions where the endpoints of the edge should be
- Either split an existing edge (right-click and select Split edge here)
- Or create a new edge with new junctions in create-edge mode
- switch to select mode
- select the original junction and the new junction near it
- Menu Processing->Join Selected Junctions (F7)
This will create a single joined junction but keep the endpoints at the original junction positions.
Setting connection attributes
- after opening the network press F5 to compute connection objects
- in inspect-mode enable the Show Connections checkbox in the menu bar
- click on a connection to inspect it and edit its attributes
Converting an intersection into a roundabout
- For each of the 'legs' of the intersection do a right click and select 'split edges in both directions' at some distance from the intersection (this will be the radius of the roundabout)
- Delete the central intersection
- Connect the new intersections with one-way roads going in a circle
- Tweak the geometry of the roundabout by creating additional geometry points in move mode to make it more rounded
- Ensure correct right of way by either
- Assigning a higher priority value to the roundabout roads (compared to the adjoining roads)
- or seting the option roundabouts.guess in the Processing menu
Assuming you have a regular intersection
- Visual example
Correcting road access permissions
In this example we wish to modify a multi-modal road network (i.e. imported from OpenStreetMap) in the following way: All dedicated bus lanes should allow bicycle access.
- in select-mode, use the Match Attribute panel to select all Lanes with attribute allow that match the string =bus (the '=' forces exact matches). All dedicated bus lanes are now selected
- in inspect-mode, click on one of the selected lanes and modify the allow attribute from bus to bus bicycle
Changing all traffic lights to right_on_red
- in select-mode, use the Match Attribute panel to select all Junctions with attribute type that match the string traffic_light
- in inspect-mode, click on one of the selected junctions and set the type attribute to right_on_red
Adapting Visualization Settings to help editing complicated intersections
Editing complex intersection clusters with many short edges can be difficult with the default visualisation settings. The following settings may help
- Junction settings
- lower value for exaggerate by (junction shapes drawn with reduced size)
- deactivate draw junction shapes (alternatively to reduced size, do not draw junction shapes at all)
- color by selection
- lower value for exaggerate by (draw thin edges)
- deactivate show right of way rules (to avoid hiding short edges)
- color by selection
When setting coloring to by selection it may also help to modify transparency for selected or unselected edges.
Creating bidirectional railway tracks
Make an existing track bidirectional
Using visualization options or attribute selection you can check whether an existing railway track can be used in both directions.
To make a unidirectional track usable in both directions,
- set the edge attribute spreadType to the value center (in many cases this value is already set as it is the default value when importing tracks).
- right-click the edge and select edge operations->add reverse direction for edge
Creating bidirectional tracks from scratch
- use #Create_Edges to create an edge
- use #Inspect to set the edge attribute allow to rail (or a combination of one or more railway vehicle classes)
- set edge attribute spreadType to center
- set the new edge as #Edge_template
- make the edge bidirectional as explained above in #Make_an_existing_track_bidirectional
- in #Create_Edges, set the checkbox to Two-way and optionally to Chain
- continue to created edges. Each click will create bidirectional track
- Support for editing traffic demand (the application will have a big toogle switch between controls for editing the network and editing the demand)
- Support for editing features already supported by NETCONVERT
- Integration of NETGENERATE
- Adding / merging of sub-networks to the existing network