Skip to main content
  • EN

Hi,

I am trying to set up an FME Server App that accepts multiple spatial file types (json, kml, shapefile) as a "file drop" from the non-FME user, to then spatial filter against hundreds of "footprints", to then email the user back a email with the zipped "footprints".

I am having an issue creating a workspace with multiple feature readers that, when published, doesn't end with a fatal error because a single reader cant read the input file. My workspace starts with a creator going to the multiple feature readers (kml, json, shapefile), they all go into a spatial filter against the "footprints". The Feature readers all have a Published Parameter for the file to be read, the workspace parameter is to "Continue Translation" for rejected features.

Thanks!

 

FME(R) 2020.0.3.0 (20200605 - Build 20252 - WIN64)

FME Server 2020.0.0.1 Build 20202 - win64

Try replacing all the format-specific FeatureReaders with a FeatureReader set to use the Generic format. This will allow any format to be read and as you ony have one reader other format readers can't complain about not being able to read the file.

This excerpt from the Advanced training manual may also help — The Generic Reader and Writer

Try replacing all the format-specific FeatureReaders with a FeatureReader set to use the Generic format. This will allow any format to be read and as you ony have one reader other format readers can't complain about not being able to read the file.

This excerpt from the Advanced training manual may also help — The Generic Reader and Writer

@tomf​ thanks for the response. I had previously tried the generic reader as a featurereader and received "expected a dataset of type directory" errors and the generic reader returned the error "Error opening the CESIUM3DTILES Reader on dataset" regardless of input (kmz, json, orzipped shapefile).

Have you tried setting the input format parameter in the generic reader? Without it FME will try to guess the format from the file extension and it doesn't always get it right.

genFeatReaderParticularly if the dataset is zip and the content format is somethogn like shapefile.

Have you tried setting the input format parameter in the generic reader? Without it FME will try to guess the format from the file extension and it doesn't always get it right.

genFeatReaderParticularly if the dataset is zip and the content format is somethogn like shapefile.

@tomf​ Thanks for all the help, setting the generic reader parameter for the file extension worked. I have three generic readers with specific extensions for the allowable inputs in the workspace, despite getting fatal errors for the generic readers not used for the file input, the workspace uses the correct generic reader file extension parameter to continue the workflow since the workspace does not terminate when a feature is rejected.

Reply


Community Stats

30,017
Posts
113,995
Replies
37,635
Members
Terms & ConditionsCookie settings