Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Layer opacity setting in Leaflet #2063

Closed
tdipisa opened this issue Jul 24, 2017 · 0 comments · Fixed by #2064
Closed

Layer opacity setting in Leaflet #2063

tdipisa opened this issue Jul 24, 2017 · 0 comments · Fixed by #2064

Comments

@tdipisa
Copy link
Member

tdipisa commented Jul 24, 2017

Using Leaflet each layer opacity changes from layer settings produce a new WMS request with the OPACITY parameter. This must be avoided.

Steps to reproduce:

  • open a map using Leaflet
  • add a WMS layer or use an existing one in TOC
  • open the layer properties tool and change the opacity, then check the performed requests using
    firebug or the chrome dev tool
@tdipisa tdipisa added this to the 2017.05.00 (Catalog Review) milestone Jul 24, 2017
@tdipisa tdipisa changed the title Layer opacity in leaflet Layer opacity setting in Leaflet Jul 24, 2017
@offtherailz offtherailz self-assigned this Jul 28, 2017
@tdipisa tdipisa modified the milestones: 2017.06.00 (Catalog Review), 2017.05.00 (TOC&GUI Review) Jul 28, 2017
offtherailz added a commit that referenced this issue Jul 31, 2017
* Extended DrawSupport to edit existing Geometries (leaflet and OpenLayers). Fix #1819
* Replaces agGrid with react-data-grid (moved old to FeatureGrid_ag). Fix #1812
* Implementation of FeatureEditor plugin. Fix #1102 
* Added support for editing/drowing features. Fix #2038 
* Finalized support for WFST. Fix #1885

We should evaluate to:
 * Replace the hold grid example with the new grid
 * Hide unwanted tools in edit mode as in the [mockup](http://demo.geo-solutions.it/mockups/mapstore2/edit/000.html)

Other minor fixes: 
 * Opacity changes  does not refresh the whole layer now. Fix #2063
 * Now only a request is performed (2 only if a "wfs natural order missing primary key" error is detected). Fix #2043
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants