Skip to content
Octo × MapGuide PT Request an assessment

Octo × MapGuide · survey of Oct 31, 2026

The map server that is still alive, checked at every step.

MapGuide Open Source 4.0, released in October 2025. Reproducible installation, mapagent API calls with curl and Python, XML resources generated and validated in batch, FDO connections to spatial databases, tiles seeded off-hours, WMS and WFS, updated viewers and moving off an old AIMS. Octo reads the server, writes the script, runs it on a copy and shows the generated map and the numbers. Changes in production stay with the server administrator.

See the pages Request an assessment
The Octo octopus over a web map served by MapGuide Browser window with a fictitious web map viewer: tile grid, parcels, river, roads, public facilities, layer panel and a status bar with scale and coordinates. Over the map, an octopus stretches out eight arms, each labeled with one of Octo's arms: Discovery, Data, Security, Architecture, Development, Review, Release and Documentation. All data is fictitious. https://mapas.exemplo/mapguide/fusion/ · fictitious LAYERS Parcels Hydrography Roads Facilities Orthophoto SCALE 1:5,000 · X 512,340 Y 7,462,180 · FICTITIOUS COORDINATES Discovery Data Security Architecture Development Review Release Documentation
Illustration: Octo's eight arms over a web map served by MapGuide, fictitious data
Tracks8one page per track of the work
Confirmed31points with a published source across the eight pages
Sources101references listed at the end of the eight pages
01

Octo working with MapGuide.

One task from request to approval, at a fictitious company. The arms measure, plan and execute; whoever is in charge checks and approves. Each tab is one track of the field and links to its page.

Octo · task #981 · Saneclaro Saneamento (fictional company)

Track pageServer and installation →mapagent API →AIMS and migration →

Simulation with a made-up company and names. The standards, versions and software cited come from the field's pages, each with its own sources.
02

Not discontinued.

What Autodesk stopped developing was its own commercial product, AIMS. MapGuide Open Source had a major release in October 2025, continues under OSGeo with the LGPL 2.1 license and has an active user list in 2026.

4.0

MapGuide Open Source 4.0, announced on Oct 12, 2025 on the OSGeo lists, six and a half years after 3.1.2, according to the maintainer's post of Oct 12, 2025 ("6 years, 6 months and 14 days"). Final build: 4.0.0.10202. RC1 had shipped on Sep 10, 2025.

Version and date
MapGuide Open Source 4.0, announcement of Oct 12, 2025 signed by the maintainer, with notes and downloads on the project Trac.lists.osgeo.org · mapguide-announce
Maintainer and license
Project listed by OSGeo (community projects, Web Mapping), LGPL 2.1 license, deployment on Windows or Linux, APIs in .NET, Java and PHP, WMS and WFS.osgeo.org · MapGuide Open Source
Activity in 2026
Messages on the mapguide-users list from June to October 2026; users ask about 4.0.1, which the maintainer planned for November 2026; not yet released as of Oct 30, 2026; in October, discussion about updating the bundled PHP 8.3.lists.osgeo.org · mapguide-users, October 2026
php2shell and 4.0.1
On Oct 22, 2026 the maintainer published how to mitigate the PHP php2shell flaw on a 4.0 installation and wrote that earlier versions have no fix: "the only recourse is to upgrade to 4.0". On Oct 23, 2026 he announced the 4.0.1 plan, with PHP 8.3.36 or newer: 4.0.1-Test expected in early November and the final at the end of November 2026. It is a plan, not a release.themapguyde.blogspot.com · php2shell and MapGuidemapguide-users · mitigation, Oct 22, 2026mapguide-users · 4.0.1, Oct 23, 2026
Ecosystem
MapGuide Maestro 6.0m13 and mapguide-react-layout v0.14.10 (MIT), both from Jan 15, 2025, with repositories updated in October 2026.GitHub · mapguide-maestro
03

One page per track.

What MapGuide offers, how it is automated through the command line, scripts or the API, where Octo can help and what has not yet been confirmed in a source.

