TRAINING GUIDE. Geodatabase Configuration Tool Overview

Transcription

1 TRAINING GUIDE Gedatabase Cnfiguratin Tl Overview

2 Gedatabase Cnfiguratin Tl Overview In this sessin, we ll intrduce yu t the Gedatabase Cnfiguratin tl fr ArcGIS 10x. We ll give yu infrmatin abut the synchrnizatin setup, synchrnizatin prcess and database cnnectin. Table f Cntents Gedatabase Cnfiguratin... 4 Cnnectin Prperties... 6 SDE Setup... 6 Versin Setup... 7 Delete Multiple Feature Classes... 8 Set Update Length/Area Flag t True... 9 Feature Class Cnfiguratin... 9 Feature Class Infrmatin Tab General Frm Infrmatin Feature Class Fields (Nt linked t Lucity) Feature Class Linking Fields Alias Names Tab Parent Recrd Linking Tab Lgical Netwrk Tab Assciated Wrkspaces Tab Feature Class Fields Grid Lucity Cde/Type fields Lucity Cmpsite Address fields Clr Cding Add a Feature Class Cnfiguratin Delete a Feature Class Cnfiguratin Spatial Relatinships Adding Spatial Relatinships Deleting Spatial Relatinships Number Generatr Add a Number Generating Field Remve an Aut-Numbering Field Dmain Tls Dmain Cnfiguratin Reslve Dmain Discrepancies Gedatabase Cnfiguratin Tl Overview (v7.6) 2

3 Update GIS Dmains t match Lucity picklists Update Lucity picklists t match GIS Dmains Update Parent Linking Dmains Update Street Name, MUTCD, and Tree Dmains Feature Class Schema Add Lucity AutID Field Add Lucity In DB Field Add Mdified/Synched Fields Set Field Alias Equal t Lucity Field Captins Set Feature Class Alias Equal t Lucity Mdule Name Imprt Feature Classes frm Schema Imprt Feature Class Alias Names Validating the Gedatabase Cnfiguratin Gedatabase Cnfiguratin Tl Overview (v7.6) 3

4 Gedatabase Cnfiguratin Once yu have created the gedatabase cnnectins with the Lucity Administratin tl yu can use the Lucity Gedatabase Cnfiguratin tl in ArcCatalg t perfrm all ther cnfiguratins. Nte: Users must have the fllwing Lucity Security permissins t use this tl GIS > GIS System Cnfiguratin > Run GIS > GIS Admin Cnnectin Strings > Edit In ArcCatalg, Click n Lucity GIS Tls>>Gedatabase Cnfiguratin. The fllwing dialg will appear: The left side f the frm lists all the gedatabase cnnectins that are currently cnfigured with Lucity. Nte: If there are n cnnectins cnfigured yu will need t use the Lucity Administratin Tl t create a new cnnectin prir t using this tl. Ntes: Gedatabase Cnfiguratin Tl Overview (v7.6) 4

5 Expanding the ndes n the left side f the frm shws the varius cmpnents f the gedatabase. The frm will be updated t shw data applicable t the selected nde type. The ndes can represent 4 types f data: 1. Gedatabase: At a minimum yu will have at least ne gedatabase cnnectin and it will be called DEFAULT. Selecting this type f nde will let yu mdify the cnnectin infrmatin and versin setup fr the gedatabase. Yu will als get the fllwing cntext menu when the nde is right-clicked. 2. Feature Class: This will be listed in the frmat f feature class name <-> Lucity table name. Fr the image abve, SWNETG is the feature class name and that feature class is mapped t the Lucity SWNET table. Selecting this type f nde will let yu mdify the prperties fr the feature class and its fields. 3. Spatial Relate: This will start with the wrd Spatial Relate and will then list the feature class field name that is updated. Select this nde t mdify the spatial relatinship prperties. 4. Number Generatr: This will start with the wrd Number Generatr and will then list the feature class field name that is cnfigured. Select this nde t mdify the number generatr prperties. Ntes: Gedatabase Cnfiguratin Tl Overview (v7.6) 5

6 Cnnectin Prperties The Cnnectin Prperties tab shws yu the gedatabase cnnectin infrmatin. T setup a Persnal r File gedatabase brwse t the database lcatin. ArcSDE setup is as fllws: SDE Setup 1. Server: This must cntain the name f the machine where ArcSDE is installed 2. Service: The nly thing that will differ between an ArcSDE spatial cnnectin and a direct cnnectin is the infrmatin stred in this field. Spatial Cnnect: This field shuld cntain the prt where ArcSDE is installed. By default this is typically D nt include the /tcp identifier; enter nly the number fr the prt. Direct Cnnect: Enter the name f the direct cnnect driver and the name f the "sde:sqlserver:gis_server\data." 3. Database: This must cntain the name f yur SQL Server gedatabase. The database listed in this field is nt the SDE repsitry database. Instead, it is the gedatabase that cntains the infrastructure data that yu want t integrate with the desktp. Fr Oracle gedatabases this must be blank. 4. Authenticatin type: Used by Lucity t cnnect t the gedatabase. If yu specify DB yu must als ppulate the UserName and Passwrd fields. UserName: If using DB authenticatin type yu must specify a user. This user must have permissin t ALL feature classes linked t Lucity. Passwrd: If using DB authenticatin type yu must als specify a passwrd fr the user. 5. Versin: This infrmatin is always required; it designates the name f the ArcSDE versin that Lucity will use when cnnecting t the gedatabase. Fr Oracle, the Versin is case sensitive. Ntes: Gedatabase Cnfiguratin Tl Overview (v7.6) 6

