You need to log in before you can comment on or make changes to this bug.
Darren's Comment: Issue noticed during cwc2 1.0.3 training course. > > 9. Choosing Auto projections from projection chooser not working - cause > "crash" message. > Projections are funny, but predictable if you understand them, the problem is most users of any map or web application do not. To make this simple a Projection is either valid for a particular region or not. In the case of WMS and the ProjectionSelector Widget, WMS will try to reproject the layer(s) requests, even if it is not realistic to do so. If the WMS fails an error occurs usually a WMS request time out error. The question is weather the resulting error makes sense to an application a “simple” user, or even GIS individuals not familiar with Serving Web Maps. The answer is probably no. Further explanation would be required within the widget interface and, an additional error explaining the failed result of a Mapserver Error App and/or WMS request. Maybe, a new widget could be created to validate projections being passed, before the request is passed to the WMS Server. It could check weather the projection is valid with the extent and/or current zoom extent of the map. Just a crazy thought….
I have never seen the auto projections work :( I think this is a case of using them correctly, but it is something that should be tested for 1.99.
Changed Target Milestone to 1.99 RC
I'm not a big fan of designing an application that allows the user to change projections. I really think that this would be almost impossible to detect in code and so it really is a documentation issue. The ProjectionSelector widget should come with a HUGE warning about requiring an KNOWLEDGEABLE EXPERT and EXTENSIVE TESTING BEFORE DEPLOYMENT.
Paul, you're stealing my words... or did you just copy that from one of my comments to an older bug? ;)
