- From: Patrick Durusau <patrick@durusau.net>
- Date: Fri, 09 Sep 2011 10:45:32 -0400
- To: public-lod@w3.org
- Message-ID: <4E6A268C.5020102@durusau.net>
Kingsley, On 09/09/2011 10:20 AM, Kingsley Idehen wrote: > On 9/9/11 8:58 AM, Leigh Dodds wrote: >> Hi, >> >> As well as the others already mentioned there's also Yahoo Geoplanet: >> >> http://beta.kasabi.com/dataset/yahoo-geoplanet >> >> This has multi-lingual labels and is cross-linked to the Ordnance >> Survey data, Dbpedia, but that could be improved. >> >> As for a list, there are currently 34 geography related datasets >> listed in Kasabi here: >> >> http://beta.kasabi.com/browse/datasets/results/og_category%3A147 > > Leigh, > > Can anyone access these datasets or must they obtain a kasabi account > en route to authenticated access? > Been a while. ;-) From the Kasabi FAQ: > Why do you require API Keys? > > An important part of Kasabi is letting data providers explore the > potential (commercial and utility) of their data. API Keys let us > track the actual usage of each dataset and API, giving us the ability > to provide stats to the data providers and curators. With these stats, > they are in a better position to understand how their data is being > used, and to what extent it's being picked up. > also relevant: > Can I download a dataset? > > No. Kasabi is a hosted service, and downloading data isn't a feature > we're planning to support. The reasoning behind this is partly for > data providers to be able to see how their data is being used, and > partly because we see Kasabi's role in curation as being a valuable > aspect of the marketplace. We can't keep download versions up to date, > for example. Data providers may make datasets available for download > on their own terms, but not via Kasabi. > Hope you are looking forward to a great weekend! Patrick > Kingsley >> Cheers, >> >> L. >> >> On 8 September 2011 15:38, M. Scott >> Marshall<mscottmarshall@gmail.com> wrote: >>> It seems that dbpedia is a de facto source of URIs for geographical >>> place names. I would expect to find a more specialized source. I think >>> that I saw one mentioned here in the last few months. Are there >>> alternatives that are possible more fine-grained or designed >>> specifically for geo data? With multi-lingual labels? Perhaps somebody >>> has kept track of the options on a website? >>> >>> -Scott >>> >>> -- >>> M. Scott Marshall >>> http://staff.science.uva.nl/~marshall >>> >>> On Thu, Sep 8, 2011 at 3:07 PM, Sarven Capadisli<info@csarven.ca> >>> wrote: >>>> On Thu, 2011-09-08 at 14:01 +0100, Sarven Capadisli wrote: >>>>> On Thu, 2011-09-08 at 14:07 +0200, Karl Dubost wrote: >>>>>> # Using RDFa (not implemented in browsers) >>>>>> >>>>>> >>>>>> <ul xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" >>>>>> id="places-rdfa"> >>>>>> <li><span >>>>>> about="http://www.dbpedia.org/resource/Montreal" >>>>>> geo:lat_long="45.5,-73.666667">Montréal</span>, Canada</li> >>>>>> <li><span >>>>>> about="http://www.dbpedia.org/resource/Paris" >>>>>> geo:lat_long="48.856578,2.351828">Paris</span>, France</li> >>>>>> </ul> >>>>>> >>>>>> * Issue: Latitude and Longitude not separated >>>>>> (have to parse them with regex in JS) >>>>>> * Issue: xmlns with<!doctype html> >>>>>> >>>>>> >>>>>> # Question >>>>>> >>>>>> On RDFa vocabulary, I would really like a solution with geo:lat >>>>>> and geo:long, Ideas? >>>>> Am I overlooking something obvious here? There is lat, long >>>>> properties >>>>> in wgs84 vocab. So, >>>>> >>>>> <span about="http://dbpedia.org/resource/Montreal"> >>>>> <span property="geo:lat" >>>>> content="45.5" >>>>> datatype="xsd:float"></span> >>>>> <span property="geo:lat" >>>>> content="-73.666667" >>>>> datatype="xsd:float"></span> >>>>> Montreal >>>>> </span> >>>>> >>>>> Tabbed for readability. You might need to get rid of whitespace. >>>>> >>>>> -Sarven >>>> Better yet: >>>> >>>> <li about="http://dbpedia.org/resource/Montreal"> >>>> <span property="geo:lat" >>>> ... >>>> >>>> >>>> -Sarven >>> >> >> > > -- Patrick Durusau patrick@durusau.net Chair, V1 - US TAG to JTC 1/SC 34 Convener, JTC 1/SC 34/WG 3 (Topic Maps) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau
Received on Friday, 9 September 2011 14:46:01 UTC