XyGrib icon indicating copy to clipboard operation
XyGrib copied to clipboard

Isoline filtering is harsh

Open did-g opened this issue 6 years ago • 4 comments

Hi, Currently isolines rendering is using every nth points which create artefacts: bad isoline

while with all points test1

Options:

  • Always use the full dataset, but it produces jagged lines.
  • Spline lines.
  • DouglasPeucker reduction.

Thoughts?

did-g avatar Nov 25 '19 11:11 did-g

Doesn't look that bad really.

rgleason avatar Nov 25 '19 13:11 rgleason

Capture d’écran de 2019-11-25 18-23-46 I notice quite rarely artefact... Personally I will prefer the use of the full dataset (raw output of the model), creating the artefact. If we start to treat them there is a risk (probably low) to create new artefact or to modify "too much" at least partially the "original output".

dominiquehausser avatar Nov 25 '19 17:11 dominiquehausser

I tend towards using more data points but with some smoothing. Looking at the "big" picture in the Atlantic does not justify the issue. In smaller geographic areas such as the Med West or East basins it is easier to recognise the synoptic pattern with smoothing. This can be seen by comparing GFS (which include smoothing) to ICON that does not.

Splines or reduction? -- Whatever works best and fast.

norulz avatar Nov 30 '19 07:11 norulz

Capture d’écran de 2019-11-30 18-40-06 1 hPa between isolines Capture d’écran de 2019-11-30 18-39-05 4 hPa between isolines (the most frequent presentation of met offices. Smoothing looks nicer, but ... What is GFS using for smoothing ? We should try to use the same to avoid a different bias between the 2 models.

dominiquehausser avatar Nov 30 '19 17:11 dominiquehausser