Export to Shapefile not working on some layers
Is there an option to give a layer the ability to have shapefiles exported and not others? I have a web map that will allow the majority of the layers to have their features exported out as a shapefile while other layers will not. I get an error stating it couldn't complete the operation, see below. When setting up the map/adding in services I don't see an option for the Export to Shapefile, nor do I see an option when I publish the service.
/customer/servlet/servlet.FileDownload?file=00P6000000eltkMEAQ
I've found that the module can be turned off/on but there's no way to specify layers. For the time being I'd be content in the ability to export features of any given layer as a shapefile.
thanks in advance,
JD
-
We have also seen this a few times. We haven't had time to investigate it further to try and narrow the problem down.
Steve
0 -
I've only seen this dialog when attempting to mix geometry types during the extract process. Since a shapefile can only consist of one geometry type, an error is thrown. Is that your situation? If so, maybe this is just a training issue with your users and extracting one geometry type at a time will solve the problem.
0 -
Unfortunately no, that's not the situation. I selected several layers consisting of various geometry types and it would export shapefiles for each. One of the layers that it won't export is a parcel layer. We thought that it might be due to complex geometry, but after checking another layer that won't export for complex geometry, it didn't contain any.
0 -
One problem we identified is related to the field length limitation on shapefiles. If the service in your essentials application references a featureclass that has more than one field where the resulting output is truncated (to 6 characters) and the resulting field name(s) are duplicates, then the export will fail.
In our case
Last_Updated_By
Last_Updated_Date
Are both truncated to the same field name and the export fails. At least that's what we think is the problem. Not sure if that help or not..
0 -
We have also noticed this issue with some layers that have integer coded domains. Running an "identify" returns a string value for the integer field. Export to shapefile will fail when that happens.
0 -
We have observed this issue as a feature class is joined to another table.
/customer/servlet/servlet.FileDownload?file=00P6000000em1AkEAI
/customer/servlet/servlet.FileDownload?file=00P6000000elziyEAA
Is this issue associated with the length of the fields after applying the join?
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
6 Kommentare