Summary
Add ArcGIS FeatureServer (GeoServices REST API) support to enable compatibility with ArcGIS clients while maintaining existing OGC API functionality.
Why?
Many organizations use ArcGIS tools alongside OGC-compliant clients. Supporting both standards from the same PostGIS backend would be valuable.
Proposed Approach
- New optional endpoints under
/rest/services/ (disabled by default via config)
- Reuses existing catalog and query infrastructure
- Converts GeoJSON output to Esri JSON format
- Handles WKID/SRID conversions (e.g., 102100 ↔ 3857)
Implementation Status
I have a working implementation ready to contribute:
- Core endpoints:
/rest/info, /rest/services/{id}/FeatureServer, /rest/services/{id}/FeatureServer/{layer}/query
- Tested with 298k+ features, works with ArcGIS JS API
- Zero impact on existing OGC API code
Questions
- Is this feature of interest?
- Any preferences on API structure or configuration?
- What test coverage level do you expect?
Happy to open a PR if this aligns with project goals.
Code: master...uucokgis:pg_featureserv:feature/arcgis-geoservices-support
uucokgis#2
Summary
Add ArcGIS FeatureServer (GeoServices REST API) support to enable compatibility with ArcGIS clients while maintaining existing OGC API functionality.
Why?
Many organizations use ArcGIS tools alongside OGC-compliant clients. Supporting both standards from the same PostGIS backend would be valuable.
Proposed Approach
/rest/services/(disabled by default via config)Implementation Status
I have a working implementation ready to contribute:
/rest/info,/rest/services/{id}/FeatureServer,/rest/services/{id}/FeatureServer/{layer}/queryQuestions
Happy to open a PR if this aligns with project goals.
Code: master...uucokgis:pg_featureserv:feature/arcgis-geoservices-support
uucokgis#2