Jody Garnett ha scritto:
I think the rendering code also is willing to "force" the CRS specified as part of the Layer (there was some horrible code that did this last time I did a code review).
Well, horrible or not, that's necessary if you want to deal with broken
data.
GeoServer could also provide a "default" CRS to use in this case.
Yeah, we could do it at layer level, but that would not fix WFS GetFeature results... I'd prefer to do this at the GeoserverFeatureSource level.
Anyways, you've not told if you you're against or pro the solution I proposed. The issue can be solved in various ways, but having Geoserver
force a CRS seems like a way to hide the issue that there's broken
data around, and that renderer should learn to cope with it.
Cheers
Andrea