| 02:47:46 | CIA-77: | tamas * r9666 /trunk/mapserver/ ( HISTORY.TXT mapgd.c ): Changed msSaveImageBufferGD to be in accordance with msSaveImageGD ( #3201 ) |
| 02:48:45 | CIA-77: | tamas * r9667 /branches/branch-5-6/mapserver/ ( HISTORY.TXT mapgd.c ): Changed msSaveImageBufferGD to be in accordance with msSaveImageGD ( #3201 ) |
| 05:47:18 | CIA-77: | assefa * r9668 /trunk/mapserver/ ( mapfile.c maplayer.c maporaclespatial.c mapserver.h mapwfs.c ): wfs pagination support #2799 |
| 05:50:46 | CIA-77: | aboudreault * r9669 /trunk/mapserver/ ( HISTORY.TXT configure configure.in mapoglrenderer.h ): Fixed configure to support FTGL 2.1.2 ( #3247 ) |
| 07:31:19 | ue: | Good day all, I don't know if it's a bug or not |
| 07:31:33 | ue: | I have mapserver 5.6.0 running and I recieve this error: |
| 07:31:37 | ue: | msWMSLoadGetMapParams( ): WMS server error. Invalid format for the EXCEPTION parameter. |
| 07:31:44 | ue: | xsi:schemaLocation="http://www.opengis.net/ogc http://schemas.opengis.net/wms/1.3.0/exceptions_1_3_0.xsd" |
| 07:31:53 | ue: | http://www.opengis.net/ogc http://schemas.opengis.net/wms/1.3.0/exceptions_1_3_0.xsd => returns 404 |
| 07:32:30 | ue: | sorry not 404, it's a valid page |
| 07:33:56 | ue: | If I try wms version 1.1.1 I get a proper error: msWMSLoadGetMapParams( ): WMS server error. Missing required parameter SRS |
| 07:44:56 | ue: | k, got figured it out, nvm me : ) |
| 08:38:12 | clj2289: | devs, I am having a problem and I wonder if someone could help point me in the right direction...I am having a problem getting our php mapscript application to scale. |
| 08:38:58 | clj2289: | The more users we spin up, the slower the response times, but the server is never pegged |
| 08:39:29 | clj2289: | it is not maxed out on i/o, memory, network or cpu |
| 08:39:38 | clj2289: | I ran across this post: http://n2.nabble.com/MapScript-multithreading-performance-td2000034.html |
| 08:39:39 | sigabrt: | Title: Nabble - Mapserver - Dev ( old ) - MapScript multithreading performance ( at n2.nabble.com ) |
| 08:40:28 | clj2289: | and it seems to hit the nail on the head for me...most of the time spent by the computer is on the draw method... |
| 08:41:42 | clj2289: | we are running mapserver in cgi mode |
| 08:41:55 | clj2289: | any clue would be greatly apperciated |
| 08:42:21 | aboudreault: | Do you know what request take so long? |
| 08:42:34 | aboudreault: | Did you try it locally with php-cli ? |
| 08:43:42 | aboudreault: | If you get the same problem locally, strace could be useful |
| 08:43:51 | clj2289: | I haven't tried with php-cli |
| 08:44:07 | clj2289: | I am on windows...can I use strace? |
| 08:44:14 | aboudreault: | *shrug* |
| 08:44:19 | aboudreault: | don't know :/ |
| 08:45:03 | clj2289: | no worries, I will try it with php-cli...that will tell me if it is a webserver/cgi problem, correct |
| 08:45:10 | clj2289: | ? |
| 08:46:14 | aboudreault: | yes, I would sugggest to test the php-cli request....... then testing to local webserver on that script. |
| 08:46:29 | clj2289: | ok, doing that now |
| 08:47:06 | aboudreault: | If there is any "unacceptable" delay, you should see it. |
| 11:48:20 | CIA-77: | aboudreault * r9670 /trunk/mapserver/ ( HISTORY.TXT maprasterquery.c ): Added support to get the extent of a raster layer that use a tileindex ( #3252 ) |
| 11:51:18 | CIA-77: | aboudreault * r9671 /trunk/mapserver/maprasterquery.c: added a small comment |
| 12:18:47 | mdev: | hi |
| 12:19:16 | mdev: | does anyone know how I can determine what zoom level or mapscale is required in order to make a feature take up the entire map view |
| 12:26:24 | springmeyer: | figure out the bounding box of the features geometry and set the map to that bbox? |
| 12:27:26 | jmckenna: | use a simple cgi viewer with the "[scale]" tag included, then zoom to your feature? |
| 12:28:11 | mdev: | this is a mapscript though |
| 12:28:19 | jmckenna: | u never said that : ) |
| 12:28:21 | mdev: | so I need it to be able to dynamically determine the zoom level |
| 12:28:35 | mdev: | based on the route that is created and line feature resultant |
| 12:28:36 | mdev: | sorry |
| 12:29:10 | mdev: | it must be a zoom level though because the user can zoom in/out from there and it needs to revert to the standard zoom levels from there |
| 12:29:30 | mdev: | so if the feature is a small one zoom might start at 30 but if it's a large one it could start at 20 |
| 12:29:51 | mdev: | but from there user can proceed to zoom in/out based on standard steps |