At the moment we have a aligner.get_formula()-function that transforms a geometry in a json-discription of the geometry based on all the reference-geometries. This can be used generic.
Example of the current formula-structure:
As we notice, when using this formula for GRB-purposes we need to enrich this formula with GRB-specific attributes (f.e. version_date)
So at the moment the formula-function-code becomes a mix between generic and GRB-specific elements
What would be the best structure to seperate the generic from the GRB-specific so it is more future-proof?
At the moment we have a aligner.get_formula()-function that transforms a geometry in a json-discription of the geometry based on all the reference-geometries. This can be used generic.
Example of the current formula-structure:
As we notice, when using this formula for GRB-purposes we need to enrich this formula with GRB-specific attributes (f.e. version_date)
So at the moment the formula-function-code becomes a mix between generic and GRB-specific elements What would be the best structure to seperate the generic from the GRB-specific so it is more future-proof?