sumo - Recent changes [en]

OpenStreetMapNetworkImport

Dkrajzew — Fri, 20 Nov 2009 14:54:55 GMT

← Older revision		Revision as of 14:54, 20 November 2009
Line 261:		Line 261:
	For removing all edges which can not be used by road vehicles the call must be extended by:		For removing all edges which can not be used by road vehicles the call must be extended by:
	--remove-edges.by-vclass rail_slow,rail_fast,bicycle,pedestrian		--remove-edges.by-vclass rail_slow,rail_fast,bicycle,pedestrian
		+
		+
		+	==Importing large Road Networks==
		+	The OpenStreetMap-API limit the size of a area to extract. The help script "osmGet.py" located within {{SUMO}}/tools/import/osm allows to extract a larger area by splitting the requests. The call is:
		+	osmGet.py <PREFIX> <BOUNDING_BOX> <TILES_NUMBER>
		+	The bounding box must be given as <LAT_MIN>,<LONG_MIN>,<LAT_MAX>,<LONG_MAX>. The script will extract n tiles with n=<TILES_NUMBER>, named "<PREFIX><INDEX>_<TILES_NUMBER>.osm.xml".
		+	{{Note\|"wget" must be installed and located in the execution path.}}
		+
		+

	==Further Notes==		==Further Notes==

Advanced Traffic Lights Simulation

Dkrajzew — Fri, 20 Nov 2009 13:51:03 GMT

← Older revision		Revision as of 13:51, 20 November 2009
(One intermediate revision not shown)
Line 1:		Line 1:
-	~~=Advanced Traffic Lights Simulation=~~
	Normally, [[NETCONVERT]] and [[NETGEN]] generate traffic lights and programs for junctions during the computation of the networks. Still, these computed programs differ quite often from those found in reality. To feed the simulation with real traffic light programs, it is possible to load additional programs. Also, [[SUMO]]/[[GUISIM]] allow to load definition which describe when and how a set of traffic lights can switch from one program to another. Both will be discussed in the following subchapters.		Normally, [[NETCONVERT]] and [[NETGEN]] generate traffic lights and programs for junctions during the computation of the networks. Still, these computed programs differ quite often from those found in reality. To feed the simulation with real traffic light programs, it is possible to load additional programs. Also, [[SUMO]]/[[GUISIM]] allow to load definition which describe when and how a set of traffic lights can switch from one program to another. Both will be discussed in the following subchapters.

-	==Adding new TLS-Programs==	+	=Adding new TLS-Programs=
	A definition of a traffic light program looks like this:		A definition of a traffic light program looks like this:
	<pre class="xml">		<pre class="xml">
Line 91:		Line 90:
	After having defined a tls program as above, it can be loaded as an addtional file; of course, a single additional file may contain several programs. It is possible to load several programs for a single tls into the simulation. The program loaded as last will be used (unless not defined differently using a WAUT description). All subkeys of the additional programs must differ if they describe the same tls.		After having defined a tls program as above, it can be loaded as an addtional file; of course, a single additional file may contain several programs. It is possible to load several programs for a single tls into the simulation. The program loaded as last will be used (unless not defined differently using a WAUT description). All subkeys of the additional programs must differ if they describe the same tls.

