Hi. You've added a few roads as tertiary by mistaking them as roads but they were canals for irrigation. No worries. I've re-purposed them as track roads that go by the canal. Just be a bit vigilant the next time. Cheers!

Fantastic work here. Thank you!

Hey! Reverted the name of Sadasivpet from Sadashivpet. Thought I'd let you know. Google has it wrong as well. ;) To look up -> http://sangareddy.telangana.gov.in/census-2011/

The left lane collides with the right(incoming traffic) in the north. Might want to recheck.

Could you recheck the National Highway connections? The roads seem to be colliding.

Oh. That’s the municipal boundary and is correct. Renaming the relation to Hyderabad would exclude other suburbs that are in Hyderabad but isn’t part of the municipal corporation. The Hyderabad you’re referring to is the Hyderabad district - which should technically be the boundary of the city but that is not really considered as the city is growing rapidly and everyone wants the city label.

@reddox It is. Could you be a bit more precise?

Doesn't JOSM behave sluggish when you load so much of data at a time?

Having district in the name makes it easier to read, easy with nominatim and when you're trying to match with say wikidata. For example, Hyderabad(city node) is in Hyderabad District which is inside Hyderabad municipal limits. So, there you go.

About the boundary load, if you don't include the al2 as part of the query, the overpass doesn't include the al2 relation. Still yet to figure out how to solve this as overpass times out when I load al2 as well. Right now I'm doing it in parts so that things don't break.

Erm. Not really. The ways are about 8 years old. Gujarat has 33 districts in total only 22 have been done. And of which some have been further split into smaller districts. It will be complete in a week perhaps. :)

Found why al2 broke. I didn't include al2 while running the overpass query.

Oh! Very strange. I didn't touch al2 of india and had only made a few al5 changes. JOSM didn't trigger anything about it as well. I'll be more vigilant about this.

Jinal did tell me about the missing al5's in India and I'm one of the volunteers filling in the gaps. And, no, I don't work with MB. :)

Kartiwar,

This isn't your personal map. Please don't ruin the map for everyone else.

Aditya

Hi. Just checking. Is this an import?
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/56121116

Thanks, Arun.

I know. It's been eons. :D

Also, on an other note, as we're talking about districts in telangana, there's an interesting issue to solve. Some of these boundaries cut through villages and towns(even according to bhuvan) but according to the mandal lists, they're not.

Well, it's tricky at this point. Here's why. The relations(or the names) can't be tagged with Bhuvan as the source because they're not. Only new ways/boundaries mapped are traced with the help of bhuvan georss. And the district work is a part of some 80+ changesets with 25-30days of work. It'll be hard to dig them up and tag, wouldn't it be? How would you suggest solving this?

Sure Srihari. I grew up here. So, had to take it up.

Here are my sources:
For new boundaries - I used a georss feed from bhuvan for telangana(mar 2017 file) to trace the new boundaries changes manually on josm and state portal maps.

For boundary relation mapping - used telangana state portal to make sure I got them right

For admin centre mapping and right naming - wikipedia list of telangana districts

Aditya

Micheal,

The tool I'm currently using is https://osm.wikidata.link/ (github: https://github.com/EdwardBetts/osm-wikidata/). The matcher looks through several aspects on both ends(OSM and Wikidata) and showcases me how it has matched and how apt it is. I've been tagging places only when I'm confident of the match and leave several when I'm not sure, to the community. So, I believe I've not been violating any CoC. But I hear you. Looping in @Edward, who wrote the tool to answer you better on this.

Aditya Thoomati