7 The cnnectin prperties tab als cntains the fllwing fields. 1. URL: (Optinal) The map service used t push edits t the gedatabase using the Lucity Data Update SOE 2. Update Frm Lucity: This indicates if the gedatabase shuld be updated with edits made in the Lucity desktp and web interfaces 3. Replica Gedatabase: This indicates if the gedatabase is a replica gedatabase. If this is checked, functinality with the cnfiguratin tl will change preventing sme actins (such as deleting feature classes) and enable ther actins (such as assciating feature classes) Versin Setup Clients using an enterprise gedatabase (ArcSDE) can indicate which versins f their gedatabase are "Lucity versins". This gives users the ability t selectively chse which versins shuld update the Lucity database when they are edited in ArcMap. Nte: If "Update Lucity frm all Versins" is checked then the infrmatin listed in the grid is ignred as edits t ALL versins f the gedatabase will be psted t the desktp applicatin. If that ptin is nt checked, then edits made t nly thse versins listed in the grid with the 'IsSyncVersin' ptin checked will update Lucity. Add/Delete a Versin T add a versin: 1. Click n the Add Versin buttn. 2. A new line will be added t the versin grid. Fill in the versin name and check "IsSyncVersin' if yu want t update the versin. Nte: Fr Oracle gedatabases this infrmatin is case-sensitive. T delete a versin: 1. Right-click n the versin yu want t delete and chse Delete. 2. The versin will be remved frm the grid. Ntes: Gedatabase Cnfiguratin Tl Overview (v7.6) 7

8 Delete Multiple Feature Classes Lucity versins prir t 7.5 were ppulated with the Lucity gedatabase schema. Yu may find that yu are nt using the Lucity default gedatabase schema r yu may nly be implementing a few f the feature classes. Instead f deleting these feature classes ne by ne, yu can use the Delete Multiple Feature Classes tl t perfrm a mass delete. 1. Frm the tree n the left f the Gedatabase Cnfiguratin Frm, right-click n the gedatabase nde that cntain the feature class mappings yu wish t delete and select Delete Multiple Feature Classes. Nte: This ptin is nt available fr replica gedatabases, instead refer t the Disassciate Feature Class(es) tl. 2. The fllwing dialg will appear, check all prducts yu wish t delete the feature classes fr. 3. In the grid n the right, the prgram autmatically checks all feature classes that are assciated t the selected prduct type. If yu wish t ver-ride the default selectins check the Edit default selectin checkbx. 4. Click OK t delete the marked feature class cnfiguratins. Ntes: Gedatabase Cnfiguratin Tl Overview (v7.6) 8

9 Set Update Length/Area Flag t True By default, when yu add a new feature class the Update Length/Area flag is set t false. This prperty determines if the feature class s field linked t the Lucity length/area field shuld be updated with the Esri shape length/area if the gemetry is mdified in the map. Yu may wish t ensure that all feature class cnfiguratins have this prperty set t true. Instead f inspecting each feature class cnfiguratin individually t check this value, yu can run this tl t set the value t true fr all feature classes. 1. Frm the tree n the left f the Gedatabase Cnfiguratin Frm, right-click n the gedatabase nde that cntain the feature class cnfiguratins yu wish t update and select the Set Update Length/Area Flag t True. Nte: This ptin is nt available fr replica gedatabases 2. The fllwing dialg will appear fr cnfirmatin: Feature Class Cnfiguratin T view feature class cnfiguratins, expand the crrect database nde frm the grid n the left. A list f all feature class mappings will be displayed. Select the feature class nde t view its cnfiguratin. Gedatabase Cnfiguratin Tl Overview (v7.6) 9

10 Feature Class Infrmatin Tab General Frm Infrmatin Feature Class Name: This is the name f the feature class. This is NOT the alias name. If the wner f the feature class is nt db, then yu must specify the wner in the frmat f wner.featureclassname. Click the drpdwn t see a list f current feature classes that are assciated t the gedatabase. Nte: The feature class drpdwn list will be empty if a cnnectin t the gedatabase fails. Mdule Name: This field is read-nly fr existing items in the feature class list. This is the name f the Lucity mdule t which the gedatabase feature class is related. Table Name: This field is read-nly and shws the Lucity table name that crrespnds t the selected Lucity mdule. Disable Feature Class: This flag allws yu t disable a feature class that yu are nt using, but d nt want t delete frm the setup. It is recmmended t disable any feature class that yu are nt using; it will speed up yur prcessing time. Always Update Length/Area: This flag indicates whether r nt the Lucity GIS Extensin shuld update the feature class field linked t the Lucity s length/area field when the shape f a feature has changed. If checked, the prgram will update the field in the feature class mapped t the Lucity length/area field. It updates the values in this field based n the shape.length and shape.area fields. If this ptin is left unchecked, the Length/Area fields will nly be ppulated when the feature is first created. Ntes: Gedatabase Cnfiguratin Tl Overview (v7.6) 10

