Sorry to bother again, when i use gdal_merge.py the part -ps 160 160, thats
the pixel dimension and i get an image 1kb. The pixel size of the original
file is 0.08 meters. So i think i should use 0.08x32 in the gdal_merge.py
command? And how many tiles should i merge together? Now i have 2T
Edi.Karadumi wrote:
Sorry to bother again, when i use gdal_merge.py the part -ps 160 160, thats
the pixel dimension and i get an image 1kb. The pixel size of the original
file is 0.08 meters. So i think i should use 0.08x32 in the gdal_merge.py
command?
Edi,
If the original resolution is 8cm
Thanx to you my questions are comming to an end [?]
Three more last things
Should i retile the new mosaiced overview? Meaning should i create smaller
size tiles of the new mosaic?
And how can i find in which scale should i switch layers? So what will be
the maxscale of the original layer?
if
Thanx to you my questions are comming to an end
Three more last things
Should i retile the new mosaiced overview? Meaning should i create smaller
size tiles of the new mosaic? or 2Gb is not a problem
And how can i find in which scale should i switch layers? So what will be
the maxscale of
Edi.Karadumi wrote:
Thanx to you my questions are comming to an end
Three more last things
Should i retile the new mosaiced overview? Meaning should i create smaller
size tiles of the new mosaic? or 2Gb is not a problem
Edi,
Generally speaking, as long as you enable internal tiling when
Sorry but im still not understanding this:
That remains a complicated question. I believe I suggested 1/32 as a
good overview level since beyond that point a normal map view will tend
to involve a significant number of files.
My only problem now is to find the correct scale for each layer.
Sorry but im still not understanding this:
That remains a complicated question. I believe I suggested 1/32 as a
good overview level since beyond that point a normal map view will tend
to involve a significant number of files.
My only problem now is to find the correct scale for each
Mike:
Two ways:
1. External Overview Pyramid
- see http://mapserver.org/input/raster.html#rasters-and-tile-indexing
and
http://mapserver.org/input/raster.html#raster-display-performance-tips
- Make image pyramid levels with gdal_translate
- create tile
One simple trick that I don't think has been mentioned is to add the shape
indexes of each of your raster layers to your mapfile to be able to see how
many raster tiles were used for each request. This makes it clear how many
files were used to create your output image.
--
View this message
Hi All,
I'm trying to set up an INSPIRE compliant (compliant to the network services
guidance doc) service for the hydrography theme but have come up against a
bit of a problem.
Essentially, in the portrayal section of the Hydrography data specifications
certain layers are defined, for instance
I stopped the AppArmor service and reran the test with no change in behavior.
Thanks,
Johan.
-Original Message-
From: Umberto Nicoletti [mailto:umberto.nicole...@gmail.com]
Sent: Tuesday, August 17, 2010 2:20 AM
To: Johan Forsman
Cc: mapserver-users@lists.osgeo.org
Subject: Re:
This procedure does not trigger a seg fault. It appears to execute as intended
based on the console output being OGR status messages followed by a binary
string in PNG format.
I filtered the output for text only and the OGR messages indeed indicate
success.
However, when I tried this
Hi there,
this is my mapfile for a WMS cascade:
http://www.privatepaste.com/37c0140648
The Serbian WMS servs EPSG:4326 only, but they're using wrong
parameters for shifting their local CRS to WGS84. They're
informed, but they don't or can't change it.
I've calculated that the shift is exaclty
Johan Forsman wrote:
In other words, all along this was a path issue that was not evident from the
console while in the correct data directory, and somehow the failure to find
the csv caused the mapserv seg fault.
Note to self: Always try with full pathnames. Sometimes it really is the
Hey guys. Still no luck on this one, thought maybe I'd ask again.
The compile gets as far as linking, then bombs. The error seems to be
related to AGG, and if I give --with-agg=no the compiles finished
successfully. Though, of course we do want AGG!
The system does not have AGG installed at
Hi Gregor,
Jump on my server gis.imaptools.com (it is Debian).
I just downloaded 5.6.5 and built it with no problem.
wood...@gis:~/work/software/mapserver-5.6.5$ ./mapserv -v
MapServer version 5.6.5 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG OUTPUT=WBMP
OUTPUT=PDF OUTPUT=SVG SUPPORTS=PROJ SUPPORTS=AGG
Jump on my server gis.imaptools.com (it is Debian).
I just downloaded 5.6.5 and built it with no problem.
Good, good. Too bad I can't advise the customer to throw out everything
he's ever done and go with Debian. (ha ha) In the meantime, I used
--with=agg=no, so he can at least start testing
Im not familiar with the code you are talking about, but i can tell you briefly
when this errro occurs: an http response consists of two parts a header and the
body. Attempts to write a http header when one has already been written and the
body started will cause an error. A common cause of
18 matches
Mail list logo
