I've been working on several projects with City and County customers. All of them use decimal degrees (lat/long coordinates) to describe their point feature locations.
In the projects, I set up publicly accessible Web Apps with view-only access to the data.
Frequently these stakeholders need to export a subset of features in a layer (for example a single installation zone) and, for example, need to be able to look at those pieces of infrastructure on Google street view which only accepts lat/long coordinates. They may also use the data in other ways, but in any case have no clue what to do with the Esri Meters units.
My organization and stakeholders use almost exclusively ArcGIS Online with point feature layers and Esri's default basemaps. My customers are not GIS professionals, don't want to pay for licenses, and have no interest in learning anything but the basics of the AGOL Web Apps.
There are currently numerous ways to export point feature data:
|Point feature export method||Number of features exported||Coordinate units||Credit cost||AGOL license requirement||Export a subset (polygon) of the data|
|1. Layer item page > Export to CSV||No limit||DD||Free||Yes, at least Creator||No - all or nothing|
|2. Analysis > Extract Data||No limit||DD||Yes, though minimal||Yes, at least Creator||Yes|
|3. Web App Builder > Select Widget > Export to CSV||No limit||Esri meters||Free||No||Yes|
|4. Web App Builder > Attribute Table > Options > Export (selected/all) to CSV||maxRecordCount, not all features have coords (see below)||DD||Free||No||Yes (when used with Select tool or a filter)|
I am looking for any of the above rows to be fully green
Option 3 is the most intuitive for my users.
Option 4's maxRecordCount limitation can be increased, but any features that were added to the layer after the initial upload (for example through Collector) have blanks in the CSV where the DD coordinates should be.
Searching the web, it looks like I'm not the only organization looking for an answer to this:
If possible, I am also open to some workarounds that I can do as an administrator to achieve the desired result for my end users.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.