11 Feature Class Fields (Nt linked t Lucity) In Lucity Flag Field- (Optinal) This field is cntrlled by Lucity t indicate t users whether r nt each recrd in the feature class has been synchrnized with Lucity. This shuld be a shrt integer field and shuld be assigned a dmain that classifies 0=N r False and 1= Yes r true. This dmain will make it easier fr end users t understand the values that will be stred in the field. Last Mdified By - (Optinal) This field is cntrlled by Lucity t indicate which user last mdified the recrd frm an edit sessin in the map. Last Mdified Date - (Optinal) This field is cntrlled by Lucity t indicate what date the recrd was last mdified frm an edit sessin in the map. Last Synchrnized Date - (Optinal) This field is cntrlled by Lucity t indicate the date when the recrd was last synchrnized with Lucity. Field fr Display - This is the field name that will be displayed with the varius Lucity GIS tls. By default, this field will be set t the cmmn ID f the feature class. Feature Class Linking Fields Cmmn Link Field 1- (Required) The unique identifier assigned by the user fr this asset. The value fr this field cannt be directly mdified; it is autmatically ppulated based n the field mappings frm the grid at the right f the page. Every mdule has ne field that defines the asset as unique. These fields are highlighted in red in the grid t the right. T enter a value in this field, find the crrespnding red highlighted field and type the field name int the Feature Class Field Name clumn. This shuld be a string field in the gedatabase, nt a numeric field. Lucity AutID Link- (Strngly Recmmended) This field is used by Lucity t stre an indexed lng integer link between the recrds in the feature class and the recrds in the Lucity inventry table. This field must be lng integer. The value fr this field name is nt editable; t update this value, use the grid t ppulate all f the red highlighted (required) fields. Nte: Starting with versin 7.1 this field is n lnger required; althugh, we still strngly recmmend yu have it. Nt having this field will impact the perfrmance f sme f the Lucity GIS tls as additinal resurces will be used t determine the AutID value based upn the cmmn ID. Gedatabase Cnfiguratin Tl Overview (v7.6) 11

12 Alias Names Tab Aliases are alternate names fr feature classes that prvide a unique identity. They are used by the Lucity Webmap, Lucity Viewer, Lucity Data Update SOE, and the Lucity Mbile fr Andrid t identify which feature classes are linked t Lucity. These Lucity mapping applicatins check the feature classes laded int them and check the display names f thse feature classes against the aliases names listed in the Gedatabase Cnfiguratin. The Alias Names tab has tw grids. The Assciated Aliases grid is a list f all the aliases assigned t the feature class. Right-click n an existing recrd t get a menu with ptins t Add, Edit, Delete, r Disassciate. Disassciating a recrd in this grid will detach it frm the selected feature class and mve it t the Available Aliases grid. Whenever a feature class appears in the Lucity Viewer, Webmap, r Mbile fr Andrid with a name frm this list, Lucity will cnnect it t the assciated mdule. The Available Aliases grid is a list f aliases already added but aren t assciated t any feature class. Right-click n an existing recrd t get a menu with ptins t Add, Edit, Delete, r Assciate. Assciating a recrd in this grid will attach it t the selected feature class, remve it frm this grid, and add it t the Assciated Aliases grid fr the selected feature class. Parent Recrd Linking Tab Sme feature classes have parent relatinships. Sme relatinships are required where thers are nt. Fr example, A Park Furniture feature can be assciated t a Park feature but it isn t a requirement. On the ther hand, a Facility Site Asset feature must be assciated t a Facility Site asset. These assciatins are maintained via a linking field in the child table. This field is typically a lng integer field that stres the parent recrd s autid (the ID assigned by the database). In rder fr Lucity t acknwledge this relatinship this field must be included in the feature class mappings. The Parent Linking tab will assist yu in ppulating the GIS field linked t the parent s autid. If using this functinality, a user wuld just need t ppulate the parent s cmmn ID field and the Lucity GIS extensin will handle the rest. Lucity Parent Tables: This is a read nly field. This lists the table(s) that can have a relatinship t the current feature class. Lucity Parent Cmmn ID Field: This is a read nly field. These are the field(s) in the parent table(s). This is typically the same field that is used as the Cmmn ID fr the parent Table. Gedatabase Cnfiguratin Tl Overview (v7.6) 12

13 Lucity Parent Aut ID Field: This is a read nly field. These are the aut ID field(s) in the parent table(s). Feature Class Parent Cmmn ID Field: This is a field in the feature class that cntains the string unique identifier that links the feature t the parent feature class r table. Fr example, if a Park Furniture feature class is being set up, this field will be the Park Number field. Separate multiple fields by cmmas. This field shuld crrespnd with the fields in the Lucity Parent Cmmn ID field. Include the cmma even if n field is t be used. Feature Class Parent Aut ID Field: This is a field in the feature class that cntains the aut ID f the parent feature class r table. Fr example, if a Park Furniture feature class is being set up, this field will be the Park AutID field. Separate multiple fields by cmmas. This field shuld crrespnd with the fields in the Lucity Parent AutID field. Include the cmma even if n field is t be used. Lgical Netwrk Tab Feature Class Frm and T Nde Table: This is read nly. It shws which table the t and frm ndes will be stred. The feature class(es) that cntains the t and frm nde pint features shuld be cnfigured t synch t this Lucity table Feature Class Frm Nde Field: This field stres the name f the string field that will stre the upstream r frm nde identifier. Fr street segments, this is the frm intersectin and is ptinal, unless the Accident mdule is being used, in which case it is required. This field shuld be a text r character field. Feature Class T Nde Field: This field stres the name f the string field that will stre the dwnstream r t nde identifier. Fr street segments, this is the t intersectin and is ptinal, unless the Accident mdule is being used, in which case it is required. This field shuld be a text r character field. Ntes: Gedatabase Cnfiguratin Tl Overview (v7.6) 13

