You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each "row" is a separate Atmospheric::Result object. You can use geometric altitude or geopotential altitude (with unit) to build the object.
The different tables will obtain their data from this object. Then we don't have to work with Hashes anymore.
classAtmosphericdefself.values_at(parameter_name,unit,value)Atmospheric::Result.new(# ... geopotential_altitude ... unit ...# ... geometric_altitude ... unit ...)endend
classAtmospheric::Result < Lutaml::Model::Serializationattribute:geopotential_altitude,:decimalattribute:geopotential_altitude_unit,:stringattribute:geometric_altitude,:decimalattribute:geometric_altitude_unit,:stringattribute:temperature,:floatattribute:temperature_unit,:stringattribute:ppn,:floatattribute:ppn_unit,:stringattribute:speed_of_sound,:floatattribute:speed_of_sound_unit,:string# ... other result attributesend
The ideal approach should be like this.
Each "row" is a separate
Atmospheric::Result
object. You can use geometric altitude or geopotential altitude (with unit) to build the object.The different tables will obtain their data from this object. Then we don't have to work with Hashes anymore.
Originally posted by @ronaldtse in #42 (comment)
The text was updated successfully, but these errors were encountered: