[MAPSERVER-DEV] FW: [UMN_MAPSERVER-USERS] Upgrade to MapServer 5.0.2 from 4.8.1: extent/scale calculation changes?

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[MAPSERVER-DEV] FW: [UMN_MAPSERVER-USERS] Upgrade to MapServer 5.0.2 from 4.8.1: extent/scale calculation changes?

Doyon, Jean-Francois-2
Upgrade to MapServer 5.0.2 from 4.8.1: extent/scale calculation changes?
G'day y'all ...
 
Posted this to the user's list but had no luck ... anyone?
 
We might have to delay upgrade to 5 and AGG by months if there are indeed undocumented changes to the way scale is calculated :(
 
Thanks,
J.F.


From: UMN MapServer Users List [mailto:[hidden email]] On Behalf Of Doyon, Jean-Francois
Sent: February 4, 2008 10:12
To: [hidden email]
Subject: [UMN_MAPSERVER-USERS] Upgrade to MapServer 5.0.2 from 4.8.1: extent/scale calculation changes?

Hello,

Although all the cartographic testing has been done, I just tested for the first time upgrading 4.8.1 to 5.0.2 with my JavaScript mapping UI, and have discovered something troubling:

For a given map file, the final extent and scale calculations are different between the two versions!

For the same mapfile "105.map" with:

EXTENT -2750564.75 -936638.5 3583872.5 4673125

With 4.8.1:

http://atlas.nrcan.gc.ca/cgi-bin/mapserv?map=/home/atlas/mapdata/english/105.map&map_web_template=/home/atlas/mapdata/to_zope_new.html&mapsize=428+380&map_scalebar_imagecolor=255+255+255

-2750564.750000 -943773.286215 3583872.500000 4680259.786215
41953025.267029


With 5.0.2:

http://dev.atlas.gc.ca/cgi-bin/mapserv502atlas?map=/home/atlas/mapdata/english/105.map&map.web=TEMPLATE+/home/atlas/mapdata/to_zope_new.html&mapsize=428+380&map.scalebar=COLOR+255+255+255

-2750564.750000 -942941.431206 3583872.500000 4679427.931206
42051275.911682

That scale change is big enough to break all our min/max scale ranges and so on :( (on hundreds of mapfiles)

I've looked through HISTORY.TXT and the Migration Guide but am not seeing anything about this (All I saw was a change in scale calculation for PHP?)

Help?

Jean-François Doyon
Data Dissemination Division | Division de la diffusion des données
Data Management and Dissemination Branch | Direction de la gestion et de la diffusion des données
Earth Sciences Sector | Secteur des sciences de la Terre
Natural Resources Canada | Ressources naturelles Canada
Ottawa, Canada K1A 0E9
[hidden email]
Telephone | Téléphone 613-992-4902
Facsimile | Télécopieur 613-947-2410
Teletypewriter | Téléimprimeur 613-996-4397
Government of Canada | Gouvernement du Canada

Reply | Threaded
Open this post in threaded view
|

Re: [MAPSERVER-DEV] FW: [UMN_MAPSERVER-USERS] Upgrade to MapServer 5.0.2 from 4.8.1: extent/scale calculation changes?

Bart van den Eijnden-3
Hi Jean-Francois,

indeed the scale calculation has changed in mapscale.c, see also:

http://trac.osgeo.org/mapserver/ticket/2300

I fear there is not much to do about it ... but it should be added to the migration guide IMHO.

Best regards,
Bart

On Feb 5, 2008 10:56 PM, Doyon, Jean-Francois <[hidden email]> wrote:
G'day y'all ...
 
Posted this to the user's list but had no luck ... anyone?
 
We might have to delay upgrade to 5 and AGG by months if there are indeed undocumented changes to the way scale is calculated :(
 
Thanks,
J.F.


From: UMN MapServer Users List [mailto:[hidden email]] On Behalf Of Doyon, Jean-Francois
Sent: February 4, 2008 10:12
To: [hidden email]
Subject: [UMN_MAPSERVER-USERS] Upgrade to MapServer 5.0.2 from 4.8.1: extent/scale calculation changes?

Hello,

Although all the cartographic testing has been done, I just tested for the first time upgrading 4.8.1 to 5.0.2 with my JavaScript mapping UI, and have discovered something troubling:

For a given map file, the final extent and scale calculations are different between the two versions!

For the same mapfile "105.map" with:

EXTENT -2750564.75 -936638.5 3583872.5 4673125

With 4.8.1:

http://atlas.nrcan.gc.ca/cgi-bin/mapserv?map=/home/atlas/mapdata/english/105.map&map_web_template=/home/atlas/mapdata/to_zope_new.html&mapsize=428+380&map_scalebar_imagecolor=255+255+255

-2750564.750000 -943773.286215 3583872.500000 4680259.786215
41953025.267029


With 5.0.2:

http://dev.atlas.gc.ca/cgi-bin/mapserv502atlas?map=/home/atlas/mapdata/english/105.map&map.web=TEMPLATE+/home/atlas/mapdata/to_zope_new.html&mapsize=428+380&map.scalebar=COLOR+255+255+255

-2750564.750000 -942941.431206 3583872.500000 4679427.931206
42051275.911682

That scale change is big enough to break all our min/max scale ranges and so on :( (on hundreds of mapfiles)

I've looked through HISTORY.TXT and the Migration Guide but am not seeing anything about this (All I saw was a change in scale calculation for PHP?)

Help?

Jean-François Doyon
Data Dissemination Division | Division de la diffusion des données
Data Management and Dissemination Branch | Direction de la gestion et de la diffusion des données
Earth Sciences Sector | Secteur des sciences de la Terre
Natural Resources Canada | Ressources naturelles Canada
Ottawa, Canada K1A 0E9
[hidden email]
Telephone | Téléphone 613-992-4902
Facsimile | Télécopieur 613-947-2410
Teletypewriter | Téléimprimeur 613-996-4397
Government of Canada | Gouvernement du Canada


Reply | Threaded
Open this post in threaded view
|

Re: [MAPSERVER-DEV] FW: [UMN_MAPSERVER-USERS] Upgrade to MapServer 5.0.2 from 4.8.1: extent/scale calculation changes?

Doyon, Jean-Francois-2
Bloody hell ...
 
Indeed, it should be in the migration guide ... and/or HISTORY.TXT (I didn't see it there?).
 
Also missing from HISTORY.TXT was the changes to the CGI URL's (the new syntax &map.layer[0]=NAME+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 :(
 
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?
 
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 ...
 
Thanks!
 
J.F.


From: UMN MapServer Developers List [mailto:[hidden email]] On Behalf Of Bart van den Eijnden
Sent: February 6, 2008 14:19
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?

Hi Jean-Francois,

indeed the scale calculation has changed in mapscale.c, see also:

http://trac.osgeo.org/mapserver/ticket/2300

I fear there is not much to do about it ... but it should be added to the migration guide IMHO.

Best regards,
Bart

On Feb 5, 2008 10:56 PM, Doyon, Jean-Francois <[hidden email]> wrote:
G'day y'all ...
 
Posted this to the user's list but had no luck ... anyone?
 
We might have to delay upgrade to 5 and AGG by months if there are indeed undocumented changes to the way scale is calculated :(
 
Thanks,
J.F.


From: UMN MapServer Users List [mailto:[hidden email]] On Behalf Of Doyon, Jean-Francois
Sent: February 4, 2008 10:12
To: [hidden email]
Subject: [UMN_MAPSERVER-USERS] Upgrade to MapServer 5.0.2 from 4.8.1: extent/scale calculation changes?

Hello,

Although all the cartographic testing has been done, I just tested for the first time upgrading 4.8.1 to 5.0.2 with my JavaScript mapping UI, and have discovered something troubling:

For a given map file, the final extent and scale calculations are different between the two versions!

For the same mapfile "105.map" with:

EXTENT -2750564.75 -936638.5 3583872.5 4673125

With 4.8.1:

http://atlas.nrcan.gc.ca/cgi-bin/mapserv?map=/home/atlas/mapdata/english/105.map&map_web_template=/home/atlas/mapdata/to_zope_new.html&mapsize=428+380&map_scalebar_imagecolor=255+255+255

-2750564.750000 -943773.286215 3583872.500000 4680259.786215
41953025.267029


With 5.0.2:

http://dev.atlas.gc.ca/cgi-bin/mapserv502atlas?map=/home/atlas/mapdata/english/105.map&map.web=TEMPLATE+/home/atlas/mapdata/to_zope_new.html&mapsize=428+380&map.scalebar=COLOR+255+255+255

-2750564.750000 -942941.431206 3583872.500000 4679427.931206
42051275.911682

That scale change is big enough to break all our min/max scale ranges and so on :( (on hundreds of mapfiles)

I've looked through HISTORY.TXT and the Migration Guide but am not seeing anything about this (All I saw was a change in scale calculation for PHP?)

Help?

Jean-François Doyon
Data Dissemination Division | Division de la diffusion des données
Data Management and Dissemination Branch | Direction de la gestion et de la diffusion des données
Earth Sciences Sector | Secteur des sciences de la Terre
Natural Resources Canada | Ressources naturelles Canada
Ottawa, Canada K1A 0E9
[hidden email]
Telephone | Téléphone 613-992-4902
Facsimile | Télécopieur 613-947-2410
Teletypewriter | Téléimprimeur 613-996-4397
Government of Canada | Gouvernement du Canada


Reply | Threaded
Open this post in threaded view
|

Re: [MAPSERVER-DEV] FW: [UMN_MAPSERVER-USERS] Upgrade to MapServer 5.0.2 from 4.8.1: extent/scale calculation changes?

Sean Gillies
In reply to this post by Doyon, Jean-Francois-2
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
Reply | Threaded
Open this post in threaded view
|

Re: [MAPSERVER-DEV] FW: [UMN_MAPSERVER-USERS] Upgrade to MapServer 5.0.2 from 4.8.1: extent/scale calculation changes?

Doyon, Jean-Francois-2
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