MAPGIS · ARCHITECTURE ASSESSMENT · COLOMBIA
MapGIS no longer has to sit at the center of your GIS
MapGIS may continue to support valuable workflows. The question is whether the installed implementation lets the organization reuse data, replace components, automate processes and evolve without rebuilding the entire system. We assess first, then recommend retaining, upgrading, decoupling or migrating in stages.
GeoSAT is an independent consultancy and is not affiliated with, sponsored by or endorsed by H&G Consultores. MapGIS is mentioned only to identify the technology being assessed. The MapGIS V10 capabilities cited are vendor claims, not GeoSAT validation of a specific installation.
Sources reviewed: 2026-07-17
Retain
The implementation meets the criteria and its cost is justified.
Upgrade
The vendor path removes dependencies with controlled risk.
Decouple
Data, APIs or rules leave the viewer without stopping operations.
Migrate
Replacement workflows pass tests before components are retired.
A PRECISE DEFINITION
Legacy does not mean useless
We call a system legacy when its continuity depends on accumulated technologies, contracts or knowledge that make it expensive to change one component without affecting others. A solution may still work, remain critical and need modernization at the same time. Purchase age alone does not establish its current technical condition.
The map-viewer-centered model belongs to an earlier architecture generation
For years, many platforms organized data, applications and processes around the viewer. A current architecture places data, APIs and business rules at the center and allows the interface to change without rebuilding the system. The MapGIS V10 announcement describes a similar evolution; an assessment must establish whether each installed implementation has completed that transition.
Viewer-centered model
- →The interface concentrates integrations and rules
- →Changing one component affects several layers
- →The platform version constrains evolution
- →Operational knowledge remains concentrated
Data-and-process-centered model
- →PostGIS or another reusable repository
- →Documented APIs and services
- →Replaceable, modular interfaces
- →Transferable deployment, tests and operations
WHAT WE KNOW · AND WHAT WE DO NOT
The installed version matters more than the product name
Public sources show a long technology lineage and, at the same time, a current product that is still evolving. Each fact has limited scope: none supports disqualifying a version or assigning risks without inspecting it.
2009–2024
A documented history of operations and upgrades
A Medellín procurement document records the first MapGIS Flex 3.0 purchase in 2009 and a 2024 contract to subscribe to, support, maintain and upgrade MapGIS 9.0. It proves continuity and evolution; it does not establish the technical state of an installation today.
Medellín public document ↗MapGIS5
A historical listing hosted by Esri
Esri’s partner listing describes MapGIS5 as a Java and Adobe Flex RIA connected to ArcGIS Server and engines such as Oracle or SQL Server. The listing shows no publication date and does not prove the architecture of MapGIS9 or MapGIS10.
Esri partner directory ↗2024
MapGIS9 implemented in Itagüí
Circular 317 reported that the SIGMI Geoportal had been implemented on the MapGIS 9.0 suite. It proves one institutional implementation; it does not describe its cost, internal architecture or complete functional scope.
Itagüí Circular 317 ↗2026
MapGIS 8.0 and 9.0 coexisted at Cornare
In May 2026, the Cornare intranet published separate links to its internal MapGIS 8.0 and MapGIS 9.0 geoportals. This is evidence of incorporation and coexistence, not proof of complete functional acceptance.
Cornare intranet 2026 ↗MapGIS10
The vendor announces a paradigm shift
H&G presented MapGIS V10 as a move from the map at the center toward data, processes and decisions, including integration with the latest ArcGIS SDK. That description must be acknowledged before assessing a particular installation.
H&G publication ↗2026
MapGIS-POT in a current Medellín case
Esri ArcNews published a MapGIS-POT implementation integrated with ArcGIS Enterprise, Pro, Online and Dashboards. It confirms current activity; it does not independently verify portability, cost or functional equivalence.
Esri ArcNews 2026 ↗ASSESS BEFORE RENEWING
Eight evidence tests for making the decision
For new investment, comparing screens or version names is not enough. We request technical and contractual evidence for the layers that determine cost and the ability to evolve.
Version and support
Runtime, library, SDK, operating system, database and support-date inventory.
Data portability
Complete export of relationships, domains, metadata, attachments, history and permissions.
APIs and standards
REST, OGC, documentation, limits, authentication and existing consumers.
Business rules
What lives in the platform, custom applications, database or manual processes.
Code and ownership
Repositories, licenses, modification rights, platform-specific components and deliverables.
Third-party maintenance
What another supplier can operate without reserved code or undocumented knowledge.
Operations and security
SSO, roles, audit, patches, backups, recovery, monitoring, performance and SLA.
Total cost
Licenses, ArcGIS, database, infrastructure, support, evolution, training and transition.
FOUR POSSIBLE PATHS
We do not replace a platform on principle
Retain and document
If the current version meets the technical and economic criteria, the recommendation may be to keep it and close documentation or operational gaps.
Upgrade with the vendor
Validate which dependencies the new version removes, how licensing changes and what application and integration work is required.
Decouple by layer
Move data, services or rules to PostGIS and documented APIs while temporarily retaining the useful interface or modules.
Migrate after testing
QGIS, GeoServer, QGIS Server or a custom application replaces only workflows that have passed acceptance criteria.
COLOMBIAN CASE
Cornare shows hybrid modernization, not a simple replacement
Cornare reported databases migrated to PostgreSQL and a move from ArcGIS to QGIS. It documented MapGIS9 integration in 2025 and linked to internal 8.0 and 9.0 geoportals in May 2026. The correct lesson is to retain what adds value, decouple the necessary layers and measure retired cost—not to present the case as a complete MapGIS replacement.
Read the case and its limits →Primary sources and scope
Each link supports a specific fact. Commercial pages describe vendor claims; public documents describe one organization at one point in time. No source replaces an inventory of the installation under renewal.
H&G · MapGIS suite ↗
The vendor claims web and mobile access, customization, compatibility and interoperability.
H&G · MapGIS V10 ↗
Announcement of the paradigm shift and capabilities claimed for the new version.
Esri ArcNews · MapGIS-POT 2026 ↗
Current Medellín case and declared integration with ArcGIS Enterprise, Pro, Online and Dashboards.
Esri · MapGIS5 ↗
Historical description of technologies and dependencies; it does not prove later versions.
District of Medellín · procurement history ↗
First purchase in 2009, declared architecture and a 2024 MapGIS 9.0 upgrade contract.
Itagüí · 2024 SIGMI implementation ↗
Institutional circular identifying MapGIS version 9.0.
Cornare · first-half 2025 report ↗
Integration of MapGIS9 modules into a new service architecture.
Cornare · 2026 intranet ↗
Separate institutional links to internal MapGIS 8.0 and MapGIS 9.0 geoportals.
Adobe · support periods ↗
The matrix records the end of extended support for Adobe Flex 3 in 2015.
For new investment, assess before renewing
We deliver a technical inventory, dependency map, portability matrix, TCO scenarios and a path with acceptance tests. The conclusion may be to retain, upgrade, integrate or migrate MapGIS components: the evidence decides.
Request an architecture assessment →