[ckan-discuss] Conventions for Location related extras (Was Geographic Metadata)

Tue May 31 13:03:19 BST 2011

I don't really have anything to say about this apart from, it sounds
like the right thing to me :)

And I don't see why this couldn't replace the current country
convention, which would seem redundant if we implemented this.

Seb

2011/5/31 Adrià Mercader <amercadero at gmail.com>:
> I'm bumping this and updating the topic of this discussion because I'd
> like to hear your thoughts about it.
> There were different things being discussed on the previous thread,
> and I would like to focus this one only on how to store location
> related information in a package.
> If I'm not mistaken, the only related current convention is to create
> a tag country.{2 digit ISO code} (please do correct me if I'm wrong).
> This sounds fine for me, and I think it can be used in parallel to my
> proposal, but we need a more generic mechanism, that supports
> different level (cities, regions) and machine-friendly formats
> (geojson/wkt/...) to make the data useful.
> I'm thinking of three possible extras (I don't really mind about the
> names: extent, location, geo...).
>
> * extent-text: The textual representation of the extent of the package
> We could discuss recommending a controlled vocabulary or allowing free text
>
> * extent: The geographic representation of the extent of the package
> Probably GeoJSON, but also worth considering WKT
>
> * extent-ld: A Linked Data link
> I'm not really an expert on this side, but I guess it could be
> something like http://www.geonames.org/2635167/about.rdf ?
>
> None of them should be mandatory per se, but some of them might be for
> certain functionalities, e.g. if you wanted the package to show up in
> spatial queries the "extent" extra should be present.
>
> This is also compatible with other tags / extras like the ones Tim was
> suggesting for continents.
>
> I'm not entering on how to add or populate this extras (via form,
> harvesting, etc), just discussing which ones they should be and how
> should they be named.
>
> Cheers,
>
> Adrià
>
>
>
>
>
>
>
> 2011/5/24 Daniel Dietrich <daniel.dietrich at okfn.org>:
>> Hi all,
>>
>> an dto take it one step beyond: Could we get clarification where the lists of
>>
>> catalogues, competitions, organisations, events
>>
>> will be maintained and updated in the future?
>>
>> All of them in CKAN? or only catalogues in CKAN? What is the plan?
>>
>> a bit lost here
>> Daniel
>>
>> On 24.05.2011, at 10:32, Maurizio Napolitano wrote:
>>
>>> Il 05/22/2011 07:26 AM, Tim McNamara ha scritto:
>>>> I'm most of the way through moving the data catalogues at
>>>> opengovernmentdata.org <http://opengovernmentdata.org> to CKAN.
>>>
>>> I agree with Daniel Dietrich that I create a script that reads frthe data catalogues at opengovernmentdata.org (google docs) and creates a map with OpenLayers and OpenStreetMap as background.
>>>
>>> From this email I suppose it is better to wait?
>>>
>>> In the list there are also events, competitions, organisations
>>> So you are planning to include this data too?
>>> My opinion:
>>> events, competitions => transform into georss
>>> catalogs, organizations => transform into geojson
>>>
>>> _______________________________________________
>>> ckan-discuss mailing list
>>> ckan-discuss at lists.okfn.org
>>> http://lists.okfn.org/mailman/listinfo/ckan-discuss
>>
>>
>> _______________________________________________
>> ckan-discuss mailing list
>> ckan-discuss at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/ckan-discuss
>>
>
> _______________________________________________
> ckan-discuss mailing list
> ckan-discuss at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-discuss
>

-- 
skype: seb.bacon
mobile: 07790 939224
land: 01531 671074
web: http://baconconsulting.co.uk