Specifying output CRS

[ghost]

We have attempted to implement pg_featureserv as our middleware for our API which handles a form of mapping. Our API consumes EPSG:27700. We are not able to configure pg_featureserv into returning data using EPSG:27700 in the output. We have tried giving it a .toml file and whitelisting ST_TRANSFORM but pg_featureserv will still return the output in EPSG:4326. We investigated the issue and it looks like that the pg_featureserv is hardcoded to always give out EPSG:4326.

Is it possible to specify the output CRS that pg_featureserv provides?

[dr-jts]

There's a design issue for this (#6). This is not currently implemented.

To align with the OAPIF Part 2 spec, we could provide a query property crs=SRID to provide output in the requested CRS (rather than the default of 4326). Is this sufficient for your needs?

[ghost]

Having the query property would be great! Do you have any rough estimation of when this could be implemented? Is there a process on requesting a new features?

Apologies for the ignorance, I am quite new to the GIS community and this repo

[dr-jts]

This is the best place to suggest new features.

Not sure about the timeline for adding this, but we are doing some work on pg_featureserv this quarter, so might be able to fold it in then.

[dr-jts]

Another question: do you also need to be able to specify the bbox query parameter in CRS 27700?

If so, this requires adding the OAPIF parameter bbox-crs and associated logic.

[ghost]

That would be a nice to have for us.

[dr-jts]

@ff-nlashkor this is added in #98. Are you able to build and test?

[ghost]

We have built this and I can confirm that this has given us the outputs that we need for our API.

Thank you!

[dr-jts]

Good to hear!