Why use glottolog:geospan ?

[GoogleCodeExporter]

What steps will reproduce the problem?

curl -L -H "Accept: application/rdf+xml" 
http://glottolog.livingsources.org/resource/languoid/id/tuva1238 | grep 
'glottolog:geospan'

What is the expected output? What do you see instead?

Output:
<glottolog:geospan> 179.16999999999999, 179.16999999999999, -8.5, -8.5 
</glottolog:geospan>

Comment:
glottolog:geospan is glottolog pacific type will NOT be understandable by 
others, why don't use some will defined type like GeoRSS 
http://dbpedia.org/page/GeoRSS

How many triples are affected? (if less than 3-5% of the whole data set,
please set priority to _low_)

Please use labels and text to provide additional information.

Original issue reported on code.google.com by mohamedd...@gmail.com on 26 Jul 2012 at 1:53

[GoogleCodeExporter]

Glottolog uses wgs84, but this was not displayed properly in the RDF. Does 
display now. 
Geospan is used for a rectangle of maximal E-W and N-S extension. I am not 
aware of any RDF spec for this, but I would be happy to hear more about this. 
There is Dublin Core bounding box (see comments in RDF), but this does not seem 
to have an RDF version, and the use of "value" seems very unsatisfactory there. 

Original comment by sebastia...@googlemail.com on 27 Jul 2012 at 1:19

[GoogleCodeExporter]

Sherif, please verify.

@RavenArkadon: is there a vocabulary for bounding boxes? What does LGD use?

Original comment by kur...@googlemail.com on 27 Jul 2012 at 1:48

• Changed state: Fixed
• Added labels: Type-Defect

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

See section 3.1.2 Bounding box
http://geovocab.org/doc/survey.html

Original comment by mohamedd...@gmail.com on 30 Jul 2012 at 12:59

[GoogleCodeExporter]

now uses bounding box as suggested

Original comment by sebastia...@googlemail.com on 30 Jul 2012 at 2:33

[GoogleCodeExporter]

Original comment by mohamedd...@gmail.com on 31 Jul 2012 at 10:06

• Changed state: Hosted

[GoogleCodeExporter]

reopened:
bugsbugsbugs *whitespaces*:
    <geo:long> 179.17 </geo:long>
    <geo:lat> -8.5 </geo:lat>
should be
    <geo:long>179.17</geo:long>
    <geo:lat>-8.5</geo:lat>

2. Claus should comment on the bounding box vocab. 

Original comment by kur...@googlemail.com on 31 Jul 2012 at 1:05

• Changed state: FixNeededByOwner

[GoogleCodeExporter]

Claus comment on the bounding box as OK

Original comment by mohamedd...@gmail.com on 31 Jul 2012 at 2:15

[GoogleCodeExporter]

whitespace fixed

Original comment by sebastia...@googlemail.com on 2 Aug 2012 at 8:15

• Changed state: DatasetAccepted

[GoogleCodeExporter]

Everything seems to be correct. What about 
<fao:hasMinLongitude>179.17</fao:hasMinLongitude>
<fao:hasMaxLongitude>179.17</fao:hasMaxLongitude>
<fao:hasMinLatitude>-8.5</fao:hasMinLatitude>
<fao:hasMaxLatitude>-8.5</fao:hasMaxLatitude>

in http://glottolog.livingsources.org/resource/languoid/id/tuva1238.rdf
Is it correct that the bounding box is just a point?
If this is intended, we can set this issue to "Verified".

Original comment by mohamedd...@gmail.com on 15 Aug 2012 at 12:18

• Changed state: Fixed

[GoogleCodeExporter]

The bounding box is the minimal rectangle that comprises all sublanguoids with 
geoinformation. Geoinformation is a point, not a polygon. In this particular 
case, the relevant set is of cardinality 1, so the resulting rectangle has all 
four corners on the same point. Min=max in this case. 

If the set is of cardinality greater than one, the bounding box has different 
values for min/max, e.g. the superlanguoid of tuva1238

http://www.glottolog.org/resource/languoid/id/elli1236.rdf
has

<fao:hasMinLongitude>
154.67
</fao:hasMinLongitude>
<fao:hasMaxLongitude>
179.17
</fao:hasMaxLongitude>
<fao:hasMinLatitude>
-8.5
</fao:hasMinLatitude>
<fao:hasMaxLatitude>
3.83
</fao:hasMaxLatitude>

Original comment by sebastia...@googlemail.com on 15 Aug 2012 at 12:42

[GoogleCodeExporter]

Original comment by mohamedd...@gmail.com on 15 Aug 2012 at 1:24

• Changed state: Verified