Re: [mapserver-users] crash on SYMBOL

[Alan Boudreault]

Fixed and committed in r10809.

Alan

On December 21, 2010 02:25:44 pm Daniel Morissette wrote:
> Bart,
> 
> Is "604310017" a symbol name? If you add quotes around it in the mapfile
> then the entry should be treated as a symbol name and the seg fault
> would go away, can you verify that?
> 
> I suspect the integer value 604310017 (without quotes) is treated as an
> index and used to access the array of symbols without bounds checking.
> Please file a ticket and we'll have a look.
> 
> Daniel
> 
> Bart van den Eijnden (OSGIS) wrote:
> > Hi list,
> > 
> > we have some faulty MAP files, which did not crash MS 5.2, however they
> > do seem to crash MS trunk.
> > 
> > It results in a segfault (e.g. in a WMS GetCapabilities request) when we
> > use e.g.
> > 
> > SYMBOL 604310017
> > 
> > Any idea what has changed in the meantime to cause this to segfault?
> > 
> > TIA.
> > 
> > Best regards,
> > Bart
> > 
> > ___
> > 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

Re: [mapserver-users] crash on SYMBOL

[Daniel Morissette]

Bart,

Is "604310017" a symbol name? If you add quotes around it in the mapfile
then the entry should be treated as a symbol name and the seg fault
would go away, can you verify that?

I suspect the integer value 604310017 (without quotes) is treated as an
index and used to access the array of symbols without bounds checking.
Please file a ticket and we'll have a look.

Daniel


Bart van den Eijnden (OSGIS) wrote:
> Hi list,
> 
> we have some faulty MAP files, which did not crash MS 5.2, however they do
> seem to crash MS trunk.
> 
> It results in a segfault (e.g. in a WMS GetCapabilities request) when we
> use e.g.
> 
> SYMBOL 604310017
> 
> Any idea what has changed in the meantime to cause this to segfault?
> 
> TIA.
> 
> Best regards,
> Bart
> 
> ___
> mapserver-users mailing list
> mapserver-users@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-users


-- 
Daniel Morissette
http://www.mapgears.com/
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] White lines when reprojecting aerial photo

[Ivan Mincik]

>
> Also, this will slow it down but in the raster layer
>
> PROCESSING "RESAMPLE=BICUBIC" rather than default NEAREST is effective
> especially for hi-rez data.

Thanks a lot Mark, I totally forgot on resampling methods. I have
tried BICUBIC which doesn't work, but BILINEAR is working fine.

Ivan
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] long-running postgres queries initiated by mapserver

[Carlos Ruiz]

Your welcome, Matt.

Now it is clear why the query is slow.

You must have indices on the columns that you're searching in (and run VACUUM 
frecuently to keep them 

updated). If you're using LIKE operator, then the indices are not useful if the 
columns are not LOCALEd.

Check if you have defined LOCALE to speed up the LIKE matching.

Also, if the data doesn't change at all, you can CLUSTER the table to improve 
the query speed.


IC Carlos Ruiz




From: Matt Mendick 
To: Carlos Ruiz ; "mapserver-users@lists.osgeo.org" 

Sent: Tue, December 21, 2010 10:43:46 AM
Subject: RE: [mapserver-users] long-running postgres queries initiated by 
mapserver

 
Carlos,
 
Thank you for your response, and indeed the tables do have  indices. The 
spatial 
search is just fine and comes back very quickly, however  the text-based 
searches do not come back quickly (propertyIsLike for  example).  I suppose I 
wasn't clear enough in my original question.   Mapserver does a case 
insensitive 
"like" query on the postgres server and on  tables that are very large 
(millions 
of rows), this takes too long.  We are  training the customers to search for 
things more intelligently, but we cannot  stop them entirely.  We are looking 
into a full-text indexing methodology,  but in the meantime, we need to solve 
the problem of the long-running  queries.
 
-Matt



 From: Carlos Ruiz  [mailto:boolean10...@yahoo.com] 
Sent: Tuesday, December 21, 2010  10:23 AM
To: Matt Mendick;  mapserver-users@lists.osgeo.org
Subject: Re: [mapserver-users]  long-running postgres queries initiated by 
mapserver


Matt,

I  suggest to enhance the PostgreSQL performance at first. Each table with 
geometry  must have a GiST spatial 

index. When you upload a shape file to PostgreSQL,  the shp2pgsql creates this 
index specifying the -I 

parameter.

Have  you uploaded your data in this way ?

If the geometry have been modified  with PostGIS, you must recompute statistics 
to have the index  updated.

Check if you have a spatial index in your table.

Cheers  from México


IC Carlos Ruiz




 From: mattmendick  
To: mapserver-users@lists.osgeo.org
Sent: Tue, December 21, 2010 8:48:19  AM
Subject: [mapserver-users]  long-running postgres queries initiated by mapserver


Hi  All-

I'm running mapserver 5.6.3 under centos 5.4, using fastcgi. I'm  using
postgres as the data storage container, and mapserver is primarily  serving
WFS requests.  Sometimes, people do WFS queries that take a very  long time
(searching for "virginia" on a nation-wide layer) and eventually  postgres
will return with the result after a long time (hours later), however  the
client has cancelled the WFS request.  Is there any way for  mapserver to
know that the client has cancelled the http request, and it can  therefore
stop the DB query to postgres?  I tried using persistent and  non-persistent
connections with this:

PROCESSING  "CLOSE_CONNECTION=DEFER"

but that didn't change the  behavior.

Thanks a lot!
-- 
View this message in context: 
http://osgeo-org.1803224.n2.nabble.com/long-running-postgres-queries-initiated-by-mapserver-tp5855539p5855539.html

Sent  from the Mapserver - User mailing list archive at Nabble.com.
___
mapserver-users  mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

NOTICE: This message is covered by the Electronic Communications Privacy Act, 
Title 18, United States Code, Sections 2510-2521. This e-mail and any attached 
files are the exclusive property of Pictometry International Corp., are deemed 
privileged and confidential, and are intended solely for the use of the 
individual(s) or entity to whom this e-mail is addressed. If you are not one of 
the named recipient(s) or believe that you have received this message in error, 
please delete this e-mail and any attachments and notify the sender 
immediately. 
Any other use, re-creation, dissemination, forwarding or copying of this e-mail 
is strictly prohibited and may be unlawful. 



  ___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

RE: [mapserver-users] long-running postgres queries initiated by mapserver

[Matt Mendick]

Carlos,

Thank you for your response, and indeed the tables do have indices. The spatial 
search is just fine and comes back very quickly, however the text-based 
searches do not come back quickly (propertyIsLike for example).  I suppose I 
wasn't clear enough in my original question.  Mapserver does a case insensitive 
"like" query on the postgres server and on tables that are very large (millions 
of rows), this takes too long.  We are training the customers to search for 
things more intelligently, but we cannot stop them entirely.  We are looking 
into a full-text indexing methodology, but in the meantime, we need to solve 
the problem of the long-running queries.

-Matt


From: Carlos Ruiz [mailto:boolean10...@yahoo.com]
Sent: Tuesday, December 21, 2010 10:23 AM
To: Matt Mendick; mapserver-users@lists.osgeo.org
Subject: Re: [mapserver-users] long-running postgres queries initiated by 
mapserver

Matt,

I suggest to enhance the PostgreSQL performance at first. Each table with 
geometry must have a GiST spatial
index. When you upload a shape file to PostgreSQL, the shp2pgsql creates this 
index specifying the -I
parameter.

Have you uploaded your data in this way ?

If the geometry have been modified with PostGIS, you must recompute statistics 
to have the index updated.

Check if you have a spatial index in your table.

Cheers from México

IC Carlos Ruiz


From: mattmendick 
To: mapserver-users@lists.osgeo.org
Sent: Tue, December 21, 2010 8:48:19 AM
Subject: [mapserver-users] long-running postgres queries initiated by mapserver


Hi All-

I'm running mapserver 5.6.3 under centos 5.4, using fastcgi. I'm using
postgres as the data storage container, and mapserver is primarily serving
WFS requests.  Sometimes, people do WFS queries that take a very long time
(searching for "virginia" on a nation-wide layer) and eventually postgres
will return with the result after a long time (hours later), however the
client has cancelled the WFS request.  Is there any way for mapserver to
know that the client has cancelled the http request, and it can therefore
stop the DB query to postgres?  I tried using persistent and non-persistent
connections with this:

PROCESSING "CLOSE_CONNECTION=DEFER"

but that didn't change the behavior.

Thanks a lot!
--
View this message in context: 
http://osgeo-org.1803224.n2.nabble.com/long-running-postgres-queries-initiated-by-mapserver-tp5855539p5855539.html
Sent from the Mapserver - User mailing list archive at 
Nabble.com.
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users


NOTICE: This message is covered by the Electronic Communications Privacy Act, 
Title 18, United States Code, Sections 2510-2521. This e-mail and any attached 
files are the exclusive property of Pictometry International Corp., are deemed 
privileged and confidential, and are intended solely for the use of the 
individual(s) or entity to whom this e-mail is addressed. If you are not one of 
the named recipient(s) or believe that you have received this message in error, 
please delete this e-mail and any attachments and notify the sender 
immediately. Any other use, re-creation, dissemination, forwarding or copying 
of this e-mail is strictly prohibited and may be unlawful.
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] White lines when reprojecting aerial photo

[Mark Korver]

Dont know if this relates to your problem, but its easy to check.  We
normally  use the GD/JPEG driver when doing image data.  My
understanding is that AGG is more useful for outputting vectors to
PNG.

Also, this will slow it down but in the raster layer

PROCESSING "RESAMPLE=BICUBIC" rather than default NEAREST is effective
especially for hi-rez data.


On Sun, Dec 19, 2010 at 1:26 PM, Ivan Mincik  wrote:
> Hi,
> we are trying to provide aerial photo images in multiple projections
> using on-the-fly reprojection in JPEG format. When reprojecting layer
> from our country's local projection to Google Mercator, thin white
> lines appearing through the whole image (see
> http://gista.sk/home/ivo/dl/white_lines.jpeg).
>
> We are using 'AGG/JPEG' driver, Mapserver 5.2 with following
> outputformat configuration:
>
>       RESOLUTION 72
>       OUTPUTFORMAT
>                NAME 'AGG_JPEG'
>                DRIVER 'AGG/JPEG'
>                MIMETYPE 'image/jpeg'
>                IMAGEMODE RGB
>                FORMATOPTION 'QUALITY=85'
>                EXTENSION 'jpg'
>        END
>
> Any idea what I can improve to get these white lines out ?
>
> Thanks,
> Ivan
> ___
> 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] long-running postgres queries initiated by mapserver

[Carlos Ruiz]

Matt,

I suggest to enhance the PostgreSQL performance at first. Each table with 
geometry must have a GiST spatial 

index. When you upload a shape file to PostgreSQL, the shp2pgsql creates this 
index specifying the -I 

parameter.

Have you uploaded your data in this way ?

If the geometry have been modified with PostGIS, you must recompute statistics 
to have the index updated.

Check if you have a spatial index in your table.

Cheers from México


IC Carlos Ruiz




From: mattmendick 
To: mapserver-users@lists.osgeo.org
Sent: Tue, December 21, 2010 8:48:19 AM
Subject: [mapserver-users] long-running postgres queries initiated by mapserver


Hi All-

I'm running mapserver 5.6.3 under centos 5.4, using fastcgi. I'm using
postgres as the data storage container, and mapserver is primarily serving
WFS requests.  Sometimes, people do WFS queries that take a very long time
(searching for "virginia" on a nation-wide layer) and eventually postgres
will return with the result after a long time (hours later), however the
client has cancelled the WFS request.  Is there any way for mapserver to
know that the client has cancelled the http request, and it can therefore
stop the DB query to postgres?  I tried using persistent and non-persistent
connections with this:

PROCESSING "CLOSE_CONNECTION=DEFER"

but that didn't change the behavior.

Thanks a lot!
-- 
View this message in context: 
http://osgeo-org.1803224.n2.nabble.com/long-running-postgres-queries-initiated-by-mapserver-tp5855539p5855539.html

Sent from the Mapserver - User mailing list archive at Nabble.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] long-running postgres queries initiated by mapserver

[mattmendick]

Hi All-

I'm running mapserver 5.6.3 under centos 5.4, using fastcgi. I'm using
postgres as the data storage container, and mapserver is primarily serving
WFS requests.  Sometimes, people do WFS queries that take a very long time
(searching for "virginia" on a nation-wide layer) and eventually postgres
will return with the result after a long time (hours later), however the
client has cancelled the WFS request.  Is there any way for mapserver to
know that the client has cancelled the http request, and it can therefore
stop the DB query to postgres?  I tried using persistent and non-persistent
connections with this:

PROCESSING "CLOSE_CONNECTION=DEFER"

but that didn't change the behavior.

Thanks a lot!
-- 
View this message in context: 
http://osgeo-org.1803224.n2.nabble.com/long-running-postgres-queries-initiated-by-mapserver-tp5855539p5855539.html
Sent from the Mapserver - User mailing list archive at Nabble.com.
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] crash on SYMBOL

[Bart van den Eijnden (OSGIS)]

Hi list,

we have some faulty MAP files, which did not crash MS 5.2, however they do
seem to crash MS trunk.

It results in a segfault (e.g. in a WMS GetCapabilities request) when we
use e.g.

SYMBOL 604310017

Any idea what has changed in the meantime to cause this to segfault?

TIA.

Best regards,
Bart

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] Label for polylines

[Forest]

Hello everyone:
    I've researched the source code of mapserver about the label for 
polylines.but as I looked into the source code,I've been confused,anyone can 
give me some direction about label for polylines? Or tell me process of 
labeling for polylines?
   Thank you very much!


  ___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users