Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom projections not supported via WFS #6981

Open
geographika opened this issue Dec 7, 2023 · 2 comments
Open

Custom projections not supported via WFS #6981

geographika opened this issue Dec 7, 2023 · 2 comments

Comments

@geographika
Copy link
Member

Pull request #6795 allowed custom projections to be requested through WMS requests, however WFS and WCS don't have the same support.

Use of custom projections currently return the following error:

<ows:Exception exceptionCode="InvalidParameterValue" locator="srsname">
    <ows:ExceptionText>msWFSGetFeature(): WFS server error. Invalid GetFeature Request:Invalid SRS.  Please check the capabilities and reformulate your request.</ows:ExceptionText>
</ows:Exception>

Adding support would allow requests such as the following to be supported:

  • map=wfs_custom_projection.map&SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&TYPENAME=province&srsname=epsg2:42304

  • map=wfs_custom_projection.map&SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&TYPENAME=province&srsname=ESRI:108022

@jratike80
Copy link

I would like to see how that custom CRS would appear in the GML3 from WFS 2.0 and in the DescribeCoverage from WCS 2.0.

@geographika
Copy link
Member Author

geographika commented Dec 7, 2023

@jratike80 if there was a custom definition such as epsg2::42304 it would be included in the Mapfile as follows:

WEB
  METADATA
    "wfs_title"		   "Test simple wfs"
    "wfs_srs"		   "epsg2:42304 EPSG:4326 EPSG:3857 esri:102001"

And would appear in the responses in the following form (for WFS 2.0 or if wfs_return_srs_as_urn is set to True for earlier WFS versions):

      <wfs:boundedBy>
      	<gml:Envelope srsName="urn:ogc:def:crs:epsg2::42304">
      		<gml:lowerCorner>2253355.750000 -76361.773438</gml:lowerCorner>
      		<gml:upperCorner>2747648.500000 515489.031250</gml:upperCorner>
      	</gml:Envelope>

GetCapabilities would look as follows:

  <FeatureTypeList>
    <FeatureType>
      <Name>ms:province</Name>
      <Title>province</Title>
      <DefaultCRS>urn:ogc:def:crs:epsg2::42304</DefaultCRS>
      <OtherCRS>urn:ogc:def:crs:EPSG::4326</OtherCRS>
      <OtherCRS>urn:ogc:def:crs:EPSG::3857</OtherCRS>
      <OtherCRS>urn:ogc:def:crs:esri::102001</OtherCRS>
      <OutputFormats>

WCS projection code paths are again different from both WMS and WFS so would be addressed separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants