Roadmap

Milestone: 3.1.2

11 hours late (Oct 20, 2018 12:00:00 AM)

MapGuide Changes

FDO Changes

  • OGR Provider enhancements/fixes
    • #953: Support for customizing the name of the default schema (instead of OGRSchema)
    • #455, #66: New optional DataSourceEncoding connection property to better support UTF-8 data sources.
    • #952: Cleaned up connect error message
    • #954, #955: Various fixes on improving provider correctness in behaviour (eg. Throwing on bad/invalid property names)

Milestone: 3.3

Due in 2 months (Dec 20, 2018 6:00:00 PM)

13%

Total number of tickets: 52 - closed: 7 - active: 45

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)

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.