search

eurodatacube / eodash

Software behind the RACE dashboard by ESA and the European Commission (https://race.esa.int), the Green Transition Information Factory - GTIF (https://gtif.esa.int), as well as the Earth Observing Dashboard by NASA, ESA, and JAXA (https://eodashboard.org)
https://race.esa.int
MIT License
89 stars 43 forks source link

Using Airquality Ozone at city level model, Hamburg is in wrong location #2527

Closed AlessandroScremin closed 2 months ago

AlessandroScremin commented 3 months ago

@lubojr

Race staging ui-panels

I see for ozone city model in Hambur is out of region (Russia), Icheched on operational Race dashboard and location os correct.

image

lubojr commented 3 months ago

This is data coming from GeoDB in table N1d. Could you please check the aoi field it there?

lubojr commented 3 months ago

hamburg "correct" coordinates are 53N10E

It happened like this but on a scale of last decimal of longitude for the last 2 months of data due to the fact that someone was probably doing this in Excel and was "dragging all the "same" columns while Excel interpretted that as a series with 1 autoincrement on the last position of the string while its hould have been the same string for further rows. Which for Berlin is 2 decimal digits but for Hamburg it is 0 decimal digits, so it ended up being in Kazachstan image (this is already in the original CAMS NO2 CSVs, not only in GeoDB)

Btw, this is true for all datasets N1a, N1b, N1c, N1d and all pois but for most of them only on the level of decimal minutes, so not so heavily problematic.

lubojr commented 2 months ago

@dmoglioni @AlessandroScremin as a summary, this should be fixed on GeoDB side, because our tooling takes the last row coordinate for a single POI, therefore the incorrect value caused by CAMS data updates error.

dmoglioni commented 2 months ago

@lubojr A clarification: is this indicator regularly updated or was it just a one-time ingestion? Because I cannot find it on the automated workflows I manage.

lubojr commented 2 months ago

@dmoglioni No the indicators N1a, N1b, N1c, N1d are not regularly updated anymore. They were one-off ingested as part of migration of original CSVs which were in eodash repo.

dmoglioni commented 2 months ago

@lubojr Hamburg AOI coordinates have been fixed for N1a/b/c/d, could you please cross-check it? Thanks

lubojr commented 2 months ago

@dmoglioni Thank you! I have tried a local build and confirm that the Hamburg AOI coordinates generated are correct now. I will re-trigger a catalog build to propagate the geodb update to the production catalog. Closing the issue.