Implemented Features

  • Support for creating MgMap instances with initial display parameters (RFC 157)
  • GeoJSON support
    • Format support in mapagent responses that return feature/geometry data (RFC 158)
    • Format support in WFS GetFeature responses and WMS GetFeatureInfo responses (RFC 163)
  • UTFGrid support for Tile Set Definitions using the XYZ tile access scheme (RFC 159)
  • New mgserver command-line capabilities to better support containerization and automated provisioning scenarios (RFC 160)
    • Package loading mgserver loadpackage
    • Setting passwords for built-in users mgserver setpwd
  • New Geometry APIs
    • Support for geometry simplification (RFC 153)
    • Support for prepared geometries (RFC 161)
    • Support for tessellating (approximating) curve-based geometries (RFC 161)
  • mapagent enhancements:
    • mapagent support for simplified and correct (with respect to schema) JSON responses (RFC 158)
    • Operations that return feature/geometry data have option for GeoJSON output (RFC 158)
    • New Geo-Processing services to bring up to feature parity with geometry APIs already available in the MapGuide Web API (RFC 161)
    • Support for batch transforming coordinates and re-projecting any response that returns feature/geometry data (RFC 162)
  • Support for building MapGuide on Linux with CMake instead of autotools (RFC 164)
  • Tile Set Definition support for meta-tiling and additional tile rendering parameters (RFC 170)


  • This milestone will no longer provide builds for 32-bit Windows (RFC 166)
  • C++11 has been adopted as the C++ standard language version for the MapGuide codebase (RFC 172)

Features in the pipeline (with strong possibility of inclusion)

  • New replacement managed API bindings generated via vanilla and un-modified SWIG
    • MapGuideDotNetApi supporting .net core and full framework
    • Java wrapper API targeting JDK 7 and higher
    • PHP wrapper targeting PHP 7.x
Note: See TracRoadmap for help on using the roadmap.