Source and provider inventory
Asks the server which providers are installed (GETFEATUREPROVIDERS), lists the repository's FeatureSources and reads the provider, parameters, extensions and joins of each one.
Octo for FDO data sources in MapGuide
Every layer starts with a connection. Who decides what it exposes is you.
In MapGuide Open Source 4.0, every map reads data through an FDO provider: PostGIS, SQL Server, Oracle, OGR, GDAL, SHP, SDF, SQLite, WMS, WFS. Octo reads the repository's providers and sources through the mapagent API, finds plaintext passwords and broken connections, moves files into the database with a checked count, and measures filters and joins instead of assuming. Swapping a source in production, creating database objects and publishing personal data stay with the administrator, the DBA and the technical lead.
MapGuide Open Source4.0announced Oct 12, 2025, LGPL 2.1
FDO in the 4.0 installer4.2FDO_VERSION=4.2.0.0, bundled GDAL 2.4.4
Providers in the Windows installer133 disabled by default (ArcSDE, King Oracle, MySQL)
Sources15listed at the end of the page
01
What Octo does with FDO sources.
Six possible deliverables, drawn from the assessment. All of them start with a read-only account, record the version of MapGuide, FDO and each provider, and go to review by whoever is accountable for the server and the data.
Plaintext passwords and separate credentials
Flags any FeatureSource with Password filled in the XML and proposes %MG_USERNAME%/%MG_PASSWORD% with the credential stored separately (MG_USER_CREDENTIALS), never copying the password.
Batch connection test
TESTCONNECTION on every source, off-peak, with the result cross-referenced against the layers and maps that depend on each one.
Files into the database
Moves SHP and SDF into PostGIS with ogr2ogr, a spatial index and source and target counts, and prepares the new OSGeo.PostgreSQL FeatureSource in staging.
Measured join
Finds AttributeRelate with ForceOneToOne hiding a 1:N, measures the layer's time and proposes a database view when the DBA agrees.
Filters the provider accepts
Cross-checks GETPROVIDERCAPABILITIES against the layers' filters and expressions, and tests LIKE, IN, NULL, INTERSECTS and WITHINDISTANCE through mapagent.
02
Eight arms, one checked connection.
The same Octo cycle, applied to MapGuide data sources. Each arm has a narrow role; the people swap sources in production, create database objects and decide what is published.
-
Discovery
Maps what already exists
Server providers and versions, the repository's FeatureSources and the layers and maps that depend on each one.
-
Data
Reads schemas and keys
Classes, identity keys, spatial context and join cardinality; points out the 1:N hidden by
ForceOneToOne. -
Security
Handles access and data
Plaintext passwords in the XML, database accounts with too much privilege and personal data in public layers. Read-only account throughout the assessment.
-
Architecture
Chooses the path
Native provider or OGR; database view or
AttributeRelate; file on the network share or PostGIS; what goes into the connection pool and what doesn't. -
Development
Writes the script
Python, shell and SQL with a log, read-only by default, passwords kept off the command line and the source of every syntax noted in the file.
-
Review
Checks by the numbers
Feature count through mapagent, map window timing and the query plan in the database. No error is not the same as checked.
-
Release
Delivers in staging
Only with your OK, it prepares the new FeatureSource in
Session://or in a staging folder. A person makes the swap in productionLibrary://. -
Documentation
Records what holds on your server
MapGuide, FDO and provider versions, parameters without passwords, tested filters, measured timings and who approved each swap.
Octo works with read access and in a support role. It does not swap sources in production, create database accounts or objects without the DBA, change serverconfig.ini without the administrator, or decide what can be published.
03
Each task, its own path.
The criteria Octo uses to choose, with the code and documentation for the installed version.
| Task | Path | Note |
|---|---|---|
| Find out what the server reads | GETFEATUREPROVIDERS, GETPROVIDERCAPABILITIES | Nothing is changed |
| List and read the sources | ENUMERATERESOURCES + GETRESOURCECONTENT | Password masked in the output |
| Test connections | TESTCONNECTION | At an agreed time |
| View schema and classes | DESCRIBEFEATURESCHEMA, GETCLASSES, GETSPATIALCONTEXTS | Spatial context of each source |
| Count and query features | SELECTAGGREGATES, SELECTFEATURES with FILTER | Operators depend on the provider |
| Write features | Web API (PHP, Java, .NET) | Not exposed by mapagent |
| Store credentials | %MG_USERNAME%/%MG_PASSWORD% + MG_USER_CREDENTIALS | Password outside the XML |
| File into the database | ogr2ogr + GIST index + count | Workstation GDAL ≠ FDO's GDAL 2.4.4 |
| Join across sources | Database view, when the DBA agrees | UseFdoJoinOptimization only applies within the same source |
| Tune pool and cache | [FeatureServiceProperties] in serverconfig.ini | Applies to the whole server |
04
From inventory to your own standard.
Three steps. Each one only makes sense after the previous one has shown results on your team.
A proposal, not a promise
Inventory and findings
Octo shows what the server reads, what is broken and where passwords are exposed, without touching anything.
- Spreadsheet of sources by provider
- Tested connections and affected layers
- List of security findings
Migration and measured joins
Files moved into the database with a checked count, and slow joins compared with views, always in staging.
- Staging schema with a report
- New FeatureSources with separate credentials
- Filter test suite with timings
Your own source standard
Approved FeatureSource templates per provider, automatic checks on every new resource and connection monitoring.
- FeatureSource template per database
- Plaintext password check on every publish
- Daily connection test with alerts
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 4.0 and FDO 4.2
- MapGuide Open Source 4.0 was announced on Oct 12, 2025; the 4.0 branch installer declares FDO_VERSION=4.2.0.0. Both are LGPL 2.1.Source: mapguide-internals list; MapGuide.wxs and License.txt in the OSGeo SVN
- ConfirmedInstaller providers
- Thirteen providers registered on Windows; ArcSDE, King Oracle and MySQL disabled by default because they require external libraries. The Linux build script does not build ArcSDE.Source: MapGuide.wxs (4.0 branch); build_fdo.sh:190 ("We never build ArcSDE provider")
- ConfirmedCredentials outside the XML
- The code defines %MG_USERNAME%, %MG_PASSWORD% and the MG_USER_CREDENTIALS resource data, which replaces the placeholders with the stored credential.Source: ResourceDefs.cpp (4.0 branch); Web API reference, SetResourceData
- ConfirmedFDO filters and joins
- Null is "property NULL" (no IS); INTERSECTS, ENVELOPEINTERSECTS, WITHINDISTANCE and GEOMFROMTEXT are available. ForceOneToOne forces 1:1 on a 1:N relationship.Source: yyFilter.y; FeatureSource-1.0.0.xsd
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.
MapGuide and FDO code in the OSGeo SVN and the GitHub mirror, OSGeo mailing lists and GDAL and PostgreSQL documentation used in the assessment, consulted on Oct 31, 2026.
- MapGuide 4.0 announcementmapguide-internals list, Oct 12, 2025
- 4.0 Beta 2 announcementmapguide-users list, Aug 14, 2024: providers, GDAL 2.4.4, PostgreSQL 12 to 16
- Building FDO on Linuxbuild_fdo.sh, 4.0 branch: ArcSDE not built
- MapGuide 4.0 installerFDO 4.2.0.0 and providers
- MapGuide licenseLGPL 2.1
- FDO licenseLGPL 2.1
- FDO SVN, 4.2 branchOfficial repository
- ResourceDefs.cpp%MG_USERNAME%, MG_USER_CREDENTIALS
- PostgreSQL providerConnection parameters
- FeatureSource-1.0.0.xsdExtensions and joins
- serverconfig.iniPool, cache and joins
- mapagent operationsNames and parameters
- FDO filter grammarSupported operators
- Developer's Guide 3.1.2Filters and queries
- GDAL, PostgreSQL driverLoading with ogr2ogr
Your data sources, checked one by one.
The assessment starts with an inventory of your MapGuide's sources and a connection test, using a read-only account, without touching anything. You get the list of what is broken, what is exposed and how to check it, and you decide with it in hand.