> ## Documentation Index
> Fetch the complete documentation index at: https://withforerunner.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Configuring objects
> Understand object types, configure attributes, and work with your CSM to set up object categories
Forerunner supports two types of objects: **properties** and **custom objects**. Both serve as containers for records, files, and tasks, but they differ in structure, data sources, and configuration options. This page explains the differences and how to work with your Customer Success Manager to configure objects for your organization.
## Properties vs. custom objects
| | Properties | Custom objects |
| ----------------------- | -------------------------------------------- | ------------------------------------------------------------ |
| **What they represent** | Land parcels, buildings, structures | Infrastructure, facilities, boundaries, any geographic asset |
| **Geometry** | Points and parcel polygons | Points, lines, or polygons |
| **Attributes** | Standard fields plus configurable attributes | Fully customizable per object type |
| **Data source** | Parcel/assessor imports | GeoJSON imports |
| **Map styling** | Standard property markers | Custom colors, icons, labels |
| **Organization** | Single Properties category | Grouped into object categories |
| **Public website** | Searchable by address | Can be displayed on public map |
## Properties
**Properties** are the foundational object type, representing land parcels, buildings, and structures within your jurisdiction. They integrate with assessor and parcel data and are the primary object type for floodplain management workflows.
### Property data
Every property can include:
* **Parcel information** - Parcel ID, legal description, boundary geometry
* **Address and location** - Street address, coordinates for map display
* **Ownership** - Owner name and mailing address from assessor data
* **Flood data** - Zone designation, BFE, FIRM panel, SFHA status
* **Elevation data** - Lowest floor, first floor, LAG/HAG, freeboard
* **Risk indicators** - Repetitive loss status, pre/post-FIRM, SI/SD status
Property data is populated from multiple sources:
* **Parcel imports** - Assessor data (owner, parcel ID, land use, values) imported during setup and refreshed periodically
* **FEMA data** - Flood zone, BFE, and FIRM panel data from the National Flood Hazard Layer (NFHL) or community-provided FIRM data
* **Elevation Certificates** - When you upload an EC, Forerunner extracts elevation data automatically
* **Records** - Some attributes update based on attached records (like SI/SD status from tracking records)
* **Raster overlays** - Attributes can be derived from elevation models or other raster data through spatial analysis
### Property attributes
Property attributes are configurable fields that display on detail pages, map popups, and table columns. Attributes are organized into sections. Common property attribute sections include:
**Flood information** - Flood zone, BFE, Design Flood Elevation, floodway status, coastal zone, SFHA status
**Building information** - Lowest floor elevation, first floor elevation, freeboard calculations
**Parcel data** - Land use, zoning, year built, square footage, assessed values
Available attributes depend on your data sources. Contact your CSM to enable additional attributes or modify what's displayed.
### Base Flood Elevation (BFE) determination
Understanding how Base Flood Elevation (BFE) is determined and applied in Forerunner is critical for accurate floodplain management and regulatory compliance.
#### How BFE is assigned to properties
Forerunner automatically assigns BFE values to properties based on FEMA flood zone data imported from the National Flood Hazard Layer (NFHL). Here's how it works:
**Single-zone properties:** When a property falls entirely within one flood zone (such as AE9), Forerunner assigns that zone's BFE to the property.
**Split-zone properties:** When a property spans multiple flood zones, Forerunner selects the most restrictive zone at the parcel level. The system first prioritizes by zone type (VE zones over AE zones, etc.), then disambiguates within the same zone type by whichever value is highest—either depth or base flood elevation. This ensures conservative compliance and aligns with how most communities interpret floodplain requirements. Users will see zone boundaries displayed on the map, and the local floodplain manager determines which zone actually applies to the structure. Because building footprints can sit entirely in one zone or partially in another, users can manually update the structure's zone and BFE in Forerunner if needed.
**Data source:** Forerunner imports FEMA's official flood hazard layers directly from the NFHL, including flood zone boundaries and their associated BFE values. This ensures properties are automatically attributed with the most current regulatory flood data.
**Structure-level determinations:** While Forerunner assigns BFE at the parcel level based on zone boundaries, floodplain managers should verify which zone actually contains the building footprint, as this determines applicable regulatory requirements.
The MSC (FEMA's Map Service Center) is the official source for all flood hazard data. Visit [msc.fema.gov](https://msc.fema.gov) to access FIRMs, FIS reports, and other flood risk products.
#### Obtaining exact BFE values
When staff needs the exact BFE for an AE zone (to the tenth of a foot), they must use the Flood Insurance Study (FIS) to look it up. BFEs shown on the FIRM are rounded up or down, so the FIS is the authoritative source for precise elevation values.
For regulatory determinations requiring exact BFE values, always reference the Flood Insurance Study (FIS) rather than relying solely on FIRM map labels, which display rounded values.
#### Estimating BFE values
Forerunner includes an approximate BFE estimation tool for riverine communities where the FIRM has no published BFE values. This tool uses linear interpolation between surveyed cross sections along a river's profile baseline to calculate an estimated BFE for properties.
**How to use the estimation tool:**
When viewing a property without a published BFE, staff can click "Add" in the BFE row and select "Use approximate BFE tool." This activates a map interface where you select two cross sections with a continuous profile baseline running through the property. The tool automatically calculates an interpolated BFE based on the distance between cross sections and their elevation values. The resulting value is saved with an "approximate" flag to distinguish it from published FEMA values.
**Important:** When BFEs are published for a zone, this estimation tool does not apply. Forerunner relies strictly on FEMA's mapped values and boundaries for zones with published BFE data.
## Custom objects
**Custom objects** extend Forerunner beyond properties to manage any geographic asset—infrastructure, facilities, boundaries, environmental features, or other data your organization needs to track.
### Common uses
**Infrastructure** - Stormwater inlets, pipes, outfalls, culverts, bridges, pump stations, retention ponds
**Community assets** - Critical facilities, emergency shelters, community centers, municipal buildings
**Boundaries** - Flood mitigation project areas, districts, service areas, watersheds
**Environmental features** - Wetlands, streams, conservation areas, natural hazard zones
Custom objects are ideal for any geographic data you need to track, inspect, or report on—especially data that doesn't fit the property/parcel model.
### Custom object attributes
Each custom object type has its own attributes defined during import. Attributes come from the properties in your GeoJSON source file.
**Example: Stormwater inlet**
| Attribute | Description |
| -------------- | -------------------------------------------- |
| Asset ID | Identifier from your asset management system |
| Inlet type | Drop inlet, curb inlet, combination |
| Material | Concrete, metal, plastic |
| Condition | Good, fair, poor, critical |
| Last inspected | Date of most recent inspection |
**Example: Critical facility**
| Attribute | Description |
| ------------- | --------------------------------------- |
| Facility name | Name of the facility |
| Facility type | Hospital, fire station, school, shelter |
| Capacity | Number of people or beds |
| Generator | Backup power availability |
| Contact | Emergency contact information |
### Object groups
Related custom object types can be organized into **groups**. For example, a "Stormwater Systems" group might contain inlets, pipes, outfalls, and pump stations.
Groups provide:
* **Organized map layers** - Toggle related objects together
* **Unified tables** - Browse all objects in a group from one table
* **Logical navigation** - Keep related object types together in the interface
## Where attributes appear
Attributes display throughout Forerunner:
**Object detail page** - The Overview tab shows all configured attributes organized into sections
**Map popup** - Key attributes appear when you click an object on the map (a subset configured for quick reference)
**Table columns** - Attributes display as columns you can show, hide, sort, and filter
**Public website** - Selected attributes appear for public property lookups (configured separately)
## Configuring objects
Object configuration requires admin access and is handled by your Customer Success Manager.
### Property configuration
Your CSM can help with:
* **Attribute visibility** - Enable or disable attributes in your account
* **Display order** - Change how attributes are sequenced
* **Section organization** - Group related attributes together
* **Custom labels** - Rename attributes to match your terminology
* **Tooltips** - Add help text explaining attributes
* **Public visibility** - Control what appears on your public website
### Custom object configuration
Your CSM can help with:
* **New object types** - Create categories for new asset types
* **Attribute setup** - Define which fields display for each type
* **Display labels** - Set user-friendly names for technical field names
* **Map styling** - Configure colors, icons, and labels
* **Object groups** - Organize related types together
* **Table setup** - Configure default columns and filters
### What to provide your CSM
**For property attribute changes:**
* Which attributes to enable, disable, or modify
* Desired display order or grouping
* Any custom labels or tooltips needed
**For new custom object types:**
* Description of what you want to track
* Source data in GeoJSON format (or Shapefile/Geodatabase for conversion)
* Which fields to display and their labels
* Map styling preferences (color, icon, line style)
* How objects should be grouped
* Which record types should be attachable
GeoJSON is the standard import format. Your CSM can convert data from Shapefile, Geodatabase, KML, and other GIS formats.
## Attribute data updates
### Property attributes
Different attributes update on different schedules:
* **Parcel data** - Updated when your CSM reimports assessor data (typically annually)
* **FEMA flood data** - Updated when new FIRM panels are adopted
* **Elevation data** - Updates automatically when Elevation Certificates are uploaded
* **Record-derived data** - Updates in real-time as records are created or modified
### Custom object attributes
Custom object attributes update when your CSM reimports updated GeoJSON data. Forerunner preserves attached records, files, and tasks during reimport by matching geometries.
## Security and permissions
Object access is controlled through Forerunner's permission system:
* **Staff users** - Access based on account role (Admin, Standard, or Limited)
* **Object visibility** - Some objects may be restricted based on user permissions or sensitive data settings
* **Public access** - Properties can be configured to appear on your public website with controlled information display
* **Audit trails** - All changes to objects are logged for accountability
Your Customer Success Manager can help configure user permissions to ensure the right team members have access to the right objects.
## Frequently asked questions
The source data doesn't include that information for the property. This could be because the data wasn't available during import, the property was added later, or the attribute doesn't apply.
Most attributes are read-only to maintain data integrity. Some update based on records you create (like SI/SD status). For corrections, contact your CSM.
Custom object categories require admin configuration. Contact your CSM to discuss adding new object types.
Forerunner matches geometries during reimport to preserve relationships. Records, files, and tasks remain attached even when attribute data changes.
Yes, custom objects can be configured for the public map. Work with your CSM to set up public visibility.