ideal setup for building survey
I am examining a survey process. The above is the setup that is already being used.
A Feature Class with 20 attributes and 185K rows is being used as reference data for surveyors. This FC is then published as 1 Feature Service which is being used by a total of 110 users (80 surveyors and 30 supervisors). 80 surveyors are using Field Map on their cellphones. 30 supervisors are using ArcGIS Pro. They all access the same Feature Service.
The Field Maps are filtered based on districts. Eg: Field Map #1 contains data only for District 1, and so on until District 5. So there are 5 Field Maps apps.
These 5 Field Maps apps are then being used by 80 surveyors accordingly. 1 Field Maps apps can be accessed by 16 - 20 users. The surveyors only updating 3-5 attributes, and put some notes if there are changes in polygons
The 30 Supervisors are accessing the Feature Service using their ArcGIS Pro. They are splitting polygons and updating attributes. Each supervisor also has filtered data, so not all data are displayed.
Both Surveyors and Supervisors are using imagery base maps.
By evidence, many times the surveyors feel that the updating of data is too slow.
Is there any way to make this setup better?
I feel that the supervisors can access the FGDB directly, but they can't do so because the FGDB is hosted. Or maybe the surveyors can take offline data to the field and synch the latter to the server, like this one:https://www.esri.com/arcgis-blog/products/field-maps/field-mobility/work-offline-with-field-maps/
Any suggestions or sharing experiences are welcome...
Thanks
