What a geoportal costs: scope the system before asking for a number

A geoportal cannot be estimated responsibly by counting screens. Cost depends on how much data needs preparation, who publishes it, which search and analysis tasks users need, what systems must integrate, how access is controlled, which availability target applies and who operates the platform after launch. A useful estimate separates discovery, implementation, migration and recurring operations.

The decision this guide supports

Before requesting a proposal, describe three scenarios: minimum publishable scope, target operation and likely growth. The minimum may be a catalogue and read-only viewer; target operations may add editing, roles, downloads, dashboards or integrations. The growth scenario avoids choosing a foundation that must be rebuilt when layers, traffic or editing teams increase.

Build the estimate from observable quantities: sources requiring cleanup, layers to publish, access roles, queries, editors, integrations, expected traffic and support hours. Separate initial investment from monthly operations and include storage, transfer, backups, monitoring, cartographic updates and incident response. A public read-only viewer does not cost the same as an application with editing, approval workflows and restricted data. Present scenarios with explicit assumptions and exclusions instead of one number. The range becomes defensible when each scope change can be traced to capacity, work or operational risk.

Recommended workflow

1. Agree. Inventory data, formats, volume, update frequency, licences and preparation work.
2. Structure. Describe tasks for public users, analysts, editors, administrators and support teams.
3. Check. List integrations, authentication, domains, permitted analytics and security requirements.
4. Document. Define availability, backup, monitoring, recovery and expected response times.
5. Operate. Estimate by phase with assumptions, exclusions, owners and annual operating cost.

Minimum controls before publishing or delivery

A useful review combines automated checks with expert judgement. At minimum, record:

• minimum scope verified through acceptance criteria.
• budget for migration and data quality.
• recurring cost separated from build cost.
• institutional owners for content and operations.

Limits that must remain visible

There is no universal price per layer, municipality or user. Two portals with the same number of maps can differ radically when one reads static data and the other edits, audits and integrates mission systems. GeoSAT’s local estimator organises assumptions; it is not a quotation or a service-level commitment. A definitive proposal requires validation of architecture, data and responsibilities.

To apply this method to a concrete project, review the GeoSAT sector service and compare its dependencies with the related service. These links serve different intents: this guide explains the process, while the service pages define scope, evidence and the appropriate commercial next step.