Yeah, but it's not 100% solid ... and I'm pressed for time. If I did
have more time, that's the way I'd go ... I could change the source as a
band aid until I can spend more time on making sure the etree parser is
more mature. The student resource I was hoping to dedicate to this work
has fallen through, and I'm changing jobs soon.
Ah well, I'll see what I can do!
Thanks,
J.F.
-----Original Message-----
From: UMN MapServer Developers List [mailto:
[hidden email]]
On Behalf Of Sean Gillies
Sent: February 8, 2008 12:39
To:
[hidden email]
Subject: Re: [MAPSERVER-DEV] FW: [UMN_MAPSERVER-USERS] Upgrade to
MapServer 5.0.2 from 4.8.1: extent/scale calculation changes?
Doyon, Jean-Francois wrote:
> This is a multi-part message in MIME format.
>
> ------_=_NextPart_001_01C86A74.10B681F9
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> Bloody hell ...
> =20
> Indeed, it should be in the migration guide ... and/or HISTORY.TXT (I
> = didn't see it there?).
> =20
> Also missing from HISTORY.TXT was the changes to the CGI URL's (the
> new = syntax &map.layer[0]=3DNAME+test). I tend to read HISTORY.TXT
> because I = expect it to be more detailed than the migration guide,
> but looks like a = few things get missed :( =20 Anyways ... Does this
> scale calculation change affect anything else in = the core? What if
> I reverted the line of code that concerns me back to = the old way?
> Could I safely do that?
> =20
> At this point this seems a lot more appealing a solution than changing
> = 500 mapfiles, especially since I'm on very tight deadlines to get =
> MapServer 5 installed ...
> =20
> Thanks!
> =20
> J.F.
>
J.F.,
My sense is that you'll be better off investing in a script that will
migrate your mapfiles. Don't you have a miraculous etree mapfile parser
already?
Sean
