Thank you for that extended comparison Jukka. It looks like there's no
feasible way to get there from here, but that too is useful to know.
For the gdalcompare results, are we confident that it is analyzing pixels at
Row,Col coordinates (or spatial X,Y?) and not at byte offset or something?
---
Hi,
Ok, so obviously you are talking about WFS service, not WMS.
Why don't you use paging with COUNT and STARTINDEX
https://www.mapserver.org/ogc/wfs_server.html?
-Jukka Rahkonen-
MRRAJESH wrote
> We are expecting feature information from our own map server for a given
> BBOX. At present we
We are expecting feature information from our own map server for a given
BBOX. At present we are limited to 500 features is the max limit. But as per
our requirement, we want to return a huge number of features from the
server. So we are planning to split the BBOX into multiple boxes and hit the
se
Hi,
I would guess that Mapserver does not care about your BBOX but by the same
you create GetMap requests with &WIDTH= and &HEIGHT= that exceeds the limit
that is configured on the server with MAP-MAXSIZE
https://mapserver.org/mapfile/map.html.
So you must split your requests smaller by the reque
Hi,
I made a couple of simple tests by following
https://trac.osgeo.org/gdal/wiki/CloudOptimizedGeoTIFF, here are the
results:
Create a jpeg compressed GeoTIFF and couple of overviews
gdal_translate -of GTiff -co tiled=yes -co compress=jpeg p4433h.tif
p2-jpeg.tif
gdaladdo --config COMPRESS_OVERV
