You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The existing methods of extracting of geographical information from schema.org documents does not meet the standards of the SOSO guidelines on describing Spatial Coverage. The beans that do this work are highlighted below. At the moment, it seems like we only support spatialCoverage sections similar to the following:
Since we claim to support all of the representations of schema.org outlined in the SOSO guidelines, we need to be able to support a broader range of spatialCoverage information as outlined in that document. For example, the following is a valid representation from a dataset with a point location, which I think should also be fairly straightforward to support:
I have no experience with SPARQL apart from looking through the resource document referenced above so would be coming at this from square zero...if someone else has some idea of what they're doing, I would appreciate some guidance :)
The text was updated successfully, but these errors were encountered:
The existing methods of extracting of geographical information from schema.org documents does not meet the standards of the SOSO guidelines on describing Spatial Coverage. The beans that do this work are highlighted below. At the moment, it seems like we only support
spatialCoverage
sections similar to the following:dataone-indexer/src/main/resources/application-context-schema-org.xml
Lines 458 to 577 in 1ad4183
Since we claim to support all of the representations of schema.org outlined in the SOSO guidelines, we need to be able to support a broader range of
spatialCoverage
information as outlined in that document. For example, the following is a valid representation from a dataset with a point location, which I think should also be fairly straightforward to support:I have no experience with SPARQL apart from looking through the resource document referenced above so would be coming at this from square zero...if someone else has some idea of what they're doing, I would appreciate some guidance :)
The text was updated successfully, but these errors were encountered: