This is the last of three blogs that outlines several of the key improvements to Esri Production Mapping’s product library at 10.1. Today, you’ll be introduced to a new set of geoprocessing tools that increases your productivity when managing files in the product library as well as some useful tips for upgrading your existing product library to 10.1.
Managing your product library files
The Product Library toolset provides a number of tools for working with the files you maintain in product library. Tools are provided for performing common tasks such as check in/out, get local copies, as well as upgrading your production databases. These tools can be called in Python scripts and models, allowing you even more flexibility for working with and managing your files in product library and the associated databases.
The recently released Manage Product Library Files is a great example of what can be accomplished when you leverage these tools in Python scripts and models. Manage Product Library Files provides capabilities for adding a layer file (.lyr) to all products in a series, exporting products in a series to georeferenced PDF, as well as creating a map package (.mpk) from a chosen product. Let’s explore each of these in more detail.
The Add Layer to Products script can be very useful when you have a new layer, or modification to an existing one, that you’d like added to all the products in a series. So, instead of having to check out each product, add the layer, then check the product back in, you can use this script to simply batch add that layer file to each. This particular script leverages the List Files, Check Out File, and Check In File geoprocessing tools.
The Export Products to PDF script gets a local copy of each product in a series and exports them to georeferenced PDFs, which can be a considerable time saver compared to exporting each individually. This script uses the Get Local Copy geoprocessing tool.
The Create Map Package from Product model gets a copy of a chosen map product in product library and generates a map package (.mpk) which can easily be shared with others. The graphic below illustrates the models configuration.
Upgrading your product library and production database
In order to take advantage of the improvements highlighted in the three posts, you will need to update the schema of any existing product library database(s) to 10.1. This is automatically done when you set the initial product library database location in 10.1. However, here are a few things you should keep in mind before upgrading.
- Make a backup of your product library database before performing the upgrade to 10.1. That way, if the upgrade does not complete successfully for some reason, you will still have a copy of your original product library.
- Remember, once the product library is upgraded to 10.1, it cannot be used with previous ArcGIS versions. If some of your users are doing production on 10 you may want to consider creating a backup, perform necessary testing on 10.1, and once complete, upgrade the databases to the new version.
- If your product library is in SDE, you must be connected as the owner of the product library tables in order to perform a database upgrade to 10.1.
That completes the last of the blogs in the Improvements to Product Library in 10.1 series. Keep an eye out for future blogs which will provide additional examples on using these new geoprocessing tools.
Content contributed by Amber Bethell