Layers from different FDO sources stacked into one map Four layers of a fictitious map drawn as sheets stacked in perspective, each coming from a different data source through an FDO provider: orthophoto via GDAL, roads via SQL Server, hydrography via shapefile and parcels via PostGIS. On the right, the resulting map with the four layers overlaid and the map definition that brings them together. Fictitious data. Parcels · PostgreSQL/PostGIS provider Hydrography · SHP provider Roads · SQL Server Spatial provider Orthophoto · GDAL provider Base.MapDefinition Library://Exemplo/ Lotes.Layer Hidro.Layer Vias.Layer Orto.Layer 4 FeatureSources 4 FDO providers 1 coord. system references checked FICTITIOUS RESOURCE NAMES AND DATA
Illustration: layers from four FDO sources brought together in a map definition, fictitious data

Server and installation

MapGuide Open Source 4.0 on Linux and Windows, configuration files, services, logs, repository backup and upgrades from 3.x and 2.x. Octo can inventory the installation and build a reproducible installation and upgrade script.

Reproducible installation12 published sources
Open the page →

mapagent API

The server's HTTP operations: map image, session map, tiles, feature queries, listing and writing resources. Octo can write service tests with curl and Python that check the image and the content of the response, not just the HTTP code.

Service tests14 published sources
Open the page →

Resource repository

Library:// and Session://, the source, layer, map and layout XML, XSD schemas and .mgp packages. Octo can generate dozens of layers from a template and validate each XML against the schema before writing.

Batch XML12 published sources
Open the page →

FDO data sources

Providers for PostGIS, SQL Server, Oracle, OGR, GDAL, SHP, SDF, SQLite, WMS and WFS, FDO filters and expressions, joins and performance. Octo can test each connection, read the schema and point out the slow layer before anyone publishes it.

Connection tests15 published sources
Open the page →

Maestro and automation

MapGuide Maestro, MgTileSeeder (which replaced MgCooker in 6.0m11), the Maestro API in .NET and scripts for bulk migration and maintenance. Octo can repoint a hundred layers' connections at once, on a copy, and show the diff of each XML before writing.

Bulk maintenance12 published sources
Open the page →

Tiles and OGC

Default and XYZ tile sets, caching and seeding, WMS and WFS published by the server, KML, printing and plotting to DWF and PDF. Octo can seed the cache off-hours and check a sample of tiles at each scale.

Seeded cache11 published sources
Open the page →

Web applications

MapGuide Web API in PHP, Java and .NET, Fusion, the AJAX viewer, mapguide-react-layout, OpenLayers and Leaflet, authentication and security. Octo can find the pages that depend on an old viewer and propose the swap, screen by screen.

Viewer swap13 published sources
Open the page →

AIMS and migration

Autodesk Infrastructure Map Server and MapGuide Enterprise, Infrastructure Studio, migration to Open Source 4.0, inventory, risks and alternatives. Octo can inventory the old server and test the resources on a 4.0 staging server before any decision.

Inventory before migration12 published sources
Open the page →
04

What it's like to use.

You ask in plain language, the way you would ask an infrastructure colleague: “list every layer that still points to the old database” or “seed the basemap tiles down to 1:2,000 overnight”. Octo reads the server, proposes, runs it on a copy and shows the map and the numbers.

Path of a request on a MapGuide server Left-to-right diagram: data sources (spatial database, files and raster) connected through FDO to the MapGuide server, which stores resources in the Library and Session repository; the server responds to the web tier, where mapagent and the Web API live; on the right, the clients: Fusion, AJAX and mapguide-react-layout viewers, OpenLayers and Leaflet, WMS and WFS clients and scripts with curl and Python. Below, a fictitious mini map as the returned image. Fictitious server names and data. PostGIS SHP · SDF GDAL raster FDO MapGuide Server resource service feature service mapping · rendering tiles · KML · drawing Library:// Session:// XML Web tier Apache or IIS mapagent Web API PHP · Java · .NET WMS · WFS Fusion · AJAXreact-layout OpenLayersLeaflet · GIS curl · Pythonscripts and tests GETMAPIMAGE → PNG QUERYMAPFEATURES → XML SIMPLIFIED DIAGRAM · FICTITIOUS NAMES
Illustration: sources, FDO, server, mapagent and clients of a MapGuide setup, fictitious data
01 To get started