14 Assciated Wrkspaces Tab A feature class cnfiguratin can be assciated between multiple gedatabase cnnectins. Fr example, a client has a feature class named SewerPipe that exists in bth a parent and replica gedatabase. Instead f having t create a feature class mapping fr bth gedatabases, the feature class mapping nly has t be created against the parent gedatabase cnnectin, and then the feature class mapping can be assciated t the replica gedatabase cnnectin. The Assciated Wrkspaces grid shws all the gedatabases that this feature class is assciated t. This grid is read-nly. T assciate/disassciate a feature class there is a right-click cntext menu when yu select the replica gedatabase nde that gives yu these ptins. Default Wrkspace- Each feature class is required t have a default wrkspace cnnectin. The default wrkspace fr a feature class is the wrkspace it is assciated t that isn t marked as a replica wrkspace. Nte: A feature class is nt able t be assciated t mre than ne nn-replica gedatabase. Feature Class Fields Grid The feature class fields grid allws yu t manage the feature class fields are mapped t Lucity fields. A mapping between the tw enables the Lucity applicatin t update the feature class when the data is updated in the Lucity desktp r web applicatin. A mapping als enables the Lucity extensin in ArcMap t update the Lucity database when the data is updated in the feature class during an ArcMap edit sessin. FieldName- The field name in the Lucity table. DisplayName- The field captin in Lucity. Field Type- The type f data stred in the field MaxMask- The data frmat. A numeric value fllwed by an x indicates the number f characters allwed. Feature Class Field Name- This is the name f the field in the feature class. This is NOT the alias field name. If yu are unsure f the field name use the Field Lkup buttn. Field Lkup- This buttn clumn displays a list f the feature class fields. Nte: If a cnnectin t the gedatabase was unsuccessful then n fields will be listed. Gedatabase Cnfiguratin Tl Overview (v7.6) 14

15 Lucity Cde/Type fields Only the Lucity cde fields are displayed in the Feature Class Fields grid. The Dmain Cnfiguratin tl can be used t further define the mapping between a GIS field t a Lucity picklist field. We supprt mapping a text GIS dmain t Lucity numeric picklist and vice versa. Lucity Cmpsite Address fields Lucity breaks ut street address infrmatin int the fllwing fields: Building number, building suffix, street directin, street prefix, street name, street type, and street suffix. Each f these fields that yu use in Lucity need t have a matching field in the feature class. Alternatively yu can use the cmpsite address fields in the feature class fields grid t map a field in yur feature class that cntains the entire building number r the entire street name. Nte: If yu map t a cmpsite field yu shuld NOT map t the individual building r street cmpnent fields. Clr Cding Red- Required Field. This is the Cmmn ID (FacilityID) field fr the asset inventry mdule. Orange- Required Field. Stres the required ID number f related features (the parent recrd number) Yellw- These are cnsidered parent linking fields. They typically stre the ID f the related feature. Green- Building and Address cmpsite field. Ntes: Gedatabase Cnfiguratin Tl Overview (v7.6) 15

16 Add a Feature Class Cnfiguratin 1. T add a new feature class cnfiguratin, in the tree n the left f the Gedatabase Cnfiguratin Frm, right-click n the gedatabase nde t which the feature class resides and select Add Feature Class. Nte: This ptin is nt available fr replica gedatabases; instead refer t the Assciate Feature Class(es) tl. 2. The fllwing dialg will appear. Select the asset type fr which this new feature class will be linked t. 3. The Gedatabase Cnfiguratin Frm will be updated t indicate the new feature type. Yu must enter the name f the feature class befre this new feature class cnfiguratin will be saved. Either enter the feature class name directly, r select it frm the drp dwn list: 4. Fill ut the remainder f the feature class and field mapping cnfiguratin. T save, simply exit the tl, r click n anther nde. Ntes: Gedatabase Cnfiguratin Tl Overview (v7.6) 16

17 Delete a Feature Class Cnfiguratin 1. T delete a feature class cnfiguratin, in the tree n the left f the Gedatabase Cnfiguratin Frm, right-click n the feature class nde that yu wish t delete and select Delete. Nte: This ptin is nt available fr replica gedatabases; instead refer t the Disassciate Feature Class(es) tl. 2. One f fllwing dialgs will appear cnfirming that yu wish t delete the feature class 3. If the feature class is assciated t multiple wrkspaces yu will receive the fllwing message: Spatial Relatinships Spatial relatinships autmatically update features based n their lcatin relative t ther features t help aid general editing and maintaining these relatinships in ArcMap. There are three ways in which spatial relatinships are triggered: 1. Within an ArcMap edit sessin, when a feature is created r when an existing feature s shape is changed. 2. Within an ArcMap edit sessin using the "Update Spatial Relatinships" tl n the Lucity GIS Edit tlbar. This tl is typically used if the data was imprted using a nn-lucity imprt tl r was added during a nn-lucity edit sessin. 3. When the Lucity Data Lader is used. Gedatabase Cnfiguratin Tl Overview (v7.6) 17