-	===Tools for TLS programs import===	+
		+	==Tools for TLS programs import==
		+	Description from real-world traffic light systems do not arrive us in form of SUMO-traffic light descriptions normally. For an easier import than editing them by hand, a tool named "tls_csv2SUMO.py" exists which parses a csv-file which describes the program and builds an according SUMO-traffic light description. The tool can be found in {{SUMO}}/tools/tls. This tool requires the program definition and the SUMO-network it shall be converted to:
		+	tls_csv2SUMO.py <TLS_CSV> <NET>
		+	It prints the generated TLS definition on stdout (you can pipe it to a file).
		+
		+	The format of the CSV description is as following. At first, three header lines must be given, which name the tls, the program's subkey, and the offset at which the program shall start in seconds - normally 0:
		+	<pre class="csv">
		+	key;<KEY>
		+	subkey;<SUBKEY>
		+	offset;<OFFSET>
		+	</pre>
		+
		+	Then, it is defined which signal (number) in the program is responsible for which link. The link may be described either using the incoming edge only, or the incoming lane only, or also incorporating the outgoing edge/lane. This means the following lines are all valid:
		+	<pre class="csv">
		+	link;<LINK_NUMBER>;<FROM_EDGE>;;0
		+	link;<LINK_NUMBER>;<FROM_LANE>;;0
		+	link;<LINK_NUMBER>;<FROM_EDGE>;<TO_EDGE>;0
		+	link;<LINK_NUMBER>;<FROM_EDGE>;<TO_LANE>;0
		+	link;<LINK_NUMBER>;<FROM_LANE>;<TO_EDGE>;0
		+	link;<LINK_NUMBER>;<FROM_LANE>;<TO_LANE>;0
		+	</pre>
		+	It is also possible to assign more than one link to a single signal.
		+
		+	Then, the signals' states are given:
		+	<pre class="csv">
		+	<LINK_NUMBER>;<STATES>
		+	</pre>
		+	The states are encoded using the signal colors (please note that only lower-case letters are used, see below) described above, separated by ';'. An example signal phase definition (for signal 1) could be:
		+	<pre class="csv">
		+	1;g;g;g;g;y;r;r;r;r;r
		+	</pre>
		+	Please not that the number of states must be the same for all defined links.
		+
		+	Now, we only have to define the phase times:
		+	<pre class="csv">
		+	time;<TIMES>
		+	</pre>
		+	The times are given in seconds, again separated using ';'. An example could be:
		+	<pre class="csv">
		+	time;18;33;3;6;3;3;9;15;90
		+	</pre>
		+
		+	A complete CSV-description could look like:
		+	<pre class="csv">
		+	key;102
		+	subkey;utopia
		+	offset;0
		+	link;1;4643;;0
		+	link;1;3078;;0
		+	link;2;3074;;0
		+	link;2;-6494;;0
		+	1;g;g;y;r;r;r;r;r
		+	2;r;r;r;r;g;g;y;r
		+	3;r;r;r;r;g;y;y;r
		+	4;g;y;y;r;r;r;r;r
		+	min;21;3;3;2;20;9;3;2
		+	time;45;3;3;2;36;9;3;2
		+	max;78;3;3;2;62;9;3;2
		+	</pre>
		+



-	==Defining the switch Times and Procedure==	+	=Defining the switch Times and Procedure=
	In the reality, a tls often uses different programs during a day and maybe also for weekdays and for the weekend days. It is possible to load a definition of switch times between the programs using a WAUT (short for "Wochenschaltautomatik" ~ weekly switch automatism).		In the reality, a tls often uses different programs during a day and maybe also for weekdays and for the weekend days. It is possible to load a definition of switch times between the programs using a WAUT (short for "Wochenschaltautomatik" ~ weekly switch automatism).

SUMO User Documentation

Dkrajzew — Fri, 20 Nov 2009 12:47:12 GMT

← Older revision		Revision as of 12:47, 20 November 2009
Line 66:		Line 66:
	* [[SUMO_Files\|Using files in a correct way]]		* [[SUMO_Files\|Using files in a correct way]]
	* [[SUMO_AdditionalStructures\|Traffic Management and Other Structures]]		* [[SUMO_AdditionalStructures\|Traffic Management and Other Structures]]
-	** [[~~SUMO_TrafficLights\|~~Traffic ~~lights~~]]	+	** [[Advanced Traffic Lights Simulation]]
	** [[SUMO_PublicTransport\|Public transport]]		** [[SUMO_PublicTransport\|Public transport]]
	** [[SUMO_VariableSpeedSigns\|Variable speed signs]]		** [[SUMO_VariableSpeedSigns\|Variable speed signs]]

SUMO TrafficLights

Dkrajzew — Fri, 20 Nov 2009 12:46:49 GMT

moved [[SUMO TrafficLights]] to [[Advanced Traffic Lights Simulation]]

New page

SUMO TrafficLights

Dkrajzew — Fri, 20 Nov 2009 12:45:03 GMT

← Older revision		Revision as of 12:45, 20 November 2009
Line 91:		Line 91:
	After having defined a tls program as above, it can be loaded as an addtional file; of course, a single additional file may contain several programs. It is possible to load several programs for a single tls into the simulation. The program loaded as last will be used (unless not defined differently using a WAUT description). All subkeys of the additional programs must differ if they describe the same tls.		After having defined a tls program as above, it can be loaded as an addtional file; of course, a single additional file may contain several programs. It is possible to load several programs for a single tls into the simulation. The program loaded as last will be used (unless not defined differently using a WAUT description). All subkeys of the additional programs must differ if they describe the same tls.

-	===~~Earlier definitions~~===	+	===Tools for TLS programs import===
-	Please note that the definition has recently changed. Up to (including) version 0.10.3, a traffic light phase was defined as following: <span class="inlxml"><phase duration="4" phase="0000000000000000" brake="1111111111111111" yellow="1100000011000000"/></span>.	+

-	Also, some of a tls' parameters - <span class="inlxml">id</span>, <span class="inlxml">programID</span>, and <span class="inlxml">offset</span> - were earlier defined in character sections of sub-elements which were named <span class="inlxml">key</span>, <span class="inlxml">subkey</span>, and <span class="inlxml">offset</span>, respectively. You may find an example of an old description below.
-
-	~~<pre class="xml">~~
-	~~<tl-logic type="static">~~
-	~~<key>0</key>~~
-	~~<subkey>my_program</subkey>~~
-	~~<phaseno>8</phaseno>~~
-	~~<offset>0</offset>~~
-	~~<phase .../>~~
-	~~... further phases ...~~
-	~~</tl-logic>~~
-	~~</pre>~~

Glossary

Dkrajzew — Fri, 20 Nov 2009 12:37:01 GMT

← Older revision		Revision as of 12:37, 20 November 2009
(One intermediate revision not shown)
Line 54:		Line 54:

	==T==		==T==
		+	;TLS:traffic lights system
	;trip :A reduced information about a vehicle's movement; contains only the departure time, the begin, and the end edge. Must be transformed into a route using a router for being used within the simulation		;trip :A reduced information about a vehicle's movement; contains only the departure time, the begin, and the end edge. Must be transformed into a route using a router for being used within the simulation
	;trip-table (trip list) :A file containing several trips		;trip-table (trip list) :A file containing several trips
