Interfacing with external datasources
Organisations are using often data from external datasources like databases, REST, WFS or SOAP services. GeolinQ can easily interface with these external datasources and is using the datastructure of the external datasource in order to generate automatically datasets in GeolinQ. The data of the external datasource is harvested or linked to the datasets in GeolinQ. The data of the external datasource is further disclosed in views, maps and dataservices.
Currently GeolinQ supports the following external datasource by the interfaces:
|Database||Retrieve data from a PostGress or Oracle database|
|REST||Retrieve data from a REST API using JSON of XML import formats|
|WFS||Retrieve features from an external WFS service.|
|SOAP||Retrieve data from an external SOAP service using the WSDL definition|
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.
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
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.