ShapefileToFeatureSet- Invalid FileCode encountered. Expecting 9994
I am trying to use the ShapefileToFeatureSet workflow activiity and can get it to work for some shapefiles, but then some from one user are throwing this error.
"Invalid FileCode encountered. Expecting 9994"
I have tried adding the various code page options, UTF-8, ISO, 88591, ANSI, 1252 but none seem to work.
Anybody have any tips?
-- Marc
0
-
Through some testing, this appears to be related to having more than one feature in a shapefile. Has anyone else been able to use this workflow activity to load more than one shape? I tried dissolving the shapefile into one multipart feature but that still had the same error...
-- Marc0 -
Hi Marc,
The workflow sample site that ships with Essentials has a workflow that converts a sample shapefile with 3000+ features. You can try it out by coping the sample site (default location "C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\REST Elements\Sample Sites\Workflow_Samples"), to your Sites folder and running the workflow from the viewer toolbar. It should be in the "Conversion" section. I tried it on my end and didn't have any issues. If you weren't able to solve the problem, you could open a support case and send us one of those shapefiles that doesn't work on your end.
Hope that helps,
Amanda0 -
Hi Marc - were you ever able to resolve this and happen to remember the resolution? We're running into a similar issue with this happening to a single user. 0 -
You could try to recreate the shapefile (import/export in ArcGIS) to see if this solves the issue. 0 -
Hi Nico,
Thanks for the information. This is happening for various shapefiles for a single user, so I think there might be a system setting for the user at play.0 -
9994 is the File Code in the Main File Header of a shapefile https://www.esri.com/library/whitepapers/pdfs/shapefile.pdf 0 -
Thanks for sending this document Nico. I'll read through and see if anything stands out. The same shapefiles work for other users, just not this one. So this value must get altered on the one user's profile somehow. 0 -
Hi Jennifer,
What I ended up having to do was check if there was more than one feature in the uploaded shapefile. If so, then I passed the features to a custom gp task to dissolve based on a temporary field added to all features. Then I used the returned dissolved multipart feature for further processing.
--Marc0 -
Thanks for the update on your resolution Marc. It's appreciated! 0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
9 Kommentare