-	~~;type(s)-file :A XML-file describing types of streets, see [[NetworkImportXML#Type_Descriptions\|type descriptions for importing networks defined as XML]]~~
	;TS :Institute of Transportation Systems at the German Aerospace Center (DLR)		;TS :Institute of Transportation Systems at the German Aerospace Center (DLR)
	;TS-BS :TS Standort Braunschweig		;TS-BS :TS Standort Braunschweig
	;TS-BA :TS Standort Berlin-Adlershof		;TS-BA :TS Standort Berlin-Adlershof
		+	;type(s)-file :A XML-file describing types of streets, see [[NetworkImportXML#Type_Descriptions\|type descriptions for importing networks defined as XML]]

	==X==		==X==
	;XML :"eXtensible Markup Language is a universal format for structured documents and data" as the w3c says. Further information may be found at http://www.w3c.org/XML/. Most of the data read and written by SUMO is stored as XML		;XML :"eXtensible Markup Language is a universal format for structured documents and data" as the w3c says. Further information may be found at http://www.w3c.org/XML/. Most of the data read and written by SUMO is stored as XML

SUMO TrafficLights

Dkrajzew — Fri, 20 Nov 2009 12:34:34 GMT

Defining the switch Times and Procedure:

← Older revision		Revision as of 12:34, 20 November 2009
Line 1:		Line 1:
	=Advanced Traffic Lights Simulation=		=Advanced Traffic Lights Simulation=
-	Normally, [[NETCONVERT]] and [[NETGEN]] generate traffic lights and programs for junctions during the computation of the networks. Still, these computed programs differ quite often from those found in reality. To feed the simulation with traffic light programs ~~from the reality~~, it is possible to load additional programs. Also, [[SUMO]] ~~(and~~ [[GUISIM]]~~) allows~~ to load a definition which ~~describes~~ when and how a set of traffic lights can switch from one program to another. Both will be discussed in the following subchapters.	+	Normally, [[NETCONVERT]] and [[NETGEN]] generate traffic lights and programs for junctions during the computation of the networks. Still, these computed programs differ quite often from those found in reality. To feed the simulation with real traffic light programs, it is possible to load additional programs. Also, [[SUMO]]/[[GUISIM]] allow to load definition which describe when and how a set of traffic lights can switch from one program to another. Both will be discussed in the following subchapters.

	==Adding new TLS-Programs==		==Adding new TLS-Programs==
Line 111:		Line 111:
	In the reality, a tls often uses different programs during a day and maybe also for weekdays and for the weekend days. It is possible to load a definition of switch times between the programs using a WAUT (short for "Wochenschaltautomatik" ~ weekly switch automatism).		In the reality, a tls often uses different programs during a day and maybe also for weekdays and for the weekend days. It is possible to load a definition of switch times between the programs using a WAUT (short for "Wochenschaltautomatik" ~ weekly switch automatism).

-	Given a tls which knows four programs - two for weekdays and two for weekend days where from 22.00 till 6.00 the night plan shall be used and from 6.00 till 22.00 the day plan, and already defined programs, named "weekday_night", "weekday_day", "weekend_night", "weekend_day". To describe the switch process, we have to describe the switch at first, assuming our simulation runs from monday 0.00 (second 0) to monday 0.00 (second 604800):	+	Given a tls which knows four programs - two for weekdays and two for weekend days where from 22:00 till 6:00 the night plan shall be used and from 6:00 till 22:00 the day plan, and already defined programs, named "weekday_night", "weekday_day", "weekend_night", "weekend_day". To describe the switch process, we have to describe the switch at first, assuming our simulation runs from monday 0.00 (second 0) to monday 0.00 (second 604800):
	<pre class="xml">		<pre class="xml">
	<WAUT refTime="0" id="myWAUT" startProg="weekday_night">		<WAUT refTime="0" id="myWAUT" startProg="weekday_night">
Line 202:		Line 202:
	\|}		\|}

-	It is possible to assign several tls to a single WAUT. It is also possible ~~toassign~~ several WAUTs to a single junction in theory, but this is not done in reality.	+	It is possible to assign several tls to a single WAUT. It is also possible to assign several WAUTs to a single junction in theory, but this is not done in reality.

Main Page

Loulloudes n — Thu, 19 Nov 2009 15:02:13 GMT

← Older revision		Revision as of 15:02, 19 November 2009
(2 intermediate revisions not shown)
Line 52:		Line 52:
	* [[Cadyts]]		* [[Cadyts]]
	: a tool by Gunnar Flötteröd which adapts the simulate flows to the real flows in a known net		: a tool by Gunnar Flötteröd which adapts the simulate flows to the real flows in a known net
		+	* [http://sourceforge.net/projects/trafficmodeler/ Traffic Modeller]
		+	: a GUI system for graphically defining high - level traffic for the SUMO.
	</div>		</div>

ChangeLog

Dkrajzew — Thu, 19 Nov 2009 12:08:38 GMT

← Older revision		Revision as of 12:08, 19 November 2009
(One intermediate revision not shown)
Line 10:		Line 10:

	* GUISIM		* GUISIM
-	** implemented [http://sourceforge.net/tracker/?func=detail&aid=1641989&group_id=45607&atid=443424 request 1641989: No view reset on reload]).	+	** implemented [http://sourceforge.net/tracker/?func=detail&aid=1641989&group_id=45607&atid=443424 request 1641989: No view reset on reload].
		+	** the number of colors used for range visualization is now variable
		+	** debugged problems with not shown junction names

	* NETCONVERT		* NETCONVERT

TraCI/Interfacing TraCI from Python

Dkrajzew — Thu, 19 Nov 2009 12:05:19 GMT

← Older revision		Revision as of 12:05, 19 November 2009
Line 1:		Line 1:
	=traciControl.py=		=traciControl.py=
	==Coverage==		==Coverage==
-	~~{{Caution\|Note that the coverage refers to the current SVN version; earlier versions may be incomplete.}}~~
-
-	~~[[Category:RevisitAfterNextRelease]]~~

	===Traffic Lights Value Retrieval / Changing Traffic Lights States===		===Traffic Lights Value Retrieval / Changing Traffic Lights States===

ChangeLog

Dkrajzew — Thu, 19 Nov 2009 12:04:49 GMT

SVN:

← Older revision		Revision as of 12:04, 19 November 2009
Line 29:		Line 29:
	** added further [[TraCI/Induction_Loop_Value_Retrieval\|induction loops variable retrieval options]]		** added further [[TraCI/Induction_Loop_Value_Retrieval\|induction loops variable retrieval options]]
	** added further [[TraCI/Multi-Entry/Multi-Exit_Detectors_Value_Retrieval\|multi-entry/multi-exit detectors variable retrieval options]]		** added further [[TraCI/Multi-Entry/Multi-Exit_Detectors_Value_Retrieval\|multi-entry/multi-exit detectors variable retrieval options]]
		+	** added further [[TraCI/Junction_Value_Retrieval\|junction variable retrieval options]]
		+	** added further [[TraCI/Vehicle_Value_Retrieval\|vehicle variable retrieval options]]
		+	** added further possibilities to [[TraCI/Change_Vehicle_State\|change vehicle values]]
		+	** added possibilities to [[TraCI/Edge_Value_Retrieval\|retrieve edge variables]] and [[TraCI/Change_Edge_State\|change edge values]]
		+	** added possibilities to [[TraCI/Lane_Value_Retrieval\|retrieve lane variables]] and [[TraCI/Change_Lane_State\|change lane values]]
		+	** added possibilities to [[TraCI/Change_PoI_State\|change PoI values]] and to [[TraCI/Change_Polygon_State\|change polygon values]]
	** added the possibility assign a vehicle a new route via TraCI		** added the possibility assign a vehicle a new route via TraCI

TraCI/Vehicle Value Retrieval

Dkrajzew — Thu, 19 Nov 2009 12:04:46 GMT

← Older revision		Revision as of 12:04, 19 November 2009
(One intermediate revision not shown)
Line 98:		Line 98:
	\|}		\|}

-	~~{{Caution\|Note that emission/consumption/noise retrieval methods (0x60-0x66) are currently only available within the SVN.}}~~
-
-	~~[[Category:RevisitAfterNextRelease]]~~

	=== Response 0xb4: Vehicle Variable ===		=== Response 0xb4: Vehicle Variable ===
Line 140:		Line 137:
	\|}		\|}

