Documentation suggestion: comparison between FeatureServer access w/ {esri2sf} + GeoServer access w/ {geosapi}

[elipousson]

I'm not sure if this is essential but I'd be curious to see a comparison between how esri2sf provides access to the FeatureServer and MapServer REST API and how geosapi provides access to any GeoServer API. It is possible there are also some features for one or the other that could be helpful to emulate.

[eblondel]

Hi @elipousson just saw this. geosapi is the R client for the GeoServer REST API designed to manage GeoServer resources (including setting workspaces, datastores; uploading data, creating feature types/layers, managing styles, etc), not for accessing OGC services (including the Web Feature Service for vector data). For this you may want to compare with ows4R (OGC Web Services for R) that covers the WFS (among others). It has been tested on several server implementations depending on the service we are talking:

• for WFS: tested on Geoserver, MapServer; which would be the scope of the comparison essentially)
• for WCS: tested on GeoServer, Rasdaman, Thredds;
• for WMS: tested on Geoserver;
• for WPS: tested on 52North,
• for CSW: tested on Geonetwork,PyCSW

The ArcGIS REST API is not really comparable here, as it is not an OGC standard service specification (AFAIK).