18 Adding Spatial Relatinships 1. T add a spatial relatinship, right-click n the feature class t which yu want t add the relatinship frm the tree n the left f the Gedatabase Cnfiguratin Frm. 2. Click Add>>Spatial Relatinship. 3. The Add Spatial Relatinship tab will be displayed 4. Ppulate the Field t Update. Required. This is the field name in the selected feature class that yu wuld like t have autmatically updated. Use the drp dwn list t chse frm a list f fields fr the feature class. 5. Ppulate the Related Feature Class. Required. This is the feature class name f the ther feature class that will participate in this spatial relatinship. This feature class des nt have t be set up t synchrnize with the desktp but it must exist in the same gedatabase. 6. Ppulate the FC Field Name. Required. This is the field name in the Related Feature Class that cntains the value yu wuld like prpagated t the field defined in the "Field Name" Field. 7. Ppulate the Relatinship Type. Required. This is a drp dwn pick list defining the relatinship type. The available relatinship types are defined belw: Frm Intersect: Finds any features in the Related Feature Class that intersect the frm pint f the feature in the selected feature class. This relatinship nly wrks fr plyline, edge, r cmplex edge features. T Intersect: Finds any features in the Related Feature Class that intersect the T Pint f the feature in the selected feature class. This relatinship nly wrks fr plyline, edge, r cmplex edge features. Is Cntained by: Finds any features in the selected feature class that are cntained by features in the related feature class. The related feature class must be a plygn feature class. Intersects: Finds the first feature in the related feature class that intersects the feature in the selected feature class. US Intersect Distance: Finds the first feature in the related feature class that intersects the feature in the selected feature class and then calculates the distance alng the line that the intersectin ccurs (frm the t pint). The selected feature class must be a plyline, edge, r cmplex edge feature class. Gedatabase Cnfiguratin Tl Overview (v7.6) 18

19 Midpint Intersect: Finds any feature in the related feature class that intersects the midpint f the feature in the selected feature class. This relatinship is designed fr plyline, edge, r cmplex edge features as the selected feature class, and a plygn feature fr the related feature class. Frce Related Feature t Self-Update: This relatinship finds any features that intersect the feature in the selected feature class and adds them t the edit cache s that they are synched t the desktp even if the recrds have nt changed. This is used primarily fr the street segment feature class (as selected feature class) and the street intersectin feature class (as related feature class). This frces the intersectins t autmatically recalculate the intersectin cnfiguratins fr the diagram in the desktp Intersectin mdule when street segments are changed. Is Within Distance f: Finds all features in the related feature class that are with a specified distance f the feature in the selected feature class. 8. Ppulate the Distance Value. Required nly if the relatinship type "Is Within Distance Of" has been selected. The field is used t specify a distance fr this relatinship type. 9. Never Overwrite a Nn-Null Value. Optinal. Check this bx t ensure that data ppulated in the "Field Name" field f the selected feature class is never verwritten if a value already exists. 10. Update Value t Null if N Relatinship is Fund. Optinal. Check this bx t allw the "Field Name" field t be set t null if n relatinship is fund. 11. This infrmatin will be saved when the selected feature class nde lses fcus r yu clse the frm. Deleting Spatial Relatinships 1. T delete a spatial relatinship frm a feature class, select the spatial relatinship listed under the feature class frm the tree n the Gedatabase Cnfiguratin frm. 2. Right-Click n the spatial relatinship and chse Delete. Ntes: Gedatabase Cnfiguratin Tl Overview (v7.6) 19

20 Number Generatr Fields in a feature class can be set up s that the Lucity extensin will attempt t ppulate the field with a unique value. Use this tl t add new number generating fields r edit an existing number generating field. When features are synched during an ArcMap edit sessin (feature are synched when they are created r mdified), if the field cnfigured with the number generatr desn t cntain a value the Lucity GIS extensin will ppulate this field with the next incremental value. Add a Number Generating Field 1. T create a number generatr field, select the feature class that cntains the field yu wish t aut-number frm the tree n the left hand side f the Gedatabase Cnfiguratin frm. 2. Right-Click n the Feature Class and select Add>>Number Generatr. 3. The Number Generatr tab will be displayed: 4. Ppulate the Field t AutNumber Required. This field is the field that will cntain the new aut number. This shuld be a text field, large enugh t supprt the numbers that will be generated based n yur settings in this dialg. 5. Ppulate the Buffered Number Length Optinal. If yu want the aut-number t cntain buffered zers, enter hw many characters yu want the entire number t be. Fr example, if a buffered length f 5 is entered, and if the autnumber generated is 985, the resulting aut number that will be ppulated is This may allw fr easier number srting. 6. Include Prefix Settings. Nne: This will be marked by default. If this buttn remains marked, yu will be unable t include a Prefix fr this AutNumber field. Use Set Prefix: This will allw yu t specify a prefix in the next number gird and allw yu t specify a separatr character. 7. Click the t set the crrect start number. If the prefix setting ptin is set t Nne r Use Set Prefix then nly ne next number recrd is allwed in the grid. If the prefix setting ptin is set t Use a Plygn Feature Class then yu can add an unlimited number f next numbers. In thery, yu wuld want a recrd fr each feature in yur plygn feature class with the prefix value fr that feature. 8. This infrmatin will be saved when yu click n a different feature class. Gedatabase Cnfiguratin Tl Overview (v7.6) 20

21 Remve an Aut-Numbering Field 1. T delete the number generatr frm a feature class, select the number generatr listed under the feature class frm the tree n the Gedatabase Cnfiguratin frm. 2. Right-Click n the number generatr and chse Delete. Dmain Tls Dmain Cnfiguratin Fields in the gedatabase that are linked t a Lucity Cde/Type field (pick list) shuld cntain a gedatabase dmain. A dmain prvides the same functins in ArcMap that a picklist prvides inside f Lucity. Dmains ensure data integrity and help with data ppulatin during an edit sessin. T ensure data integrity between Lucity and the Gedatabase the picklist values shuld match up t the dmain values. The Dmain Cnfiguratin Tl in the Gedatabase cnfiguratin allws users t quickly cmpare dmains t picklists and fix and differences between the tw. 1. T access the Dmain Cnfiguratin screen, rightclick n either a gedatabase r feature class nde in the tree lcated n the left-hand side f the Gedatabase Cnfiguratin brwser. 2. If yu are integrated with an enterprise gedatabase yu will be prmpted with the fllwing: Gedatabase Cnfiguratin Tl Overview (v7.6) 21

22 This screen is asking the user t lgin as the Dmain Owner. Dmains within a gedatabase can nly be edited by the riginal creatr (dmain wner). Often, nt even system admin accunts can edit a dmain if they weren't used t create it. Make an authenticatin chice and enter if username and passwrd if needed. Click OK. 3. When this tl is run it validates the Lucity picklists and GIS dmains fr all fields mapped between the tw systems. The validatin prcess is tracked and displayed in the resulting dialg: 4. The tp sectin shws the validatin prgress and can be reviewed by using the scrll n the right. The bttm sectin prvides the results in a tabular frmat allwing yu t easily review and reslve any cnflicts. 5. Click the Manage buttn t assist with the reslutin f any cnflicts. Ntes: Gedatabase Cnfiguratin Tl Overview (v7.6) 22

23 Reslve Dmain Discrepancies 1. After clicking the Manage buttn n the Dmain Cnfiguratin grid results the fllwing frm will appear: The grid n the left shws the GIS dmain values. The grid n the right shws the Lucity picklist values. Discrepancies are shwn in red. Within this windw yu can: add/edit/delete GIS dmain values, add/edit/delete Lucity picklist values, reppulate the GIS dmain values t match Lucity, and reppulate the Lucity picklist values t match the GIS dmain. The GIS Cde field is used t link a Lucity Value t a Dmain value with a different cde. This is used when neither the picklist nr dmain values can be changed. It can als be used t link tgether number picklists/dmains t alpha-numeric nes. 2. After making changes yu must click Apply Changes buttn at the bttm f the grid fr the changes t save. 3. Click Clse when yu are finished. Yu will be returned t the Dmain Cnfiguratin results frm. Nte: The dmain yu just mdified will still be listed as having a discrepancy. Yu must click the Revalidate buttn n the tp menu if yu wish t have the frm refreshed. Ntes: Gedatabase Cnfiguratin Tl Overview (v7.6) 23

24 Update GIS Dmains t match Lucity picklists Yu can perfrm a mass update that will verwrite all the GIS dmains with values frm the related Lucity picklists. If a dmain desn t exist fr a field, it is created in the gedatabase and linked t the feature class field. By default the dmain name is given the Lucity table name and Lucity field name. Fr example, if a GIS field is mapped t sewer pipe s material field the assigned dmain name will be SWNET_NT_MAT_CD. If multiple feature classes are mapped t the same field and there isn t already a GIS dmain assigned t these fields this tl will nly create ne dmain and assign it t all GIS fields linked t the Lucity field. If the GIS field type desn t match the Lucity field type (GIS field is text, Lucity is numeric r vice versa), the Lucity GIS Cde is required befre the GIS dmain can be updated. 1. Frm the Dmain Cnfiguratin Results frm, click Sync Dmains>>Update GIS dmains t match Lucity picklists. 2. The tl will start prcessing the GIS dmains, results are shwn in the upper sectin f the Dmain Cnfiguratin windw. Please refer t the results fr any issues. Gedatabase Cnfiguratin Tl Overview (v7.6) 24

25 Update Lucity picklists t match GIS Dmains Yu can perfrm a mass update that will verwrite all the Lucity picklists with values frm the related GIS dmains. If a Lucity picklist value is hardcded (unable t be altered) the tl will attempt t find the equivalent GIS dmain cde using the descriptin. If it finds the matching GIS dmain value it uses the Lucity GIS cde field t stre the crrespnding GIS dmain cde. If the GIS field type desn t match the Lucity field type (GIS field is text, Lucity is numeric r vice versa), the Lucity GIS Cde will be used t stre the crrespnding GIS dmain cde. The Lucity picklist cde will be autmatically assigned a sequential number. 1. Frm the Dmain Cnfiguratin Results frm, click Sync Dmains>>Update Lucity picklists t match GIS dmains 2. The fllwing prmpt will appear. Select Yes, if yu want t delete Lucity picklist values that aren t in the GIS dmain. 3. The tl will start prcessing the Lucity picklists, results are shwn in the upper sectin f the Dmain Cnfiguratin windw. Please refer t the results fr any issues. Gedatabase Cnfiguratin Tl Overview (v7.6) 25

26 Update Parent Linking Dmains In many feature classes there will be fields that link a feature t a related feature in anther feature class. It des this by string the related feature's LucityID. Fr example, a park bench might stre the ID f the Park that it is in. This prvides imprtant cnnectin infrmatin fr Lucity, but is less useful t users because it just displays a number. The Update Parent Linking Dmains tl creates userfriendly dmains fr these fields. While the field will still stre the linking ID, the dmain culd display parent recrds: Facility ID number, Name/Descriptin, Facility ID and Name/Descriptin, r Name/Descriptin and Facility ID. 1. T update parent linking dmains, right-click n either a gedatabase r feature class nde in the tree lcated n the left-hand side f the Gedatabase Cnfiguratin brwser and select Update Parent Linking Dmains 2. A prmpt fllwing prmpt will appear. 3. Select the descriptin ptin and click OK. Nte: When the D nt shw this prmpt again ptin is checked any additinal parent linking dmains needing prceed will use the same ptin. Gedatabase Cnfiguratin Tl Overview (v7.6) 26

27 4. If there currently is nt a dmain assigned t the GIS field the fllwing prmpt will appear. Click Yes. 5. The dmain will be created and/r updated. The prcess will be updated in the Validatin Results windw. Ntes: Gedatabase Cnfiguratin Tl Overview (v7.6) 27

28 Update Street Name, MUTCD, and Tree Dmains Fields in the gedatabase that are linked t Lucity fields string the fllwing infrmatin shuld have a special dmain assigned: Address infrmatin such as street directin, street prefix type, street name, street type, and street suffix Street sign cdes (MUTCD) Tree cdes These fields in Lucity are assciated t a library which requires them t be handled a little differently than a typical Lucity picklist. T ensure data integrity it is highly recmmended that yu cnfigure a GIS dmain fr these fields that match the crrespnding Lucity picklist. 1. Right click n yur gedatabase nde in the tree lcated n the left-hand side f the Gedatabase Cnfiguratin brwser and select Dmains>>Update Street Name Dmains (r MUTCD r Tree) 2. After yu click Update Street Name Dmains, yu will be prmpted t chse the dmain wner. 3. Chse a dmain ptin and click OK. A series f messages similar t the fllwing will appear: Nte: If yu are updating Street Name Dmains yu will be prmpted multiple times fr each street name cmpnent: Street Directin, Street Prefix, Street Name, Street Type, Street Suffix, and Street Name ID. Gedatabase Cnfiguratin Tl Overview (v7.6) 28

29 4. Click Skip, Select, r Create New t navigate thrugh each dialg. If the dmain desn t already exist, yu can chse the Create New ptin fr the tl t create the dmain. The fllwing is the hardcded dmain names used by this tl: Lucity.StreetNameDirectin, Lucity.StreetNamePrefixType, Lucity.StreetNameName, Lucity.StreetNameType, Lucity.StreetNameSuffix, Lucity.StreetNameList Lucity.MUTCD Lucity.TreeCmmnName 5. When yu click Select n the last dialg, the validatin results will be generated. Feature Class Schema There are varius tls available that can be applied n individual feature classes r all feature classes in a gedatabase cnnectin that alter the feature class schema. T use any f these tls yu will be prmpted t enter gedatabase credentials that will have the necessary permissins t make schema changes and yu must be able t acquire an exclusive lck n the feature class. Gedatabase Cnfiguratin Tl Overview (v7.6) 29

30 Add Lucity AutID Field Starting with versin 7.1, this field is n lnger required; hwever, fr best perfrmance it is strngly recmmend this field exists in each feature class. Once the field is added and mapped t Lucity, the Lucity extensin will maintain it. It requires n data input frm the user. Use this tl t create this field in yur feature class(es) and map it t Lucity. Add Lucity In DB Field Starting with versin 7.1, this field is n lnger required. It is a simple Blean field that indicates if there is an assciated feature in the Lucity database. Once the field is added and mapped t Lucity, the Lucity extensin will maintain it. It requires n data input frm the user. Use this tl t create this field in yur feature class(es) and map it t Lucity. Add Mdified/Synched Fields This tl can be used t create 3 fields in yur feature class(es): Last Mdified Date, Last Mdified By, and Last Synch Date. Once these fields are added and mapped t Lucity, the Lucity extensin will maintain them. It requires n data input frm the user. Set Field Alias Equal t Lucity Field Captins This tl can be used t update the alias name fr the feature class fields linked t Lucity. The alias names will be updated t match the Lucity field captins. Set Feature Class Alias Equal t Lucity Mdule Name This tl can be used t update the alias name fr the feature class linked t Lucity. The alias names will be updated t match the Lucity mdule name. Fr example, a feature class linked t the Sanitary Structure Inventry mdule will have its alias updated t Sanitary Structure. Ntes: Gedatabase Cnfiguratin Tl Overview (v7.6) 30

