Geova Docs

Appearance

Geova website

Layers & Symbology ​

Purpose: Prepare geometry, layer appearance, and data definitions.

Before you start: A project and a role allowed to configure its layers.

Expected result: The intended layer is ready for its collection or review task.

Layers organize spatial data by theme. Each layer has a geometry type, visual style, and optional form schema. This module covers creating layers, styling them, labeling features, and applying field-based symbology.

1. Creating a New Layer ​

  1. Open Layers from the menu or navigation available in your layout. The standard Collector phone layout uses the menu rather than a bottom tab bar. Layer creation requires Owner, Admin or Editor permissions.
  2. Tap + New Layer.
  3. Fill in the Define New Layer dialog:
    • Layer Name — A descriptive name (e.g., "Street Lights", "Water Pipes").
    • Geometry Type — Choose one from the dropdown:
      • Point (pins, assets, trees) — For discrete single-location features.
      • Line (pipes, roads, cables) — For continuous linear features.
      • Polygon (areas, parcels, zones) — For enclosed boundaries.
    • Marker Color — Select from the curated palette (11 colors), or tap the + ring to pick any custom color using the color wheel.
    • Polygon Fill Color (Polygon type only) — Choose an internal area color. Toggle the Hollow checkbox to make the polygon transparent (outline only).
    • Marker Icon (Point type only) — Tap to open the Icon Picker with searchable categories: Location, Nature, Infrastructure, Transport, Emergency, Buildings, and more.
  4. Tap Create Layer.

The new layer appears in the Layer Manager with its geometry type, style preview, and form status.

Example: A fiber survey project might use three layers: "Splice Enclosures" as points, "Fiber Routes" as lines, and "Service Areas" as polygons. Keeping these themes separate makes forms, styling, and exports easier to manage.

2. Layer Card Interface ​

Actions depend on your role. A Collector can use prepared layers but does not configure their structure, style or dictionary. Eligible team layers can also offer Work Schedule or My work; see team workflows.

Each layer card displays:

ElementDescription
Layer NameTap to select this layer and jump to the Map View for drawing
Geometry BadgeShows Point, LineString, or Polygon
Form BadgeGreen ✅ Form if a form is attached; amber ⚠️ No Form if not
Symbology PreviewVisual swatch showing current marker/line/polygon style
Visibility ToggleShow or hide the layer on the map
Zoom to LayerMove the map to the layer's feature extent
StyleOpen the Edit Layer Style modal
DictionaryOpen the Data Dictionary modal
DeleteRemove the layer and all its features after confirmation

Choose a control by its effect ​

  • Layer name: activates that collection layer and opens Map.
  • Visibility: changes what you can see; it does not select the destination for new collection.
  • Zoom to Layer: helps find the dataset's extent without changing its geometry.
  • Style: changes presentation, including labels and classification.
  • Dictionary: explains the fields' meanings and units; edit actual record values through their forms.

For example, show a district reference and activate Streetlights to collect a new asset against that background. Hiding the district later changes the view, not the asset's saved attributes.

Reference Layers ​

Reference layers are imported background polygons used for spatial auto-fill. They support visibility toggling and deletion, but they are not drawing layers.

3. Editing Visual Styles ​

  1. Tap the 🎨 Style button on any layer card.
  2. The Edit Layer Style modal opens with these options:

Marker / Line Color ​

Select from the palette or use a custom color via the + ring.

Polygon Fill Color ​

(Polygon layers only) Set an internal area color, or check Hollow for a transparent outline.

Marker Icon ​

(Point layers only) Tap to open the searchable Icon Picker. Browse categories like Nature (trees, water), Infrastructure (power, construction), Buildings, Transportation, and Hazards.

4. Completion Indicator ​

The Completion Indicator toggle is inside the Edit Layer Style modal.

Completion mode colors individual features green when complete and red when incomplete. It checks all eligible editable form fields, including optional fields. Hidden fields, system fields, read-only fields, and auto-geometry fields are excluded; Smart Logic also excludes fields it currently hides.

A missing value, empty text, or whitespace-only text is incomplete. Numeric zero and a saved false/No value count as values. A layer with no usable form or no eligible fields is not automatically complete.

Example: Asset ID and Condition are filled, but an optional visible Notes field is empty. The feature remains red. If a saved Smart Logic rule hides Notes for that condition, Notes no longer contributes to completion.

Color priority: Completion mode replaces category/range colors and category-specific icons. It also takes precedence over Hide Unclassified. Turn completion off to review Condition or pressure classification again. The map legend explains the current colors; overview cells containing a mix of records remain neutral.

Use this indicator to find unanswered fields. Green does not mean the asset is in good condition, its values are correct, or its record has synced. Required-field validation when saving and AI completeness checks can answer different questions.

How to Enable ​

  1. Open the Edit Layer Style modal.
  2. Scroll to Completion Indicator.
  3. Enable the switch and read the completion-priority note.
  4. Tap Save Style.

5. Text Labels on the Map ​

Display selected attribute values directly on the map so users do not need to tap every feature to identify it.

