4. Synchronize as often as possible. Frequent synchronization reduces the amount of data that gets pushed back to the server at once, which reduces the chance of a synchronization failing.Tip: If you are using ArcGIS for Server and need to synchronize large amounts of data, consider increasing the upload size, which by default is set to 2 GB. You may also need to increase the upload size of your web server to accommodate large synchronizations.5. Use the strongest network connection available. Public WiFi, for example, is not a best practice for synchronizing because you cannot trust the source; the network bandwidth or restrictions may not be capable of processing the request. If possible,
synchronize when connected to a trusted source, like the internal WiFi of your organization. Collector for ArcGIS sends 2 MB bundles of data at a time during the synchronization process, so the strength of the network connection becomes more important as the size of the data increases.Tip: If your offline data fails to synchronize successfully the first time, test it again using a different network.Trick: You can configure Collector for ArcGIS to only push edits up to the server when you synchronize, and to not pull down edits made by others while you are offline. This reduces the amount of data transferred, making it faster to share your changes and save on data transfer costs from cellular networks. If the edits being made by others are important to you, leave 'Push Only' synchronization disabled.
6. Consider the data. Simply put: the more data, the slower the performance. That being said, sometimes performance decreases are less obvious than just the number of features in the data. For example, the number of fields, relationship classes, the projection, and the visibility scale can all affect performance. If you are looking to improve performance, you can hide fields, ensure the projection of the data matches the basemap, and set a reasonable visibility scale on the data or within the web map.
Tip: Keep in mind the number and size of photo attachments that you are collecting. Photo attachments cause the data to expand due to the size of each respective photo. When synchronizing many photos, it is especially important to have a strong network connection.Trick: You can limit the size of photos that you attach to features within Collector for ArcGIS on the Settings page.Tip: The next release of Collector will support new offline settings that authors can adjust in ArcGIS Online on the item properties pages of their web maps. These settings will allow map authors to specify what types of information field workers retrieve from the server for both editable and read-only layers. As a result, workers can sync less data, which can decrease the risk of sync failure.7. Test before deploying to the field! Create a sample web map and try collecting data and synchronizing the edits before taking the map into production. Collector for ArcGIS is supported on iOS, Android, and Windows; you may find that an issue is specific to the hardware or to the operating system of your mobile device. If you are unable to synchronize from your sample map, please contact Esri Technical Support.Related information:You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.