For folks who would want to add some road names in Klang Valley, we have an interesting maproulette challenge for you! These are for mappers who are a little experienced. Here’s where you can get started: https://maproulette.org/browse/challenges/23131

Put your mapping hats on and let’s do some mapping!

We would love to hear your suggestions and feedback on these tasks so that we could better next time.

PS: Can’t wait to see who is going to be on top in this challenge (psst.. We have some goodies for you) 😉

Happy Mapping!

It was great going through the challenges in part 1. We have a few more interesting tasks as the next maproulette challenges for you all. They are for mappers who are just starting or are experienced. Here are the tasks for you all:

1. Connectivity checks: https://maproulette.org/browse/challenges/21203
2. Building-Road intersection checks: https://maproulette.org/browse/challenges/21201
3. Inconsistent Road Classification checks: https://maproulette.org/browse/challenges/21207
4. Intersecting Buildings checks: https://maproulette.org/browse/challenges/21208
5. Correcting mixed name case: https://maproulette.org/browse/challenges/21215
6. Connectivity checks: https://maproulette.org/browse/challenges/19892
7. Invalid Turn restrictions checks: https://maproulette.org/browse/challenges/19890

Put your mapping hats on and let’s do some mapping!

We would love to hear suggestions and feedback from you on these tasks so that we could better ones next time.

PS: Can’t wait to see who is going to be on top in this challenge (psst.. We have some goodies for you) 😉

Happy Mapping!

Are you wondering what to map next? Don’t worry we got you covered! We have three interesting tasks as the next maproulette challenges for you all. They are for mappers who are just starting or are experienced. Here are the tasks for you all:

1. Connectivity checks: https://maproulette.org/browse/challenges/17714
2. Sharp Angle checks: https://maproulette.org/browse/challenges/17716
3. Invalid turn restrictions: https://maproulette.org/browse/challenges/17715
4. Crossing ways: https://maproulette.org/browse/challenges/17943
5. Wrong one way- double way - https://maproulette.org/browse/challenges/17958
6. Road Islands - https://maproulette.org/browse/challenges/17950

Put your mapping hats on and let’s do some mapping!

We would love to hear suggestions and feedback from you on these tasks so that we could better ones next time.

PS: Can’t wait to see who is going to be on top in this challenge (psst.. We have some goodies for you) 😉

Happy Mapping!

My team at Grab and I got an opportunity to experiment with the RapiD – AI-assisted mapping editor. We found this tool to be useful in mapping missing road networks. It is also helpful in increasing the mapping speed, as:

• Missing features are already highlighted – helped us focus on the exact location where the feature is missing than going through an entire area.
• Once selected, they are already traced, thus minimising the tracing efforts and help us better the quality of tracing
• Help in increasing mapping speed plus give us full control of the data that can be uploaded and the ones that need not be uploaded.

This would be a great tool for the community in SEA as the folks here are new and would be willing to explore this to map the unmapped regions here.

Here are our major takeaways post using the tool:

• The AI detections are pretty clear and are correctly detecting the roads.
• The user has the option to accept or reject a detection, clearly establishing that a mapper intervention is necessary even if the AI is pretty good in identifying.
• It automatically connects the new roads to the preexisting ones or warns when a new segment that we accept has been connected or not, which is great for new mappers to understand and validate.
• The detections stand out but also doesn’t take up too much space, making it easier to spot the roads without having to disable to rapid assist.
• The detections already had predefined tags, which makes it quicker for the mapper to add the roads and since the tags are already defined, it eliminates the cases of having or uploading untagged ways.
• The AI detects the features until the end of that grid and allows the mappers of the other grid to connect the roads, which makes it easy and conflict-free.

The detections have been great. It still allows us to experience the thrill of mapping :) Just makes it easy as it detects places/roads that are missing and through these detections, they are easy to identify, thus making the process faster.

As you can see below, the tool manages to identify and suggest adding roads that align with the imagery. As a mapper and having an eye to making it more precise, I, of course, did add a couple of more nodes but most of my work was done. I managed to map more in lesser time. I loved the fact that even though these are generated, they will be uploaded on OSM if and only if the mapper approves. The quality of the data is in the mapper’s hands.

It also took care of the possible errors which one could have missed. In this case, even though the road is a small extension, the tool suggests the mapper to extend it and trace according to the imagery.

How would it be of use in SEA region:

We would be exploring this tool in dense areas and validate these detections work. We will also be integrating this with our Geo*Stars program and other community activities. This will enable mapping enthusiasts to map in SEA.

Happy Mapping! :)

Grab is excited to share with the community, that our maps team in Thailand has been uploading street-level imagery in Mapillary for Chiang Mai City areas and we are now hitting ~82% which is approximately 1,667 kilometres of roads. We are expected to complete the 100% upload by the end of this month.💥 Update: We have completed 100% upload of the street-level-imagery in this region.

We also have uploaded imagery on OpenStreetCam for the Singapore area. ((edited-29th April 2019) This upload was done sometime last year)

Here’s how you can start mapping using Mapillary imagery, here are the detailed steps involved if you are using iD editor or JOSM for mapping. Want to start contributing imagery in your region, here’s how you can do it!

Happy Mapping!

State of the Map conferences celebrates the essence of the amazing communities that form an integral part of the OpenStreetMap. These conferences continue to strengthen the relationships that contributors around the world build both online and in person. The whole team at Mapbox cannot wait to connect with new and familiar friends around the globe at the many OpenStreetMap events happening this year.

Here’s the map of all events, find the interactive one here

Take a look at our event-full calendar for this year:

• The sixth State of the Map France, and one of the first State of the maps of 2018, took place in Pessac (near Bordeaux), France from 1st - 3rd June. The videos from the conference are online!
• State of the Map, the global OpenStreetMap gathering is taking place in the global capital of fashion and design — Milan, Italy from 28th - 30th July
• State of the Map, Japan, the regional conference is happening in Tokyo, Japan on 11th August
• The first ever FOSS4G in Dar es Salaam, Tanzania, Africa will be co-hosted by the Humanitarian OpenStreetMap Team and FOSS4G. This will take place from 27th August - 2nd September
• The fourth edition of State of the Map Latin America takes place in Buenos Aires, Argentina from 24th - 25th September, the call for proposal closes on 25th August.
• State of the Map US, the annual US community conference in Detroit, Michigan from 5th- 7th October. Look out for an interesting challenge of making Detroit the best map in the World
• State of the Map Asia is hosted by Bengaluru, India and takes place from 17th - 18th November
• The first FOSS4G State of the Map Oceania is happening in Melbourne, Australia from 20-23 November.

Are you planning to be there too? Connect with us at these events or online here and on social media. Happy mapping!

The OpenStreetMap Navigation map is a web application which uses Mapillary vector layer to highlight the traffic signages detected in Mapillary images. The application is helpful to add/verify/modify turn-restrictions on OpenStreetMap.

Using the navigation map, our team and the community reviewed 38,658 turn restrictions signs from Mapillary, out of which there were 18,565 valid, 11,924 redundant and 7,989 invalid turn restrictions.

We’d like to announce Mapbox will no longer maintain this tool and will no longer work from today. This is an open source project, if you’d like to run a similar project or re-use this, you can find all the information in the repository. Thank you to all the contributors!

Wikimania 2018 is happening in Cape Town, South Africa on July 18-22, 2018, it’s the annual international conference that celebrates Wikipedia and its sister free knowledge projects.

The previous year, Montréal, Canada, was the host of this conference. The OSM community in Montréal had set up a booth and did an amazing work of introducing people to the OSM project. It also became a great place for answering questions related to OSM as well as explore more ways to collaborate with different Wiki projects.

Group photo - Wikimania 2017

There were some interesting sessions related to OpenStreetMap in the previous Wikimania:

• Workshop - Mapathon! Contribute and connect OpenStreetMap and Wikipedia using Wikidata
• OpenStreetMap project and how to get involved
• OpenStreetMap loves Wikipedia

The last date for submitting proposals for talks/sessions/workshops was 18th March but the community can still attend and give a lightning talk and/or organise a Birds of the Feather (BoF) session.

It’ll be great if the South Africa/Cape Town OSM communities would want to do something along these lines. OpenStreetMap and Wikipedia communities have a lot in common, let’s meet, collaborate and make the most of this opportunity!✨

OpenStreetMap is an integral part of Mapbox, I’m happy to share the announcement about our new logo with the community! 🎉

The logo is a helmet of an astronaut and my favorite part of this logo is that it reinstates Mapbox’s culture of curiosity and passion! It showcases the team’s vision and enthusiasm towards new opportunities. The star that you see in the astronaut’s helmet demonstrates our spirits to reach new heights! Know more details about the logo here.

