SuperMap
Enterprise geospatial platform technology for GIS, spatial services and advanced 2D/3D applications where its architecture fits the project requirements.
Software Engineering / Platforms & Technology
Technology chosen to support the system — not define it.
MapSoft works with commercial, open-source and custom technologies according to the architecture, users, information model, deployment environment and long-term requirements of each project.
Architecture first
Problem & usersResponsibilities · workflows · constraints
↓
ArchitectureData · integrations · deployment · security
↓
Platform choiceCommercial · open-source · custom
Platform principle
We do not force every project into the same stack.
The operating environment determines what is appropriate. Existing client technology, interoperability requirements, internal expertise, licensing, infrastructure, deployment constraints and long-term maintainability all influence the solution architecture.
Platform when appropriate. Custom engineering when required.
Strategic platforms
Platforms are engineering foundations, not universal products.
We present these technologies through their role in real solutions rather than repeating generic vendor marketing.
MapInfo | Precisely
Established GIS technology relevant to spatial data management, analysis and client environments where MapInfo continuity or integration is required.
Odoo
A modular foundation for selected ERP and operational-system implementations where its architecture matches the client's process model.
Technology ecosystem
Organized by architectural role — not as a logo wall.
The exact technology set varies by project. The categories below show the types of engineering environments MapSoft already works with and how they fit into the system architecture.
Application Engineering
TypeScript · JavaScript · React · Node.js · Python · .NET · REST APIs
Geospatial Technology
PostgreSQL/PostGIS · GeoServer · GDAL · QGIS · ArcGIS · Mapbox · Google Maps Platform
Data & Integration
SQL · ETL pipelines · APIs · validation · reporting · synchronization
Infrastructure & Delivery
Docker · Git · CI/CD · automated testing · cloud · on-premise deployment
Identity & Governance
Role-based access · identity integration · auditing · configuration management
AI-supported Engineering
Research · development assistance · test generation · documentation · controlled evaluation
Architecture principles
Technology should remain understandable, maintainable and interoperable.
The objective is a system that fits the client environment and can evolve, not the most fashionable stack or the largest number of tools.
Fit the operating environment
On-premise, cloud and hybrid systems have different constraints and responsibilities.
Prefer interoperability
Data and services should remain usable beyond one interface or one application.
Keep architecture maintainable
Avoid unnecessary complexity and make responsibilities explicit.
Design for evolution
Processes, integrations, data volumes and user expectations change over time.
Related engineering
Architecture choices are part of the delivery process.
Technology decisions are validated against requirements, data, integrations, security boundaries, deployment constraints and the support model. They are not isolated decisions made before the project context is understood.
Explore Engineering & Delivery Approach →UsersDataIntegrationsInfrastructure
↓Architecture decision↓PlatformApplication stackDeploymentOperations
MapSoft
Discuss architecture→Have an existing technology environment the new system has to fit?
Tell us about the applications, infrastructure, data and integration constraints involved.