Design the street-tree geodatabase crews edit offline

Data ManagementintermediateGeospatial systems

A Montréal borough's forestry division is moving its public-tree inventory into a geodatabase designed in ArcGIS Pro 3.7, published as a hosted feature layer that its crews edit offline in ArcGIS Field Maps. Its register today is laid out like the city's open inventory, Arbres publics sur le territoire de la Ville: one row per tree, with one trunk diameter (DHP) and the date of its latest reading (Date_Releve), so each new reading overwrites the last. The division wants every reading kept, the trees' records to outlive the pits they grew in, and its work orders recorded tree by tree, in the field. You are drawing the design.

Draw the design as UML classes. The four things the division keeps are on the canvas already, undecided: say what each is stored as, put each attribute from the list below on the class it describes, hold attributes to the domains listed where the division has a fixed list or span of values, and draw the relationship classes between classes that need one — from the origin to the destination, with how many of each end it joins, and whether it is simple or composite.

What the division needs from it:

Each inspection records the tree's trunk diameter and its condition, rated 1 to 5, on the date of the visit. Every reading and the date it was taken are kept; none is overwritten by the next.
Each planting site is surveyed as one point, at the centre of the pit. A site is replanted when its tree is removed, so over the years one site holds several trees, one at a time, and each tree stands in one site.
Each tree is surveyed as one point, at the base of its trunk, which is not always at the centre of its pit; the crews walk to it and open it in Field Maps.
A planting site outlives the trees planted in it. When a site is abolished — paved over or redesigned — its record is deleted, and the records of the trees that grew there are kept.
A removed tree is retired, not deleted, and its inspections are never deleted along with it.
A work order has no location of its own and can cover trees anywhere in the borough. An order covers several trees, a tree is worked on by many orders over the years, and each order says what it does to each tree it covers, chosen from a fixed list. The crews record that in Field Maps, at the tree, offline.
A tree's species is one of the city's species codes; a remarkable tree is marked O or N, as the city marks it; a site's type, an order's status and the action are each one of a fixed list; a trunk diameter runs from 1 to 300 cm.

What the software allows, as of ArcGIS Pro 3.7 and ArcGIS Field Maps 26.2.2 (July 2026):

A geodatabase has no Boolean field type.
A range domain holds a span of numbers or dates; a coded value domain holds a list of allowed values, for text, numbers or dates. Each domain is made for one field type.
A simple relationship class is one to one, one to many or many to many; when an origin is deleted, its destinations stay and their foreign key "is set to Null". In a composite one, "destination objects can't exist independently of origin objects": deleting an origin deletes its destinations, and it is never many to many.
A many-to-many or attributed relationship class keeps its pairs in an intermediate table, and Esri's documentation says "this intermediate table is not recognized as an object class in the geodatabase", so "attribute rules, domains, subtypes, contingent values, and default values cannot be applied or used" with it.
Field Maps edits related records feature to table, feature to feature, and table to table "where the first table is accessed through a feature"; "for each, one-to-one and one-to-many relationships are supported". Taken offline, every feature layer needs Global IDs.

The attributes to place:

Attribute	Type	What it holds
`site_type`	text	The kind of pit: in a sidewalk, a lawn verge, a park
`species_code`	text	The species, as the city's `Sigle` code
`planted_on`	date	When the tree was planted
`remarkable`	text	Whether the city lists the tree as remarkable, `O` or `N`
`inspected_on`	date	The date of the visit
`dbh_cm`	double	Trunk diameter at breast height (1.4 m), in cm
`condition`	integer	The condition found, 1 to 5
`action`	text	What an order does to a tree: prune, remove, stake, water
`order_status`	text	Whether the order is open, in progress or closed
`issued_on`	date	When the order was issued

The domains, each made for one field type:

Domain	Kind	Field type	Holds
`site_type_codes`	coded value	text	The division's site types
`species_codes`	coded value	text	The city's species codes
`yes_no`	coded value	text	`O` (yes) and `N` (no)
`dbh_range`	range	double	1 to 300 cm
`condition_codes`	coded value	integer	1 to 5
`action_codes`	coded value	text	The actions an order can take
`order_status_codes`	coded value	text	The statuses an order can have

