Difference between revisions of "Data/Scenarios/TAPASCologne"

From Sumo
Jump to navigation Jump to search
(Quality)
(Quality)
Line 11: Line 11:
  
 
==Quality==
 
==Quality==
In the current version, we even have not tested the data, completely. The following assumptions are made on the quality:
+
In the current version, we even have not tested the data, completely. The assumptions made on the quality are shown below. We decided not to use a numeric ranking, because we do not have real world numbers for most of the issues. The rank tries to distinguish between "good" (arrow upwards, green) and "bad" (arrow downwards, red) influences on the overall simulation quality.
  
[[Image:level16px_-1.gif]] [[Image:level16px_-2.gif]] [[Image:level16px_-3.gif]] [[Image:level16px_-4.gif]] [[Image:level16px_-5.gif]] [[Image:level16px_-6.gif]]
+
* [[Image:level16px_00.gif]] Network Topology and Edge Parameter (from OSM)
 
+
** [[Image:level16px_+3.gif]] Completeness
 
 
[[Image:level16px_00.gif]]
 
 
 
 
 
[[Image:level16px_+1.gif]] [[Image:level16px_+2.gif]] [[Image:level16px_+3.gif]] [[Image:level16px_+4.gif]] [[Image:level16px_+5.gif]] [[Image:level16px_+6.gif]]
 
 
 
 
 
* <q0/> Network Topology and Edge Parameter (from OSM)
 
** <q3/> Completeness
 
 
*** Seems to be quite complete (including even minor roads) when compared to other (commercial or administral) road networks; still, there is no information about "black spots";  
 
*** Seems to be quite complete (including even minor roads) when compared to other (commercial or administral) road networks; still, there is no information about "black spots";  
 
*** '''todo:''' build density plot comparing commercial and this network (legal?)
 
*** '''todo:''' build density plot comparing commercial and this network (legal?)
** <q-3/> Lane Number Information
+
** [[Image:level16px_-3.gif]] Lane Number Information
 
*** The information about lane numbers is stored via types, mainly. For several roads, an explicite lane number is given  
 
*** The information about lane numbers is stored via types, mainly. For several roads, an explicite lane number is given  
 
*** '''todo:''' evaluate how much information is given explicitely
 
*** '''todo:''' evaluate how much information is given explicitely
 
*** '''todo:''' compare to images, write down lane number per street
 
*** '''todo:''' compare to images, write down lane number per street
** <q-2/> Maximum Speed Information
+
** [[Image:level16px_-2.gif]] Maximum Speed Information
 
*** Again, mostly available via types, as for lane numbers; is assumed to be mismatching on some places
 
*** Again, mostly available via types, as for lane numbers; is assumed to be mismatching on some places
*** Where can one get better information frmo?
+
*** Where can one get better information from?
* <q-1/> Traffic Management Artifacts
+
* [[Image:level16px_-2.gif]] Traffic Management Artifacts
** <q-2/> Traffic Light Positions
+
** [[Image:level16px_-2.gif]] Traffic Light Positions
 
*** Given for some junctions (nodes); Still, there seem to be no information whether a node not marked as controlled is really uncontrolled
 
*** Given for some junctions (nodes); Still, there seem to be no information whether a node not marked as controlled is really uncontrolled
 
*** '''todo:''' Try to find further controlled junctions or improve guessing
 
*** '''todo:''' Try to find further controlled junctions or improve guessing
** <q-3/> Traffic Light Programs
+
** [[Image:level16px_-3.gif]] Traffic Light Programs
 
*** Ungiven
 
*** Ungiven
 
*** '''todo:''' Ask about the default cycle time (if there is one) in Cologne; apply at least this one to the generated tls logics
 
*** '''todo:''' Ask about the default cycle time (if there is one) in Cologne; apply at least this one to the generated tls logics
** <q-1/> Other Traffic Management Artifacts
+
** [[Image:level16px_-1.gif]] Other Traffic Management Artifacts
 
*** completely ungiven  
 
