Add new exact indicators at grid scale

[ebocher]

Here the list

• [x] ASPECT_RATIO (GeoClimate method https://github.com/orbisgis/geoclimate/wiki/RSU-indicators#aspect_ratio)
• [x] SVF (done with Ground Sky View Factor process)
• [x] HEIGHT_OF_ROUGHNESS_ELEMENTS (Geometric average of building heights (LCZs 1–10) and tree/plant heights (LCZs A–F) (m))
• [x] TERRAIN_ROUGHNESS_CLASS (Davenport et al.’s (2000) classification of effective terrain roughness (z0 ) for city and country landscapes)

@j3r3m1 @MGousseff

[ebocher]

The HEIGHT_OF_ROUGHNESS_ELEMENTS is not yet available because the effectiveTerrainRoughnessLength algorithm must be replaced by frontalAreaIndexDistribution to compute its exact value.

[ebocher]

To limit the number of calls to basic geometric functions such as area, I suggest calculating them when the data is formatted. e.g building layer must contains a column name area, perimeter...

[ebocher]

projectedFacadeAreaDistribution and frontalAreaIndexDistribution do not used the same notation for the result columns.

The first one use XX_INDEX_H50_D0_30 and the second one XX_INDEXH50${layer_top}_D0_30

See : https://github.com/orbisgis/geoclimate/blob/master/geoindicators/src/main/groovy/org/orbisgis/geoclimate/geoindicators/RsuIndicators.groovy#L1940

[j3r3m1]

The first one use XX_INDEX_H50_D0_30 and the second one XX_INDEXH50${layer_top}_D0_30

Seems more relevant to use the second notation: even though it induces longer column names, it is probably simpler to collect informations such as deltaH in the interval in the second case. Should we create an issue to solve this problem ?

[ebocher]

Here we are ;-)