The metric mesh refinement based on Python-expressions is broken. This is reproducible in one of the test cases (see below). Possible solution: The size field should be sampled in meters (not deg), then projected from UTM to Lon-lat, and finally the data set should be queried.
- Observed output in
NorthSea_metric.pos samples in lon-lat (ignoring the defined projection):
-13.9833 63.95 0
0.0332776867289 -0.0332714923016 1
599 539 1
27789.6
[...]
- Expected output in
NorthSea_metric.pos is a 3D rectangular structured mesh in utm coordinates, which specifies the size field.
The metric mesh refinement based on Python-expressions is broken. This is reproducible in one of the test cases (see below). Possible solution: The size field should be sampled in meters (not deg), then projected from UTM to Lon-lat, and finally the data set should be queried.
Shingle/test/UK_NorthSea_region_opendap_utm_metric/UK_NorthSea_region_opendap_utm_metric.brml
Line 102 in 75c61af
NorthSea_metric.possamples in lon-lat (ignoring the defined projection):NorthSea_metric.posis a 3D rectangular structured mesh in utm coordinates, which specifies the size field.