nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Local Government Information Model November Release

AnthonyNguyen1

Hello!

I've been working with the local government information model for some time now, and see that there is a new release available as of November (according to the 'What's New?' in the 10.1 Resource Center). This new release would fix several of the problems I have been having with the previous version. However, I can't seem to find where to get it! When I go to the Local Government Information Model (ArcGIS 10.1) page, it still shows the latest release as July.

Does anyone know or can redirect me to where I can get the latest version?

Any help would be appreciated!

Vind meer berichten getagd met

Local

Accepted answers

AlanToms

http://www.arcgis.com/home/item.html?id=5f799e6d23d94e25b5aaaf2a58e63fb1

All comments

AlanToms

http://www.arcgis.com/home/item.html?id=5f799e6d23d94e25b5aaaf2a58e63fb1

AnthonyNguyen1

Thanks! I guess I was just a little too early looking for it.

JustinNgan

Do the following errors from X-Ray mean that the XML cannot be successfully used to create a GDB?

Errors

MissingClass RelationshipClassName - lrParceltoLine DatasetName -
MissingClass RelationshipClassName - lrLinesToAnno DatasetName - ParcelDimensions
MissingClass RelationshipClassName - lrParceltoPlan DatasetName -
MissingClass RelationshipClassName - lrParcelToCondo DatasetName - TaxParcelCondo

Warnings

ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DEPTH DatasetType - swDetention/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DEPTH DatasetType - swOpenDrain/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - ACTION DatasetType - CIPPoints/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - ACTION DatasetType - CIPPolygons/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - ACTION DatasetType - CIPPolylines/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - TimeStamp DatasetType - AGM_FieldCrewLog/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - Note DatasetType - AGM_FieldCrewMembers/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - TimeStamp DatasetType - AGM_FieldCrewMembers/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - STATE DatasetType - FEMAFloodZone/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - ssManholeInspection__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - wHydrantInspection__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - wValveInspection__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - ssOverflowEvent__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - ssBackupEvent__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - OutfallInspection__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - CatchbasinInspection__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - MarkupPolygon__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - wLeak__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - TIMESTAMP DatasetType - MarkupPolygon/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - START DatasetType - piAlert/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DEPTH DatasetType - ssDetention/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DEPTH DatasetType - ssOpenDrain/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - ACTION DatasetType - piCIPCost/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - ACTION DatasetType - piCIPReplacement/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - STATE DatasetType - PollingPlace/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - LandUseCase__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - RANK DatasetType - ServiceRequestComment/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - TYPE DatasetType - Plume/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - ServiceRequest__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - PollingPlace__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - Value DatasetType - Band_1/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - Count DatasetType - Band_1/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - ACTION DatasetType - luCodeViolationInspection/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - luCodeViolationInspection__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - STATE DatasetType - FacilitySitePoint/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - TYPE DatasetType - Waterbody/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - TYPE DatasetType - Waterline/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - PreFirePlanPoint__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - PreFirePlan__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - RANK DatasetType - ParkRecComment/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - ParkRecInfo__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - FacilitySitePoint__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - BuildingFloor__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - BuildingPhotoLocation__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - Sign__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - DamageCommercialBuilding__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - DamagePublicFacility__ATTACH/Field/Name
ReservedName ErrorDesc - SQL Reserved Word detected. Please verify that this is not a reserved word on your database platform(s) ReservedWord - DATA DatasetType - DamageResidentialBuilding__ATTACH/Field/Name

ScottOppmann

Justin -

I would import the XML workspace in to a file geodatabase first, then copy it to your SDE database. The warnings you are getting are primarily on system fields within the geodatabase (Parcel Fabric, Attachments, etc.) and when you copy and paste it in to your SDE database, ArcCatalog should take care of that for you.

Dont know if you've seen this help topic, but it will help you get an empty schema set up.

Scott

ScottOppmann

Ryan

I would use X-ray for ArcCatalog to analyze the differences between your schema and the November release and then use the merge schema tool as you wish to apply the changes. X-ray also has a tool called Import Using Geoprocessing that can be used to append schema changes to your existing model. You'll just need to isolate the updates you want to make prior to using this tool.

Scott

AdamCottrell

Ryan

I would use X-ray for ArcCatalog to analyze the differences between your schema and the November release and then use the merge schema tool as you wish to apply the changes. X-ray also has a tool called Import Using Geoprocessing that can be used to append schema changes to your existing model. You'll just need to isolate the updates you want to make prior to using this tool.

Scott

Is there a document describing this workflow?

ScottOppmann

No documentation, but the video will help get you started.

Scott

JoshWhite

I cannot get the Water Utility Network toolbars to show up. The attribute assistant updates went just fine and the new toolbar appears. The other two toolbars are not in the list and do not appear in the add-in even after re running the AddIn File.

The previous Infrastructure Reporting and Editing toolbars are still available. Do I need to unistall these older ones first?

LindsayThomas

Hi Josh,

Yes, please delete your addin's before you add your new ones.

Make sure you have ArcGIS closed when you install your new addins.

Cheers,
Lindsay

JoshWhite

Thanks, I had already done this and the installation went through. It would be helpful to have this pointed out in the installation guide.

JamesGirvan

I am a county GIS Coordinator. After years of 9.3.1 we just upgraded to 10.0 on our enterprise system. Our plan is to upgrade system hardware then upgrade to 10.1 and beyond. Should I wait until upgrading to 10.1 before moving to the LGIM?

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.