How to Enable ​

  1. Open the Edit Layer Style modal.
  2. Scroll to Show Feature Labels.
  3. Toggle the switch on.
  4. A Label Field dropdown appears. Select which attribute to render (e.g., Shelter_Name, Road_ID). Choose Auto-detect to let the engine pick the best field.
  5. Tap Save Style.

Example: On an inspection map, labeling the Asset_ID field lets reviewers identify hydrants, poles, or valves without opening each feature popup.

6. Field-Based Symbology (Classification) ​

Classification styles features by attribute values. Instead of showing a layer in one color, Mapplex reads a selected field and applies colors based on the configured rules.

Selecting a Classification Field ​

  1. In the Edit Layer Style modal, scroll to Field-Based Symbology.
  2. Open the Color by Field dropdown.
  3. Select a property from your layer's schema (e.g., Zoning_Type, Pressure_PSI).

Choosing a Symbology Type ​

A toggle switch appears with two options:

Categorical (Qualitative) ​

Best for text/string properties. Select a field, review the suggested values and rules, and assign a meaningful color to each category. For example:

  • Residential → Yellow
  • Commercial → Red
  • Industrial → Purple

You can manually add rules with the + Add Rule button and customize each rule's value and color. A style supports up to 64 rules; categories that differ only in case or surrounding spaces are treated as duplicates.

Graduated (Quantitative) ​

Best for numeric data. Configure:

SettingOptions
MethodQuantile (equal feature count per bin), Equal Interval (consistent numeric steps), Natural Breaks / Jenks (clusters around natural data gaps)
ClassesNumber of bins (2–10)
Color RampBlues, Reds, Greens, Yellow-Orange-Red (Heat), Red-Yellow-Green (Diverging)

Tap Generate Bins to compute draft ranges, then review their limits and colors and tap Save Style.

Read the distribution message before using the result. It distinguishes an exact distribution from cached data and identifies limited suggestions or sampled numeric values. Category suggestions are limited to 200 values; they are not a guarantee that every value has a rule. Natural Breaks can use a representative sample for large datasets, as the screen reports.

Choose the method by the question: Equal Interval is useful for equal numeric steps; Quantile balances record counts; Natural Breaks groups the current distribution. Generated bins describe the data. They do not establish engineering limits or acceptable operating ranges. Review units and apply your agreed thresholds before using colors to prioritize work.

Hide Unclassified ​

Hide Unclassified hides unmatched features from the map without deleting them. When you save, Mapplex checks the distribution and asks you to confirm how many unmatched records will be hidden. Hosted layers require an authoritative online distribution for this check; reconnect if the save reports that it cannot verify coverage.

For the first review, leave this option off so unexpected or missing values remain visible. After saving, compare the legend and several known records. If a feature disappears, check visibility, completion mode, and classification rules before treating it as missing data.

Example: A water utility uses Graduated classification on Pressure_PSI:

  • Red = low pressure
  • Yellow = expected range
  • Green = higher pressure in this illustrative ramp

This helps reviewers spot pressure issues without opening each record.

7. Data Dictionary (Schema) ​

The Dictionary button on each layer card opens the Data Dictionary modal. Use it to document what each field means so filters, reports, and Geova AI queries are easier to interpret.

For each field in your layer's schema, you can configure:

SettingPurpose
AliasHuman-readable name for the field (e.g., field_abc123 → "Tree Height")
UnitMeasurement unit (e.g., "meters", "PSI", "hectares")
RoleSemantic category: Name, Category, Population, Area, Capacity, Date, Status, Slope, Amount, Identifier, Code, Notes
Type HintInterpretation hint: Auto, Text, Number, Date, Category, Yes/No; does not convert stored values

The Fields configured indicator shows how many non-technical fields have dictionary information. Technical fields are marked and excluded from this score. It describes metadata coverage, not record completion or data accuracy. Unit inputs appear for numeric fields.

For example, give Pressure_PSI the alias Pressure, unit PSI, and an appropriate numeric hint, then save the Dictionary. This explains the existing values; entering a different unit does not convert them. Use Forms to change the questions and feature forms to edit answers.

Why does this matter? Imported files often use short or unclear field names such as field_x47 or ht_m. The Data Dictionary lets you record that the field means "Tree Height" and uses meters, which improves filtering, reporting, and AI-assisted queries.

8. Example: Annual Fire Hydrant Inspections ​

Need: A municipal water department needs to inspect hydrants and make sure each record includes a pressure reading.

Solution using Mapplex Layers:

  1. Create the Layer: A Point layer named "Hydrants 2026" — points are ideal for exact curb locations.

  2. Style the Baseline: Open Style, select a water-related icon, and set the marker color to gray.

  3. Enable Labels: Toggle on Show Feature Labels and target the Cross_Street field. The map shows labels such as "Main & 5th" over each point.

  4. Track Completion: Mark "Pressure (PSI)" as required for saving and enable the Completion Indicator for review. Points are red until all eligible visible fields have values, then green. Optional visible fields count too.

  5. Review Results: Turn completion mode off. Switch symbology to Graduated, target Pressure_PSI, and generate bins. Review the ranges and colors against your inspection criteria before saving; high pressure is not automatically acceptable.

Next: Proceed to Module 03: Map View to start drawing, measuring, and collecting data on the map.

Spatial intelligence. Clear next steps.

© 2026 Geova