Latest Contributions by LindsayRaabe_FPCWA

IDEA: In ArcGIS Pro, have the ability to password protect an element to prevent it from being modified or deleted from a layout altogether, similar to how Microsoft Excel lets users protect whole tabs or just certain cells with a password.  USE CASE: Our GIS Team are custodian of a number of map templates that any number of users can access, Save As and modify to suit their requirements. Lately though, there's been a couple of compliance incidents that have resulted in close scrutiny of the maps produced and whether they were using up-to-date templates (or and older one with broken data sources). To make this easier to identify in the future, we have included a small, faint text box in the bottom corner of each layout stating when the template was last updated by our team. This is of course Locked, but that only prevents it being selected via the Layout display and moved by accident. Someone could of course still unlock it if they wish, update the text and even delete it outright if they so chose. Having the option to password protect elements means we could set certain elements up that must be included regardless of what other changes users may like to make. This could apply to disclaimers, corporate branding and Logos, or any number of other items deemed essential for all products exported from a template.  ... View more

Existing functionality: Currently, when you insert an "Table Attribute" dynamic text element into a layout in ArcGIS Pro, you set the input source to a table (layer) in a single map frame and can filter the values to return by changing the "Query" from 'All rows' to 'Visible rows' or 'Custom query' (SQL Expression).  IDEA: Add an new 'By search table' option to the "Query" list that lets you filter the available rows using a spatial relationship with another layer (with X units of another feature/s).      USE CASE: I have many scenarios come up in my map production where we try to minimise the amount of manual input required by our users over elements in the layout. This feature would hopefully enable us to perform search between 2 layers in the map, so that a focus feature set by a definition query or map series (e.g. a Plantation) can be used to select one or multiple intersecting features from another layer (e.g. Local Government Authority) to then display on the layout. In the image below, it would return only features "A" & "P" (with a 100m search distance) instead of All rows (A-Z) or Visible rows (A,M,P & Z) from the grey layer.  This would be a relatively simple tool to use with similar functionality to Select by Location or any number of other tools that use an input layer and search distance parameters.  ... View more

Existing functionality: Currently, when you insert an "Table Attribute" dynamic text element into a layout in ArcGIS Pro, you set the input source to a table (layer) in a single map frame.  IDEA: Add an expression option to the "Table" parameter so that Arcade can be used to generate a new or modified input table based on multiple map layers/tables.  USE CASE: I have many scenarios come up in my map production where we try to minimise the amount of manual input required by our users over elements in the layout. This feature would hopefully enable us to perform an intersect between 2 layers in the map, so that a focus feature set by a definition query or map series (e.g. a Plantation) can be used to select one or multiple intersecting features from another layer (e.g. Local Government Authority) to then display on the layout. In the image below, it would return only feature "P" instead of all features (A-Z) or all visible features (A,M,P & Z) from the grey layer.  This would open up more possibilities than simply adding in another option to the Query parameter (e.g. a "Search Table" option with distance settings) that could be used to find features in the "Table" that are within X of the "Search" table, but I've listed that as a separate idea as well (potentially 'simpler' option to implement?) Include "Search Table" option for 'Table Attribute... - Esri Community   ... View more

