Latest Contributions by ScottOppmann

Hanlie -  The CapitalPlanning feature dataset is actually used in the Capital Improvement Planning, which is an ArcMap based planning solution offering.  It is not used in the web based Capital Improvement Plan.  The feature layers used in the new Capital Project Planning solutions are created when you deploy the solution with the ArcGIS Solutions Deployment Tool, or manually configure the solution using the steps outlined on the solution site. Scott ... View more

Eddie - Assume you're looking for the Capital Project Planning solutions in the deployment tool?  Please verify if you are logged in to an ArcGIS Online or ArcGIS Enterprise organization when using the Solutions Deployment Tool. Currently, all of the Capital Project Planning solutions are supported in an ArcGIS Online organization and a few are supported in ArcGIS Enterprise 10.6.  So you will see the Capital Planning solutions in the list when you are logged in to ArcGIS Online or an ArcGIS Enterprise 10.6 organization.   We'll add ArcGIS Enterprise support for the remaining solutions later this year.  Scott ... View more

Hanlie -  The Capital Improvement Plan can be deployed to ArcGIS Online and ArcGIS Enterprise 10.6 organizations.  See the minimum system requirements here - Capital Improvement Plan | ArcGIS for Local Government.  I would assume you are trying to deploy the solution to an older version of ArcGIS Enterprise / Portal.  Please confirm. In this case, the Capital Improvement Plan is a configuration of the Storymap Journal and can be manually configured in other supporting ArcGIS Enterprise versions.   Scott ... View more

Jay - The feature layer views for the capital planning solutions have a series of View Definitions set on them that define which fields and features are visible.  The view definitions help us manage the state of capital projects and ensure only certain fields are visible / can be edited by specific users in an organization.  Go to the Visualization Tab for the feature layer view and review the View Definition.  Then compare the View Definitions to the sample project data you created.  Let me know if you have any questions. Scott ... View more

On 3/24/17 we posted a new version of the Schema Migration Wizard.   This update includes a series of enhancements to the validation routines that increase the reliability of the migration workflows.  In addition, we have removed many of the legacy information models and included the June 2016 and March 2017 releases.  If you are using an earlier release (pre ArcGIS 10.3) of the information model, start with None when selecting a Current Solution Version in the wizard.  Thanks for your patience and don't hesitate to contact us if you have any problems. ... View more

Erik -  If you haven't resolved your issue yet, I would encourage you to contact Esri Support Services.  They should be able help you resolve the issue you're having. Scott ... View more

Bob / Skyler -  Let me take a minute to highlight the changes that have been occurring with the Local Government Information Model (LGIM) because I think this context will help local government GIS professionals understand the changes we made in 2016 and where we are heading with this information model in 2017.   With the emergence of ArcGIS organizations (online and on premise), we have been pivoting away from a single data model for local governments.  We never intended the LGIM to be a “standard” for local governments.  GIS professionals can configure the LGIM to fit their unique organizational needs.  The information model is a living data model that evolves as new maps and apps are added to the ArcGIS for Local Government solution; and ArcGIS evolves in ways that simplify the deployment of these solution offerings.   The LGIM has historically been supplied as a geodatabase schema.  At the time of the LGIM’s inception, this was the most popular way for local governments to store data in ArcGIS.  Delivering the LGIM as a geodabase also provided a foundation for the ArcGIS for Local Government solutions and helped you organize your data so you could quickly deploy the solution offerings.  But with today’s popularity of hybrid WebGIS implementations, local governments are frequently using both geodatabases and hosted feature services.  Now, many of the ArcGIS for Local Government solutions use hosted feature services solely and we are sharing these feature layer designs in the ArcGIS for Local Government Service Catalogs so they can be used to create new hosted feature services in your ArcGIS organization.  And with the release of the ArcGIS Solutions Deployment Tool, many ArcGIS for Local Government maps and apps can be now be quickly deployed in your organization without having to construct the solution offering manually.    Finally, the Local Government Information Model isn't going anywhere.  We still plan on maintaining it and evolving the content included as we add new maps and apps to the ArcGIS for Local Government solution.  But you will see (the March 2017 release was the first step) us start to refine the content included in the model so it generally includes content that would naturally be managed / used / analyzed in ArcGIS Desktop.   More detailed notes on the changes we made can be found in the release notes.  Hope this context helps and feel free to let me know if you have any further questions. Scott ... View more

Jeff -  Over the last few months, we have been working on a series of enhancements to the schema migration wizard and Xray to improve the overall experience when using the Schema Migration Wizard.   Know we are delinquent on its release but we are finishing final certification and plan on releasing a new version in a week or so.   Saying that, I also want to also take a minute to highlight the changes that have been occurring with the Local Government Information Model (LGIM) because I think this context will help local government GIS professionals understand the changes we made in 2016 and where we are heading with this information model in 2017. With the emergence of ArcGIS organizations (online and on premise), we have been pivoting away from a single data model for local governments.  As Cassidy stated, we never intended the LGIM to be a “standard” for local governments.  GIS professionals can configure the LGIM to fit their unique organizational needs.  The information model is a living data model that evolves as new maps and apps are added to the ArcGIS for Local Government solution; and ArcGIS evolves in ways that simplify the deployment of these solution offerings.   The LGIM has historically been supplied as a geodatabase schema.  At the time of the LGIM’s inception, this was the most popular way for local governments to store data in ArcGIS.  Delivering the LGIM as a geodabase also provided a foundation for the ArcGIS for Local Government solutions and helped you organize your data so you could quickly deploy the solution offerings.  But with today’s popularity of hybrid WebGIS implementations, local governments are frequently using both geodatabases and hosted feature services.  Now, many of the ArcGIS for Local Government solutions use hosted feature services solely and we are sharing these feature layer designs in the ArcGIS for Local Government Service Catalogs so they can be used to create new hosted feature services in your ArcGIS organization.  And with the release of the ArcGIS Solutions Deployment Tool, many ArcGIS for Local Government maps and apps can be now be quickly deployed in your organization without having to construct the solution offering manually.  Finally, the Local Government Information Model isn't going anywhere.  We still plan on maintaining it and evolving the content included as we add new maps and apps to the ArcGIS for Local Government solution.  But you will see (the March 2017 release was the first step) us start to refine the content included in the model so it generally includes content that would naturally be managed / used / analyzed in ArcGIS Desktop.   I'll update this post when we ship the new Schema Migration Wizard and hope the additional context helps.   Talk soon. Scott ... View more

