Coverage, honestly

Why it is thin

The one category open mapping does well. A derasar is a building with a name on a street, so a passing mapper can record it without knowing anything about Jainism — which is why we have hundreds of them and why most carry nothing but a name.

What would fix it

Not more records — better ones. Timings and a telephone number for the temples already listed, which only the trust holds.

Why it is thin

The starkest gap on the site, and it is structural rather than accidental. A sthanak is often an upper floor, a hall inside a housing society, or a room attached to a residence — it has no shopfront and no signboard a mapper would photograph. Nothing about it says "map me" to a stranger walking past.

What would fix it

One person at each sthanak, once. This is the single category where the community can add more in a month than any amount of research could in a year — nobody outside the sangh knows these exist.

Why it is thin

Community halls and bhavans are usually recorded as somebody's address rather than as a public place, and many share a building with a derasar that is mapped instead. The hall exists; the map has no reason to know it is separately bookable.

What would fix it

A line from whoever takes the bookings — capacity, whether there is a kitchen, and who to ring.

Why it is thin

A dharamshala is not a hotel and does not advertise like one. It takes bookings by telephone through a pedhi office, so it appears in no booking platform and on almost no map.

What would fix it

The pedhi office number and the booking rule, tirth by tirth. The tirth pages carry what we have and say plainly where we have nothing.

Why it is thin

Restaurants tagged as Jain food in open data are mostly commercial kitchens in large cities. The bhojanshala attached to a derasar, which is what a travelling family actually wants, is almost never tagged at all.

What would fix it

Bhojanshala timings from the trusts that run them — and confirmation of what the kitchen actually observes, which no dataset records.

Why it is thin

Empty, and it always will be from open data — because it is not a fact about a building. Where sadhus and sadhvijis are staying changes with every vihar, and only the sangh hosting them knows. No map can hold this; a community can.

What would fix it

Institutions posting it themselves, which is an app feature and is not built. Until then this section will stay honestly empty rather than showing stale information about where a sadhu was last month.

Why it is thin

The one category we did not leave to open data. The tirth kshetra pages were researched and written individually, which is why they are the deepest content on the site — and why there are only a few dozen of them.

What would fix it

Telephone numbers, mostly. Most tirths here have none, and that gap closes with phone calls rather than more web research.