Gujarat/Administrative Boundaries

Part of Gujarat mapping project.

Administrative Boundaries

Political Boundaries

Local Government Boundaries

Most tagging of boundaries is carried out in accordance with the table in Tag:boundary=administrative.

Boundaries should be marked on a containing way (for small areas) or a relation for larger areas. Administrative boundaries should be marked 'boundary. The admin level for each way or relation should be set according to the following table.

Naming in different scripts and languages

See also: Map internationalization

See also: Map internationalization (India)

India has many languages and writing systems. The community convention is to use the Roman alphabet ('English') for the name key, and to use the name in the local language for the name:xx key (where xx is the lowercase locale tag preferred for that language in the IETF BCP47 standard, based on ISO 639 language codes). Wherever possible, add the names in all languages that you can; this will make it possible to create maps in multiple languages.

For example, to name the city of Bengaluru (Bangalore), use the following keys and values:

Key	Value	Meaning
name	Ahmedabad	Default official name in English (or romanized Hindi)
name:gu	અમદાવાદ	Local official name in Gujarati
name:hi	अहमदाबाद	Local official name in Hindi
alt_name	Karnavati	Alternate wellknown name(s) in English

Where an official name exists, use it for the "name" key. If another name is more popular, it can be added using the alt_name key; in some cases it may be appropriate to place it in brackets after the official name. Sometimes the name:en or alt_name:en key may be used as well, notably if the international English name is better known than the national romanized name. For example, alt_name:en=Calcutta may be used along with the newer and preferred name:en=Kolkata, and will help improve searches by name, even if maps will preferably render the newer national official name for use in English (actually a better romanisation of the name in Hindi).

Do not use abbreviated names, especially for localities. If the abbreviated name is more popular, treat it as described in the previous paragraph: use the short_name key (append a language code suffix if needed, to match the same language as the one used for the unabbreviated name).

If multiple scripts are used in a name given using the name key, e.g. name=ग्वालियर (Gwalior), then this will cause problems when used on systems where both sets of fonts are not present. The fonts that the system cannot show will be shown as empty boxes, question marks, or other meaningless forms. Use name=Gwalior, and also name:hi=ग्वालियर.

If there are multiple alternate names, please avoid pasting them in the same name or name:xx key; but several names in the same language may be specified in alt_name=* or alt_name:xx by separating them with semicolons (;).

Mapping terminology

Most terms used as keys should be according the general guidelines, and different usage for India should be after discussion here. This section lists some terms specific to India, with preferred spellings when they are used.

Use the following terms;

• taluk - covers subdistricts with variable terms (taluka, tehsil, mandal) depending on each state or union territory
• panchayat - for panchayath
• district - for zilla etc.

Note that this refers especially to the key, not always to the value. So you can have the other usage in the value for names. So a district would be subdivided into areas tagged as 'taluk', but a taluk could be called 'xxx tehsil' or 'xxx mandal' or otherwise according to local usage. e.g. name="Daund taluka".

admin_level	Division type		Notes	Overpass data csv
	Rural	Urban
2	National borders of India		International standard
3	Zonal Council / North Eastern Council		Proposed
4	State / Union territory		Effective and stable
5	District (Zilla Panchayat)		Current use
6	Subdistrict (Tehsil / Taluka / Taluk / Mandal / Circle / Subdivision / Commune Panchayat)		Current use
7	Block/Revenue Circle			http://overpass-turbo.eu/s/LJ2
8				http://overpass-turbo.eu/s/LJ3
9	Revenue Village			http://overpass-turbo.eu/s/LJ5
10	Revenue Survey No			http://overpass-turbo.eu/s/LKs

One of our members had contacted Survey of India, and has received the clarification that Admin Boundaries till the Village layer can be freely used for commercial and non-commercial uses

Status of openstreetmap data in Gujarat

Administrative

• State Boundary
• District Boundary
• Taluk Boundary
   

  253 Subdistricts completed
• Revenue villages

Political

• Lok Sabha Constituencies
• Assembly Constituencies

Local Govt Bodies

Local Bodies in Gujarat

• Corporations
• Municipalities
• District panchayat
• Taluka panchayat
• Gram panchayat
• Local Wards in Gujarat