Version: mapproxy 1.35 (built on Jul 13 2018 12:57:52 at pomerol)
The geodata-vector driver never sets the config.workingSrs or config.rasterDsSrs fields in the config struct provided to the heightCode() function. So it always fails because the heightCode() function seem to require it.
vts-mapproxy_1 | 2018-11-06 11:37:50 I2 [9(gdal:1)]: OGRGeoJSON: 9 points, 0 (multi)linestrings, 0 (multi)polygons. {featurelayers.cpp:load():376}
vts-mapproxy_1 | 2018-11-06 11:37:50 I2 [9(gdal:1)]: No hint given as to what SRS to use in heightcoding. {heightcoding.cpp:heightCode():69}
vts-mapproxy_1 | 2018-11-06 11:37:50 I2 [9(gdal:1)]: Warped DEM to 1016x641 pixels at [12.5,12.5] resolution. {featurelayers.cpp:heightcode():522}
vts-mapproxy_1 | 2018-11-06 11:37:50 W2 [6(prepare:4)]: Failed to prepare generator for <sweden/test1/mypoints> (Could not obtain DEM value.); removing from set of known generators. {generator.cpp:operator()():580}
The geodata-vector-tiled driver does not suffer from this as it sets the workingSrs field.
Version: mapproxy 1.35 (built on Jul 13 2018 12:57:52 at pomerol)
The
geodata-vectordriver never sets theconfig.workingSrsorconfig.rasterDsSrsfields in the config struct provided to theheightCode()function. So it always fails because the heightCode() function seem to require it.The
geodata-vector-tileddriver does not suffer from this as it sets theworkingSrsfield.