Configure fields for export to xlsx, csv and shp
Terminée
RELEASED: Web 5.6
The ability to configure which fields are exported to xlsx, csv or shp isn't currently supported in Geocortex Web. This would be a valuable feature for users.
In particular it would be helpful to be able to exclude the feature geometry details when exporting to xlsx and csv because in Excel the geometry attribute for all but the simplest features causes Excel to give warning messages due to the number of characters in that field. Most of my users don't need the geometry details and wouldn't understand them!
-
I think what you are ultimately trying to accomplish is possible today, but not nearly as 'easy' as it could be.
I suspect we'd need to provide you some examples, but the underlying viewer operation results.convert-to-csv supports a number of arguments for customizing the .CSV output. We may need to put up a forum post with some examples of how you'd customize the JSON command chain so you can visualize how to use the arguments.
0 -
Thanks Cam, I'd certainly like to see some examples of how to customize the csv/xls output. I can see that I can choose to include selected attributes using the outFields argument but the Geometry column and ObjectID columns appear to be included by default. ObjectID isn't a problem but when exporting attributes associated with complex geometries I'd prefer to remove the Geometry column to prevent Excel giving warnings to users and then telling them that it has repaired the Geometry field by truncating it.
My ideal would be to be able to exclude Geometry in all cases if possible. The user scenario is
- Use Rectangle or Polygon Identify to find features associated with a specific area
- Export the attributes of those features to Excel for further analysis.
The extent of each polygon is valuable info but not the locations of each node.
2 -
The ability to configure which fields are exported to xlsx, csv or shp would be beneficial for users who need to export data from the web product into spreadsheets or other formats for use in other applications. It would allow users to select the fields relevant to their use case and make the output format more easily readable and actionable. Additionally, it would reduce the risk of data corruption due to an excessive number of characters in Excel.
1 -
Cam Barnard We've been trying the configure the export to csv to exclude the geometry and object_id.
Were examples ever created to demonstrate this functionality as we've not been able to achieve it?
Our use case is similar to Peter Jackson
Cheers.
1 -
With the help of Lance Bolton I modified the export to xlsx to be:
[
{
"name": "results.convert-to-xlsx",
"arguments": {
"geometryFormat": "NONE"
}
},
"system.download-file"
]
This also works for export to csv.
2
Vous devez vous connecter pour laisser un commentaire.
Commentaires
5 commentaires