GeoServer layergroups are only valid for 26986 (too slow to reproject). We
deal with that by having the folderset XML attribute only_project="EPSG:26986".
However, tilesets, if based on Google projection, are not valid for 26986
(custom projection). Currently, we are setting all tilesets
(type="tiled_layer" in folderset XML) to be valid only for 900913 (Google
projection). When layergroups or tilesets are showing in non-supported
basemaps they appear with a yellow "!" icon to tell the user that they are not
currently valid. However, if we eventually create EPSG 26896 based tilesets
we'll need a more sophisticated method of handling this.
One possible implementation is to add an attribute to the folderset XML that
identifies the list of valid projections.
The lists are never going to be very long. We could add an optional attribute
to the folderset. If it's not there, the layer is a vector/raster that can be
reprojected to anything. If it's valid_proj="26986" or valid_proj="900913" for
example, then it would be valid for the list vaild_proj="A,B,C" sort of thing.
That would then make only_project redundant I think.
Original issue reported on code.google.com by Aleda.Fr...@state.ma.us on 7 Jan 2013 at 8:15
Original issue reported on code.google.com by
Aleda.Fr...@state.ma.uson 7 Jan 2013 at 8:15