Even Rouault spatialys.com> writes:
> > and "-spat [xmin ymin xmax
> > ymax]|WKT|datasource" would not be good.
>
> Why ?
Only because I thought that -spat is tightly made to support only
rectangular selections and to make search by bboxes from spatial index if
such exists.
-Jukka-
___
Le vendredi 03 octobre 2014 23:11:31, Jukka Rahkonen a écrit :
> Hi,
>
> There are advanced options in ogr2ogr for clipping features to WKT or to a
> clipping layer. However, there does not seem to be a way to only select
> features without clipping them in a same way. A typical use case would be
Hi,
There are advanced options in ogr2ogr for clipping features to WKT or to a
clipping layer. However, there does not seem to be a way to only select
features without clipping them in a same way. A typical use case would be to
select features from global dataset by country borders. Could this be
Because I didn't see a difference between Tiff and BMP I started testing
some more with the GDALwarp options...
And because the resolution made a difference, I tested with the -r
filters...
When I used an other filter then cubicspline, the problem was gone. So
the problem was a combination wit
Hi Xavier,
there is a couple of options with WCS 2.
- you can request another format which is easier to handle by the client, such
as PNG (builtin browser support).
- you can send a separate DescibeCoverage request and get an XML structure
containing all metadata.
- you can direct the serv
Hi
WCS has the ability to return a coverage as a GeoTiff file. Then if you
want to display or process row data from this file in a Javascript web
client, you need to have to ability to decode the "GeoTiff" part of this
file.
I found a Tiff.js library compiled with Emscripten. I succeed to disp
