On Sat, Oct 20, 2018 at 9:58 PM Jonathan Moules <
jonathan-li...@lightpear.com> wrote:
> Hi Lists,
>
> I'm cross posting this to GeoServer-Users over from QGIS-Dev as the
> current QGIS code seems to be trying to work around a GeoServer quirk
> based on Nyall's code-comment snippet.
>
> Is there
Hi Lists,
I'm cross posting this to GeoServer-Users over from QGIS-Dev as the
current QGIS code seems to be trying to work around a GeoServer quirk
based on Nyall's code-comment snippet.
Is there something different QGIS can do to work around the stated issue
in a better way given I guess
I don't remember more than i wrote in comments and i don't know if it is
still necessary. Better to keep it i think, but it could be done optional.
Radim
On Oct 15, 2018 01:54, "Nyall Dawson" wrote:
> On Fri, 12 Oct 2018 at 20:48, Richard Duivenvoorde
> wrote:
> > which is the whole of the
On Fri, 12 Oct 2018 at 20:48, Richard Duivenvoorde wrote:
> which is the whole of the Netherlands (in a 10x10 pixel output??) and
> after that a more proper bbox.
I can't explain the background here, but it seems deliberate. There's
a comment before this request is made:
"
// It may happen
Hi Richard,
I don't know about the QGIS side, but from the server side I'd agree
with your assessment.
The WCS 1.0 spec says that the server will use the interpolation method
specified in the getcapabilities (or if none is defined (as here), then
assume Nearest Neighbour) for alternative
Hi,
using our national DEM WCS:
https://geodata.nationaalgeoregister.nl/ahn3/wcs?
Loading the layer ahn3_5m_dtm for an area of a couple of km in
epsg:28992 is very slow.
I'm not so familiar with the WCS specs, but I see QGIS asking:
