Skip to main content
Solved

2016 vs 2017 Feature Reader Envelope Intersect Envelope, why the difference?

  • March 19, 2018
  • 3 replies
  • 36 views
dfresh
Forum|alt.badge.img

I am running a simple workspace in 2017 and 2016.1. Read Shapefile, bounding box accumulator and feature reader, with spatial filter on WMS.

The process works fine in 2017, but in 2016 with the exact parameters, transformers and variables will not clip the full extent,

simply when the envelope is applied the URL request is something along the lines of BBOX=xmin,ymin, xmax, ymax,

2017 works fine the the variables are correct in the request URL, however in 2016, the bounding box coordinates in URL are that of the WMS. Again everything is identical between the two workbenches except for the result.

Best answer by lars_de_vries

Can you tell us why it must work in FME2106 as well? If you want it to work in an older version as well, I would always advice to build the workspace in the older version, making sure that you don't have issues with backward compatibility, like you seem to have now.

Off course it is possible to build the URL dynamically using the parameters from the boundingbox, you could use the BoundsExtractor for that. The advantage is that you'll have a solid URL that always will make the same request.

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

dfresh
Forum|alt.badge.img
  • dfresh
  • Author
  • 19 replies
  • March 19, 2018
it is very frustrating, I might just dynamically build the URL myself by using the Get Extents transformer. again this is not preferred at all.

 

 

lars_de_vries
Forum|alt.badge.img+10
  • lars_de_vries
  • 388 replies
  • Best Answer
  • March 29, 2018

Can you tell us why it must work in FME2106 as well? If you want it to work in an older version as well, I would always advice to build the workspace in the older version, making sure that you don't have issues with backward compatibility, like you seem to have now.

Off course it is possible to build the URL dynamically using the parameters from the boundingbox, you could use the BoundsExtractor for that. The advantage is that you'll have a solid URL that always will make the same request.

dfresh
Forum|alt.badge.img
  • dfresh
  • Author
  • 19 replies
  • May 5, 2018

Can you tell us why it must work in FME2106 as well? If you want it to work in an older version as well, I would always advice to build the workspace in the older version, making sure that you don't have issues with backward compatibility, like you seem to have now.

Off course it is possible to build the URL dynamically using the parameters from the boundingbox, you could use the BoundsExtractor for that. The advantage is that you'll have a solid URL that always will make the same request.

I just ended up building the URL dynamically.

Community Stats

32,086
Posts
121,848
Replies
39,729
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.