Closed christianbraun closed 9 years ago
tracked down to mass_import, just happens (as discovered so far) for Ludwigsburg data sets
The DescribeCoverage response in version 1.0.0 is ambiguous, neither the mass_import nor the harvester are able to determine grid resolution properly. For instance this request:
Returns this information:
gml:offsetVector100 0/gml:offsetVector gml:offsetVector0 -100/gml:offsetVector
Whereas this request:
Return this:
I prefer to stick with version 1.1.0 for now and try to resolve this issue some other way.
The request BBOX x,y parameter of a layer derived by WCS calculated by our WPS (e.g. Ludwigsburgs 00_solar_irradiation_02) is switched. We had issues like this constantly...
The mapfile seems to be correct. Probably an issue about how the request is put together form variables in the database.