Though we have a new look and feel, we still continue to be the Mapbox that you all know. Our commitment towards improving OpenStreetMap data remains the same and so is our attribution around OpenStreetMap! ✨

The OpenStreetMap Ottawa community was working on the Ottawa building import that led to an addition of 350K buildings and address points to OpenStreetMap.

This project was completed on the 7th of April with a mapping party hosted by the community, and Mapbox had an opportunity to sponsor this mapping party. As a Mapbox data team member, this was a great opportunity for me to interact with the community and get an understanding of the workflows they follow to make this import happen! The community is currently validating these tasks.

The map showing the buildings added by the community made using Mapbox

It was early morning (5 am) in Bangalore but it was worth waking up to interact with the folks from literally the other end of the world ;). There were nearly 25 attendees for the meetup and it was great to chat with the organisers and get an understanding of the import, and in general the community! Love how different communities work together for making OpenStreetMap the best map of the world! Special thanks to Rps333 for helping us in making this happen!🙇🏼

Members of the OSM Ottawa community at the weekend mapping party to discuss the Ottawa building import and mapping the remaining buildings in the city interacting with the Mapbox data team in India

OpenStreetMap diaries are a great way to communicate with the community worldwide. Since past few months, few of us are receiving irrelevant comments on our diary posts from users who mostly have no edits (likely that they are new to OpenStreetMap)

Some examples of such comments are:

• This is a snapshot from a diary post by SrrReal, which has many such comments.

• This is a snapshot from a diary post written by me.

• Can there be a way, where we can close the option to comment on a diary post after a particular period?
• Is there a possibility of deleting such comments from the post?
• Is anyone else also facing similar issues?

The data team at Mapbox has been trying out mapping missing motorway exit numbers in the US. Based on the density of Mapillary street photographs, the following 9 US states were chosen to improve:

• California
• Florida
• New Jersey
• Maryland + DC
• Pennsylvania
• Washington State
• Colorado
• Texas
• Illinois

We used the checkautopista2 tool which made it very easy to detect exits that lack a ref tag. In summary we found most of these exits to have no official exit number and added the noref=yes tag when we could confirm it on official documents or on Mapillary photographs.

These are the exit numbers added by the team. The pink dots represent ref=* tags and the blue dots represnt noref=yes tags added by the team, click here to view the full map

The team has been working on this from 31 March 2016 to 14th April 2016 and reviewed more than 220 highways.

• Number of ref=* added by team on nodes highway=motorway_junction are 63
• Number of noref=yes added by team on nodes highway=motorway_junction are 219

This is the workflow that was used for this mapping activity. Would be great to hear your feedback on how it can be improved for further such tasks, please drop a comment here or on the project tracker.

Happy Mapping!

Maps.me is a mobile application that provides offline map service world wide and it uses OpenStreetMap. It also provides a provision to add POIs and building information. This means more eyes and contributors to OpenStreetMap. I played around with maps.me application for Android, these are some points that we should make note of:

• The UI is smooth and makes it easy to add POI’s on map.
• It’s a really good mobile editor.
• The app provides fields that will help the user add information about a POI/Buildings conveniently.
• The maps are updated only with the next release of the application, so the changes made by the user on OpenStreetMap will not be reflected until the next release of the application.
• The tags provided are limited, for example common tag like university is absent.

• These maps are downloaded and saved offline, so the changes made are also saved locally and they get pushed automatically to OpenStreetMap once the user connects to the Internet.
  • There is no pop-up stating that the data is being uploaded to OSM
  • The app adds it’s own changeset comment (the user doesn’t have an option to add custom comment to the changes they make)

Adding a place using maps.me application

Issues that are concerning:

• Since the map is only updated with the new release of the application, there are possibilities of duplication of data.
• One can add POIs on top of another POIs. The application doesn’t caution users with a warning that data already exists.
• Many POIs were found to be in the middle of the road, this is probably due to gps variations.

poornibadrinath and I came across these changesets which has the editor=maps.me, here are the observations:

• Marked a point in the middle of the road. Probably an issue while placing the point due to gps variations. - https://www.openstreetmap.org/user/%D8%AD%D9%85%DB%8C%D8%AF%D8%B1%D8%B6%D8%A7%DA%A9%D9%85%DB%8C%D9%84%DB%8C%D8%A7%D9%86/history#map=13/35.7344/51.4712

• http://www.openstreetmap.org/changeset/38717235

