Open mabijkerk opened 1 year ago
Additionally, given the increasing importance of the API, our clients are using the ETSource folders themselves to find specific queries. This increases the need for:
Notifying @ChaelKruip
Nice idea @mabijkerk, would actually also be nice for our own use!
Added to this list is the goal to restructure and link the queries that are used by the Transition Paths tool. Currently, they use separate queries.
This causes difficulties, for example in the agriculture sector where the edge group method to query final demand does include geothermal but the node group method does not. The queries in the ETM therefore use the edge group method, but for some reason, completely new queries have been written for the Transition Paths tool and this detail for geothermal heat has been overlooked. It would be much better if the queries in the Transition Paths tool refer to the same queries that are used in the ETM.
Some input statements that are still used in the datasets but not by the user:
area:
Costs
investment_costs_batteries.ad
investment_costs_electric_boilers.ad
investment_costs_power_to_gas --> Is an empty file Emission --> ccus --> capture
share_of_industry_chemicals_other_captured_co2
I created a script to see if queries where referenced. I have checked for all queries if they where referenced to in the etmodel, etsource and mechanical turk repositories. Around 1300 queries where not referenced in these repositories, I will not post them here, since this will blow up this post. @mabijkerk Are there any other repositories I should check with this script, and where should I post the unreferenced queries?
Some of the inputs and gqueries on ETSource are outdated. It would be useful to clean them up, to avoid clients using inputs and gqueries that are no longer valid.
For example: