This session will introduce you to ArcGIS Production Mapping and ArcGIS Defense Mapping extensions in ArcGIS Pro and how you can leverage them to efficiently and cost-effectively produce standardized data with exacting quality and output requirements for end-to-end production workflows. Whether you are new to this extension or a longtime user, you should attend to learn how to implement an efficient production environment in ArcGIS Pro and what's new in the latest release.
Mapping agencies require highly tuned data and map production technologies capable of supporting mission critical needs. Learn how the latest developments in ArcGIS Production Mapping and ArcGIS Defense Mapping standardize and streamline standards-based cartographic production tasks using ArcGIS Pro.
In this workshop we will demonstrate the tools and workflows to automate creation of multi-scale data and cartographic products from a single best scale database. Learn how to generalize your topographic data by leveraging the tools from ArcGIS Production Mapping and ArcGIS Defense Mapping extensions in ArcGIS Pro.
Learn how to improve the quality and consistency of your topographic data. This workshop will show how to manage topographic processes with ArcGIS Production Mapping and ArcGIS Defense Mapping extensions. See how to manage your topographic data using ArcGIS workflows and improve data quality with ArcGIS Data Reviewer using Production Mapping and Defense Mapping product files.
Use the following Booth IDs toChat or Schedule a Meeting with an Expert!
Topographic Mapping - SH-09-05 (Located in the National Mapping, Charting and Official Statistics area)
ArcGIS Defense Mapping - SH-04-04 (Located in the Defense and Intelligence Solutions area) or SH-09-02(Located in the National Mapping, Charting and Official Statistics area)
When you have limited, non-administrative privileges to theDefense Mappinginstallation folder, the Unpack Product Files geoprocessing tool in the Utilities toolset allows you to use Defense Mappingtools that require access to the installed product files.
Thus copying and extracting selected product files to the path provided, by you.
A special recognition goes to the years of work by@David Watkinsfor Product Management,@Clint Lovemanand ESPECIALLY@Amber Bethellfor her extraordinary work to make Automation of Multi Resolution Geospatial Production (multi-scale mapping) with generalization possible.
There are many other people that worked with@Amber Bethellto make the Multi Resolution Geospatial Production modeling, geoprocessing tools and parallel processing work that Amber did with Kadaster to be successful. Please forward this to them and my apologies for missing them.
Lastly, I want to recognize Paul Hardy (now retired from Esri) and John van Smaalen, formerly of Esri-NL, who enabled Dutch Kadaster in this vision in the early days.
@Citabria Stevensdid a great job focusing on the innovation of Dutch Kadaster and particularly Ben Bruns who insisted the GIS Hero article focus on his team and not him, but all of you had a part to play in it. We can all be proud that Multi Resolution Geospatial Production powered by Esri is absolutely changing our national mapping and geospatial authority customers in a very positive and profound way.
Here are some tips for allocating resources to properly run a world Gazetteer GeoLocator. I started by using these tools created just for this located here Geonames Locator | ArcGIS for Defense . These were a great help but I ran in to some minor issues with this when I modified it to turn on the suggest for the GeoLocator. I found I had to update it to run in the background and install the 64bit background GP processing to my ArcMap. Once I did this I was able to create the GeoLocator with out any issues. When I went to publish it there were System Memory issues that had to be address. I found an old blog post that helped with this so I thought I would post it here for other to find.
ArcGIS locators support a “Run Time Memory Limit” parameter. For large geocoding jobs working against a large locator such as US streets, or world, you will want to set this limit near the capabilities of the system. With ArcGIS 10.5.1, geocoding performance continues improving as the cache grows beyond 2GB. By default, ArcGIS locators are configured to use 1024 MB of system memory. ArcGIS supports use of 2GB memory on a 32-bit system and 3GB of memory on a 64-bit system.
There is a formula for determining out how much memory the system should have to run this kind of locator. When the RuntimeMemoryLimit is set to 2 GB then you should allocate 3 GB per locator instance (there is some additional overhead and then we round up). Additionally, you will want to have aminimumof 4 GB of RAM for ArcGIS Server.
(8 instances * 3 GB) + 4 GB for Server = aminimum28 GB of RAM required.
Instructions for increasing the run time memory limit.This step must be done prior to publishing the locator as a service:
Open the Gazetteer folder containing the Gazetteer locator.
Open the *.loc file in a text editor (e.g. NGAGeonames.loc).
Look for the line that starts with RuntimeMemoryLimit =
If the value does not exist, create one and change the value to represent the number of bytes of system memory you want to allocate for the locator: RuntimeMemoryLimit = 2048000000
Save the locator.
Open the *.loc.xml file (e.g. NGAGeonames.loc.xml).
Update each instance of “RuntimeMemoryLimit“ to 2048 MB
Lastly use the locator and compare performance and system memory use.
I hope you found this useful. If you have any other tuning suggestions I would love to see them in the comments.