Opened 14 years ago
Last modified 12 years ago
#171 new enhancement
Database config - Toggle layer merging
| Reported by: | adube | Owned by: | belug |
|---|---|---|---|
| Priority: | major | Milestone: | 1.8.0 |
| Component: | server | Version: | |
| Keywords: | Cc: |
Description
Currently, all resources sharing the same WMS service are automatically merged in a single OpenLayers.Layer.WMS layer. It would be nice if we could deactivate/activate this behavior with an option since not everyone wants this feature.
A new "mergeLayers" MapContext option (boolean) would do the trick.
We also need to decide what should be the default behavior. I'm in favor of leaving the merging option to 'false' by default. Recent tests proved that single WMS layers can be very efficient.
Change History (7)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
| Milestone: | → 1.2.0 |
|---|
comment:5 by , 12 years ago
| Owner: | set to |
|---|
comment:7 by , 12 years ago
| Milestone: | 1.6.0 → 1.8.0 |
|---|
Note:
See TracTickets
for help on using tickets.
http://trac.osgeo.org/geoprisma/ticket/172#comment:2
The PGSQLMapContextConfig driver now use the MapPanel and Layer widgets instead of the Map widget, which don't support layer merging yet. This should be considered. Layer merging would be done on xslt side.