Skip to main content

Sites and site areas

A Site is the spatial scope in Erde — a single managed physical place, such as a former industrial property or a landfill. Everything spatial hangs off a Site: its Locations, the field artifacts beneath them, and the environmental data collected there. A site area subdivides a Site into named sub-areas (operable units) that close out on their own timelines.

What a Site holds

A Site is the top-level spatial container — an aggregate root that owns Locations, site users, contacts, registrations, and site areas. Its identity is the Code: a short, unique label (Code is unique across all Sites; Name is descriptive and is not required to be unique). You classify a Site by Site Type (a reference data value) and track its lifecycle with Status.

A Site carries two land-use fields by design — Current Land Use (what is there now) and Intended Land Use (what cleanup targets). Risk-based screening levels depend on the intended use, so the two are tracked independently.

FieldTypeRequiredDescription
CodetextYesUnique identifier, up to 50 characters. Carries the Site's identity.
NametextYesDescriptive label, up to 200 characters. Not unique.
Site Typereference dataYesClassification; must be active.
StatusenumYesLifecycle. Defaults to Active.
Current Land UseenumNoWhat occupies the Site now.
Intended Land UseenumNoThe cleanup goal that drives screening levels.
Start Date / End DatedateNoOperating range. End Date requires Status of Closed.
Address fieldstextNoAddress Line 1 / Address Line 2, City, County, State, Postal Code, Country.
CoordinatepointNoSite location, always stored in WGS84 (World Geodetic System 1984; EPSG:4326).
BoundarypolygonNoSite outline, managed through dedicated boundary editing.
Coordinate Systemreference dataNoDefault working frame for child geometry.
Vertical Datumreference dataNoDefault vertical reference for child geometry.
Area / Area Unitnumber + enumNoSet both or neither.
Time ZonetextNoSystem time-zone identifier (IANA — Internet Assigned Numbers Authority — on Linux/macOS, Windows IDs on Windows).
DescriptiontextNoFree text, up to 2000 characters.

The Site's own representative Coordinate (its map pin) is always in WGS84. The Boundary can be entered in any coordinate system — you pick it when editing the boundary, and Erde reprojects to WGS84 for the map (see Edit site and area boundaries). A separate Coordinate System and Vertical Datum set the default working frame for child geometry (Locations, Wells), so a Texas Site can default its features to a State Plane zone without changing how the Site point itself is mapped.

Status values

ValueMeaningNotes
ActiveOperating Site under managementDefault for a new Site.
ClosedRegulatory close-outPairs with End Date.

Land use values

Both Current Land Use and Intended Land Use draw from the same set: Residential, Commercial, Mixed Use, Industrial, Agricultural, Recreational. There is no "Unrestricted" value — that is a regulatory cleanup outcome, not a land use.

Site areas

A site area is a named sub-area of a Site — an operable unit. Because different parts of one Site reach closure at different times, a site area carries its own Status, independent of the parent Site's status. Each site area also carries a Color so it reads distinctly on the map; the Site itself has no color.

A site area's Name is required and is unique within its Site (two areas on the same Site cannot share a name). You classify each area by its Type (a Site Area Type reference data value).

FieldTypeRequiredDescription
NametextYesUnique within the Site, up to 100 characters.
Typereference dataYesClassification (a Site Area Type value).
StatusenumYesDefaults to Under Investigation.
ColorenumYesMap color. Defaults to Blue.
BoundarypolygonNoArea outline, managed through boundary editing.
DescriptiontextNoFree text, up to 1000 characters.

Site area status values

ValueMeaning
Under InvestigationDefault for a new area; characterization in progress.
In RemediationActive cleanup.
MonitoringPost-cleanup monitoring.
ClosedTerminal; the area is closed out.

Site area colors

A site area is one of 16 colors: Blue, Red, Amber, Emerald, Purple, Orange, Cyan, Pink, Teal, Indigo, Lime, Brown, Slate, Navy, Olive, Maroon. The default is Blue.

How it fits together

A Site contains Locations and any number of site areas. A Location can be assigned to any number of site areas (including none), which is how you tie a monitoring or sampling point to the operable unit it belongs to. The field artifacts — Wells, Boreholes, Test Pits, and Sediment Cores — live beneath Locations.

Figure: a Site contains Locations and site areas; Locations are assigned to site areas and may carry field artifacts (Wells, Boreholes, Test Pits, or Sediment Cores).

A Site is spatial; a Project is the work scope. The two are linked many-to-many: one Project can span several Sites, and one Site can be worked under several Projects. Data such as Samples and field measurements is scoped to a Project–Site pair, so the link must exist before that data can be recorded.

AspectSiteProject
Answers"Where?""Under what scope of work?"
OwnsLocations (and their field artifacts), site areasSamples, Lab Reports, field measurements
LifespanOutlives any single ProjectA defined engagement
Linked toOne or more ProjectsOne or more Sites

For how the Site–Project link grants access and scopes data, see Sites and projects. For where Sites sit in the overall data model, see the data model.