Version 1 (modified by 13 years ago) ( diff ) | ,
---|
MapGuide 2.4 Release Notes
MapGuide Open Source 2.4 Preview Release is now available!
- Release wiki: Release/2.4
- Milestone: 2.4
- Resolved Tickets
Installation
Binaries for Windows have been posted to OSGeo
Windows 32 bit installer:
Windows 64 bit installer:
Additional Post Release Patches
N/A
Major New Items
- A new service for profiling performance (RFC 110)
- Web Tier directories now include SVN metadata, allowing for the pulling of viewer updates and fixes instantly with a subversion client (RFC 111)
- Path scaling support in Symbol Definitions (RFC 113)
- New Feature Service API for save points RFC 114
- Improved Coordinate System conversion performance (RFC 116)
- IPv6 support (RFC 118)
- Support for enhanced URL information in Layer Definitions (RFC 119)
- Configurable Coordinate System dictonary paths via serverconfig.ini and webconfig.ini (RFC 122)
- Feature Join performance optimizations (RFC 123 and http://themapguyde.blogspot.com.au/2011/12/improving-feature-join-experience-or.html)
- Toggle-able tooltips for AJAX and Fusion viewers (RFC 120)
- Lots of performance and usability improvements in Fusion (see this link for an overview)
Also included are features from the (cancelled) 2.3 milestone
- Datum Transformation enhancements (RFC 94)
- WMS 1.3.0 support (RFC 95)
- QuickPlot command for AJAX and Fusion viewers (RFC 96)
- EPSG/SRID code changes (RFC 98)
- WFS 1.1.0 support (RFC 106)
- Watermark support (RFC 108)
Thanks to the ever growing team of developers who are contributing to make the MapGuide Open Source project a more self-sustaining project.
Please report any defects.
Compatibility
MGOS 2.4.0 is compatible with FDO 3.7.0.
FDO
FDO is compiled against the Oracle 11.2 instant client available from Instant Client Downloads. For a Linux installation, the Oracle shared library path should be included in LD_LIBRARY_PATH or ldconfig.
Installer notes
Please observe the updated software requirements if you are using .net and/or IIS configuration:
- IIS (all versions) require FastCGI to be installed. See this link for more information
- The supported .net Framework version for the MapGuide .net API is 4.0
- For IIS6 and below, the installer will still set the ASP.net version to 2.0.50727. You will have to manually change the ASP.net version to 4.0.30319 post-install
To assist new MapGuide users and developers, the installer also now bundles the following optional components:
- .net/PHP/Java viewer samples
- MapGuide Developer's Guide in HTML format with updated content
- .net/PHP/Java Developer's Guide Samples
All bundled samples require the Sheboygan dataset to be loaded into the MapGuide Server. For Developer's Guide samples, the developer's guide data package needs to be loaded. These can be found in the root directories of the respective devguide samples in your MapGuide Web Tier installation.
Finally, due to coordinate system dictionary paths no longer tied to a global environment variable (RFC 122) a mandatory system reboot after installation is no longer required for all supported versions of Windows. However, a restart of Apache and/or IIS may be required for PHP to work.
API changes
RFC 110 A new API for rendering performance profiling
RFC 114 A new API for transaction save points
New Server Configuration (serverconfig.ini) Options
RFC 122 introduces the MentorDictionaryPath configuration property, which is the first place MapGuide Server will look for the coordinate system dictionary files. The MENTOR_DICTIONARY_PATH environment variable will be used instead if the specified path in serverconfig.ini does not exist
New Web Configuration (webconfig.ini) Options
RFC 122 introduces the MentorDictionaryPath configuration property, which is the first place the MapGuide Web Tier will look for the coordinate system dictionary files. The MENTOR_DICTIONARY_PATH environment variable will be used instead if the specified path in webconfig.ini does not exist
Disk Space
The installer requires at least 1.5GB of disk space on C: during installation. Otherwise installation may not proceed.
If you do not have sufficient space on C:, you can open the installer file with 7-zip and extract the contents to another drive, and run the extracted setup.exe from there. It may also be helpful to set your TEMP environment variable to a different drive.