Skip to main content
Solved

OGC WFS and version dependent parameter typeName(s) ?

  • June 30, 2022
  • 3 replies
  • 75 views
lifalin2016
Supporter
Forum|alt.badge.img+40

Hi all.

I'm trying to consume a WFS service (Geoserver), which for some reason only works as version 1.0.0. This even though that the capabilities document clearly says 2.0, and accepts all versions.

In versions 1.0.0 (and 1.1.0?) the parameter "typeName" is used to specify the layer (feature type), but this is later renamed to "typeNames" (with an S).

I get an HTTP error 401 from the service when attempting to fetch data in version 1.0.0, but the very same URL works if I just add an "s" to "typeName".

Can FME be tricked into instead using or adding the "typeNames" parameter?

Actually, URLs may contain both "typeName" and "typeNames" parameters with the same value, which would make the requests robust against version problems. Can this be achieved?

Cheers.

Best answer by lifalin2016

It seems that the issue has been solved in version 2022, so I'm closing this.

-- Cheers, Lars I.
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

kailinatsafe
Safer
Forum|alt.badge.img+23

Hello @Lars I Nielsen​ , I know there was a parameter added to the WFS Reader recently regarding TYPENAMES. Not sure what version of FME you're using, so its hard to say if you'll have access to it, but it should be in a 'Workaround' section in the WFS reader parameters. Could you try enabling the 'Seperate WFS v2.0 TYPENAMES with commas' parameter? I cannot gaurantee this will work, but it may be worth trying. Alternatively, would you be able to share your WFS URL? Best, Kailin.

lifalin2016
Supporter
Forum|alt.badge.img+40
  • lifalin2016Supporter
  • Author
  • Supporter
  • August 11, 2022

Hello @Lars I Nielsen​ , I know there was a parameter added to the WFS Reader recently regarding TYPENAMES. Not sure what version of FME you're using, so its hard to say if you'll have access to it, but it should be in a 'Workaround' section in the WFS reader parameters. Could you try enabling the 'Seperate WFS v2.0 TYPENAMES with commas' parameter? I cannot gaurantee this will work, but it may be worth trying. Alternatively, would you be able to share your WFS URL? Best, Kailin.

Thanks Kailin.

Alas, as I described, the version has to be fixed to 1.0.0, so this option is not accessable.

But version 2022.0 did read the data without problems. I normally use 2020.2.5, which showed the error.

I have already been tasked with upgrading our FME servers to 2022.x, but in this job our desktop is used, and here we can switch version much easier.

Cheers.

-- Cheers, Lars I.
lifalin2016
Supporter
Forum|alt.badge.img+40
  • lifalin2016Supporter
  • Author
  • Supporter
  • Best Answer
  • September 9, 2022

It seems that the issue has been solved in version 2022, so I'm closing this.

-- Cheers, Lars I.

Community Stats

32,154
Posts
122,048
Replies
39,812
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.