ArcGIS Pro - Creating Project Templates without Default File Geodatabase

11-21-2016 12:44 PM
Status: Open
Labels (1)
Occasional Contributor II

With Pro, it doesn't want to remember SDE connections or folder connections, I have template MXDs that I always start with ArcMap projects, so I'd like to the same thing with Pro. Or even start a blank Pro Project, however have all those folder/SDE connections and maybe a layout set with page sizes. The solution it to create Project Templates.

I've created Templates. Now want to update that templates with some new changes. I've even tried creating a brand new templates. However when creating a new Project, you have to select the default folder location, which sets the default file geodatabase, and toolbox. So I get everything set in my Pro Project, then Share > Export Project Template. It creates the template and I can share it how I please. However those default file geodatabase come with the template. Therefore another user at my organization that would use this template would have the same default FGDB as me. Which is something I don't want.

I know there is an option to pick the same FGDB for every Project, for example a network location, however I don't really want my users to be using the same one for all projects.

I'd like to be able to create a template without the default file geodatabase that was used in that original template Project (aspx file). Because the user creates the default FGDB when they open the template and create a new Project.


Using a template actually creates two FGDB's: The default one that was in your project when you made the template, then another one when you create a new project using the template. So instead of 40 files (typical # in a new blank FGDB) fire-hosing your nightly back up, there are now 80, when you wanted zero because you're using things like Portal, Server, and AGOL. Tech support is telling me that this is the designed behavior, which I don't buy. How could filling up a project folder with that much clutter be "designed"? . Pro doesn't allow you the option of not creating a default GDB (why?), just use the same one over and over, or create a new one for each project. Setting the default one to an SDE simply isn't possible in our security model.


You are correct that the templates have actually two file geodatabases. For my templates I've created 'Junk' FGDB's and toolboxes that are there just for the purpose of template creation. My Users know not to use those and that they are just junk areas that we can't get around. So when a User uses the template and creates a new project their default items get created with the new Project, however they also have the 'junk' areas that have to be there when creating a template. If this is by design, as your tech support person said, then what is the purpose of that? What use case requires that? It doesn't make sense that you have to have default items for template creation, because all of the default items get created when a new project is created, which is what happens when you use a template to start a project.


When creating a project template there are options to include toolboxes and include history items, how about an option to include the geodatabase which, when unchecked, would exclude the geodatabase and create a new one when the template is opened?


Along similar lines, we have proposed not allowing for a geodatabase to persist in projects created from a template that was created from a project with an empty home/default geodatabase. This would mitigate for extraneous geodatabases in the file structure that is set up in a new project generated from a project template. Please check out this Idea Post:


Many of my projects have geodatabases already set up with pre-set feature datasets and directories. I would like to not have any of the automatically created stuff ... at all ... ever. It is just extra unwanted stuff that takes up space.