Geoportals and web GIS viewers

A geoportal creates value when it publishes trustworthy information, helps users complete a real task and can still be operated after launch. We design WebGIS viewers and platforms around those three conditions: defined users, governed sources and fundable operations. The interface matters, but it depends on earlier decisions about updates, permissions, performance, accessibility and support.

Architecture before screens

Discovery identifies who searches, edits or downloads; which layers are public, internal or restricted; and how frequently each source changes. We review spatial databases, OGC services, APIs, files, providers and identity systems. The resulting architecture assigns responsibilities across catalogue, storage, services, caching, application, observability and editorial workflow. It can coexist with ArcGIS, QGIS, PostGIS or other platforms when the combination is consistent with existing licences and contracts.

We also set performance budgets. A complex national layer cannot be published like a small municipal inventory. The team agrees scales, generalization, tiles, query limits and behaviour when a source is unavailable. A visible fallback should explain service status instead of leaving an empty screen when WebGL, a font or an external provider fails.

What the operating team receives

An engagement may include a user and task map, target architecture, functional prototype, API design, publishing configuration, accessibility controls, tests, operating guide and evolution plan. Metrics connect to actions such as locating an asset, comparing scenarios, downloading a source or reporting an issue, not only counting page visits.

OpenGIS demonstrates an open geospatial architecture with identified sources and a working mapping experience. Its local estimator explores how layers, users, updates, availability and integrations affect the design. The output guides discovery but is neither a quotation nor a substitute for infrastructure and security review.

The Medellín geographic platform case uses public contractual evidence. It describes the documented object and scope without turning them into proof of unpublished results. That precision enables a useful experience comparison.

Preparing a scope conversation

A productive starting brief includes three priority tasks, a source list, approximate volumes, access profiles and availability expectations. We separate launch from operations across build, cloud, support, data updates and continuous improvement. This allows an organization to compare alternatives by total cost, control and maintainability rather than the appearance of an initial demonstration.