Data is available in different data types and formats. Traditionally data was available as files. Nowadays data can be harvested from web services, download services and messaging and is available in databases. GeolinQ provides configurable datasources to access these variety of external datasources. Data can be imported from different formats or can be accessed directly by linking depending on the type of datasource.
Datasources in GeolinQ
GeolinQ offers five base datasource types to harvest, import or link external datasources and maintain datasets:
- Catalog: In a Catalog datasource class definitions are configured and datasets are maintained and stored. The configuration describes the needed data and meta-data structures. Based on this configuration datasets are created, maintained and extended. Point clouds, raster images, feature/vector data and administrative data can be imported from files into a catalog datasource. An example of the use of the catalog datasource is given in the Seamless Point Surface tutorial on GeolinQ support.
- WFS: WFS datasource generates the GeolinQ object classes and datasets from the WFS feature type definitions of an external WFS. The data harvested from the external WFS is stored in the generated GeolinQ datasets. Information (in Dutch) concerning WFS as GeolinQ datasource is available via WFS tutorial on GeolinQ support
- GML/XML: A GML/XML datasource generates the GeolinQ object classes and datasets from the XSD. The data imported from GML/XML files is stored in the generated GeolinQ datasets. Examples are the Dutch standards BRK, BAG and Stuf-TAX datasources.
- WSDL: Link a WSDL webservice and generate the GeolinQ object classes and datasets from the webservice. The webservice can be linked anddata harvested. An example of WSDL services are the BRO datasource themes.
- Databases: A database datasource generates the GeolinQ object classes and datasets from the data dictionary of an external database (e.g. Oracle or PostgreSQL). The data in the external database can be accessed via GeolinQ datasets that are linked to the remote database tables.