31 Imprt Feature Classes frm Schema The Imprt Feature Classes frm Schema tl prvides a quick way t cnfigure Lucity t wrk with specific pre-cnfigured gedatabases. This tl has stred cnfiguratins based n linking Lucity t the Esri Lcal Gvernment Infrmatin Mdel and Lucity gedatabase schemas. This tl des nt create the feature classes in the gedatabase. It simply creates cnfiguratin recrds in the Lucity gedatabase cnfiguratin t recgnize feature classes and fields based n ne f these standardized schemas. This tl des nt create r update any Dmains. This must be dne after the imprt using the Dmain Cnfiguratin tl. T imprt feature class cnfiguratins frm a default schema: 1. Right-click n the gedatabase cnnectin nde that cntains the feature classes yu wish t lad the mappings fr and click Imprt Feature Classes frm Schema. 2. The fllwing frm will appear: 3. Select a schema. Yu can either select a Lucity gedatabase schema r an Esri s Lcal Gvernment Infrmatin Mdel schema. Gedatabase Cnfiguratin Tl Overview (v7.6) 31

32 4. Select the schema versin/release. Fr Lucity, this will be the Lucity versin number (7.4, 7.5, 7.6, etc.) Fr Esri, this will be the versin fllwed by the release date. Fr example, there have been tw releases f the 10.1 Lcal Gvernment Infrmatin Mdel, ne n 7/12/12 and 11/5/12, these will be listed as 10.1_ and 10.1_ Select the feature class(es) yu wuld like t lad the schema mappings fr. 6. Preview by selecting a specific feature class n the left side. The Field Mappings grid will shw which fields in the feature class will be mapped t which fields in Lucity The Spatial Relatinships grid will shw the default spatial relatinships fr the feature class Nte: Yu are unable t mdify the defaults at this time. Hwever, nce yu imprt the schema, yu can then mdify the feature class cnfiguratin just like any ther feature class. 7. Click the Imprt Schema Mappings buttn nce yu are ready t imprt the settings 8. The Validatin results windw will appear and prvide feedback n the imprt prcess. Imprt Feature Class Alias Names Aliases are alternate names fr feature classes that prvide a unique identity. They are used by the Lucity Webmap, Lucity Viewer, and Lucity Mbile fr Andrid t identify which feature classes are linked t Lucity. These Lucity mapping applicatins check the feature classes laded int them and check the display names f thse feature classes against the aliases names listed in the Gedatabase Cnfiguratin. Aliases can be setup in a few different ways. This tl is designed t update the gedatabase cnfiguratin with the default alias names fr the gedatabase cnnectin as listed in ArcCatalg. 1. Select the gedatabase cnnectin r the feature class nde 2. Right click n the selected nde and select the Imprt Feature Class Alias Name(s) tl 3. The imprt will start immediately and a lg screen will appear that prvides additinal infrmatin including imprt errrs. Gedatabase Cnfiguratin Tl Overview (v7.6) 32

33 Nte: An alias name can nly be assciated t ne feature class; therefre, prir t assciating an alias t a feature class the imprt verifies the alias name is nt currently being used. If it is being used, the alias name will nt get assciated and the warning will be lgged. Validating the Gedatabase Cnfiguratin Once a gedatabase is cnfigured it is gd idea t check t make sure that there are n prblems with links between Lucity and the gedatabase. This helps insure that all the expected data will be transferred. T run a check there is a Validate tl within the gedatabase cnfiguratin. This tl can either be run against the entire gedatabase r an individual feature class. This tl can als be run against a replica gedatabase, r feature class. Hwever, any errrs detected n the replica shuld be fixed in the DEFAULT gedatabase's cnfiguratin. There are tw parts t the gedatabase verificatin. The first is a verificatin f the gedatabase setup based n Lucity requirements. If n critical errrs are encuntered during that verificatin it will cntinue t the verificatin. The secnd part checks the gedatabase t ensure that the setup is valid based n the gedatabase data structure. It checks feature class names, field names, and field types. 1. Select the gedatabase cnnectin, OR the feature class t be checked 2. Right-click n the selected gedatabase OR feature class and select the Validatin tl If it is a gedatabase the tl will be Validate Wrkspace If it is a replica gedatabase the tl will be Validate Replica Wrkspace If it is a feature class the tl will be Validate 3. The tl will immediately begin t run the first part f the validatin and results will be displayed in a validatin windw. The first part f the validatin is checking the setup against Lucity requirements it checks t make sure the Required and Optinal linking fields are all filled ut. The results display the Lucity Mdule name: Feature Class Name. Any messages fr a feature class are displayed belw. Gedatabase Cnfiguratin Tl Overview (v7.6) 33

34 Suggestins are displayed in Light Gray, Warnings in Orange and Errrs in Red. If an Errr is detected the Validatin will NOT cntinue n t check the gedatabase. The feature class with the errr will NOT be able t sync with Lucity. The fllwing message will be displayed 4. If the first part f the validatin passes the secnd part f the validatin will immediately start and the results will be shwn in the same validatin windw. The secnd part is checking the cnfiguratin between the gedatabase and Lucity it is checking t make sure the specified fields exist in the gedatabase and that the data types and field masks match. The results display the Lucity Mdule Name: Feature Class Name. Warnings are displayed in Orange, and Errrs in Red. If an errr is detected the fllwing message will be displayed If it was successful the fllwing wuld be displayed: Ntes: Gedatabase Cnfiguratin Tl Overview (v7.6) 34