Hi @Hannah Wheldon,
Most WMS viewer are interactive, so their requests automatically include the bounds of the view they will be displaying the image in. FME has no view, so you must manually set the bounds of the downloaded image in the WMS reader:
If you try the settings shown above, you will get an image with a reasonable pixel spacing:
Hi @Hannah Wheldon,
Most WMS viewer are interactive, so their requests automatically include the bounds of the view they will be displaying the image in. FME has no view, so you must manually set the bounds of the downloaded image in the WMS reader:
If you try the settings shown above, you will get an image with a reasonable pixel spacing:
Hi @daveatsafe . Thanks for your response, that makes sense. I've added in the bounds based off what the metadata says. But how do I know what the map width and height is? Without that, I'm still not getting a spacing of 2m, as I would expect.
Hi @daveatsafe . Thanks for your response, that makes sense. I've added in the bounds based off what the metadata says. But how do I know what the map width and height is? Without that, I'm still not getting a spacing of 2m, as I would expect.
Map width and height is the size of the resulting image in pixels. So if you want a 2m resolution, set the image width to (bounds maximum X - bounds minimum X)/2 and the image height to (bounds maximum Y - bounds minimum Y)/2.
Hi @daveatsafe . Thanks for your response, that makes sense. I've added in the bounds based off what the metadata says. But how do I know what the map width and height is? Without that, I'm still not getting a spacing of 2m, as I would expect.
Thanks so much for this. Unfortunately, they updated the wms and I wasn't able to read it in again but will give this a try when I'm next able