• http://www.openstreetmap.org/changeset/38716955/

• http://www.openstreetmap.org/changeset/38716556/

Feature requests, bugs and suggestions regarding this application can be reported in their github repository.

Motorways are access controlled highways with designated points of entry and exits. Missing an exit on a motorway can result in long detours of tens of kms to get back to that point. In OSM we tag the exit nodes on the highway as highway=motorway_junction with a ref tag indicating the exit number that is displayed on the road signages.

According to the OSM wiki, motorway junctions should have a unique ref indentifier or name. In the US alone there are around 7,000 exits without a ref identifier. Many exits have no official idetifier and they are usually tagged with an additional noref=yes. What about the rest? Are they missing a ref or does it not have one?

Overpass query to find exits without a ref or noref=yes

Here’s how you can investigate the missing ref on motorways in your area:

Find exits without a identifier

There are multiple ways to do this:

• Run this Overpass Query for your area http://overpass-turbo.eu/s/ftm to see where to focus your effort
• Use Check Autopista 2 to analyze a specific motorway for missing information

• Use this tms background layer in JOSM or iD tms:https://api.mapbox.com/v4/pratikyadav.3b94b1a9/{zoom}/{x}/{y}.png?access_token=pk.eyJ1IjoicHJhdGlreWFkYXYiLCJhIjoiMTA2YWUxNjRkNmFmZGQ4YzAxZWFiNDk0NDM1YjE1YjAifQ.4P6N5dNmA_WQXd3BsJvu5w to spot exits with missing ref tags (blue dots)

• Red dots are exits with a ref
• Red lines represent motorway_link
  

Find a source for the exit number

The recommended approach is to survey the location yourself for the correct information. If you are short of cash to travel all the way, there are some armchair resources:

• Use the Mapillary Photos via the plugin in iD or JOSM for street level imagery of the location to check the highway signages
• Check official sources like the local transport agency exit number documents.
• Wikipedia
• Cross Country roads
• Aaroads

Add the missing data

If you find an exit number, then use ref=* tag to add it to motorway junction. If there is no exit number and the sign board has exit or nothing written on it then add noref=yes tag to the motorway junction.

The Mapbox data team is currently mapping the missing exit numbers in the USA using this workflow. Our progress and observations are documented here. Feel free to join in and give us feedback on how this can be improved.

Continuing from the previous diary post.

I worked on cleaning up the tags amenity=picnic_site & leisure=picnic_site and replaced them with tourism=picnic_site tag. Here are the changesets related to the changes made on OSM.

Changesets for amenity=picnic_site

• https://www.openstreetmap.org/changeset/36122000 (South America)
• https://www.openstreetmap.org/changeset/36122166 (North America)
• https://www.openstreetmap.org/changeset/36122432 (MockBa)
• https://www.openstreetmap.org/changeset/36122706 (Europe)
• https://www.openstreetmap.org/changeset/36122849 (Australia)
• https://www.openstreetmap.org/changeset/36122958 (Kunming,China)

Changeset for leisure=picnic_site

• https://www.openstreetmap.org/changeset/36123139 (Australia)
• https://www.openstreetmap.org/changeset/36123577 (Thailand)
• https://www.openstreetmap.org/changeset/36123927 and https://www.openstreetmap.org/changeset/36124505 (California, British Columbia, Oregon, Vancouver)
• https://www.openstreetmap.org/changeset/36124755 and https://www.openstreetmap.org/changeset/36124910 (Rest of North America)
• https://www.openstreetmap.org/changeset/36125178 (Israel, Egypt)
• https://www.openstreetmap.org/changeset/36125857 (United Kingdom)
• https://www.openstreetmap.org/changeset/36126193 (Rest of Europe)
• https://www.openstreetmap.org/changeset/36126675 (South Korea)

If an edit was made with-in a year, I have sent a message to the user, informing about the change I made to their edit. There were a total of 44 messages sent.

---

This was the message format

Subject: Re-tagging picnic sites with tourism=picnic_site tag

Hi,

I’ll be changing the tag from amenity=picnic_site to tourism=picnic_site tag as per this wiki, to find more information on this you can refer this diary entry.

This is the node that I have changed the tag for - https://www.openstreetmap.org/node/3353080237/history (The link to their node)

Thank you!

Best,

Jinal Foflia

---

Some pain points:

• It is a good idea to send a message to user intimating them about the change, but the process becomes tedious after a point of time. Since this was small number it could be managed. For bigger edits it would be a great idea to have a better way in which it can be communicated.