-
-	~~{{Caution\|Note that "edge travel time information" (0x58), and "edge effort information" (0x59) are currently only available within the SVN.}}~~
-
-	~~[[Category:RevisitAfterNextRelease]]~~

	The request message contents are as following:		The request message contents are as following:

TraCI/Junction Value Retrieval

Dkrajzew — Thu, 19 Nov 2009 12:03:38 GMT

← Older revision		Revision as of 12:03, 19 November 2009
Line 29:		Line 29:
	\|-		\|-
	\|}		\|}
-
-	~~{{Caution\|Note that retrieval of id list is currently only available within the SVN.}}~~
-
-	~~[[Category:RevisitAfterNextRelease]]~~

TraCI/Change Vehicle State

Dkrajzew — Thu, 19 Nov 2009 12:02:27 GMT

← Older revision		Revision as of 12:02, 19 November 2009
Line 70:		Line 70:
	(1): The first occurence of the edge is currently at is searched within the new route; the vehicle continues the route from this point in the route from. If the edge the vehicle is currently does not exist within the new route, an error is generated.		(1): The first occurence of the edge is currently at is searched within the new route; the vehicle continues the route from this point in the route from. If the edge the vehicle is currently does not exist within the new route, an error is generated.

-
-	{{Caution\|Note that "change route by id" (0x54), "change route" (0x57), "change edge travel time information" (0x58), and "change edge effort information" (0x59) are currently only available within the SVN.}}
-
-	~~[[Category:RevisitAfterNextRelease]]~~

	The message contents are as following:		The message contents are as following:

TraCI/Traffic Lights Value Retrieval

