It could be useful to summon the ORBIT turbine library from a python package. This would involve moving the turbine library (https://github.com/WISDEM/ORBIT/tree/dev/library/turbines) to within the installed ORBIT package.
WindIO has suggested a turbine schema which seems well suited for this application: https://github.com/IEAWindTask37/windIO/blob/main/windIO/plant/turbine.yaml. If you wind up hosting this python turbine library, would you be open to using the WindIO schema? We could update it to include the additional fields that ORBIT requires.
I notice that these turbines could be translated into a more refined schema and moved to an installable python package: https://github.com/NREL/turbine-models/. Do you have any interest in including these definitions? It would be straight-forward to translate these data into the windIO turbine schema.
It could be useful to summon the ORBIT turbine library from a python package. This would involve moving the turbine library (https://github.com/WISDEM/ORBIT/tree/dev/library/turbines) to within the installed ORBIT package.
WindIO has suggested a turbine schema which seems well suited for this application: https://github.com/IEAWindTask37/windIO/blob/main/windIO/plant/turbine.yaml. If you wind up hosting this python turbine library, would you be open to using the WindIO schema? We could update it to include the additional fields that ORBIT requires.
I notice that these turbines could be translated into a more refined schema and moved to an installable python package: https://github.com/NREL/turbine-models/. Do you have any interest in including these definitions? It would be straight-forward to translate these data into the windIO turbine schema.