[Chameleon-dev] [Bug 153] [chameleon] case sensitivity in keymap widget

[bugzilla-daemon at www.maptools.org]

http://www.maptools.org/bugzilla/show_bug.cgi?id=153





------- Additional Comments From morissette at dmsolutions.ca  2004-04-14 10:09 -------
The different cases in MapServer are a bit confusing I have to admit, but there
are technical (and performance) reasons behind them that can be justified for
MapServer as a toolkit I think. In MapServer, EPSG SRS are specified in one of
two ways:

1- In the PROJECTION object as 
   PROJECTION
     "init=epsg:42304"
   END

2- In wms_* metadata as "EPSG:42304" in uppercase.

#1 is passed directly to PROJ, MapServer doesn't control that format and the
epsg part of the init= argument is a filename, that's why it has to be
lowercase.  #2 is used for OGC-related metadata and uses the uppercase form that
OGC dictates.

However Chameleon doesn't have to repeat the same since it is targetted at a
different audience. Actually, what Chameleon does is not exactly in line with
either of MapServer's behavior: it creates a third way of setting SRS which is
to use "epsg:xxx" in lowercase, so it's not in line with anything MapServer does.  

I think I know why things were done this way internally: you probably just take
whatever value you receive and prepend it with "init=" before setting the
projection object.  So you're not passing the SRS value directly to MapServer
anyway, and since you're modifying the value anyway it might not be a huge deal
to adjust the cases.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.