Skip to content

Latest commit

 

History

History
42 lines (31 loc) · 2.8 KB

README.md

File metadata and controls

42 lines (31 loc) · 2.8 KB
Raw

DWD-Provider for Koop

This provider makes it possible to access dwd's geoserver-WFS endpoints as either a raw geoJSONs output or an ESRI FeatureService. Because the geoserver already serves geojsons as an output, there is not that much magic about the internal procedure.

Installation

Perform the following steps to install the dwd-koop provider. Install koop including its dependencies.
Clone the repo
git clone git@github.com:Esri/koop.git
Enter the koop project directory
cd koop
Install koop-server and node.js dependencies
npm install
Install koop-dwd provider via
npm install https://github.com/schlomm/koop-dwd/tarball/master

Quick Go-Through

Checking the .js in the models-directory, you'll notice the dwd geoserver URL.: http://maps.dwd.de/geoserver/dwd/ows?service=WFS&version=1.0.0&request=GetFeature&typeName='+id+'&outputFormat=application/json

By replacing the id with the name of a service, you can access the different dataitems. Those need the "OpenLayers KML GML"- description as common format. Check DWD's Geoserver Layer Preview for available services.

If you want to access and process a DWD layer via koop and this koop-dwd provider, follow this URL schema, where id is the LayerID of a DWD Layer.

  • Raw GeoJSON: /dwd/id
  • FeatureService: /dwd/id/FeatureServer/0
  • Query: /dwd/id/0/query

Example request for DWD's Basiswarnungen:

  • Raw GeoJSON: your_server:port/dwd/dwd:BASISWARNUNGEN
  • FeatureService: your_server:port/dwd/dwd:BASISWARNUNGEN/FeatureServer/0
  • Query: your_server:port/dwd/dwd:BASISWARNUNGEN/0/query

Outlook

A timer will be needed, which checks and compares the cached and requested data. If they differ, the old cached data will be deleted and the updated data cached to the database. koop-dwd will be generalized later on, so all geoservers with geoJSON WFS-endpoints can be used. Until now, only dwd's geoserver is working.

Limitations

  • dwd's geoserver creates mixed geoJSONS, which are not supported by koop based on ESRI's REST specification. Currently there is no workaround for this issue. Check the koop-server issue for more information.
  • Once a service is was used, this is cached in the PostGIS database permanently. Until now, services will not be updated (cf. Outlook).