​

What are Custom Objects in Forerunner?

Custom Objects are user-defined geospatial features that can represent any type of geographic data your organization needs to track. Unlike Properties (which are always address-based points), Custom Objects support any geometry type—points, lines, polygons, and more. Custom Objects enable Forerunner users to extend the platform beyond traditional property management to support infrastructure tracking, zone management, and any other geospatial use case.

​

Why Custom Objects Matter

Custom Objects provide flexibility to:

• Track infrastructure like stormwater systems, utilities, roads, and critical facilities
• Define zones and regions such as community boundaries, flood zones, or planning areas
• Import existing GIS data from GeoJSON (your CSM can convert Shapefiles and other formats first)
• Create custom schemas with exactly the fields your organization needs
• Visualize any geometry including points, lines, areas, and multi-part features
• Engage public users through the public website, where community members can view custom object details, submit records, and attach files

​

Key Features

​

Flexible Geometry Types

Custom Objects support all standard GIS geometry types:

• Points: Individual locations (fire hydrants, signs, trees)
• Lines: Linear features (roads, pipes, power lines)
• Polygons: Areas (communities, flood zones, land parcels)
• Multi-part geometries: Complex features with multiple components

​

Dynamic Field Structure

Unlike Properties with fixed address fields, Custom Objects have:

• Label: The primary display name for each object
• Fields: Attributes your CSM sets up for each object type, like Text, Number, Date, Checkbox, User, URL, Relationship, and Lookup fields
• Editable values: On objects drawn in the app, fields marked as editable can be changed right in the info panel
• Custom styling: Colors, icons, line widths, and opacity per object type

​

Bulk Import Workflow

Custom Objects are typically created through bulk import:

1. Prepare GeoJSON data with your features (your CSM can convert a Shapefile or Geodatabase)
2. Send the file to your CSM to load
3. System processes and validates the data
4. Objects appear on map and in tables
5. Attachments (records, files, tasks) are preserved during re-imports

​

How Custom Objects Work

​

Object Types

Each set of Custom Objects belongs to an object type. For example:

• “Fire Hydrants” object type containing individual hydrant objects
• “Stormwater Systems” object type containing pipe and inlet objects
• “Community Boundaries” object type containing neighborhood polygons

Object types define:

• What fields all objects of that type will have
• How objects are styled on the map (colors, icons, line styles)
• Whether labels appear on the map
• Display order and legend settings

​

Object Groups

Related object types can be organized into object groups for easier navigation and management. For example, you might create a “Stormwater Infrastructure” group containing:

• Stormwater inlets
• Stormwater pipes
• Outfall structures
• Drainage basins

Groups enable:

• Organized navigation in the sidebar
• Combined table views across multiple object types
• Logical grouping of related features

​

Object Information Panel

Click any custom object on the map or in a table to open the Object Information Panel (OIP):

​

Importing Custom Objects

​

Supported Data Formats

Custom object imports use GeoJSON: GeoJSON:

• Standard web-friendly geospatial format
• JSON-based, human-readable
• Supports all geometry types
• Includes feature properties as fields

Shapefiles and other formats:

• Your CSM can convert a Shapefile or Geodatabase to GeoJSON for you before importing
• If you’re drawing a single object in the app, you can use Import from file with a GeoJSON or zipped shapefile

​

Import Process

​

Re-Importing and Updates

When you re-import Custom Objects:

• Matching by ID or shape: Objects are matched by source_id, or by how much their shapes overlap, and are updated (not recreated)
• Attachments preserved: Records, files, tasks, and comments remain linked
• Schema must match: New imports must have the same fields as existing data
• Nothing gets lost: If an object with records, files, or tasks can’t be matched in the new file, the import stops with an error

​

Map Visualization

​

Styling Options

Custom Objects support rich styling configurations: For Points:

• Icon selection from library
• Icon size and color
• Custom marker images

For Lines:

• Line color and opacity
• Line width
• Dash patterns

For Polygons:

• Fill color and opacity
• Border color and width
• Border opacity

Labels:

• Toggle labels on/off per object type
• Automatic label positioning
• Collision detection

​

Layer Controls

Each custom object type appears as a separate map layer:

• Toggle layers on/off in map controls
• Control layer order (z-index)
• Visibility based on zoom level
• Legend showing all active layers

​

Common Use Cases

​

Custom Object vs. Property

Understanding when to use each type: Use Properties when:

• You’re tracking buildings or addresses
• You need elevation certificates
• You want manual entry through UI
• You need parcel data integration

Use Custom Objects when:

• You need line or polygon geometry
• You’re importing existing GIS data
• You need flexible field structure
• You’re tracking non-address features

​

Limitations and Constraints

​

Schema Constraints

• Fields in your source file must be flat key-value pairs (no nested objects or arrays)
• Field names must be valid JSON keys
• Your CSM sets up each object type’s fields, and can change them without re-importing

​

Import Constraints

• Large imports (>10,000 features) may take significant processing time
• Only one import per object type at a time
• Import is atomic (all features succeed or all fail)
• Maximum file size depends on system configuration

​

Editing

• Objects created manually on web or mobile can have their label and geometry edited in the app
• Objects brought in through a GIS import are updated by re-importing the source data
• On manually created objects, fields marked as editable can be changed in the info panel by Creators and up. Other field values are updated by re-importing

​

Next Steps