Which services and implementations should we add initially?

[nuest]

https://wiki.osgeo.org/wiki/INSPIRE has a list of INSPIRE components and services.

• View services
  • MapServer
  • deegree (inspireNode)
  • MapGuide
  • Mapbender
  • OpenLayers
• Discovery services
  • GeoNetwork
  • Mapbender
  • deegree (inspireNode)
  • pycsw
• Download services
  • deegree
  • GeoServer
  • MapServer
• Transformation services
  • ?

---

Docker can also be a bridge between commercial and open source implementations, we could consider adding an ArcGIS container, for example.

[tfr42]

Another inventory was added to the OSGeo Wiki which is more up to date (but not complete yet): https://wiki.osgeo.org/wiki/INSPIRE_tools_inventory

I would start with the following set of service implementations:

• View Service (based on WMS 1.1.1)
  • MapServer
  • deegree - OGC RI for WMS 1.1.1
• View Service (based on WMTS 1.0)
  • deegree - OGC RI for WMTS 1.0 (currently under compliance testing)
• Download Service (Direct-access DLS bases on WFS 2.0)
  • deegree - OGC RI for WFS 2.0
• Download Service (Pre-defined Dataset Download Service based on WFS 2.0)
  • deegree
• Download Service (Pre-defined Dataset Download Service based on Atom feed)
  • TBD
• Discovery Service (CSW 2.0.2 APISO)
  • deegree
  • GeoNetwork
  • pycsw

[tfr42]

Continued at https://inspire-reference.jrc.ec.europa.eu/tools

[nuest]

@tfr42 Thanks for the updated link!

Can you explain the difference between "service" and "server" on that list?

The full list of server tools is quite extensive. We should come up with a roadmap for several Docker compose configurations, i.e. later also include stuff like processing services or portals.

Here's the list as of now (not all of these make sense for us to consider):