Closed jrjdavidson closed 3 years ago
it might be that the paths in the vrt file are relative paths, not absolute?
Hi,
Nested VRTs are surely a no-go currently (tested) - e.g. you cannot run mapproxy-setup-resource
on the resulting DEM produced by the same tool because that contains nested VRTs.
The tool tries to copy the input DEM, there should be an option to just link it but it is not currently implemented. It is meant for simpler cases to be honest.
If gdal_translate
ing the VRT into simgle tiff is an option, it should work. Otherwise I'd fall back to the old approach (generatevrtwo
, mapproxy-calipers
, mapproxy-tiling
, tutorial here ) - it is slightly more complex but you have a complete control over it.
ok thanks again. should i leave this open in case someone else tries this?
Yes, let's leave that open until there are some updates from either side.
You can now use --linkdataset with mapproxy-setup-resource on vrt files
Hi,
I tried using mapproxy-setup-resource on a vrt dataset and got the error below- it looks like vrts are a no go?
Jonathan