Skip to main content

Property

Properties represent real-world parcels, sites, or areas of land associated with your work.
They provide the spatial foundation for projects, jobs, and GIS outputs.

A property typically includes both geometry (where it is) and metadata (what it represents).

What a Property Represents​

A property represents a physical location or boundary, such as:

  • A parcel of land
  • A development site
  • A tract, lot, or easement area
  • A study boundary or project extent

Properties are first-class objects and can be reused across multiple workflows.

Where Properties Are Used​

Property records are referenced in:

  • Projects
  • Jobs and scheduling
  • GIS outputs and analysis
  • Maps and spatial views
  • Reports and deliverables

Because of this, properties act as the spatial anchor for work performed in the system.

Creating a Property​

Properties are most commonly created using the Map Widget, where boundaries or locations can be drawn directly on the map.

Depending on the workflow, properties may be created:

  • During project setup
  • While creating a job
  • From a map-focused workflow

In some cases, the property form appears in a popup after geometry is drawn.
Regardless of where it appears, the property fields and behavior are the same.

➡️ Widget: Map Widget

Property Fields​

Property Name (required)​

The primary identifier for the property.

  • Used in lists, maps, and workflows
  • Should clearly describe the site or location
  • Required to save a property

Geometry (required)​

The spatial representation of the property.

  • May be a point, line, or polygon (depending on configuration)
  • Defines where the property exists geographically
  • Required for GIS outputs and map-based workflows

Geometry is typically created or edited directly on the map.

Associated Project​

Links the property to a project.

  • Provides organizational context
  • Allows the property to participate in project workflows
  • A property may be linked to one or more projects, depending on configuration

➡️ Reference: Project

Address / Location Description​

Optional descriptive location information.

  • Street address (if applicable)
  • General location notes
  • Used for reference and reporting

This field does not replace geometry and may exist even if an exact address is unknown.

Notes​

Optional internal notes related to the property.

  • Useful for access instructions, site constraints, or assumptions
  • Not exposed unless explicitly included in outputs or reports

Editing Property Geometry​

Property geometry can be edited after creation using the map.

When geometry is updated:

  • GIS outputs update automatically
  • Map views reflect the change
  • Linked workflows continue to reference the updated boundary

All geometry edits are subject to permissions and validation rules.

Read-Only Behavior Outside the App​

When accessed through external tools (such as GIS software), property data is read-only.

This ensures:

  • Data integrity
  • Consistent validation
  • No accidental changes from external systems

All edits should be performed inside the application.

➡️ See: GIS Data Access

Permissions & Visibility​

Access to property data is controlled by your company’s permission model.

Depending on your role, you may be able to:

  • Create new properties
  • Edit property details or geometry
  • View property data on maps
  • Access properties in GIS outputs

Summary​

Properties connect your work to real-world locations.

They provide the spatial context needed for mapping, analysis, and deliverables—making them a critical part of projects, jobs, and GIS workflows.