Skip to main content
Question

Inconsistency in flow app behavior (Shapefile reading)

  • January 13, 2025
  • 2 replies
  • 21 views

afod
Contributor
Forum|alt.badge.img+6
  • Contributor

I have a flow workspace app that simply takes a shapefile and converts it to a 2D grid, previously (most of 2024) this accepted a zip file of the shape components and worked fine. My user has been using this for months with no problem. Seemingly now it stopped accepting zip files and instead through trial and error i got it working ONLY selecting the .shp component from my PC. This seemed a bit weird as i know it needs more than this but it seemed to work.

I've since downloaded the workspace, made a tiny adjustment to something unrelated to reading the shapefile, republished. This new version now will only work if you select both the .dbf and the .shp, the previous version still works with just the .shp.

I've tried to trouble shoot, recreate the app, anything i can think of but i cant for the life of me explain this inconsistency im finding, has anyone had anything similar?

2 replies

virtualcitymatt
Celebrity
Forum|alt.badge.img+34

Are you able to clarify a couple of things?

1. Do you get errors when running the workspace or when uploading?

2. Are the errors always different or is it the same error?

3. What version (deskop and server) are you working with here.

I’ve had weird behaviour with shape uploading shapefiles the past as well but I’ve forgotten what my specific issues was. 
 


afod
Contributor
Forum|alt.badge.img+6
  • Author
  • Contributor
  • February 19, 2025

Sorry for the late reply to this, the transformer i added inside the workspace seemed to be the difference between needing a .dbf or not, the log didn't provide this information so it was hard to pinpoint.

The change from needing to use a .zip seemed to occur after a security patching on our FME server, this also happened to a colleague at another organisation.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings