Skip to main content

Create a GIS Layer

This workflow explains how to create a GIS Layer inside an existing GIS View.

A GIS Layer defines how business data from your database is queried, related, and presented spatially. It does not store or edit data. Instead, it acts as a controlled, read-only query that external mapping tools can consume safely.

Layers are the mechanism that turn raw business records into map-ready information.

Before You Start​

To create a GIS Layer, you must already have:

  • An existing GIS View
  • A clear understanding of which business data you want to expose
  • Basic familiarity with how your tables relate to one another

If you have not created a view yet, start here:

Mental Model (Important)​

Think of a GIS Layer as a read-only query definition with geographic context.

Conceptually:

Business Table (t0) ↓ Optional Related Tables (joins) ↓ Selected Business Fields ↓ One Geographic Field ↓ Map Layer

Layers describe how data is assembled, not where it is stored.

Step-by-Step: Creating a GIS Layer​

1️⃣ Select a GIS View​

Navigate to the GIS Views page and select the view that will contain the layer.

Layers always belong to a view and cannot exist independently.

2️⃣ Click + New Layer​

Click + New Layer in the Layers section to open the Create GIS Layer popup.

This popup is used for both creating and editing layers.

3️⃣ Name the Layer (Required)​

Choose a name that describes what business data the layer represents.

Best practices:

  • Use lowercase, descriptive identifiers
  • Avoid spaces and special characters
  • Keep names stable over time

Good examples

  • projects
  • client_properties
  • operational_assets

The layer name may appear in external GIS tools and URLs.

4️⃣ Choose a Base Table (t0)​

The base table is the primary business table for the layer.

This table:

  • Acts as the starting point for the query
  • Determines which fields are available
  • Controls which related tables can be joined

Choose the table that best represents the main subject of the layer.

Example
If you want to visualize projects with client information, the base table should be projects, not clients.

5️⃣ Review Available Columns​

After selecting a base table:

  • All available business fields are loaded
  • Columns can be searched and filtered
  • Foreign key relationships are detected automatically

At this stage, no data is queried — you are only defining the structure of the layer.

6️⃣ Select Business Fields to Expose​

Select the columns you want to make available to external tools.

Each selected column:

  • Becomes an attribute in the map
  • Is included in the live query
  • Can be used for labeling, filtering, or analysis

Unselected columns are not exposed.

Tip
Only expose what is useful. Lean layers are easier to understand and perform better.

If a selected column represents a relationship:

  • Related table fields become available automatically
  • Joins are created safely and predictably
  • Only selected related fields are exposed

You may:

  • Choose specific related fields
  • Rename outputs using an alias
  • Pull only what is relevant

Example:

  • projects.client_id → clients.name
  • Output alias: client_name

These joins provide context, not ownership of related data.

8️⃣ Choose a Geographic Field (Required)​

Every GIS Layer must reference exactly one geographic field.

This field determines how the business records are placed on the map.

You can choose a geographic field from:

  • The base business table
  • A related table

Only one geographic field can be active at a time.

⚠️ Important
This system visualizes location-aware business data.
It does not manage or edit spatial features.

9️⃣ (Optional) Configure Visibility & Order​

You may optionally set:

  • Visibility – Whether the layer is shown by default
  • Z-index – Draw order relative to other layers

These settings affect presentation only.

🔟 Save the Layer​

Click Create Layer to save.

At this point:

  • The layer definition is stored
  • The layer becomes available immediately
  • External GIS connections reflect the change on refresh

No exports or server restarts are required.

Editing a GIS Layer​

Editing a layer allows you to:

  • Adjust which business fields are exposed
  • Modify relationships
  • Change which geographic field is used

Edits:

  • Update the live query definition
  • Do not change underlying data
  • Take effect immediately for connected tools

Common Mistakes to Avoid​

  • Exposing too many fields without purpose
  • Choosing a base table that does not represent the main subject
  • Using an unintended geographic field
  • Treating layers as disposable or experimental

Layers should be intentional and purpose-driven.

Performance & Safety Notes​

  • All layers are read-only
  • Joins are deterministic and controlled
  • Duplicate joins are automatically avoided
  • External tools cannot modify data

This