Dkrajzew — Thu, 19 Nov 2009 12:01:14 GMT

← Older revision		Revision as of 12:01, 19 November 2009
Line 62:		Line 62:
	\| Returns the assumed time at which the tls changes the phase - please note that the time may vary in the case of actuated/adaptive traffic lights		\| Returns the assumed time at which the tls changes the phase - please note that the time may vary in the case of actuated/adaptive traffic lights
	\|}		\|}
-
-	~~{{Caution\|Note that retrieval methods 0x24, and 0x2d are currently only available within the SVN.}}~~
-
-	~~[[Category:RevisitAfterNextRelease]]~~

TraCI/Multi-Entry/Multi-Exit Detectors Value Retrieval

Dkrajzew — Thu, 19 Nov 2009 12:01:04 GMT

← Older revision		Revision as of 12:01, 19 November 2009
Line 44:		Line 44:
	\|-		\|-
	\|}		\|}
-
-
-	~~{{Caution\|Note that retrieval method 0x14 is currently only available within the SVN.}}~~
-
-	~~[[Category:RevisitAfterNextRelease]]~~

TraCI/Induction Loop Value Retrieval

Dkrajzew — Thu, 19 Nov 2009 12:00:55 GMT

← Older revision		Revision as of 12:00, 19 November 2009
Line 50:		Line 50:
	\|}		\|}

-	~~{{Caution\|Note that retrieval methods 0x13, 0x15, and 0x16 are currently only available within the SVN.}}~~
-
-	~~[[Category:RevisitAfterNextRelease]]~~

	== Response 0xb0: Induction Loop Variable ==		== Response 0xb0: Induction Loop Variable ==

TraCI/Change Polygon State

Dkrajzew — Thu, 19 Nov 2009 12:00:00 GMT

← Older revision		Revision as of 12:00, 19 November 2009
Line 47:		Line 47:


-	~~{{Caution\|Note that these APIs are currently only available within the SVN.}}~~
-
-	~~[[Category:RevisitAfterNextRelease]]~~

	The message contents are as following:		The message contents are as following:

TraCI/Change PoI State

Dkrajzew — Thu, 19 Nov 2009 11:59:22 GMT

← Older revision		Revision as of 11:59, 19 November 2009
Line 42:		Line 42:
	\|}		\|}

-
-	~~{{Caution\|Note that these APIs are currently only available within the SVN.}}~~
-
-	~~[[Category:RevisitAfterNextRelease]]~~

	The message contents are as following:		The message contents are as following:

TraCI/Lane Value Retrieval

Dkrajzew — Thu, 19 Nov 2009 11:58:04 GMT

← Older revision		Revision as of 11:58, 19 November 2009
Line 58:		Line 58:
	\|}		\|}

-	~~{{Caution\|Note that the following APIs can only be retrieved using the SVN version: id list, edge id, allowed vehicle classes, disallowed vehicle classes.}}~~
-
-	~~[[Category:RevisitAfterNextRelease]]~~

TraCI/Change Lane State

Dkrajzew — Thu, 19 Nov 2009 11:57:37 GMT

← Older revision		Revision as of 11:57, 19 November 2009
Line 37:		Line 37:
	\|-		\|-
	\|}		\|}
-
-	~~{{Caution\|Note that these APIs are currently only available in the SVN.}}~~
-
-	~~[[Category:RevisitAfterNextRelease]]~~

TraCI/Edge Value Retrieval

Dkrajzew — Thu, 19 Nov 2009 11:57:06 GMT

Edge Value Retrieval:

← Older revision		Revision as of 11:57, 19 November 2009
(One intermediate revision not shown)
Line 33:		Line 33:
	\|-		\|-
	\|}		\|}
-
-	~~{{Caution\|These APIs are currently only available within the SVN.}}~~
-
-	~~[[Category:RevisitAfterNextRelease]]~~


Line 76:		Line 72:
	\|-		\|-
	\|}		\|}
-
-
-	~~{{Caution\|These APIs are currently only available within the SVN.}}~~
-
-	~~[[Category:RevisitAfterNextRelease]]~~

TraCI/Change Edge State

