We help organizations inventory geospatial estates, migrate services and databases, reconstruct applications, develop new operational tools and execute phased cutovers with explicit technical acceptance criteria.
Every engagement can stand alone or combine into a modernization program.
Crawl service directories, inspect portal content, decode web maps/scenes/apps, inventory databases and files, map dependencies and identify unsupported extensions or hidden coupling.
Move feature classes, rasters, attachments, relationship classes, domains, subtypes and history into open or target-native stores with reproducible validation.
Stand up 3DGeoServEngine endpoints that existing applications can exercise before final cutover.
Reconstruct maps, forms, dashboards and workflows in GeoLibre, the ArcGIS Maps SDK, or a purpose-built client while separating business logic from vendor APIs.
Design and build mission-specific web, desktop, mobile, data, automation and AI-assisted workflows on the shared service layer.
Package, secure, monitor, publish and transfer the self-hosted platform into the client’s operating model.
Professional services can validate implemented surfaces, complete partial paths and build missing adapters. The engagement plan labels those activities differently so a client knows whether it is configuring, testing or developing a capability.
| Capability track | Current maturity | Engagement work | Acceptance gate |
|---|---|---|---|
| FeatureServer and dynamic MVT | Implemented service surfaces with client/workflow-specific validation still required | Map schemas and identifiers, configure sources, translate renderers/filters, exercise query/edit paths and tune dynamic tile SQL | Golden query results, edit round trips where applicable, visual tile checks, client-version matrix and performance baseline |
| VectorTileServer, StreamServer and SceneServer | Implemented route families whose coverage depends on source profile and consuming client | Register representative packages/feeds/scenes, configure styles and subscriptions, test reconnect and client-specific behavior | Metadata and resource retrieval, visual/feature correctness, reconnect/failure tests and representative client sign-off |
| MapServer | Partial: directory/metadata and raster-bridge components are present; the full dispatcher was not substantiated | Complete required request routing and rendering operations for the migration scope instead of assuming universal MapServer parity | Reference GetMap/export outputs, layer/scale/style matrix, error semantics and tested desktop/web clients |
| Local ImageServer | Implemented operation paths with raster/client-specific validation required | Register representative local rasters and validate metadata, export, identify, samples, statistics and tile variants | Pixel/value, nodata, extent, reprojection, overview, performance and consuming-client tests |
| Remote object-storage COG → ImageServer | Integration target: HTTP range-reader and ImageServer components exist, but general registration/caller wiring was not substantiated | Complete the endpoint wiring for the selected S3/Azure/GCS HTTPS access pattern, then harden signed-URL and failure behavior | End-to-end remote registration, range-request evidence, pixel/value parity, expiry/retry behavior and real-client validation |
| Application reconstruction | Project-specific development, not an automatic converter claim | Decode source configuration, preserve portable contracts and deliberately redesign vendor-specific widgets, identity and business logic | Use-case scripts, accessibility and responsive checks, security tests, user acceptance and documented exceptions |
A reliable migration distinguishes portable contracts from platform-specific behavior before implementation begins.
| Source asset | Migration treatment | Target options | Acceptance evidence |
|---|---|---|---|
| Feature services | Schema, spatial reference, domains, subtypes, GlobalIDs, attachments, related records, sync and edit semantics | GeoPackage/DuckDB/PostGIS + FeatureServer + OGC API Features + MVT | Query parity, edit round trip, attachment/relationship validation, performance baseline |
| Map and vector tile services | Layer order, scale ranges, labels, renderers, symbols, popups and tile strategy | Implemented dynamic MVT/VectorTileServer paths; stored MBTiles/PMTiles; scoped completion and validation for MapServer/WMS | Visual regression at reference extents/scales, request-dispatch coverage and tile-load performance |
| Imagery and mosaics | Band metadata, nodata, overviews, footprints, time/elevation dimensions and raster functions | Local COG/ImageServer paths; object-storage COG range-reader integration; WCS and STAC assets | For remote COG, completion of registration/dispatcher wiring precedes pixel/value, reprojection, export/identify/statistics and range-read validation |
| Scenes and 3D | I3S/SLPK nodes, materials, attributes, coordinate systems and conversion feasibility | SceneServer, OGC 3D Tiles 1.1, GLB/glTF and web 3D workflows | Scene extent, feature query, texture/geometry integrity and frame-rate targets |
| Web maps, scenes and apps | Decode item JSON, operational layers, basemaps, forms, widgets, interactions and identity dependencies | GeoLibre projects/plugins, ArcGIS SDK client, custom responsive app or Experience builder output | Use-case scripts, screenshot/behavior parity and user acceptance sessions |
| Geoprocessing and notebooks | Tool inputs/outputs, environments, dependencies, schedules, credentials and artifact publication | Core services, Python capability jobs, JupyterLite or managed Notebook Service | Golden datasets, numerical tolerances, reproducible environment and job observability |
A short compatibility pilot should answer the hardest architectural questions before an organization commits to a full estate move.
Automated crawl plus stakeholder interviews; classify by protocol, data owner, criticality and migration complexity.
Migrate one complex dataset, publish all required endpoints and test real desktop, web, mobile and automation clients.
Automate transforms, validation reports, service configuration, regression tests and environment promotion.
Dual-run, reconcile deltas, switch consumers, monitor service objectives and retain an agreed rollback window.
The exact scope depends on the estate, but a useful pilot should include more than a read-only map.
Domains, GlobalIDs, attachments and related records migrated into the target store.
Wire a representative remote COG through the range-reader and ImageServer registration path, then test export, identify, samples, statistics, pixel parity, signed-URL behavior and failure handling.
Normalized into StreamServer with a geofence or threshold rule and observable downstream alert.
Existing application repointed or a GeoLibre workflow reconstructed against the new endpoints.
TLS, auth, rate limits, CORS, health monitoring, backup/restore and documented runbook.
Once the service layer is open and interoperable, application teams can focus on domain workflows instead of rebuilding storage, tiling, catalog and identity integration for every project.
XLSForm and custom workflows, attachments, GNSS, sync conflict handling, work orders and resilient field packages.
Real-time maps, incident command, mission packages, communications bridges, alerts and after-action review.
I3S/3D Tiles, BIM, point clouds, indoor models, live sensors and analytical overlays combined into task-specific interfaces.
Notebook Service, spatial jobs, GeoAgent tools, data-lake query interfaces and publication back to governed services.
