Bug 462

Summary:	[Chameleon-Widget] Projection Selection WGS84 produces errors and wrong keymap extent.
Product:	Chameleon	Reporter:	Chris Thorne <cthorne@dmsolutions.ca>
Component:	Widget	Assignee:	chameleon-dev <chameleon-dev@lists.maptools.org>
Status:	RESOLVED FIXED
Severity:	normal	CC:	warmerdam@pobox.com
Priority:	P2
Version:	1.99
Target Milestone:	1.99 beta 4
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description From Chris Thorne 2004-06-22 13:05:04

[Chameleon-Widget] Projection Selection WGS84 produces errors and wrong keymap
extent.

I realize setting keymap extent on the fly with the current projection is
difficult, but I think there is a problem.

testing with sample app: http://localhost/chameleon/samples/sample_enhanced.phtml


Issue 1:
At full extent select: WGS84 / LCC Canada

The resulting map is the full extent of Canada where the keymap is shifted
south. I believe there is a calculation issue here with this projection.

Issue 2:
At full extent select: using any WGS84 / ** Projection

I get the error: 
Fatal error: [MapServer Error]: msProcessProjection(): major axis or radius = 0
or not given in D:\ms4w\apps\chameleon\htdocs\widgets\Widget.php on line 618

I thought maybe this was a result of being at the extent of Canada and since UTM
is invalid at that extent, but it occurs at any scale, with any WGS84 projection.


I think this bug should not stop the beta 2 to go out but is important for beta 3.

------- Comment #1 From Darren Redfern 2004-07-08 12:59:52 -------

Changed target to 1.99 beta 3.

------- Comment #2 From Liz Godwin 2004-09-14 09:26:06 -------

The second issue mentioned, seemed to go away when I changed the line of code in
Widget.php (line 618 in this case) to be "init=epsg:4326" not "proj=latlong". 
This may not be the correct fix, but it worked for me.

------- Comment #3 From Daniel Morissette 2004-09-14 09:32:57 -------

I think that may be because "proj=latlong" is not enough, you also need to
specify an ellipsoid (e.g. ellps=WGS84). 

I have CC'd Frank who may be able to shed some more light on the minimum
required parameters for proj=latlong.

------- Comment #4 From Frank Warmerdam 2004-09-14 09:43:09 -------

Any coordinate system (proj=latlong or otherwise) needs at least an 
ellipsoid definition.  This is handled in the various lookup files (ie. epsg)
or if a datum is provided. 

I would generally suggest using "+proj=latlong +datum=WGS84" when you mean 
normal WGS84. 

I don't have enough information to comment on Issue 1.

------- Comment #5 From Paul Spencer 2004-09-14 10:09:44 -------

I've committed the change for issue 2 and it seems to work for all the AUTO
projections in the enhanced sample app.

Issue #1 is still a problem.  The map and keymap extents are the same and the
aspect ratios of they map and keymap are also the same, so it must be in the
widget code somewhere. I'm going to file a separate bug on this issue. (bug 668)

------- Comment #6 From Darren Redfern 2004-10-25 08:28:41 -------

Changed target for verification to 1.99 RC 1.