search

ESA-APEx / apex_algorithms

Hosted APEx algorithms
Apache License 2.0
0 stars 0 forks source link

record algorithm output area in scenario metrics #38

Open jdries opened 1 day ago

jdries commented 1 day ago

output area allows us to compute cost per output area perhaps it's best to have 2 metrics: output pixels, in megapixel output resolution, in m²

Then we can avoid that low resolution algorithms have a seemingly low cost per km², but we can still compute it if we want to?

soxofaan commented 1 day ago

added these two new metrics:

[
        "results:proj:shape:area:megapixel",
        0.033369
      ],
      [
        "results:proj:bbox:area:utm:km2",
        3.3369
      ]

results:proj:shape:area:megapixel comes from batch job result "proj:shape": product of the shape sizes, in megapixel:

https://github.com/ESA-APEx/apex_algorithms/blob/7b1759f7a4fb9f0c784ab796f0b9ebd04b318a52/qa/tools/apex_algorithm_qa_tools/benchmarks.py#L37-L39

results:proj:bbox:area:utm:km2 comes from batch job result "proj:bbox" if "proj:epsg" is a UTM code: area in square km based on UTM coordinates: https://github.com/ESA-APEx/apex_algorithms/blob/7b1759f7a4fb9f0c784ab796f0b9ebd04b318a52/qa/tools/apex_algorithm_qa_tools/benchmarks.py#L41-L46