The first thing you need to do is create the feature layers in your ArcGIS organization.  Here is a help topic that will guide you through the process of using our feature layer templates to publish a new service in your organization.  Once you have it in your ArcGIS organization, you can download the layers as a file geodatabase and merge it in to your local geodatabase as you wish.  Don't hesitate to contact Esri support services as well for assistance here.  I would be glad to get on a call with you as well if you'd like. ... View more

Brian -  The workflow is very similar to the configure feature layer topic.  Essentially the steps are: Sign in to your ArcGIS organization. Export the data from the hosted feature layer you deployed in your ArcGIS organization. Browse to the file geodatabase item in your ArcGIS organization, then click Open and Download to save the zipped file geodatabase locally. Unzip the file geodatabase and place the contents on your computer. If necessary, modify the file geodatabase schema with ArcCatalog. Author a map with layers and/or tables you modified. Optionally, load your data into the new layers and tables. Publish a new feature service to ArcGIS Server using ArcMap. Configure the map and application you deployed in your organization and wire up the new ArcGIS Server service.  Hope this helps and please let me know if you have any further questions. Scott ... View more

Brett -  We never envisioned the local government information model as an all encompassing (or enterprise) data model for cities and counties.  It was designed to support the ArcGIS for Local Government solutions and provide you a way to organize your geographic content so you could quickly deploy the configurable maps and apps in the solution.  When we started developing the solution, a geodatabase schema was the only way we could provide that information model to ArcGIS users.  But as ArcGIS has evolved and web services have become a larger part of the deployment model, we have been able parse the information model in to more bit size chunks (service definitions) that directly support the specific solutions we provide. This simplifies the deployment of each individual solution offering yet still allows you to configure the individual layers to meet specific needs of your organization. Please don't assume that these service definitions have to be deployed in ArcGIS Online.  You can deploy these services on premise with ArcGIS for Server (or Portal for ArcGIS) or in the cloud with your ArcGIS Online subscription.  You will certainly be able to take the layers we provide going forward and merge them in to a single enterprise model for your organization.  I don't generally suggest users implement the entire information model we're providing and instead focus on the specific solutions you'd like to deploy in your organization.  Once you identify the solutions you'd like to deploy, then work through the required services, maps, and ultimately the underlying information model.   Would be glad to discuss this  more fully if you'd like and how you might be able to incorporate our plans in your implementation.  Just send me an email if you'd like to connect up. ... View more

Brett -  Yes, we have been removing operational layers (like community events) from the Local Government Information Model and instead providing them as service definitions you can quickly deploy online or on premise without having to worry about the larger information model.  Our goal is to leverage advancements in ArcGIS and simplify your adoption of the ArcGIS for Local Government solution.  The release of the Community Events solution in June (previous version was an ArcMap workflow - new version is a collection of apps that are tuned for specific users in your organization) was a perfect time to simplify these features and remove them from the information model.    Saying that, the service definitions can be used to stand up community event layers in your enterprise GDB. This is a trend you will see going forward in the ArcGIS for Local Government solution.  We will be removing content that can be quickly deployed with service definitions (on premise or online) from the information model and only delivering content in the Local Government Information Model that is pertinent to desktop data management and analysis workflows.  Hope this helps and let me know if you have any further questions.   Scott ... View more

Russell - We simplify the data structure on the road centerline and site address layers by storing all the road name elements in the master street name table.  This helps us optimize the editing workflows and really simplified the configuration of the locators you'll use in the rest of your ArcGIS maps and apps. I do encourage users to load their existing data in to the road centerline and site address layers and then use the master street name table to clean up/standardize these values.  For example: if you have road centerlines that were gathered for a 911 project and they have their unique list of road names - load those in to the road centerline layer and push the road names in to the master street name table.  If you have site addresses that were derived from parcel centroids, load them in to the site address layer and push those road names in to the master street name table as well.  Then you can use the Attribute Assistant rules to push edits (to standardize names) you make to the master street name table to the site address and road centerline layers. Hope this helps and let me know if you have any further questions.  There is a video on the ArcGIS for Local Government Meetup site from a few years back that provides a detailed overview of the Addressing solutions.  A bit dated now, but the fundamentals of the address data management solution are still valid.   We will probably have another meetup this fall to review the addressing solutions again and talk about the enhancements we provided in the June 2016 release. Finally - if you are going to the UC this year, we have a TW that will dive deeply in to our Addressing Solutions. ... View more