Specifying the Road Network

SimMobilityST requires a detailed representation of the road network. The details about the various components of the road network can be found here. The network components can be supplied in one of the following two ways:

• Database
• XML file

Note: Providing the network as input through XML files is yet to be implemented

How to supply the network through the database

1. Open the common settings configuration file

2. Ensure that the databases and credentials sections contain the necessary information to connect to the database containing the road network components.

   Note: Information on the databases and credentials section can be found here

3. Open the short-term specific configuration file

4. In the db_proc_groups tag, define the the procedure mapping as

   <proc_map id = "<map_name>" format = "aimsun">
      <mapping name = "" procedure = ""/>
   </proc_map>

5. Within the procedure mapping defined above, add a mapping for each of the following mandatory components of the network as shown in the below table

   Network Component	Mapping
   Nodes	<mapping name= "nodes" procedure="<procedure_name_for_nodes>"/>
   Links	<mapping name= "links" procedure="<procedure_name_for_links>"/>
   Turning Groups	<mapping name= "turning_groups" procedure="<procedure_name_for_turning_groups>"/>
   Turning Paths	<mapping name= "turning_paths" procedure = "<procedure_name_for_turning_paths>"/>
   Turning Poly-lines	<mapping name="turning_polylines" procedure="<procedure_name_for_turning_polylines>"/>
   Turning Conflicts	<mapping name="turning_conflicts" procedure="<procedure_name_for_turning_conflicts>"/>
   Road Segments	<mapping name="road_segments" procedure="<procedure_name_for_segments>"/>
   Segment Poly-lines	<mapping name="segment_polylines" procedure="<procedure_name_for_segment_polylines>"/>
   Lanes	<mapping name="lanes" procedure="<procedure_name_for_lanes>"/>
   Lane Poly-lines	<mapping name="lane_polylines" procedure="<procedure_name_for_lane_polylines>"/>
   Lane Connectors	<mapping name="lane_connectors" procedure="<procedure_name_for_lane_connectors>"/>

6. If you are executing SimMobilityST with public transit enabled, you need to add the following additional mappings

   Network Component	Mapping
   Bus Stops	<mapping name= "bus_stops" procedure="<procedure_name_for_bus_stops>"/>
   Bus Dispatch Frequency	<mapping name= "pt_bus_dispatch_freq" procedure="<procedure_name_for_bus_freq>"/>
   Bus Routes	<mapping name= "pt_bus_routes" procedure="<procedure_name_for_bus_routes>"/>
   PT Bus Stops	<mapping name= "pt_bus_stops" procedure="<procedure_name_for_pt_bus_stops>"/>
   Train Station Segments	<mapping name= "mrt_road_segments" procedure="<procedure_name_for_mrt_segments>"/>

7. In the network tag, set <network_source value = "database"/> and provide the values of the database, credentials and proc_map defined in steps 2 and 4

   <network>   
      <network_source value = "database" />   
      <network_database database = "<database_id>" credentials = "<credential_id>" proc_map = "<map_name>"/>         
   </network>   

How to supply the network through XML files:

Note: This feature is yet to be implemented

1. Open the short-term specific configuration file

2. Update the network tag as shown below

<network>    
     <network_source value = "xml" />   
     <network_xml_file_input value = "<input_file_path>"/>    
     <network_xml_file_output value = "<output_file_path>"/>         
</network>   

Step by step guide: How to edit network using QGIS and import in SimMobility