Read access to the server

A read-only mapagent account or an exported .mgp package. The production Library:// is never changed without approval.

02 For scripts

Linux or Windows with curl and Python

HTTP calls and XML need nothing more than an ordinary machine. The Maestro API needs .NET; the Web API needs PHP, Java or .NET on the server.

03 To make changes

Staging and approval

A 4.0 staging server or the Session:// repository for dry runs. Writes to production only through the routine approved by the administrator.

Nothing changed at the start
05

Eight arms, one server.

The same Octo cycle, applied to a map server. Each arm has a narrow role; the people decide what goes to production, who can see each layer and what data is published.

  1. Discovery

    Maps what already exists

    Server version, configuration files, repository resources, FDO connections, viewers, the pages that depend on them and old scripts.

  2. Data

    Pins down the references

    Which source feeds each layer, coordinate system, scales, feature keys and which database is production and which is a copy.

  3. Security

    Handles access

    Repository accounts and permissions, passwords out of scripts, bundled PHP and components kept up to date, exposed services and personal data in layers.

  4. Architecture

    Chooses the path

    mapagent with curl or the Web API; generated XML or the Maestro API; default or XYZ tile set; upgrade in place or migrate to a new server.

  5. Development

    Writes the script

    Bash, Python, PHP or C#, with a log, exit code, dry run in Session:// or in staging and the source of every operation noted.

  6. Review

    Checks by the map

    Compares the generated image and the query response against a known case. Checks by content, not by the 200 code.

  7. Release

    Delivers for staging

    Only with your OK, it loads the package onto the staging server. Writing to production is done or approved by the administrator.

  8. Documentation

    Leaves a record

    Script, inventory, XML diffs, versions, sources and what was decided are written down for the server's next upgrade.

Tile pyramid of a fictitious basemap Three levels of a tile pyramid drawn in perspective: at the top, one tile at 1:50,000; in the middle, four tiles at 1:12,500; at the bottom, sixteen tiles at 1:3,125, some already seeded in the cache and others pending. On the right, the panel of an off-hours seeding run with the tile count per scale and the checked sample. Fictitious scales, counts and names. 1:50,000 · 1 tile 1:12,500 · 4 tiles 1:3,125 · 16 tiles seeding · 02:00 Base · Background group scale 0 … 1/1 scale 1 … 4/4 scale 2 … 6/16 sample checked 3 tiles per scale publishing: administrator FICTITIOUS SCALES AND COUNTS · EACH LEVEL SPLITS THE PREVIOUS ONE INTO FOUR
Illustration: three-scale tile pyramid and cache seeding, fictitious data
06

What this page is, and what it isn't.

Only what has a published source goes into the field's pages: every point carries its reference, and every page ends with its list of sources.

31

points with a published source across the field's eight pages, each with its reference on the page itself.

Illustrations with fictitious data
Maps, screens and diagrams are original SVG drawings. Coordinates, names of places, resources and servers, and values do not correspond to real places or systems.Caption "Illustration: ... fictitious data" on each one
Versions and status
Product version, date, license and status appear only with a source and a date.Sources at the end of each page
07

What Octo does and what stays with you.

Octo prepares everything, but it does not sign. The document of record stays with whoever is accountable for it.

Octo prepares

Gathers, calculates, organizes and generates the documents: scripts, inventories, reports and maps.

Deliverable: material ready to check

Your team checks

The licensed professional checks what Octo delivered before signing. If something doesn't add up, it goes back to Octo with the correction.

Step: review by the signer

The signer

Octo does not sign. Designs, technical reports, ART/RRT, accountability reports and any official document are still signed by the licensed professional of the company or agency: here, the technical lead for the map or system.

Signature: technical lead for the map or system
08

Sources.

Primary sources, consulted on Oct 31, 2026. Each page of the field ends with its full list.

What is holding back your map server?

The assessment starts by reading the server or a resource package your team already has, without changing anything. You get the inventory and a map of what can be automated or migrated, with a dry run on a known case, and you decide with it in hand.

Request an assessment