Statistics

I spent half a day doing this clean-up. A good amount of time was spent in communicating the users with the change made to their edits. These are the number of nodes added by me.

As per the wiki picnic sites should be tagged tourism=picnic_site and not as amenity=picnic_site or leisure=picnic_site.

There are a small number tagged as amenity=picnic_site and leisure=picnic_site through out the world. I think these should all be tourism=picnic_site.

These are the number of picnic sites tagged as leisure=picnic_site

These are the number of picnice sites tagged as amenity=picnic_site ways

I’m looking into re-tagging the above into tourism=picnic_site in-order to have uniform tagging for picnic sites through out the world. The work-flow i’ll be following:

• I’ll be extracting the picnic sites with amenity=picnic_site and leisure=picnic_site using Overpassturbo.
• I’ll be going to each of the picnic sites and look for re-tagging it.
• If the tag has been recently added, then I shall make sure I inform the user about the current tagging scheme so that they have an idea before I touch their work.
• The changeset comment i’ll be using is Re-tagging picnic sites with tourism=picnic_site tag https://github.com/mapbox/mapping/issues/147

For further details on the progress please refer to this repository.

Mapillary images are a good source to verify and add information like turn restrictions and speed limits. This is not possible with satellite images. We realised that we need to have a thorough knowledge about the traffic signs used in the region we are mapping, as they are region specific.

Initially we started exploring the traffic data in USA. With help of the traffic data wiki for USA, we came up with a list of road signs which can be mapped using the Mapillary imagery. This list was created after pruning a list containing 467 traffic signs used in USA, after comparing them to the signs detected by Mapillary. We have also listed the OSM tags associated with each traffic sign.

Refer to the table given below to match the traffic sign in the Mapillary image against the list of traffic signs and it also consists of the OSM tags:

Here is the traffic signal guide.

This is the workflow we used to map the turn restrictions:

STEP 1: Setting up JOSM for mapping traffic data

In order to be able to map traffic data easily, there are some plugins that JOSM needs to be configured with:

• Layers to be added:
  • Mapillary layer: tms:http://d2cd86j8eqns9s.cloudfront.net/tiles/{zoom}/{x}/{y}.png
  • Bing imagery: bing[22]:http://www.bing.com/maps/
• Plugins to be downloaded:
  • Mapillary plugin for JOSM: This plugin allows the user to view mapillary images in JOSM.
  • Turn restrictions plugin for JOSM: This plugin allows to add turn restrictions to the selected roads with ease.
  • RoadSigns plugin for JOSM: This plugin offers a dialog for selection of traffic signs from a list of presets. With simple clicks you can create combinations of signs and generate tagging suggestions.

• Map-paint styles to be added:
  • traffic_signs: It displays all the existing traffic signs that have been already mapped on OSM.
  • Maxspeed: It displays the already existing speed restrictions on OSM.

STEP 2: How to use the mapillary and turn restriction plugins

Using the Mapillary plugin

• The Mapillary imagery can be added by clicking on imagery -> Mapillary in JOSM. This will add the mapillary layer over the dataset layer.

• The explanation for how the plugin works can be found here.

  Note: - If one is using tasking manager, first download the task from the tasking manager and then add the Mapillary layer.

• Every time a new task is downloaded from the tasking manager, a new Mapillary layer must be added after deleting the old one.

Using the turn restriction plugin - The explanation for how the turn restriction plugin works can be found here.

STEP 3: How to add the traffic data using mapillary

• Probe the different Mapillary images present in that area to find useful traffic data that can be added to the Open Street Map.
• The Mapillary point on the GPX trail that has a red triangle along with it contain Traffic-signs.

• Probe the images to get a good idea of the surroundings and then compare them with the existing imagery to find the exact location of the traffic-sign.

  To add a turn restriction using the turn-restriction plugin

• We need to cautious while adding a U-turn/No U-turn in OSM, here is how we can add it:

Note

• To get a better idea about the area/road, always inspect multiple images.
• With the help of the plugins, look for one-ways, speed-limits and traffic restrictions which are already present on the road/area.
• Unless you are sure about the start and end point of a road, it is advisable to avoid adding oneway=yes tag to it.

• We should avoid adding turn restriction to roads that are leading to oneways going in the opposite direction, like the example below. It will only result in redundant data:

  

Here we should avoid adding turn-restriction as it will result in redundant data

