Geobble Help Center

Geobble helps you move from raw geographic information to reviewable analysis and publishable interactive maps. This guide explains the main working surfaces and the safest path through them.

Start with the Outcome You Need

After signing in, choose the closest starting action:

  • Create a Project to investigate a question, combine context, run spatial analysis, or draft a map with AI assistance.
  • Find a public dataset to reuse a Source that is already available in the catalogue.
  • Upload your data to create a Source from a supported geospatial file.
  • Extract Features to propose geographic features and attributes from supported documents, URLs, text, or other evidence.
  • Enrich a Source to propose additional attributes for features in an existing Source.
  • Open Studio to prepare data, refine cartography, collaborate, and manage map-production work directly.

Geobble does not automatically start paid work from public links or starter actions. Review the operation and confirm it before supported billable processing begins.

The Core Workflow

1. Create or Connect Sources

A Source is reusable geographic data. Sources can come from:

  • supported GIS files;
  • external PostGIS tables;
  • public Sources in the Geobble catalogue;
  • reviewed feature-extraction results;
  • reviewed enrichment results.

Keep source names, descriptions, licences, dates, limitations, and provenance accurate. These details become important when a Source is reused or published.

2. Work in a Project

A Project is a conversational workspace for a geographic question or map objective. Add relevant Sources and Maps as context, then ask for work such as:

  • filtering or summarizing features;
  • creating buffers or intersections;
  • comparing places;
  • measuring accessibility;
  • joining related datasets;
  • creating analysis layers;
  • drafting symbology and map structure.

AI-assisted results remain part of a reviewable workflow. Inspect assumptions, inputs, generated layers, and styles before relying on them.

3. Refine in Studio

Studio is the direct production environment. Use it when you need closer control over:

  • source extraction and enrichment;
  • layer order and grouping;
  • visibility and zoom ranges;
  • classifications, palettes, labels, legends, and popups;
  • map composition and interaction;
  • collaborative editing and publication preparation.

Projects and Studio are complementary. Projects accelerate exploration and the first result; Studio is where you apply production craft.

4. Share or Publish Deliberately

Published Maps, Collections, Sources, and other supported catalogue resources can be public or private. Projects remain private but can be shared with selected users or teams at an appropriate permission level. A Source's public visibility is inherited from its required primary Collection.

Before publishing, check:

  • whether the data licence permits redistribution;
  • whether sensitive attributes should be removed;
  • whether the analysis and symbology communicate the intended conclusion accurately;
  • whether descriptions, citations, dates, and limitations are complete;
  • whether the map is understandable to its intended audience.

Working with Data

Uploading a Source

  1. Open Sources and choose the upload action.
  2. Select a supported file and provide the required metadata.
  3. Review any displayed storage, processing, or credit information.
  4. Confirm the upload.
  5. Follow the source status until processing completes.
  6. Preview the data before using it in analysis or publication.

Accepted formats and limits can vary by workflow. Use the current upload interface as the source of truth for file constraints.

Source Statuses

  • PENDING — accepted and waiting for processing.
  • PROCESSING — ingestion or preparation is running.
  • READY — available for preview and use.
  • ERROR — processing failed; inspect the displayed reason before retrying.
  • ARCHIVED — retained but no longer active in ordinary workflows.

Extract Features

Extract Features helps create a proposed Source from evidence.

  1. Open Extract Features in Studio.
  2. Add the supported evidence requested by the workflow.
  3. Describe the geographic features and attributes you need.
  4. Start the operation after reviewing its scope and expected cost.
  5. Inspect each proposed feature, its attributes, and the supporting evidence.
  6. Correct or reject uncertain output.
  7. Save the accepted result as a Source.

Extraction is not a promise of perfect ground truth. Treat the output as a structured first result that must be validated for the intended use.

Enrich a Source

Enrich Source proposes attributes for existing features.

  1. Open Enrich Source in Studio.
  2. Select the Source you are allowed to modify.
  3. Provide the evidence and define the attributes you want to add.
  4. Review the operation and confirm it.
  5. Inspect proposed values and their provenance.
  6. Accept, correct, or reject changes before committing them.

