Default or XYZ tile set
Writes the Tile Set Definition (provider, format, extent, meta-tiling, TileExtentOffset), validates it against the 3.0.0 schema and separates the stable base from what should stay dynamic.
Octo for tiles, WMS, WFS and printing in MapGuide
The map comes out of the server. What goes public is your call.
In MapGuide Open Source 4.0, released on Oct 12, 2025, XYZ tiles, WMS, WFS, KML and plots come out of the same server and can be prepared and checked from the command line. Octo writes the tile set, seeds it with MgTileSeeder, measures the cache by content, audits what is published and prints sheets in batch. What goes public, when to clear the cache and what counts as a document of record stay with the administrator and the technical lead.
MapGuide Open Source4.0released Oct 12, 2025, LGPL 2.1
MgCooker dropped from Maestro2022MgTileSeeder is the replacement since 6.0m11
OGC servicesWMS 1.3.0and WFS 1.1.0, on the same mapagent
Sources11listed at the end of the page
01
What Octo does with tiles, OGC and printing.
Six possible deliverables, drawn from the assessment. All of them start by reading the server without changing anything, and all of them go to the administrator before reaching production.
Seeding with failures logged
Runs MgTileSeeder in xyz or mapguide mode with a failures file and retries only what failed with xyz_replay, outside peak hours.
Cache measured by content
Reads the z/x/y folder of the XYZ cache, compares it with what the extent requires and flags incomplete zooms, tiles outside the area and tiles suspected to be empty.
WMS and WFS audit
Reads the GetCapabilities, tests one GetMap and one GetFeature per layer and cross-checks with each resource's _IsPublished metadata, to show what is public and whether it responds.
KML for Google Earth users
Generates KML for a map, layer or features with GETMAPKML, GETLAYERKML and GETFEATURESKML, checking the file before delivering.
Batch printing
Draws the index map and requests one sheet per request, as PDF through mapguide-rest or as DWF through GETPLOT, checking the signature, size and hash of each file.
02
Eight arms, one map checked before it ships.
The same Octo cycle, applied to map delivery. Each arm has a narrow role; the people decide what is public, when to touch production and what counts as a document of record.
-
Discovery
Surveys what the server delivers
MapGuide version, tile providers, tile sets and maps with tile groups, layers in WMS and WFS, installed extensions.
-
Data
Separates stable from dynamic
Where each layer comes from, how often it changes, what CRS it is in and up to which zoom the data's accuracy holds.
-
Security
Looks at what is exposed
Layers published in WMS and WFS, queryable attributes, personal data (LGPD) and the server version against the 4.0 security fixes.
-
Architecture
Chooses the path
Default or XYZ tile set; maximum zoom; serve static or through mapagent; printing through
GETPLOTor mapguide-rest. -
Development
Writes the resource and the script
Tile set XML, seeding with failures logged, OGC audit and batch printing, with dry-run mode and the source of each parameter noted.
-
Review
Checks by content
Tile MIME type, GetMap image, GetFeature GML, PDF signature, cache coverage. A 200 status is not a check.
-
Release
Only with your OK
Production seeding, cache clearing and publishing changes happen in the agreed window and with the administrator's approval.
-
Documentation
Records what was delivered
Tile sets, seeded zooms, date of the last clear, public layers and who approved each one, so the next person doesn't have to rediscover it.
Octo works with read access and in a support role. It does not decide what is public, clear the cache or change configuration without approval, or sign a printed sheet.
03
Each task, its own path.
The criteria Octo uses to choose, with the documentation and code for the installed version.
| Task | Path | Note |
|---|---|---|
| Create an XYZ tile set | Tile Set Definition XML + SETRESOURCE | Validate against TileSetDefinition-3.0.0.xsd |
| Find the server's providers | OPERATION=GETTILEPROVIDERS | Default and XYZ, with parameters |
| Test a tile | GETTILEIMAGE version 1.2.0 | No session; errors come back as XML, so check the type |
| Seed | MgTileSeeder xyz or mapguide | Always with --failed-requests; bbox in lon/lat |
| Retry failures | MgTileSeeder xyz_replay --tile-list | Once; whatever fails again gets investigated |
| Clear the cache | OPERATION=CLEARTILECACHE | Deletes everything for the resource; only with approval |
| Audit WMS and WFS | GetCapabilities + test GetMap and GetFeature | Read-only |
| Publish a layer to WMS | _IsPublished metadata in the resource header | Administrator's decision |
| Export KML | GETMAPKML, GETLAYERKML, GETFEATURESKML | Check the FORMAT values on the server |
| Print DWF | OPERATION=GETPLOT | With a PrintLayout, if there is one |
| Batch-print PDF | mapguide-rest plot.pdf | Separate extension; installing it is the administrator's decision |
04
From one-off seeding to a cache that maintains itself.
Three steps. Each one only makes sense after the previous one has shown results on your team.
A proposal, not a promise
Inventory of what goes out
Octo shows what the server delivers in tiles, WMS, WFS and KML, without touching anything.
- Existing tile sets, groups and zooms
- Public layers and whether they respond
- List of questions for the administrator
Cache and batch printing
XYZ tile set seeded and measured, and sheets printed from an index map, each file checked.
- Cache with coverage by zoom
- Report of failures and empty tiles
- Sheets with a check report
Maintenance routine
When data changes, that part of the cache is rebuilt and publishing is checked again, with a record.
- Reseeding by changed area
- Periodic OGC audit
- History of what was published and by whom
05
Confirmed in a source.
Every point below has a source published by OSGeo (project page, official mailing lists, downloads area), by the official repository or by Autodesk. The examples are scripts, not executions. The sources are in the next section.
4
points with a published source, each with its reference shown alongside.
- ConfirmedMapGuide Open Source 4.0
- Final release announced on Oct 12, 2025, after RC1 on Sep 10, 2025; the first major stable release since 3.1.2.Source: mapguide-users list, October 2025
- ConfirmedMVT removed, WMS and WFS fixed
- 4.0 Beta 2 lists "#2880: Removed immature MVT tile rendering support" and "#2878: Buffer overflow fixes in WMS/WFS service layer".Source: mapguide-users list, Aug 14, 2024
- ConfirmedMgCooker replaced
- Maestro 6.0m11 (Aug 3, 2022) removed MgCooker; MgTileSeeder, with
xyzandmapguidemodes and failure retries, is the replacement.Source: mapguide-maestro releases and Program.cs - ConfirmedXYZ cache layout
base/group/z/x/y.format, with PNG, PNG8, JPG, GIF and UTFGRID; in the mapagent URL template,TILECOL={y}andTILEROW={x}.Source: Git mirror of the code (through Jan 2023) and the maintainer's blog
06
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 checkYour 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 signerThe 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
07
Sources.
Project announcements, source code, the Maestro and mapguide-rest repositories and the maintainer's blog, consulted on Oct 31, 2026.
- MapGuide Open Source 4.0 announcementOct 12, 2025
- 4.0 Beta 2 announcementMVT removed, WMS/WFS fixes
- OSGeo, MapGuide Open SourceLGPL 2.1 license, WMS and WFS
- Supercharged tile setsXYZ, retina, UTFGrid, meta-tiling
- An introduction to MgTileSeederXYZ URL template
- MapGuide Maestro, releases6.0m11: MgCooker removed
- MgTileSeeder, optionsxyz, mapguide, replay
- Tile Set Definition schemaGit mirror of the code
- mapagent operationsTiles, KML, plotting
- WMS configurationVersions, formats, CRS
- mapguide-rest, routesXYZ, KML, plot.pdf
Your map server, checked by what it delivers.
The assessment starts with an inventory of what the server publishes in tiles, WMS, WFS and KML, without touching anything. You get the list of what is exposed, what is out of date and the decisions only your team makes, and you decide with it in hand.