*** completely ungiven  
** <q-1/> Closures, Roads At Work
+
** [[Image:level16px_-1.gif]] Closures, Roads At Work
 
*** completely ungiven  
 
*** completely ungiven  
* <q-2/> Public Transport
+
* [[Image:level16px_-2.gif]] Public Transport
 
** completely ungiven  
 
** completely ungiven  
* <q-2/> Demand Data
+
* [[Image:level16px_-1.gif]] Demand Data
** <q5/> Activity-Based single Person Trips  
+
** [[Image:level16px_+5.gif]] Activity-Based single Person Trips  
*** <q5/> No Time Aggregation
+
*** [[Image:level16px_+5.gif]] No Time Aggregation
*** <q5/> No Start/End Position Aggregation
+
*** [[Image:level16px_+5.gif]] No Start/End Position Aggregation
** <q-2/> unverified
+
** [[Image:level16px_-2.gif]] unverified
** <q-2/> starts partially at highways
+
** [[Image:level16px_-1.gif]] starts partially at highways
** <q-2/> ad-hoc, errorneous mapping to OSM
+
** [[Image:level16px_-2.gif]]ad-hoc, errorneous mapping to OSM

Revision as of 20:40, 4 March 2009

Availability

88x31.png

The data is available under the Creative Commons licence. You must tell where the data is from, it is not allowed to use it for commercial purposes, as soon as you use it we want to be informed about it (use the sumo-user mailing list).

Setting up such a large scenario is a lot of work and we can not do it by ourselves only. That's why we currently only offer a reduced data set, which contains routes between 6:00 and 8:00 am. If you are really interested in the complete data set, ask how to obtain it at the sumo-user mailing list.

Contents

The TAPASCologne scenario package includes:

  • The road network (cologne_plain.net.xml)
  • The routes file (routes6-8.rou.xml) for time between 6:00 and 8:00 (am)
  • The SUMO-configuration file (tapascologne.sumo.cfg)

Quality

In the current version, we even have not tested the data, completely. The assumptions made on the quality are shown below. We decided not to use a numeric ranking, because we do not have real world numbers for most of the issues. The rank tries to distinguish between "good" (arrow upwards, green) and "bad" (arrow downwards, red) influences on the overall simulation quality.

  • Level16px 00.gif Network Topology and Edge Parameter (from OSM)
    • Level16px +3.gif Completeness
      • Seems to be quite complete (including even minor roads) when compared to other (commercial or administral) road networks; still, there is no information about "black spots";
      • todo: build density plot comparing commercial and this network (legal?)
    • Level16px -3.gif Lane Number Information
      • The information about lane numbers is stored via types, mainly. For several roads, an explicite lane number is given
      • todo: evaluate how much information is given explicitely
      • todo: compare to images, write down lane number per street
    • Level16px -2.gif Maximum Speed Information
      • Again, mostly available via types, as for lane numbers; is assumed to be mismatching on some places
      • Where can one get better information from?
  • Level16px -2.gif Traffic Management Artifacts
    • Level16px -2.gif Traffic Light Positions
      • Given for some junctions (nodes); Still, there seem to be no information whether a node not marked as controlled is really uncontrolled
      • todo: Try to find further controlled junctions or improve guessing
    • Level16px -3.gif Traffic Light Programs
      • Ungiven
      • todo: Ask about the default cycle time (if there is one) in Cologne; apply at least this one to the generated tls logics
    • Level16px -1.gif Other Traffic Management Artifacts
      • completely ungiven
    • Level16px -1.gif Closures, Roads At Work
      • completely ungiven
  • Level16px -2.gif Public Transport
    • completely ungiven
  • Level16px -1.gif Demand Data
    • Level16px +5.gif Activity-Based single Person Trips
      • Level16px +5.gif No Time Aggregation
      • Level16px +5.gif No Start/End Position Aggregation
    • Level16px -2.gif unverified
    • Level16px -1.gif starts partially at highways
    • Level16px -2.gifad-hoc, errorneous mapping to OSM