Roadmap

The goal of the RAMP technical roadmap is to provide a glimpse of what is planned for the future of RAMP from both a short and long term perspective.

By providing this information, we hope to provide some predictability on where RAMP will focus its development efforts and provide context to help elicit feedback and suggestions from users of RAMP.

Short Term

The short term technical goals for RAMP are organized into planned releases that have already been assigned a product name, as well as have a high level scope defined.

Release Activities Planned Release Date
Dragonfly v4.0
  • RAMP Configuration Service (RCS)
    • Platform neutral Python/NoSQL based REST Services
    • Dynamic map configuration
    • Dynamic registration of map layers and with JSON payloads for capturing layer metadata
  • Support for non-Simple layer symbology including class breaks and unique value rendering methods
  • Support for complex layer legends based on configuration, or extracted dynamically from Feature Service defintions (performed by RCS)
  • Migration to WET 4.0 support - Intranet, Web Usability and Canada.ca themes
 Nov. 2014
Elk v5.0
  • Export maps as images (PNG/JPG)
  • Support visualization of layers added by user
    • File Based CSV/GeoJSON
    • Service Based (REST Feature Services, WMS)
  • Improved handling of Feature Service Zoom Scale Dependencies
  • RAMP Configuration Service (RCS)
    • Ability to authenticate requests
    • Allow caching/updating of layer extents
  • Accessibility/Usability improvements
  • Auto-hyperlinking of URLs in datagrids/panels
 Jan. 2015

Long Term

RAMP maintains a backlog of product features and activities that are drawn from to form the scope of future releases. The following table is a high level summary of this requirement backlog. Note: The backlog is not confined to specific functional requirements, but also addresses quality initiatives, process improvement, etc.

Release History

Please refer to the Version History page.

Date modified: