Discuss India here
The major addressing problem in India
As some of you may have noticed (hopefully), India does not have a street + housenumber addressing system unlike most western countries (Most of europe, Russia, USA etc.). Instead, rural areas generally have housenames and more urban areas have different types of addressing. For example, one type of addressing system (which I have seen in cities such as mumbai and pune) is using "housing societies", plots of lands containing multiple buildings. Buildings within this society has given house numbers (and sometimes building names). This can be mapped in OSM but currently there is no consensus on how it should be done.
A building within a society can be mapped as addr:place=SOCIETYNAME & addr:housenumber=3 However there is no specific tags for such societies. The closest I could find is place=neighbourhood. This creates problems because this a unconventional addressing system that is not supported by most OSM search engines. In real life, a full address is written, e.g. Foobar Building, Survey number 12/2, Foobar Society, Some "nagar" (addr:suburb), some city. This can clearly be represented using "ADDR:FULL" but again there is absolutely no consensus on this so it is not used anywhere.
To add to the confusion, sometimes "Survey Numbers" are introduced. So the "plot number" is the number given to the building within a housing society (plot number + society name) and "survey number" too? Which one should go in the addr:housenumber tag? (As a side note, what are survey numbers? I couldn't find anything on the internet except the "survey of india" which explained nothing.)
Why does it create a problem?
Because all the current OSM geocoders simply do not work with addr:place. If for example, a place is tagged addr:housenumber=3 & addr:place=foobar_place, nominatim shows "3,nagar,city". But if a place is tagged addr:housenumber=3 & addr:street=foobar_street, nominatim shows, "3 foobar street, nagar, city". So you can't search using addr:place, it doesn't work with nominatim and other osm geocoders. Google maps gets around this by only showing the full address, and its geocoder is so powerful that when you do a search it can pick out the fact you are searching for that specific building. However, osm geocoders are nowhere near as powerful, and require a exact match. So if you search "Something Co-operative Housing Society" and the name in osm is "Something CHS", nominatim won't get you the result, while Google Maps would.
Since osm's geocoders are not that powerful, we have to think of a system that is both geocoder friendly, but searchable too.
Here is steps I think the OSM India community needs to take:
1. Figure out all the different addressing systems that are used in India but are not used in Europe/America (I only mentioned a system I found in Mumbai, Pune and Goa. I have no idea how this works in Bangalore for example.) 2. Decide as a community on what tagging schemes fit these Indian addressing systems. This can be done using a vote, like all proposals in osm 3. Propose missing tags (e.g. place=society) 4. Update WikiProject India page on addressing. 5. After doing step 2, the OSM India community can also start raising awareness of lack of support for indian tagging schemes in their github issue pages. (here is nominatim's) 6. I think some steps need to be taken to point people on how to tag addresses in india properly. For example, in the id editor steps are taken to make addressing involving street names easy, but I think steps to make Indian addressing possible should be made. Again this can be voted on later by the community, and then can be proposed on the iD editor's github page.
Of course, all of this will take work and support for the community, but I think if it is pulled of it could be well worth it, delivering decent open-data maps to indian users with a internet connection - a huge benefit.
P.S If any one of you have additional necessary/useful steps, feel free to edit the list yourself. P.S.S If anything seems unclear to you (i'm not the greatest explainer), just ask and i'll try to clarify and fix the error in my proposal
JOSM isn't currently translated in any language spoken in India (except English, of course). We'd love to see this situation improve. 2000 core strings must be translated for a new language to be added. Marathi is the language the most advanced with about 500 strings translated. Bengali and other languages have no translation at all. We'd love to see the Indian community complete these translations so we could add new languages to JOSM. See JOSM wiki for details and Launchpad to translate more strings. --Don-vip (talk) 02:06, 12 May 2018 (UTC)
How to tag small general store?
Those small stores, selling everything ranging from food such as fruits and vegetables to crisps to kitchenware etc (those were the things that came off the top of my head.)
Whoever is mapping bangalore, please try to increasing the logging frequency, If you are riding a bike or driving a car, 1 sec between points is really good. -- User:Sarath.email@example.com - 20:24, 1 October 2006
Agreeing on tagging standards for India
here has been quite a bit of mapping progress in various indian cities by a small bunch of dedicated mappers and its about time we all came together and set common mapping guidelines for future development -- PlaneMad|YakYak 08:07, 13 October 2008 (UTC)
Suggest and discuss features that is unique to india
en:name is incorrect
Using "en:name" for the English name of an entity as described in the Naming section is incorrect. It should be "name:en" instead. See http://wiki.openstreetmap.org/wiki/Map_Features#Naming. --Sunil Mohan 19:13, 4 March 2009 (UTC)
Use English for the "name" tag
I've edited the Naming section to indicate that the "name" tag should be in English, with "name:lang" for local languages. The section previously suggested the reverse, which is bad practice for the following reasons:
1. OpenStreetMap.org displays only the "name" tag. If all of India is tagged in the local script, most Indians will be unable to read the map. This does not help anyone.
2. English is the most widely accepted language in India, while Hindi has the most speakers, but not all over India. Therefore, English is the best candidate for tagging.
3. From personal experience, most computer users are not comfortable with keyboard entry in the local language script, even if they prefer speaking the local language. A quick overview of OSM's India coverage suggests this applies to OSM editors too, as nearly everything is tagged with the Roman alphabet. We might as well recognise this fact.
4. Mapnik has traditionally had difficulty with rendering Indic scripts. This ruins the map. While this is an area requiring and receiving some attention, it's not ready to go on the live OSM site. (Someone please correct this if things have improved.)
Finally, local language data is important, so by all means please add "name:lang" tags where you can. We should however reserve that data for special bi/multi-lingual renderings.
-- Kiran Jonnalagadda 20:46, 30 September 2009 (UTC)
- Im using the local language of the state and mentioning the english name in brackets. Hope that is fine till we have language tiles. Also setting name:lang anyway. -- thevikas 02:25, 7 December 2009 (UTC)
- Okay thanks for that. I thought mapping in the language that I saw written when surveying was best, but now I will tag in English. --ADepic (talk) 14:51, 30 July 2018 (UTC)
Misaligned Landsat and Yahoo tiles
Has anyone else noticed these? Particularly in southwest Karnataka and northern Kerala. Some tiles are a few hundred metres off to the south. Indigomc 09:33, 8 March 2010 (UTC)
Karnataka, Srirangapattna. SH17 bridge over Kaveri. Google sat reports the centre of the bridge at 12.424342,76.693838. Yahoo sat, out by about 50-100m on the north bank. Actual location of the road is confirmed by gpx tracks.
Railway bridge over Kaveri near this location. Google sat centre of the bridge at 12.422194,76.675041. Yahoo sat; out by about 100m.
Karnataka, Kaveri river by Kushalnagar. Centre of bridge on SH88. Google maps show this spot as 12.448291,75.970303 Yahoo sat; the above spot is shown as a location about 175-200 metres to the northwest. Landsat; the river may be shown closer to the actual spot. Around 50m to the northwest, though I'm not certain of this. Lots of gpx tracks here to confirm this, the location of the bridge can be seen, it is clearly to the northwest of the location seen on the Yahoo sat.
Kerala, Iritty. South bank of the river under the bridge for the road leading north from Iritty. Google maps 11.99137,75.679833 Landsat and Yahoo; this spot is shown as being about 300 metres away, on the north bank of the river. No gps tracks here.
Note that google sat pics also show what seem to be misaligned tiles to the east of Iritty.
Indigomc 10:22, 8 March 2010 (UTC)
Karnataka, river crossing just east of Bantwal Cross Road. Centre of bridge on NH48 across the Netravati. Google maps report that coords are 12.880009,75.041488, seems to be confirmed by gps tracks. This location on Landsat is shown on the east side of the river; offset by 50-100m in an eastward direction. The river seems to be correctly drawn on OSM.
Kerala, river to the south of Cherkala, e.g. the bridge at 12.493819,75.05657 (Google and OSM). This is off by at least 250m on Landsat. Indigomc 16:32, 8 March 2010 (UTC)
Adding shop icons
(This section moved from the project page, pending a new location; Indigomc 21:02, 11 May 2011 (BST))
To add new icons for shops. First open inkscape, make the page size 16px x 16px and draw your icon. Save it as png with a reasonable name. Then open it in Gimp, select the blank areas with shift clicking the magic wand. Click on edit-clear and save as png. This will make the background transparent. then put the png file in the symbols/ directory of osmindia and do
- hg add symbols/yournewfile.png
You need to modify the osm-template.xml file in three places in order for your new shop and text to appear. Here are excerpts from that file: 1.
<Rule> <Filter>[shop]= 'computer' or [shop]='bakery' or [shop]='electronics' or [shop]='convenience' or [shop]='tea' or [shop]='alcohol' or [shop]='electricals' or [shop]='furniture' or [shop]='department_store' or [shop]='confectioner' </Filter> <MaxScaleDenominator>5000</MaxScaleDenominator> <TextSymbolizer name="name" face_name="unifont Medium" size="8" fill="#0092da" dy="10" halo_radius="1" wrap_width="5"/> </Rule>
in this you add 'or [shop]='whatever'
<Style name="computer"> <Rule> <Filter>[shop]='computer'</Filter> <MaxScaleDenominator>5000</MaxScaleDenominator> <PointSymbolizer file= "%SYMBOLS_DIR%/computer.png" type="png" width="16" height="16" allow_overlap="yes"/> </Rule> </Style>
substitute the appropriate names
<Layer name="shops" status="on" srs="+proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 +x_0=0.0 +y_0=0 +k=1.0 +units=m +nadgrids=@nul+no_defs +over"> <StyleName>computer</StyleName> <StyleName>bakery</StyleName> <StyleName>electronics</StyleName> <StyleName>convenience</StyleName> <StyleName>tea</StyleName> <StyleName>alcohol</StyleName> <StyleName>electricals</StyleName> <StyleName>furniture</StyleName> <StyleName>department_store</StyleName> <StyleName>confectioner</StyleName>
add the new StyleName here
hg commit and hg push will send it to the repository, then wait for it to render.
requesting help for the tagging of Ghats
I recently posted a question to help.openstreetmap.org and I thought that people here might take an interest: how to tag Ghats? Please give your input if you have some. Thanks!
Removing "WikiProject" prefix
The name of the pages related to the India mapping project would be "India" (name of place) instead of "Wikiproject India", as recommended by the wiki conventions. It is a change that I have already made in United States, Canada, Spain, Australia, New Zealand, South Africa, Denmark, Norway, United Kingdom, Italy, Germany, and all Spanish-speaking countries on this Wiki (and more).
Hello Dcapillae, following pages have to be changed
- I support the renaming in favour of being consistent with the conventions followed in the wiki --Planemad/Talk 10:38, 23 August 2019 (UTC)