Dkrajzew — Thu, 19 Nov 2009 11:55:09 GMT

Command 0xca: Change Edge State:

← Older revision		Revision as of 11:55, 19 November 2009
Line 30:		Line 30:
	\|}		\|}

-
-	~~{{Caution\|These APIs are currently onyl available in the SVN.}}~~
-
-	~~[[Category:RevisitAfterNextRelease]]~~

	The message contents are as following:		The message contents are as following:

TraCI

Dkrajzew — Thu, 19 Nov 2009 11:54:42 GMT

TraCI Commands:

← Older revision		Revision as of 11:54, 19 November 2009
Line 56:		Line 56:
	** [[TraCI/Change Polygon State\|Change Polygon State]] change a polygon's state (or add/remove one)		** [[TraCI/Change Polygon State\|Change Polygon State]] change a polygon's state (or add/remove one)
	** [[TraCI/Change Edge State\|Change Edge State]] change an edge's state		** [[TraCI/Change Edge State\|Change Edge State]] change an edge's state
-
-
-	~~{{Caution\|Note that APIs for changing PoIs, polygons, edges, and lanes are currently only available within the SVN. This also counts for retrieving edge values,}}~~
-
-	~~[[Category:RevisitAfterNextRelease]]~~

	== Example use ==		== Example use ==

NetworkImportXML

Dkrajzew — Thu, 19 Nov 2009 11:53:52 GMT

Edge Descriptions:

← Older revision		Revision as of 11:53, 19 November 2009
Line 266:		Line 266:
	\| Information which lanes should exist after the split		\| Information which lanes should exist after the split
	\|}		\|}
-
-	~~{{Caution\|Note that "split" are available within the SVN only by now.}}~~
-
-	~~[[Category:RevisitAfterNextRelease]]~~

	==Type Descriptions==		==Type Descriptions==

← Older revision		Revision as of 12:47, 20 November 2009
Line 66:		Line 66:
	* [[SUMO_Files\|Using files in a correct way]]		* [[SUMO_Files\|Using files in a correct way]]
	* [[SUMO_AdditionalStructures\|Traffic Management and Other Structures]]		* [[SUMO_AdditionalStructures\|Traffic Management and Other Structures]]
-	** [[~~SUMO_TrafficLights\|~~Traffic ~~lights~~]]	+	** [[Advanced Traffic Lights Simulation]]
	** [[SUMO_PublicTransport\|Public transport]]		** [[SUMO_PublicTransport\|Public transport]]
	** [[SUMO_VariableSpeedSigns\|Variable speed signs]]		** [[SUMO_VariableSpeedSigns\|Variable speed signs]]

← Older revision		Revision as of 12:04, 19 November 2009
Line 29:		Line 29:
	** added further [[TraCI/Induction_Loop_Value_Retrieval\|induction loops variable retrieval options]]		** added further [[TraCI/Induction_Loop_Value_Retrieval\|induction loops variable retrieval options]]
	** added further [[TraCI/Multi-Entry/Multi-Exit_Detectors_Value_Retrieval\|multi-entry/multi-exit detectors variable retrieval options]]		** added further [[TraCI/Multi-Entry/Multi-Exit_Detectors_Value_Retrieval\|multi-entry/multi-exit detectors variable retrieval options]]
		+	** added further [[TraCI/Junction_Value_Retrieval\|junction variable retrieval options]]
		+	** added further [[TraCI/Vehicle_Value_Retrieval\|vehicle variable retrieval options]]
		+	** added further possibilities to [[TraCI/Change_Vehicle_State\|change vehicle values]]
		+	** added possibilities to [[TraCI/Edge_Value_Retrieval\|retrieve edge variables]] and [[TraCI/Change_Edge_State\|change edge values]]
		+	** added possibilities to [[TraCI/Lane_Value_Retrieval\|retrieve lane variables]] and [[TraCI/Change_Lane_State\|change lane values]]
		+	** added possibilities to [[TraCI/Change_PoI_State\|change PoI values]] and to [[TraCI/Change_Polygon_State\|change polygon values]]
	** added the possibility assign a vehicle a new route via TraCI		** added the possibility assign a vehicle a new route via TraCI