Use enrichment for evidence-backed additions, not for silently overwriting uncertain facts.

Collections and Catalogue Metadata

A Collection groups related Sources. Use collections to make a coherent body of data easier to discover and maintain.

For public Sources and Collections, provide useful catalogue metadata such as:

  • subject and geographic scope;
  • country or administrative coverage;
  • creator and source URL;
  • licence and redistribution conditions;
  • temporal or reference dates;
  • processing notes and known limitations;
  • a recommended citation.

Projects and Maps

Create a Project

  1. Open Projects and create a new Project.
  2. Choose a starter action or describe the objective directly.
  3. Attach relevant Sources or Maps as context.
  4. Review the proposed work before confirming operations.
  5. Inspect the resulting layers, calculations, and styling.
  6. Continue in the Project or open Studio for direct refinement.

A Project should represent a clear question or deliverable. Keeping unrelated work in separate Projects makes the context easier to understand and audit.

Publish a Map

Publish only after the map is ready for its audience. A published map can provide an interactive result that viewers can pan, zoom, and inspect.

Before publication, verify:

  • title and description;
  • visible layers and initial extent;
  • labels, legends, and popups;
  • attribution and citations;
  • access settings;
  • mobile and desktop readability;
  • whether the data may legally and ethically be shown.

AI-Assisted Work and Review

Geobble uses AI to accelerate data work, spatial analysis, and map creation. It should reduce repetitive effort, not remove professional judgement.

For important work:

  • verify source quality and coordinate assumptions;
  • inspect joins, filters, buffers, routes, classifications, and aggregations;
  • check units and geographic coverage;
  • review uncertain extracted or enriched values;
  • compare the result with trusted references;
  • record limitations in the Source or Map metadata.

Accounts, Access, and Collaboration

Handles

Your handle is the stable identifier used in account and resource URLs. Eligible accounts may be offered a one-time confirmation or change for an automatically generated handle. Handle changes are currently restricted and are not generally available, so choose carefully and contact support when the setting is unavailable.

Individual and Organization Accounts

  • Individual accounts are suitable for personal and independent work.
  • Organization accounts support multiple members, role-based permissions, and shared resources.

Organization roles and resource-specific shares are separate controls. Give users only the access needed for their work.

Public, Private, and Shared Access

  • Public Maps and catalogue resources can be viewed by the wider audience supported by the product.
  • Private resources remain limited to authorized account access.
  • Shared access grants selected users a role on a supported resource without making it public.

Review access whenever a collaborator changes role or a project becomes sensitive.

Credits and Billing

Credits account for storage and compute-heavy operations such as AI work, ingestion, data processing, and spatial services. The exact cost depends on the operation and input.

Use the billing area to review:

  • plan and included credits;
  • current balance;
  • storage usage and ongoing cost;
  • credit reservations or completed charges;
  • additional credit options where available.

When the interface presents an expected cost, review it before confirming the operation. If a job fails, consult its status and billing record before retrying repeatedly.

Troubleshooting

A Source Failed to Process

  • Read the displayed error.
  • Confirm the file type and required companion files.
  • Check that the geometry and coordinate information are valid.
  • Reduce unnecessary size or complexity where appropriate.
  • Correct the input before retrying.

An AI-Assisted Result Looks Wrong

  • Check the Sources and context attached to the task.
  • Restate the intended area, units, attributes, and output.
  • Inspect the operation rather than judging only the rendered map.
  • Correct or reject uncertain data-work proposals.
  • Start a narrower task when the original request combined too many objectives.

A Collaborator Cannot Open a Resource

  • Confirm the resource is owned by the expected account.
  • Check whether it is public, private, or explicitly shared.
  • Verify the collaborator's organization role and resource-specific permission.
  • Ask the collaborator to sign in with the account that received access.

Getting Further Help

Use the Contact page for product questions, support requests, partnerships, or a geospatial workflow you would like to discuss. Include the relevant resource, what you attempted, and the visible error or unexpected result. Do not send passwords, private keys, or raw sensitive data.

Last updated: August 2026