[ckan-dev] geo data modelling

Mon Nov 25 10:30:00 UTC 2013

hello all,

i have a data model design question for the geo-aware folks:

i find the current way of storing W*S services in the CKAN model not
adequate, in the sense that OGC resources (feature types, layers, ...)
don't get captured.
Rather, whole services are mapped into datasets, with resources containing
capabilities, legend, and so forth.

Wouldn't it be better to
    - have a dataset per OGC service, and then a resource per layer/feature
type
or  - have a dataset per layer/feature type, as these deserve metadata on
their own, and then a 'related' link to the service dataset

does anyone else feel that need?
are there any plans for something like that?

thanks,

Philippe Duchesne
OKFN.be
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20131125/fc07fa65/attachment-0002.html>