Preamble In our organisation, we've been using ArcGIS Online since the early days after it's initial release. This means we have many layers that have been around for quite some time. One thing we never really understood early on, and have found to be problematic in the last couple of years, is not having well considered and consistent spatial references for all our feature services.  Whilst the default spatial reference in ArcGIS Online WebMaps is WGS 1984 Web Mercator (auxilary sphere), feature services can be published using any coordinate system ArcGIS Online then projects them on-the-fly in webmaps. This usually is not an issue. We have found it though to be problematic when using the layers in ArcGIS Pro, and when there are a mix of spatial references that use both GDA94 and GDA2020. This mix was introducing data shifts that could not be dealt with through transformation selections. We have since decided the most robust way forward would be to republish everything in ArcGIS Online to use the same projection: WGS 1984 Web Mercator. This way, when loaded into a ArcGIS Pro project, we don't have to worry about incompatibility between GDA94 and 2020 being an issue any more.  NOTE: We still have many non- AGOL datasets that need to be reprojected as well, but thats a much simpler task.  Considerations As I'm sure many could appreciate, making significant changes to many feature services is no small feat. This meant scheduling a freeze period where users would not be able to capture or edit data without risking that data being lost. It also meant that all offline areas in Field Maps would need to be recreated (which is quite a lot in our org)! We estimated it would take our team 3 days to republish our feature services , check them then update impacted WebMaps & ArcGIS Pro templates. We had 102 feature services in total that needed their spatial reference updated. These then had another 120 associated hosted views that needed to be considered. We also wanted to preserve the Editor Tracking history in all our layers (something easily lost without proper consideration).  You may have seen recently issues around Editor Tracking fields and new default high-precision date fields in ArcGIS Online (Solved: Editor Tracking – High Precision Date Fields issue... - Esri Community). To mitigate these issues and speed up the process as much as possible, I built a model builder tool that would download each sub-layer/table in a feature service and recreate the Editor Tracking fields, preserving the creation/editor history and enabling editor tracking on the local (temp) data prior to publishing. This speeds up 's Solution in the above post. These tools are attached for download (one for feature services with and without tracking and one for tables with tracking).  NOTE: It looks for the default Creator/CreationDate/Editor/EditDate fields created in ArcGIS Online. If your fields vary from this, the model will need to be modified to recognise these.  Model to download feature service and maintain editor tracking     Process ArcGIS Pro Setup Open new ArcGIS Pro project and insert a new map Check the “Enable assignment of Unique ID’s” option in the Map Properties > General window Ensure map projection is set to WGS 1984 Web Mercator (auxiliary sphere) Consider using the setting Project > Options > Map and Scene > Spatial Reference > “Choose spatial reference” instead of “Use spatial reference of first operational layer” to prevent the map changing to a different spatial reference when adding data Layer Setup Add hosted feature service to ArcGIS Pro from Portal Run “Download FS with Editor Tracking” tool (W:\Mapping.atbx) NOTE: Select the input feature service by browsing through Portal – don’t select the layer in the map. Ensure you select the sub-layer so that the URL has the layer ID number at the end (e.g. /0) If the tool fails, it is due to the layer not having matching Editor Tracking fields. Run the version of the tool called “Download FS without Editor Tracking” or update the tool to match your editor tracking field names.  If a feature service has more than one sub-layer, run this process for each sublayer. Right click feature service layers you added to the map in Step 1 > Copy then right click the corresponding layer/sublayer output from Step 2 > Paste Properties. Repeat for each downloaded (temp) sublayer until all are are done.  Rename the layers to match the existing feature service sublayers.  Update the new layer properties to match the feature services ID (number) at the end of the service URL (data source) – ensure you do this last as “Paste Properties” will change this   Remove the layer added in Step 1 (existing feature service) leaving only your temporary data Confirm your map projection is still the desired spatial reference Updating Feature Service Go to ArcGIS Online and disable Sync on any Hosted Views (and the base if applicable) – all replicas need to be deregistered or the next step won’t be able to proceed Go to the Share ribbon > Web Layer > Overwrite Web Layer Select the original feature service and click OK In the Configuration section, ensure you check the “Preserve editor tracking info” (unless no editor tracking was found when downloading the feature service) Update the Time Zones (if required)   Analyse the layer for any errors and rectify as required Publish the feature service NOTE: If the republish fails, check that you didn't miss any Sync options on Views. If you can't get it to publish successfully, you may need to publish the layer as a V2 feature service and then change the data source of any associated Views to the new feature service. See "Learnings" below for more details.  Check feature service and all hosted views to ensure that they work (check the Data tab in ArcGIS Online). If you find any views where the Data tab shows “Data Error”, try republishing the layer again (this will likely fix the issue). Also ensure you check that you can select a feature in your feature service View attribute tables and zoom to the features. We found occasionally a view appeared to be working (showed records) but no features were visible in the map. See "Learnings" below for more details.  Reenable Sync on any Views Learnings When overwriting a feature service, you get a warning window that states you may lose all of it's associated data and popups. Data should be retained through the download process undertaken at the beginning. Popups and other styling (symbology, labels, etc) should also be retained through the Copy > Paste Properties steps undertaken earlier. This warning does NOT affect any views of the feature service. They will remain as they were before the layer was overwritten.    As mentioned in Step 8 above, sometimes we successfully overwrote a feature service, but a view may fail to reflect the updates, returning a Data Error on the Data tab of the items page on ArcGIS Online Item page.  Sometimes clicking Publish in ArcGIS Pro again would fix this. If you tried the Publish step again and you still can’t get all Views working, you may need to recreate the view manually and replace it in all WebMaps and ArcGIS Pro templates that it exists in. We found this was easiest done with the old one and new one side-by-side on screen so you can step through the defined view settings (Settings > Update View), Visualisation and Settings pages.   We found that some of our feature services simply refused to be overwritten. These ones we had to publish again from scratch (with "V2" appended to the name - see screenshots below). It's important to remember that you can't change the source of a hosted view to another feature service unless they have the same spatial reference as the original, and all the required fields are present (amongst other things - further reading here: Swap the source of a hosted feature layer view—ArcGIS Online Help | Documentation). Because we were going through this process in order to update spatial references, this meant publishing the V2 layer with the original spatial reference (e.g. GDA94 MGA Zone 50), changing the sources of all the views to the V2 feature service, and then we would go through the above republish (overwrite) process again on the V2 layer to update it's spatial reference (to WGS 1984 Web Mercator) with much more success.      Summary Despite a slow start as we ironed out the kinks in our process and ran at 2/3 team capacity for a while, we soon got on a roll and were churning through layers at a good pace. It certainly helps having someone involved who is intimately knowledgeable about the data being worked with as you can soon land in big mess if you misunderstand the relationships between hosted feature services, their views and the map/app products they exist in (not to mention the potential complications that related tables and other such things bring to the party - thankfully we only had 1 of those).  Overall, it took us 3 days to: Republish (or recreate if necessary) all 100 of the target feature services Check that they (and their views) were functional Check WebMaps and ArcGIS Pro templates for broken data sources and update them Ensure that all offline enabled WebMaps were still ready to work offline (and fix if required) Beyond the 3 day "freeze" period, a few small oversights were found and were fixed (thankfully nothing major) and Experiences were updated to reflect changed data sources (resulting in broken expressions).  ... View more