Sara Makarenko wrote:
> Asking for your feedback. If you could take MapGuide in any direction you want for the next release, what would it be?
Hi Sara. Here goes:
- Better support for unmanaged data sets!!!
- Support for dynamic KML with implementation as good or better than
GeoServer.
- Focus on speed and stability.
- Active Directory and LDAP integration
- A more flexible, templatable front end. Better yet, adopt one of the
existing Open Source web mapping toolkits such as Chameleon or
MapBuilder as MapGuide's official front end. This would annoy existing
developers to no end, but hey, you asked 🙂
- Full support for important OGC standards such as WFS-T and SLD.
- A full metadata storage and retreival service/front end that supports
important relevant standards such as Z39.50 search, FGDC & ISO 19115
(TC211) metadata, and OGC Catalogue Services. Population of this should
be integrated into the Studio load procedures, and the metadata for all
of the layers in any specific map should be should be readily available
from the map legend and from the API so that a custom metadata index
listing could be developed. Addition of information around unmanaged
data sets should also be permitted. Contact information, Locations,
Departments, Organisations, etc should all be normalized in the metadata
store rather than stored independantly for each dataset.
- GeoRSS support:
- Ability to define GeoRSS URLs as data sources.
- Ability to publish data sources as GeoRSS feeds (would need date
column, number of latest entries to publish, expression builder for
title and contents, etc...)
- Collaboration tools:
- sharing of current map state with other users
- redlining/markup tools that allow markup sessions to be stored to
the server, shared with other users (fine-grained authorization) and
saved out as DWF and SDF.
- integration with an open IM tool for spatial-enabled chat while
redlining
- Projection of rasters on the fly. Better projection support for WMS.
- Enhanced server-to-server communication. Binary WFS??? Something to
take the place of the client side multi-site capabilities of MG 6.5.
- A cool "history" tool, with thumbnails of recent map states, allowing
the user easy access to previous views.
- A layer between Layouts and Maps, allowing many maps to be integrated
into a single layout, with a drop-down list allowing choice between
them. This layout->map lookup layer should maintain for each map:
- Theme name
- Map resource
- Reset or maintain current extents
- Active tools
... want more? 🙂
Jason