Convert to datapackage about ocd-division-ids HOT 6 CLOSED

Most users just use the single compiled CSV for their country, which is easy to maintain by just downloading the latest version. Perhaps a third-party data package could be maintained?

from ocd-division-ids.

You mean one per country? Or still one with all countries, but just the CSVs and metadata?

from ocd-division-ids.

For example, I only use this file: https://github.com/opencivicdata/ocd-division-ids/blob/master/identifiers/country-ca.csv

I don't use the individual files in https://github.com/opencivicdata/ocd-division-ids/tree/master/identifiers/country-ca

from ocd-division-ids.

Ah gotcha. I'll admit that one thing I really liked about the datapackage philosophy was that it seemed to encourage the co-location of the data and the scripts from which the data is massaged/derived.

Any preference on that yourself, or are you just as happy to have the data live on its own in a datapackage repo?

from ocd-division-ids.

Isn't this repo already in a situation where the scripts and data are collocated? (They are in the same repo.)

from ocd-division-ids.

Def. The original ask was whether it would be worthwhile to add a datapackage.json describing the data :)

But I suppose until this data is in a CKAN portal somewhere, having that metadata isn't much value-add for the effort. So I'll just close until such a time. Sorry for the noise on this one

from ocd-division-ids.