OpenStreetMap logo OpenStreetMap

Jothirnadh's Diary

Recent diary entries

Breaking route relations while splitting roads

Posted by Jothirnadh on 8 June 2017 in English. Last updated on 14 September 2018.

The most common error we end up doing while splitting well-mapped roads in a highly mapped area is by breaking a route relation. This usually involves breaking the continuity of a bus or highway route due to missing members. The community has reported broke route relations while the data team was trying to improve navigation features (Turn lanes & turn restrictions) in US cities. On thorough research found some points to share with you all and hope this helps in solving route relations breakages in future.

The first thing to note, there is nothing wrong with any of the split way or knife-tool that we use to split the road. In general, route relations are very long and spreads across the city. When two or more persons work at the same time, on editing roads part of the same route relation, JOSM will throw relation edit conflict. This conflict is very specific on which version of the edit to keep and which one to remove. In general, people tend to resolve the conflict by pushing their edits and skipping the other’s edits. This causes the route relation breakage. Let me explain clearly with examples.

Example:

For this use case, I took a bus route (Relation: 333P) in Bangalore, India and tried to download the data into JOSM at two corners of the route into two different layers (layer-1 & layer-2). Now the route relation 333P has 89 members at version-61.

See full entry

Location: Old Binnamangala, Bengaluru, Bangalore North, Bengaluru Urban, Karnataka, 560038, India

Reverting huge changesets using JOSM

Posted by Jothirnadh on 14 September 2016 in English. Last updated on 14 September 2018.

OpenStreetMap is a great place where we can share the on-ground information with the community. Most of the time the data we add is good, but sometimes we might end up adding bad data. We might even come across unspecified bad imports which are supposed to be reverted. To overcome this we have a reverter plugin in JOSM, which helps in reverting data on changeset basis. The plugin works fabulously in reverting small changesets but fails to revert huge changesets with the below popup:

screen shot 2016-09-14 at 5 22 16 pm

There is no proper documentation for reverting huge changesets. On through research found that it’s because of the less socket.timeout given by default in JOSM. If we adjust the socket.timeout then the reverter plugin started to work well with big datasets. The below values worked for me.

See full entry

Mapping turn lanes in San Francisco, Washington DC and Los Angeles

Posted by Jothirnadh on 13 April 2016 in English. Last updated on 14 September 2018.

San Francisco, Washington DC and Los Angeles just got 51,385 turn lanes added to the map over the last 3 months. This was part of the push by the Mapbox data team to enrich OSM for better navigation and guidance.

screen shot 2016-04-13 at 3 15 06 pm Turn lanes added in LA

All the mapping tasks were coordinated and documented on GitHub. We’re simultaneously working to create a navigation mapping guide to consolidate a lot of documentation on the wiki with added context for the areas we work on. This should make it easy for new mappers improve OSM in their areas and also help potential users of the map data understand the tagging model. The comments and suggestions from the community helped us a lot in improving the guide and to speed up the mapping process.

See full entry

Fixing the tagging errors in Rajahmundry

Posted by Jothirnadh on 16 February 2016 in English. Last updated on 14 September 2018.

In my previous hometown mapping of Rajahmundry post, I pointed out some of the data errors present. I contacted most of the OSM contributors and found that most of the data was added as part of a local muncipality project. It is nice to see that my local municipality is adopting open data in order to reach citizens and it will be the best opportunity to provide awareness of open data among the local citizens.

The data they added were from local surveys. I personally verified some points and I can attest that the locations are accurate, however, I found several cases of wrong tagging. For example, they mostly used the Name instead of name. According to OSM convention, keys should be the lower case.

screen shot 2016-02-16 at 2 23 56 pm

Wrongly tagged point features

See full entry

Location: Indiranagar 1st Stage, Bengaluru, Bangalore North, Bengaluru Urban, Karnataka, 560038, India

Improving the road network coverage in Myanmar

Posted by Jothirnadh on 2 February 2016 in English. Last updated on 14 September 2018.

Myanmar is witnessing an unprecedented growth in international tourist arrivals following major democratic reforms since 2011. On OSM, around 70,000 kms of roads have been mapped so far, or roughly 42% of the total reported roadways.

Most of the major highways (motorways, trunk, primary, secondary and tertiary roads) are well mapped in the major cities of Yangon, Mandalay, and Naypyidaw, but there are a lot of missing residential and unclassified roads visible in the imagery. Over a period of three weeks, the Mapbox data team was able to add a total of 7,690 missing streets, out of which 2559 and 5131 streets were added in Mandalay and Yangon respectively.

yangon changes
Missing streets in Mingaladon locality in Northern Yangon

A full map of all objects added or modified by the Mapbox data team.

Issues we faced

See full entry

Location: 12.981, 77.637

Adding missing towns and villages in OSM

Posted by Jothirnadh on 25 November 2015 in English. Last updated on 14 September 2018.

Adding missing towns and villages in OSM (India)

In India, there are ~7935 cities/towns officially recognized by the Government of India according to the 2011 census. But in OSM, there are only 3352 (as of 2015-11-23) cities/towns mapped as place node.

As the first step of mapping, it is important to mark all the major cities and towns in the country. The Mapbox data team did some background analysis of the data in OSM and compared it to other publicly datasets. This guide will walk through the step of using a public domain map layer from geonames.nga.mil for improving the location of India’s towns/cities in OSM using JOSM.

Download JOSM

  • JOSM - If you are new to JOSM you can find help in this guide

Add the GNS layer in JOSM’s Imagery Preferences

See full entry

Location: Indiranagar 1st Stage, Bengaluru, Bangalore North, Bengaluru Urban, Karnataka, 560038, India

Mapping my hometown Rajahmundry

Posted by Jothirnadh on 10 November 2015 in English. Last updated on 14 September 2018.

Rajahmundry is one of the most populated cities in Andhra Pradesh, India. It is located on the banks of Godavari river and it is most known for its high cultures and traditions. Rajahmundry is also known as the ‘Cultural Capital’ of Andhra Pradesh.

Problems encountered while mapping

I started my OSM mapping journey recently and the first thing I wanted to map is my hometown (Rajahmundry). In the beginning, I was quite surprised to see that most of the roads and buildings of the city are already mapped by OSM mappers for which I’m always thankful. This made my work much simpler and thought of adding names to the streets which I’m familiar with, but soon I started to encounter errors in the data. The most common error is the misalignment of data, which I mentioned in the following context.

1. The difference in Satellite data

The city is having overall coverage of Bing imagery but the Satellite data is divided into three major blocks. The center block is from 2013 coverage, the upper block is from 2012 coverage and the lower right block is from 2011 coverage.

See full entry

Location: Rajamahendravaram, Rajahmundry (Urban), East Godavari, Andhra Pradesh, 533100, India