Skip to content

Search imloka

No results for “{{query}}”

Try:

  • using fewer words
  • a broader topic
  • checking the spelling

Related topics

Some results are missing. Stories loaded, but topics and authors did not answer. What is shown below is complete for stories.

Search is temporarily unavailable

You can still browse by topic, format, or place while we sort this out.

Explore all coverage

Business Analysis

A Decade After the First Municipal Open Data Portal, Researchers Still Cannot Answer the Simplest Questions About Who Actually Uses It

Ten years of publishing, and almost no measurement of whether any of it was read.

The first municipal open data portal in the country went live in 2015 with 41 datasets and a launch event. It now holds 2,847. Nobody involved can tell you, with any confidence, how many of them have ever been used for anything.

This is not a scandal. It is something more ordinary and harder to fix: a decade of institutional effort aimed at a goal that was never operationalised.

What “open” came to mean

The original commitment was specific: publish machine-readable data, under an open licence, without registration. By that standard the programme succeeded almost completely. Roughly 94 percent of the catalogue meets all three conditions.

The trouble is that those three conditions describe a publishing practice, not a usability one. A CSV with undocumented column headers, no update schedule, and no contact address satisfies every letter of the commitment and is nearly useless to anyone outside the department that produced it.

Published, but not documented

Share of the 2,847-dataset catalogue meeting each condition. Publishing rules are met almost everywhere; the conditions that determine whether a dataset can be used are met far less often.

Share of datasets meeting each condition Machine-readable 94 percent, open licence 91 percent, no registration required 88 percent, documented columns 31 percent, stated update schedule 22 percent, named contact 9 percent. Machine-readable 94% Open licence 91% No registration 88% Documented columns 31% Update schedule 22% Named contact 9%
Source: imloka analysis of the municipal catalogue, August 2026. Conditions assessed programmatically; documentation assessed by sampling 300 datasets.

Nobody counted the readers

Download counts exist. They are also close to meaningless: a scheduled scraper hitting a file nightly for four years produces 1,460 downloads and zero uses.

What the next decade would need

The programme's own staff are, on this point, considerably more candid than its annual reports. Three of the four data officers interviewed independently named the same first step: stop counting datasets.

“Two thousand eight hundred is not an achievement,” one said. “It is an inventory. An achievement would be forty datasets that somebody outside this building depends on, and knowing which forty.”

End of article

Coverage Business Analysis

About the author

Vijay Singh

Staff Writer, Technology

Writes about civic technology, data infrastructure, and the gap between publishing something and making it usable.

Advertisement Loading…

Continue exploring

Discussion 19 comments

Shobha Rangappa Pinned 3 hours ago

Nineteen public consultations and counting. The treatment-plant utilisation number is the one nobody publishes, and it is the only one that would tell you whether any of this works.

Vijay Singh Author 2 hours ago

They published it at 4:15pm. I've added it to the piece as an update rather than a correction, since nothing in the original was wrong; it was simply unanswered.

Vasanthi Kumar 5 hours ago

The cascade point deserves more attention than it usually gets. Restoring a lake in isolation is a real improvement to that lake and almost nothing to the system.

Comment removed

A. Menon 6 hours ago

Even so, the diversion drains are doing something; they buy time while the plants get built.

Stay in the loop

The week's best reading from imloka, in one email. No noise.

Sign in to continue

This action needs an account.

imloka uses a federated or passwordless sign-in. Creating a password is not required.