QuickCapture retain records on basemap after sync

[JenLangevin]

Hello,

I would like QuickCapture mobile app users to be able to visualize the records they captured after syncing the data. We use QuickCapture for field surveys, and it is essential that users can see their previous day's tracks and points even when disconnected/offline. It is also helpful that they sync that day at the end of each work day so that I can see their daily progress. Currently, the only way I know to accomplish this is to have them sync, then I create a new MMPK each evening with their data, and then they can update the project with the new MMPK before leaving service/wifi for the next field day. 

Can records be retained on the basemap after syncing? 

[SaiKrosuri]

Yes, it is possible to retain records on the basemap after syncing in QuickCapture, but there are some considerations depending on how the app and data are configured.

In your current workflow, after syncing, the records are stored in the mobile map package (MMPK) and you create a new MMPK each evening for the next day. This is a valid approach, but there are other ways to ensure users can visualize their captured records offline without the need to re-sync or manually update the MMPK every day. Here's how you can streamline the process:

1. Using the Offline Data Caching Feature: QuickCapture allows users to download data to their devices, so when they are offline, they can still view previously captured points and tracks on their basemap. To enable this, you need to ensure that the basemap and feature layers are set up to allow offline use. When the user syncs their data, the app can update the local cache on their device with the latest changes. This means that users can continue to see their previous day's records without requiring an updated MMPK for each field day.

2. Syncing Data: Once the data is captured and synced at the end of each day, users can continue to see the latest synced data on their basemap. The synced records should appear as part of the local offline cache, which will be retained on the device until the next sync. This allows users to visualize previous data even when disconnected from the network, and ensures that progress is regularly updated.

3. Managing MMPK Versions: If you still prefer using MMPKs for managing the data, you can automate the process of creating and updating the MMPK at the end of each day. This ensures that the users always have the latest data in their mobile app. However, using offline layers and caching may reduce the need for this manual update, providing a more seamless experience for the field users.

4. Field Data Visibility: If you want to provide your field users with easy access to their captured data and tracks from previous days, ensure that your basemap layers and feature service are configured to display these records correctly. You can also consider implementing feature services with "sync enabled" so users can see changes in real time after syncing their data back to the server.

In summary, you can retain records on the basemap after syncing, either by using the caching mechanism for offline maps or by updating the MMPK at the end of each day. The key is ensuring that the appropriate offline and synchronization settings are configured in your QuickCapture project and that data visibility is set up properly for field users.

[JenLangevin]

Hello Sai,

Thank you for your reply. Can you provide more information on the Using the Offline Data Caching Feature? I did some searching, but I'm unsure how to implement this. All my feature layers have offline enabled, I  put my phone in airplane mode, shut off the Wi-Fi, capture a point, turned on Wi-Fi, synced the data and my point disappears from the basemap. 

[JohnathanHasthorpe · Accepted solution]

Hi @JenLangevin 

I'm on the QuickCapture team. The answer from @SaiKrosuri is not accurate.

To clarify:

QuickCapture projects can be configured to have one map; either an online web map/basemap or an offline package (MMPK, TPK or VTPK).

When local data is sent from the mobile application it is removed from the map. The only way to see it after it is sent is one of the following options:

1. You create a web map that contains the project layers. Once the map is panned, the user will see any new features that have been to it. This approach supports basic map caching. i.e. if the user opens the map when online, and pans/zooms around the extent of the data, the cached features will be viewable in the map when the device goes subsequently offline. However, if the project is closed or the devices crashes, this cache would be lost and the map could not be reloaded while offline.

2. You create an offline MMPK that that contains the project layers as online feature layer (see reference online content). This is similar to the web map approach, as the user will need to be online to see the features, but these can be temporarily cached for offline use (by panning/zooming around the map) . However, if the mmpk is re-loaded while offline, only the static layers in the mmpk will be visable - not the online features.

I have some questions, in relation to a possible enhancement we could make in the app:

- Do your users need to see the data submitted by others?

- If we enhanced tha app to retain sent feature in the map for a fixed time, would that help you? For example if we did not delete sent records for 24 hours or 7 days?

Thanks 

John

[JenLangevin]

Hello John,

I appreciate the clarification. I will take a look at the second option.

In an ideal world, my users (who are almost 100% offline) would be able to see other's data. If they could at least see their own data they have collected, that would still be very helpful. 

Some times 1-7 days would be enough time to retain the data, other survey types may go on for 1-2 months. Could there be an option, to clear retained data? Then users could clear it when they wanted, but otherwise it would be retained. In my mind, a backend setting in the QC web designed portal, when you could toggle on "retain records" for a project. Then the end use had a options to select "clear data after submission" or "retain data after submission" and then another button on the basemap in the app to "clear retained records". I would be happy to chat about this future if it would be helpful.