Issues

While mapping, we came across the following issues:

While mapping turn restrictions

• They are easily visible in the imagery and map but are leading to splitting of major roads and also leading to addition of multiple relations
• Is this something we need to follow while adding the turn restrictions or there is a better-way?

While mapping speed-limits

• It is difficult to identify the start and end point of the road to which the speed-limit should be applied.
• Is there a better way to add speed limits or any convention that is followed while adding them?

For further details about how we created the workflow please refer to this repository.

Last week, we celebrated osmgeoweek in Bengaluru, India with a community mapping party at the Mapbox office on 15th of November. On a drizzly Sunday morning, @planemad and several OSM-IN volunteers set out to map garbage dumping sites, waste baskets and street lamps in the locality.

Deciding what to map

We do a lot of detailed mapping around our neighborhood in Indiranagar to showcase the possibilities of mapping with OpenStreetMap for the local mapping community, and is now probably the most well mapped neighborhood in the country.

House-numbers, building heights, trees, street lamps, waste baskets and more only on OSM

The 6 mappers managed to collect the locations of 220 street-lamps and 16 waste dumping sites in a couple of hours using just field-papers. After a tasty lunch, we got back to the Mapbox office to upload our data and made a quick map to visualize the street lamps.

Map of street-lamps in Indiranagar. We don’t know how many are actually operational!

To top it off, we got covered by the popular city paper - Bangalore Mirror, which gave OSM some great publicity for OSMGeoWeek!

Read the full article on Bangalore Mirror

On Thursday, we organized a mapathon for the data team in office. We decided to time our mapping to an on-going event and collaborate across the world instead of doing our own event. We spotted an OSMGeoWeek event scheduled at University of Management & Technology, Lahore which got us excited. We had maning coordinate with Usman Latif of @Mapgive Pakistan to join hands to map remote areas of Afghanistan. We started the mapathon with a Skype video call with the mappers from our neighbouring country. This was an exciting moment for the entire data team as it was a wonderful experience to work together with our friends from across the border.

Historic first for mappers from Pakistan and India, united by technology!

Geoweek has been great fun, and has given an opportunity for all of us in the Mapbox data team to be aware of the possibilities of geography uniting people over a common idea. Looking forward to hearing more stories from around the world. Happy Mapping!

SUMO is a free and open traffic simulation suite which is available since 2001. SUMO allows modelling of intermodal traffic systems including road vehicles, public transport and pedestrians.

• This simulator has many options to customise the simulation, options like CO2 emissions on roads, speed limits of the roads etc
• The data for simulation is taken from the OpenStreetMap

Some useful links to help installation of SUMO simulator for

• OS-X-Yosemite
• Ubuntu 12.04

Steps to simulate traffic of a particular region.

Step 1: Download OSM data from Open Street Maps (<file_name>.osm)

Step 2: Run this command to get the .net file required for simulation. (Netconvert imports digital road networks from different sources and generates road networks that can be used by other tools from this package.)

netconvert --osm-files <file_name>.osm -o <file_name>.net.xml --output.street-names true --output.original-names true

Step 3: From the following link copy the additional polygons structures

http://sumo.dlr.de/wiki/Networks/Import/OpenStreetMap

Step 4: Save the data into a file and name it as ‘typemap.xml’ then run the following command. (Polyconvert imports geometrical shapes (polygons or points of interest) from different sources, converts them to a representation that may be visualized using SUMO-GUI)

polyconvert --net-file <file_name>.net.xml --osm-files <file_name>.osm --type-file typemap.xml -o <file_name>.poly.xml

python /Applications/sumo-0.23.0/tools/trip/randomTrips.py -n <file_name>.net.xml -e 100 -l

python /Applications/sumo-0.23.0/tools/trip/randomTrips.py -n <file_name>.net.xml -r <file_name>.rou.xml -e 100 -l

• After the above steps, the routes have been generated, in the xml file you need to configure the file for the SUMO gui

Step 5: Search for the sumo.cfg file in the sumo folder and copy it to your working folder.

The configuration file should be modified with the following contents:

</input>

Step 6: To run the simulator

sumo-gui <file_name>.sumo.cfg

Outcome

• Helps one understand how each tag that we use impacts the traffic.
• Helps in, in-depth analysis of the road network that’s established by the OSM data.
• It by default simulates right-hand driving traffic conventions and has no options for left-hand driving conventions.

For more questions.