1

I recently upgraded GeoServer from 2.12 to 2.142 because of a GeoNode update. A WFS GetFeature link failed in the new version of GeoServer:

http://myhost/geoserver/wfs?service=wfs&version=2.0.0&request=GetFeature&typeName=geonode:fr_admin1&outputformat=SHAPE-ZIP

The error message I got was something like:

<ows:Exception exceptionCode="InvalidParameterValue" locator="typeName">
    ows:ExceptionText>Feature type geonode:fr_admin1 unknown</ows:ExceptionText>

There is an exception "Feature type unknown" returned. However, I never had this issue in GeoServer ver. 2.12. Is there any changes for the WFS GetFeature request in GeoServer ver. 2.14? How to solve this problem?

3
  • 1
    Version 2.0.0 uses typeNames not typeName
    – Ian Turton
    May 9, 2019 at 18:34
  • @IanTurton Thanks for the response. I changed the url into "myhost/geoserver/…", but the issue persists.
    – Ran L.
    May 9, 2019 at 19:50
  • service=wfs should be service=WFS
    – nmtoken
    Jul 2, 2019 at 16:41

1 Answer 1

1

Both typeName and typeNames work fine on a local machine for me.

http://localhost:8080/geoserver/wfs?service=WFS&version=2.0.0&request=GetFeature&typenames=topp%3Atasmania_cities

and

http://localhost:8080/geoserver/wfs?service=WFS&version=2.0.0&request=GetFeature&typename=topp%3Atasmania_cities

Things to check:

  1. Make sure that you really have a layer geonode:fr_admin1 and it is enabled.
  2. Test with a standard data layer (like topp:tasmania_cities).
  3. look in the log file to see if there is an error message.
  4. Turn logging level up to GEOSERVER_DEVELOPER and check again.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.