Add a class of your own only if the design needs one, and give it a name. A note on a class is kept with your answer and shown beside the reference afterwards; it is never scored. You need no ArcGIS software to answer: the design is drawn here, on the canvas, and graded on what it holds.

What to submit

Submit: A data model: say what each class is stored as, put each attribute on the class it describes, hold attributes to their domains, and draw the relationships between classes with how many of each end they join.

Objectives

Choose what each class is stored as at the map's scale
Keep repeating readings in records of their own
Hold controlled attributes to the domains given
Relate the classes with the right cardinality and lifetime, in a shape Field Maps can edit

Constraints

These are where the teaching is. Read them twice.

Every diameter and condition reading is kept; none is overwritten
A tree's records outlive its planting site, and a tree's inspections are never deleted with it
What an order does to each tree comes from a fixed list and is recorded in Field Maps, offline
A geodatabase has no Boolean field type

Graded requirements

Planting sites are stored as what they are at the map's scale
Trees are stored as what they are at the map's scale
Inspections are stored as what they are
Work orders are stored as what they are
Where each diameter reading is kept
No diameter reading overwrites the last
Where each condition rating is kept
No condition rating overwrites the last
Where the date of each inspection is kept
No inspection date overwrites the last
Where the species code belongs, and nowhere else
Where the planting date belongs, and nowhere else
Where the remarkable-tree flag belongs, and nowhere else
Where the site type belongs, and nowhere else
Where an order's status belongs, and nowhere else
Where an order's issue date belongs, and nowhere else
Where what an order does to each tree is recorded
What an order does to one tree is not written over another's
Site type is held to its list
Species is held to the city's codes
The remarkable-tree flag is held to its two values
Trunk diameter is held to its span
Condition is held to its scale
The action is held to its list
An order's status is held to its list
How planting sites and trees are related
How trees and their inspections are related
How work orders and trees are related
The crews can edit each order's work on a tree in Field Maps
What a deletion takes with it

Modelled on a Montréal borough's forestry division (illustrative) and on the City of Montréal's open data, Arbres publics sur le territoire de la Ville (Creative Commons Attribution 4.0): its inventory file has one row per tree, with one trunk diameter (DHP, measured at 1.4 m), the date of its latest reading (Date_Releve), the Sigle species code and the O/N remarkable-tree flag (Arbre_remarquable), and the city publishes the readings themselves in a separate file, Historique DHP arbres publics, one row per diameter reading. The rules are modelled on Esri's documentation as of ArcGIS Pro 3.7 and ArcGIS Field Maps 26.2.2 (July 2026): the ArcGIS Pro pages "ArcGIS field data types", "Introduction to attribute domains", "Create Domain (Data Management Tools)", "Geodatabase relationship class types", "Create Relationship Class (Data Management Tools)" and "Update an attributed relationship class", and the ArcGIS Field Maps pages "Requirements" and "Configure the map". The skill is one the ArcGIS Pro Associate 2025 exam lists under Data Management: "Given a scenario, determine the appropriate existing geodatabase elements to use." Kharita is not affiliated with Esri.

Data model

Loading the canvas

What will be checked

30 scored, 0 informational

Planting sites are stored as what they are at the map's scale
4%
Trees are stored as what they are at the map's scale
4%
Inspections are stored as what they are
4%
Work orders are stored as what they are
4%
Where each diameter reading is kept
5%
No diameter reading overwrites the last
5%
Where each condition rating is kept
4%
No condition rating overwrites the last
4%
Where the date of each inspection is kept
3%
No inspection date overwrites the last
3%
Where the species code belongs, and nowhere else
4%
Where the planting date belongs, and nowhere else
2%
Where the remarkable-tree flag belongs, and nowhere else
2%
Where the site type belongs, and nowhere else
3%
Where an order's status belongs, and nowhere else
3%
Where an order's issue date belongs, and nowhere else
2%
Where what an order does to each tree is recorded
3%
What an order does to one tree is not written over another's
5%
Site type is held to its list
2%
Species is held to the city's codes
2%
The remarkable-tree flag is held to its two values
2%
Trunk diameter is held to its span
2%
Condition is held to its scale
2%
The action is held to its list
2%
An order's status is held to its list
2%
How planting sites and trees are related
6%
How trees and their inspections are related
6%
How work orders and trees are related
6%
The crews can edit each order's work on a tree in Field Maps
5%
What a deletion takes with it
5%