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!
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
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
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
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
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
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
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
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
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
10 matches
Mail list logo