RE: [mapserver-users] MapScript resultsGetShape confusion [solved!]
Yes, adding the tileindex argument to the resultsGetShape call in PHP mapscript seems to have solved my problem with moving my application from MapServer 5.6.1 to 5.6.3. Worth -Original Message- From: mapserver-users-boun...@lists.osgeo.org [mailto:mapserver-users-boun...@lists.osgeo.org] On Behalf Of Worth Lutz Sent: Wednesday, June 02, 2010 8:12 PM To: 'Christian Jauvin'; 'Daniel Morissette' Cc: mapserver-users@lists.osgeo.org Subject: RE: [mapserver-users] MapScript resultsGetShape confusion [solved!] This may be the problem I had when I tried to update to 5.6.3. from 5.6.1. I'm in the middle of a project and did not have time to figure out what was causing the problem. The only change was the change to the MapServer version so I quickly reverted back. I'm using PHP Mapscript. I'll see if I can find the time to check to see if this is the problem I was having. Worth -Original Message- From: mapserver-users-boun...@lists.osgeo.org [mailto:mapserver-users-boun...@lists.osgeo.org] On Behalf Of Christian Jauvin Sent: Wednesday, June 02, 2010 11:18 AM To: Daniel Morissette Cc: mapserver-users@lists.osgeo.org Subject: Re: [mapserver-users] MapScript resultsGetShape confusion [solved!] Ok.. so with a lot of fiddling around (and with inspiration from a Frank Warmerdam's testing script) I've been able to find the cause of the problem, as well as its solution: with a PostGIS connected layer, a call to resultsGetShape *has* to include the third parameter, tileindex: resultsGetShape(shp, res.shapeindex) -- hangs MS 5.6.3 resultsGetShape(shp, res.shapeindex, res.tileindex) -- works great! I don't know if it's really a bug, but it contradicts the documentation, in which the tileindex argument is optional, and it wasn't behaving like that (to my knowledge) with MS in [5.6.0, 5.6.2]. By the way, an initial observation I made was wrong: it also affects the PHP version, and the workaround is the same. Best regards, Christian On Tue, Jun 1, 2010 at 5:02 PM, Daniel Morissette dmorisse...@mapgears.com wrote: Christian Jauvin wrote: I did what you suggested, and added: CONFIG MS_ERRORFILE error file CONFIG CPL_DEBUG ON DEBUG 5 Did you also include DEBUG 5 inside the POSTGIS layer itself? to my mapfile, and performed my query again. It generated a very long file (200K+ lines!) with only two types of line: [Tue Jun 1 14:36:01 2010].765230 getSymbol(): Symbol definition error. Parsing error near (null):(line 208) [...] [Tue Jun 1 14:36:01 2010].777963 msPostGISLayerResultsGetShape called for record = 338 [...] 200k times the same message sounds like an infinite loop of some sort. Perhaps look at the first few lines of debug/error messages. There may be a different message that would have been output *before* entering the infinite loop and that could give a hint about what is happening. Just a guess... can't do much more from here. What is the last version that worked fine? 5.6.2? Daniel -- Daniel Morissette http://www.mapgears.com/ ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] MapScript resultsGetShape confusion [solved!]
Steve and I are in discussion to solve this issue. If you have other useful information or want to follow the bug processing, here's the trac ticket: http://trac.osgeo.org/mapserver/ticket/3467 regards, Alan On June 3, 2010 08:57:27 am Worth Lutz wrote: Yes, adding the tileindex argument to the resultsGetShape call in PHP mapscript seems to have solved my problem with moving my application from MapServer 5.6.1 to 5.6.3. Worth -Original Message- From: mapserver-users-boun...@lists.osgeo.org [mailto:mapserver-users-boun...@lists.osgeo.org] On Behalf Of Worth Lutz Sent: Wednesday, June 02, 2010 8:12 PM To: 'Christian Jauvin'; 'Daniel Morissette' Cc: mapserver-users@lists.osgeo.org Subject: RE: [mapserver-users] MapScript resultsGetShape confusion [solved!] This may be the problem I had when I tried to update to 5.6.3. from 5.6.1. I'm in the middle of a project and did not have time to figure out what was causing the problem. The only change was the change to the MapServer version so I quickly reverted back. I'm using PHP Mapscript. I'll see if I can find the time to check to see if this is the problem I was having. Worth -Original Message- From: mapserver-users-boun...@lists.osgeo.org [mailto:mapserver-users-boun...@lists.osgeo.org] On Behalf Of Christian Jauvin Sent: Wednesday, June 02, 2010 11:18 AM To: Daniel Morissette Cc: mapserver-users@lists.osgeo.org Subject: Re: [mapserver-users] MapScript resultsGetShape confusion [solved!] Ok.. so with a lot of fiddling around (and with inspiration from a Frank Warmerdam's testing script) I've been able to find the cause of the problem, as well as its solution: with a PostGIS connected layer, a call to resultsGetShape *has* to include the third parameter, tileindex: resultsGetShape(shp, res.shapeindex) -- hangs MS 5.6.3 resultsGetShape(shp, res.shapeindex, res.tileindex) -- works great! I don't know if it's really a bug, but it contradicts the documentation, in which the tileindex argument is optional, and it wasn't behaving like that (to my knowledge) with MS in [5.6.0, 5.6.2]. By the way, an initial observation I made was wrong: it also affects the PHP version, and the workaround is the same. Best regards, Christian On Tue, Jun 1, 2010 at 5:02 PM, Daniel Morissette dmorisse...@mapgears.com wrote: Christian Jauvin wrote: I did what you suggested, and added: CONFIG MS_ERRORFILE error file CONFIG CPL_DEBUG ON DEBUG 5 Did you also include DEBUG 5 inside the POSTGIS layer itself? to my mapfile, and performed my query again. It generated a very long file (200K+ lines!) with only two types of line: [Tue Jun 1 14:36:01 2010].765230 getSymbol(): Symbol definition error. Parsing error near (null):(line 208) [...] [Tue Jun 1 14:36:01 2010].777963 msPostGISLayerResultsGetShape called for record = 338 [...] 200k times the same message sounds like an infinite loop of some sort. Perhaps look at the first few lines of debug/error messages. There may be a different message that would have been output *before* entering the infinite loop and that could give a hint about what is happening. Just a guess... can't do much more from here. What is the last version that worked fine? 5.6.2? Daniel -- Daniel Morissette http://www.mapgears.com/ ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users -- Alan Boudreault Mapgears http://www.mapgears.com ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
[mapserver-users] PHP mapscript does not use GRID information when reprojecting rect object [solved??]
Hello list, Some time ago I posted a problem about reprojection using mapscript. I solved it sort of say, and I think that this note can help users as well as developers. To reassume: I had a map projection and a layer in another projection. Mapserver perfectly uses the GRIDS in the projection information of the layer when it draws, but it did NOT use them when calling the mapscript function project( projectionObj proj_in, projectionObj proj_out ) . The answer is that the null keyword gave the incorrect reprojection. Deleting the ,null string and leaving only the name of the grid file will work fine. INCORRECT nadgrids=lombardia_tot.gsb,null CORRECT nadgrids=lombardia_tot.gsb *main project projection* PROJECTION proj=utm zone=32 ellps=WGS84 datum=WGS84 units=m no_defs END *layer projection* PROJECTION proj=tmerc lat_0=0 lon_0=9 k=0.9996 x_0=150 y_0=0 ellps=intl units=m no_defs nadgrids=lombardia_tot.gsb,null END -- *Francesco Pirotti* Dep. TESAF CIRGEO -- Interdepartmental Research Center on Cartography Photogrammetry Remote Sensing and G.I.S. University of Padova Web: http://www.cirgeo.unipd.it/cirgeo/francescopirotti.htm Email: francesco.piro...@unipd.it mailto:francesco.piro...@unipd.it Phone: +39 049 827 2710 Phone: +39 349 55 39 261 ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
[mapserver-users] Cascading WMS
Hi, I have set up Mapserver to read a WMS server and then feed this out via WMS. The image quality is degraded by MapServer so it is re rendering the image. How can I get MapServer to simply pass the image that it gets from the WMS server on instead of re rendering? Thanks, Jerry ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
[mapserver-users] how pass parameters to map file
Hi, in this moment i have working with mapserver and geomoose framework , and I need make a filter dynamic but I don´t know how pass the parameters to map file. how implement this ? best regards , Salas ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] Cascading WMS
Jerry O'Sullivan wrote: I have set up Mapserver to read a WMS server and then feed this out via WMS. The image quality is degraded by MapServer so it is re rendering the image. How can I get MapServer to simply pass the image that it gets from the WMS server on instead of re rendering? I can think of two reasons for loss of image quality in cascaded WMS layers: 1- Incompatible output format. For instance, if the cascaded WMS returns 24 bit imagery (PNG24 or JPEG) and your MapServer is configured for 8 bits output (GIF, PNG8) then you will experience some color issues. 2- Reprojection. Make sure the SRS that is used by the WMS client is supported by the cascaded server and listed in the wms_srs metadata. Reprojection of the cascaded WMS request (required if the requested SRS is not listed as being supported by the remote server) can greatly degrade image quality. If your client calls MapServer with a SRS that is supported by the remote WMS server then it should make essentially the same request to the remote server and there should be no transformation or quality loss. HTH Daniel -- Daniel Morissette http://www.mapgears.com/ ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
