New release of Local Government Information Model supports upcoming Address and Facilities Maps and Apps

ArcGIS for Local Government provides a simple, harmonized local government information model that supports a series of maps and apps used by local governments. The information model reflects specific application requirements and the cartographic requirements necessary to produce rich, multi-scale base maps and operational layers.   You can download the information model from ArcGIS.com and migrate your content into this geodatabase design.  When you do, you can quickly take advantage of the maps and apps published on the ArcGIS for Local Government Resource Center.


The Local Government Information Model in ArcCatalog

This release of the local government information model includes a series of major updates.

Major Updates:

The Address feature dataset was updated to support the active management of site addresses. The SiteAddress feature class was retired and three new feature classes were added to the local government information model. This update supports a series of Address Editing apps currently under development. The new feature classes and a PostalAddress table in the local government information model are a physical implementation of the FGDC United States Thoroughfare, Landmark, and Postal Address Data Standard and were adapted to support site address maintenance in local government.

The FacilitiesStreets feature dataset was updated to support the active management of facilities and campuses.This update supports a series of Facility/Campus management apps currently under development.  For many who have already begun to use the features in this dataset, you’ll find we’ve done some pretty extensive work on the data model for features like, signs, streetlights, and signals. In addition, we’ve incorporated portions of the Building Interior Space Data Model (BISDM) to support building/interior space management and extended it to support exterior features found on government grounds, parks, and even campuses.  Much of this work will also support Public Works apps that require information about paved areas, pavement markings, poles, signs, signals, etc.

This update to the information model also supports a new campus basemap we will release later this summer.  When you begin to use this information model, you will be able to produce a great basemap for your government facilities, downtowns, and campuses.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The new campus basemap with sample data from the Esri Campus

This release of the local government information model also includes a series of more minor updates.

Minor Updates:

The Parcel Fabric, contained in the ParcelEditing feature dataset now supports the active management of PLSS Sixteenth Sections. A new parcel type was added to the ParcelType domain to accommodate this requirement.

The ParkRecInfo table was added to the local government information model to support the Parks and Recreation Finder application currently under development.

The ServiceRequest feature class in the CitizenService feature dataset now supports the creation of service requests within buildings.  The building floor and interior space attributes were added to the feature class to support Facilities Management applications currently under development.

Known Issues:

There are a few known issues we’re working to resolve in future releases.

Your imagery and surface models must be added to this schema manually.

Layer Packages (LPKs) do not currently support standalone tables in the geodatabase.  After you’ve created your schema, please copy the ten stand alone geodatabase tables from the sample dataset in a recent application download.  Refer to the Data Dictionary for a complete list of the standalone tables you’ll need to complete the Local Government Information Model.

If you are using ArcGIS Desktop SP1, the ParcelType domain will have to be applied to the Type field in the Parcel fabric class manually after you create your schema.  

Quick Summary:

We continue to evolve the local government information model as we add new maps and apps to the ArcGIS for Local Government system. Your feedback is vital. So don’t hesitate to let us know what you think about the information model and what maps and apps will help you in your local government.  

We’ve got some exciting things coming this summer and early fall so keep a close eye on the Local Government Blog or follow us on Twitter if you’d like to learn more about how ArcGIS for Local Government can help you effectively deploy GIS.  

This entry was posted in Local Government and tagged , , , , , , , , , , , , , , , , , , , , , , , , . Bookmark the permalink.

Leave a Reply

8 Comments

  1. snelsonbanff says:

    Looking forward to testing/implementing this model and especially take advantage of the additional LG maps/apps!
    One big hurdle for me is I already have production data in GDBs, how do you recommend a user adopt the model, but still maintain data in production? I’m concerned with the ability to implement this model, while at the same time allow for the data contained in the same model be available to existing ArcServer services – especially with only Standard WorkGroup licencing and ArcEditor capabilites.
    Is there any documentationsuggestions on implementing the model and merging existing data/processes?
    Steve

  2. scot6032 says:

    Steve -

    You could think about using the Local Government Information Model as a publishing schema and using GP or other ETL tools to migrate your data in to this publishing schema. Then you could begin to take advantage of the web and mobile apps, basemaps and even some of the new editing maps you may not have in your organization. The information model really is there to tie together the maps and apps we’re providing in the ArcGIS for Local Government system – so the data migration issues you mention should be tied tightly to your plans to leverage the maps and apps we’re providing on the Resource Center. One other note, we’re starting to work with Safe Software to develop a set of FME templates that will help users migrate their content to the local government information model. We’ll have more information on that at the UC this year and later this summer.

    Hope this helps.

    Scott

  3. Leitha says:

    Scott,
    Is there an easy way to incorporate these most recent changes into the last version of the model? Can we cut and paste the new feature classes into what we have already built(loaded) without starting from scratch? Is there a methodology/white paper/help file out there to help us with this?

    And if I’m not interested right now in the new facility/campus updates, is there any problem with just updating the Address portion only?

    Leitha

  4. ricki says:

    I downloaded the LG Information model and was wondering if there is any documentation or examples for the content of the attributes. Many are self-explanatory, but some are not. For example, what values would go in the POINTTYPE field. The metadata has a one-sentence, very general description which doesn’t really tell me what goes in there. What is this attribute used for? Where can I look this up?

  5. ricki says:

    Just found the domain in the data dictionary. That helps a lot.

  6. marauder57 says:

    Scott,

    Same question as Leitha is there a script or an easy way to incorporate the new parts of the model into the previous version without having to reload everything and then resource all the maps and apps we are currently using?

  7. scot6032 says:

    We’re starting to work on a series of enhancements to the Xray for ArcCatalog Add-in that will help users apply incremental changes to their production data models. Essentially, Xray will help users develop scripts that can be used to apply changes to the data model as we release updates. Look for these enhancements to start making their way on to the Resource Center in late 2011.

  8. jmward says:

    I am wondering why the domains for the SiteAddress feature class use abbreviations. The standard recommends the full spelling of the words.