Latest Contributions by LindsayRaabe_FPCWA

In Field Maps, if a user needs to redownload a map area for offline use, they currently need to manually remove the offline area, either find the offline area for download or define it themselves (our standard workflow) and download the map.  Idea: Add a button to each offline area in Field Maps that allows the user to recreate the offline area from scratch (not just sync datasets within the offline area).  Use Case: Streamline and simplify the data management for end users within the Field Maps app. Removes the need to manually remove maps, and then select or redefine (navigate to desired area) for each map. This can be quite time consuming when multiple offline areas across multiple maps are in use as you need to wait for each map to download before proceeding to the next one.  ... View more

In Field Maps, if a user has offline areas downloaded, and the map owner makes changes to the webmap (or feature services in the webmap) shema, those changes don't get automatically updated when the map is sync'd.  IDEA: Add a warning message in Field Maps alerting users to changes to the webmap that can only be seen if the offline area is redownloaded.  Use Case: Currently, there are no warning messages when changes are made, relying solely on comms to be sent by the map owner (which, lets face it, isn't always effective - raise your hand if you read all your emails every day?   🦗🦗🦗). A warning that changes have been made which won't be shown via Sync is an effective way of alerting the user that they need to regenerate an offline area (bonus points if the message states what the changes are).  ... View more

The Append tool has the Update Features option, allowing the user to define fields to match the input data to the target data, and where features in both datasets match, those features are updated instead of appended (avoiding duplication).  IDEA: Add a toggle box option as part of the Update Features function that removes and features from the Target dataset that don't have a matching feature in the Input dataset.  USE CASE: This will be handy where a dataset should be a complete copy of the input dataset, but currently requires 2 different processes to achieve this. Either Append (to add new features and update existing matching features) plus a Join > Filter > Delete Rows process to find and remove any old features that are no longer relevant. The other way of achieving this would be to delete all existing features and appending the complete new input dataset. I want to avoid this though as we're talking thousands of records and that is time consuming when dealing with feature services in ArcGIS Online.  ... View more