A Geospatial Source Selector for Federated GeoSPARQL Querying - Datasets

Open data API in a single place

Provided by Zenodo

Get early access to A Geospatial Source Selector for Federated GeoSPARQL Querying - Datasets API!

Let us know and we will figure it out for you.

Dataset information

Catalog

Zenodo catalog

Country of origin

EU institutions

Updated

2022.03.10 00:00

Created

2022.03.09

Available languages

English

Keywords

Federated and distributed query processing, Linked geospatial data, Source selection, GeoSPARQL query processing

Datasource

Official portal for European data link

Quality scoring

Dataset description

This dataset comprises of a set of individual RDF files. It contains 3 data layers that cover Austria (namely Administrative data, Snow cover data, and Crop-type data), and each layer is also divided geospatially. Thus, each RDF file contains only one thematic layer and refers to a specific area. This data can be used in the context of experimenting with federated query processors. Thus, if we deploy each RDF file in a separate GeoSPARQL endpoint, we will have a resulting federation of 34 GeoSPARQL source endpoints. The objective of this scenario is to evaluate the effectiveness of a source selection mechanism of a federation engine, and, in particular, if the source selector is aware of the geospatial nature of the source endpoints.

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

countries and EU institutions

2019

API-first since

Free API quota

for evaluation and prototypes

SLA

history and push on production APIs

FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.

Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.

Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.

Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.

Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

api.store Built by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacy Terms of Service