[ckan-dev] geo data modelling

Mon Nov 25 10:40:26 UTC 2013

hello phillip,

we implemented a mapping between ogc resources and ckan objects. it is
relevant, that you map a dataset as dataset and the corresponding services
as resource endpoints. you may have a look at http://www.govdata.de.
in the ogc metadata concept, there is a relation from the service content
(layer/featuretype) to one or more dataset metadata. if you don't have the
relation, you may map a fictive layer/featuretype as a dataset object.
the problem with the ogc metadata is, that the relations are not well
maintained or don't exists. maybe the EU INSPIRE Directive will produce
more consistent metadata in this point of view.

if you have further questions or need some practical examples please ask
;-)

hope this helps a little bit

regards
armin

2013/11/25 Philippe Duchesne <philippe at okfn.be>

>
> 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
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20131125/b90a7675/attachment-0003.html>