Closed chughes-lincoln closed 1 year ago
Created a filter to catch the "placeholder" images that Mapserver returns.
This fixes 1 and 2. I'm still seeing a larger gap after a layer if the layer has multiple classes. That's a weird one and only really an issue if someone has a complex dataset with a lot of classes. Fixing 1 and 2 is a huge improvement.
This is going to be mapserver... I didn't see any easy fixes for this in the documentation.
... the only way to fix this on the client would be to make some big assumptions about the legends:
I'm not sure I'm wholly comfortable making those assumptions.
I kind of figured that but was still holding out hope. I'm comfortable enough with the enhancements that have already been made.
There are a few situations that result in blank spaces between layers in print legends, which can make the legend look a bit less professional and can make it more difficult to fit all of your layers in the legend. I'm not sure how much of this is a mapserver vs a geomoose issue, but I thought I'd document them.
1) If a layer is on in the catalog but not visible at that scale.
2) If you have multiple layers grouped together into a single layer in the catalog. If the legend is on for that catalog layer, any layers that don't have a class name will show up as blank spaces. The issue here is that you can't turn off legends for individual map-sources, so the only way to avoid adding legends for individual map-sources is to omit the class name.
3) If you have a layer that has multiple classes in the map-source, there will be a gap in the legend after the layer, which is proportional to the number of classes in the layer.
Example below:![image](https://user-images.githubusercontent.com/43766648/226475901-097ee92f-6ca4-410b-9fe4-dd7f333efb93.png)