Hi Alan,
I tried the mapcache_seed with delete mode as in your example but it still
doesn't work :(
Ludovic
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/MapCache-A-way-to-delete-a-whole-zoom-level-tp4978491p4978902.html
Sent from the Mapserver - User mailing list archive
How can it doesn't work? Any error output? Have you checked the
directory of the zoom level?
Alan
On 12-06-04 03:52 AM, Ludovic Gnemmi wrote:
Hi Alan,
I tried the mapcache_seed with delete mode as in your example but it still
doesn't work :(
Ludovic
--
View this message in context:
Hi Alan,
I'm using Berkeley DB cache type so i haven't any directory.
No errors. I'v just checked my bdb.db file which still has the same size :(
Ludovic
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/MapCache-A-way-to-delete-a-whole-zoom-level-tp4978491p4978968.html
Hi,
Just guessing without knowing anything about Berkeley DB, but if it is like
other databases it would probably need vacuuming after delete before it really
frees any disk space. And if you do mass delete and Berkeley DB behaves even
closely similarly than SQLite, vacuuming may be extremely
Ludovic' problem is that he is out of disk space so that is probably not
going to work for him. If he can not free some space to start with it is
likely he will have to delete the whole cache.
Ludovic, You might want to write an enhancement request to mapcache,
that requests each zoom level
Hi all,
We are trying to get VHR satellite imagery to run as a WMS in different
GIS clients. When we compare the original image (we tried different
formats, tif, ecw, virtual formats etc.) to the hosted image we see a
shift in the pixels. Looks like a minor warp or transform.
We are
Hi Steve,
I tried to save some space (80 Mo) before running tile_seeder but it still
has no effect.
Otherwise you are right: one db file per zoom level would be a great
enhancement.
I've submitted a new request.
Ludovic
--
View this message in context:
Hello,
I received a report that a GeoMOOSE / Mapserver web mapping application
http://geomoose.lyonco.org/MurrayMoose/ is creating pink tiles when zoomed out.
I found out that the user has a very large monitor, so I thought that I may
have forgot to set the MAP MAXSIZE parameter. That was
Hello,
I'm experiencing very odd behavior that wasn't in previous versions of
Mapserver i used such as 5.7. The problem is certain layer geometry and
symbol combinations ( only 1 i can identify so far ) cause mapserver
processes to spike at 100% and hang for a long time ( 60 minutes ). I've
Mark,
I just tried from my work station and turned everything off except the Boundary
and base layer. I zoomed in and out with no problems using a hi res screen.
Could the problem have been a momentary thing, or is the user still seeing the
pink tiles? There may be a permissions problem
Mark,
Could this be a timeout issue?
What happens if the user right clicks on the pink tile in FF and selects
View Image? or Reload Image?
Do you have some kind of max memory limit or ulimit set?
Or a long running process killer?
-Steve W
On 6/4/2012 12:14 PM, Mark Volz wrote:
Hello,
I
I'm trying to migrate an application which now uses MapServer 6.0.2,
from 6.0.1. I understand this should be seamless, but I am having
problems with a query, the FireBug error says it cannot open the map
file.
Here are the lines of code triggering the error:
Bob,
What disk drive its it on?
C:, D:, E:, etc Different on the two machines?
-Steve W
On 6/4/2012 1:11 PM, Bistrais, Bob wrote:
I’m trying to migrate an application which now uses MapServer 6.0.2,
from 6.0.1. I understand this should be seamless, but I am having
problems with a query, the
Hello everyone,
I have a Map file with a polygon layer that has an OPACITY value of 20
defined as:
I see a correctly opaque display when I do a GetMap or a GetLegendGraphic,
so I know the OPACITY value is set properly. However, when I perform a
GetStyles request, the returned SLD doesn't include
If you're not using queryable layers with STATUS DEFAULT then you can just
use the normal layer or layers parameter. Of course the workaround mentioned in
the referenced ticket is still valid.
Steve
From: mapserver-users-boun...@lists.osgeo.org
[mailto:mapserver-users-boun...@lists.osgeo.org]
What version are you talking about? How do you know there is a shift? That is,
what is your reference? Is it possible there's a difference in the bounding box
model? For WMS the bbox represents the outside dimensions of the pixels in an
image.
Steve
Note: MapServer uses a pixel center bbox
Are we missing a few things like the response and the mapfile snippet? Also are
you talking layer opacity or style opacity?
Steve
-Original Message-
From: mapserver-users-boun...@lists.osgeo.org
[mailto:mapserver-users-boun...@lists.osgeo.org] On Behalf Of myOpenLayersUName
Sent:
17 matches
Mail list logo