Roadmap

This is a maintenance release of the 3.1 branch.

  • MapGuide Changes
    • Updated Web Tier components (RFC 165):
      • Apache 2.4.29
      • PHP 5.6.33
      • Tomcat 7.0.85
    • Fixes and other changes:
      • #2754: Fail to stylize layer when expression in symbol definition has invalid value
      • #2750: Isapi mapagent crashes when server error message is too long
      • #2767: Add missing JSON format conversion support for the various mapagent operations
      • #2764: Select Within returns all features when actually no result should be found
      • AJAX Viewer: Zoom selection doesn't work if the select panel is invisible
      • Ignore abstract classes when DescribeSchema? because they should not be visible to consumer.
      • Enable ACE IPv6 support
      • Sanitize user input in various php mapagent test scripts
  • FDO Changes
    • #941 sin(int) expression no longer returns invalid value
    • #912 GDAL/OGR/WMS providers updated to use GDAL 2.2.3
      • You can swap out the GDAL dll with an equivalent custom GDAL build from gisinternals (http://www.gisinternals.com/stable.php). Make sure you are downloading the MSVC 2015 build for this.
      • Updated instructions here
      • Reminder that by using drivers like ECW/MrSID/etc you are bound by their terms of use in their respective licensing agreements.
      • Another reminder that swapping the GDAL dll with a custom one is not supported by us. Use at your own risk/discretion.
    • #937 OGR provider fixes:
      • Better handling/support of VRT data sources
      • Ensure dots in property names are replaced with tildes (~) as dot characters are illegal characters in FDO property names.
      • Better FDO exception error propagation from failed GDAL/OGR API calls within the provider.
      • #912 New GDAL 2.x capabilities are surfaced to their FDO counterparts
        • int64 data types
        • nullable fields
        • default values
    • WFS provider fixes:
      • #915 Features not fully loaded
      • #917 Curve strings properly serialized to their GML counterparts
      • #932 xsd:long values no longer capped at 2147483647 if value is beyond that.
    • WMS provider fixes:
      • #931 Fix SSL connect error if connecting to a WMS server using TLS 1.2
    • PostgreSQL provider fixes:
      • #923 Better handling of check constraint clauses (eg. '10'::integer)
      • #943 Add support for materialized views
    • SHP provider fixes:
      • Fix SHP file cannot be read if it had been opened for writing
    • SQL Server provider fixes:
      • #933 No longer tries to connect to and list every database on the SQL Server, only the ones your login credentials can actually access.
      • #920 Computed columns now properly advertised as read-only properties in the FDO schema
      • (Long standing) patches from Bruno Scott:
        • #875 Date columns not appearing in FDO schemas
        • #766 Use locale-independent date formatting

Milestone: 3.3

Due in 2 months (Jun 30, 2018 6:00:00 PM)

10%

Total number of tickets: 49 - closed: 5 - active: 44

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)
Note: See TracRoadmap for help on using the roadmap.