Lucity GIS Editing for Park

The following feature classes are available in the parks feature dataset:

Note: Refer to Editing Requirements for a description of the format of these requirements.

Feature Class Type	Feature Class Name	Required Fields (Alias)
PARKS	PKPARKG	PKG_NUMBER [Park Number]

Feature Class Type	Feature Class Name	Required Fields (Alias)
PARK STRUCTURES	PKSTRUCG	STG_NUMBER [Alt Structure ID]
PARK LIGHTING	PKLIGHTG	LTG_NUMBER []
PARK IRRIGATION VALVE	PKIVALVG	IVG_NUMBER [Alt Valve ID]
PARK IRRIGATION CONTROLLER	PKICONTG	ICG_NUMBER [Alt Controller ID]
PARK FURNITURE	PKFURNG	FAG_NUMBER [Alt Furniture ID]
PARK PLAYGROUND EQUIPMENT	PKEQUIPG	EQG_NUMBER [Alt Equipment ID]
PARK PATH	PKPATHG	PHG_NUMBER [Alt Path ID]
PARK PARKING LOT	PKPGLOTG	PGG_NUMBER []
PARK LANDSCAPE	PKLSG	LSG_NUMBER [Alt Landscaping ID]
PARK FIELD	PKFIELDG	FDG_NUMBER [Alt Field ID]
PARK COURT	PKCOURTG	CTG_NUMBER [Alt Court ID]
PARK REFUSE	PKREFUSEG	RCG_NUMBER [Alt Refuse ID]
PARK METER	PKMETERG	MTG_NUMBER [Alt Meter ID]
PARK POOL	PKPOOLG	POG_NUMBER [Alt Pool ID]
TREE	TREEG	TRG_NUM [Alt Tree ID}

When you include the Tree Common Name in the map, the genus, species, cultivar, and type will be populated in the desktop as follows:
- If you have a field mapped to TR_COMMON, the system will look up TZ_CODE, TZ_GENUS, TZ_SPECIES, TZ_CULTIVR, TZ_TYPE_CD, and TZ_TYPE_TY and populate that information in the desktop. If these fields also exist in your feature class and are null the Lucity GIS Editor extension will also populate those fields.
  Note: Lucity provides a domain for TRG_COMMON; however, since this is not a code/type field, if you add new tree codes you will need to manually add them to the GIS domain.