coders2iamc 1.0.0__tar.gz

coders2iamc-1.0.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 SESIT
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

coders2iamc-1.0.0/PKG-INFO

@@ -0,0 +1,112 @@
+Metadata-Version: 2.2
+Name: coders2iamc
+Version: 1.0.0
+Summary: Scripts that pull data from the CODERS database and format it for use in the IAMC format
+Home-page: https://gitlab.com/sesit/coders-to-iamc
+Classifier: Programming Language :: Python :: 3
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pandas>=2.2.1
+Dynamic: classifier
+Dynamic: description
+Dynamic: description-content-type
+Dynamic: home-page
+Dynamic: requires-dist
+Dynamic: requires-python
+Dynamic: summary
+
+# CODERS to IAMC
+
+
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin https://gitlab.com/sesit/coders-to-iamc.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+- [ ] [Set up project integrations](https://gitlab.com/sesit/coders-to-iamc/-/settings/integrations)
+
+## Collaborate with your team
+
+- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
+- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
+- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
+- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
+- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

coders2iamc-1.0.0/README.md

@@ -0,0 +1,93 @@
+# CODERS to IAMC
+
+
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin https://gitlab.com/sesit/coders-to-iamc.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+- [ ] [Set up project integrations](https://gitlab.com/sesit/coders-to-iamc/-/settings/integrations)
+
+## Collaborate with your team
+
+- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
+- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
+- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
+- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
+- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

coders2iamc-1.0.0/coders2iamc.egg-info/PKG-INFO

@@ -0,0 +1,112 @@
+Metadata-Version: 2.2
+Name: coders2iamc
+Version: 1.0.0
+Summary: Scripts that pull data from the CODERS database and format it for use in the IAMC format
+Home-page: https://gitlab.com/sesit/coders-to-iamc
+Classifier: Programming Language :: Python :: 3
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pandas>=2.2.1
+Dynamic: classifier
+Dynamic: description
+Dynamic: description-content-type
+Dynamic: home-page
+Dynamic: requires-dist
+Dynamic: requires-python
+Dynamic: summary
+
+# CODERS to IAMC
+
+
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin https://gitlab.com/sesit/coders-to-iamc.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+- [ ] [Set up project integrations](https://gitlab.com/sesit/coders-to-iamc/-/settings/integrations)
+
+## Collaborate with your team
+
+- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
+- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
+- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
+- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
+- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

coders2iamc-1.0.0/coders2iamc.egg-info/SOURCES.txt

@@ -0,0 +1,28 @@
+LICENSE
+README.md
+setup.py
+coders2iamc.egg-info/PKG-INFO
+coders2iamc.egg-info/SOURCES.txt
+coders2iamc.egg-info/dependency_links.txt
+coders2iamc.egg-info/requires.txt
+coders2iamc.egg-info/top_level.txt
+coders_to_iamc/__init__.py
+coders_to_iamc/ca_system_parameters.py
+coders_to_iamc/capacity_factors.py
+coders_to_iamc/constants.py
+coders_to_iamc/cost.py
+coders_to_iamc/demand.py
+coders_to_iamc/forecasted_annual_demand.py
+coders_to_iamc/generation_cost_evolution.py
+coders_to_iamc/generation_planning_reserve.py
+coders_to_iamc/generators.py
+coders_to_iamc/grid_cells.py
+coders_to_iamc/hydro_greenfield.py
+coders_to_iamc/hydro_pump_storage.py
+coders_to_iamc/hydro_renewal.py
+coders_to_iamc/nodes.py
+coders_to_iamc/provincial_transfers.py
+coders_to_iamc/storage.py
+coders_to_iamc/technology_parameters.py
+coders_to_iamc/transmission.py
+coders_to_iamc/transmission_generic.py

coders2iamc-1.0.0/coders2iamc.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

coders2iamc-1.0.0/coders2iamc.egg-info/requires.txt

@@ -0,0 +1 @@
+pandas>=2.2.1

coders2iamc-1.0.0/coders2iamc.egg-info/top_level.txt

@@ -0,0 +1 @@
+coders_to_iamc

coders2iamc-1.0.0/coders_to_iamc/ca_system_parameters.py

@@ -0,0 +1,33 @@
+import json
+from urllib.request import urlopen
+import pandas as pd
+
+from coders_to_iamc.constants import CODERS
+
+mappings = {
+    'reserve_requirements_percent': 'Reserve Requirements Percentage',
+    'system_line_losses_percent': 'System Line Losses Percentage',
+    'water_rentals_CAD_per_MWh': 'Water Rentals',
+}
+
+
+def get_data(api_key: str):
+    """
+    This function is used to get the technology parameter data from the CODERS API
+    """
+    with urlopen(f"http://206.12.95.102/CA_system_parameters?key={api_key}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+
+    modeled_attributes = modeled_attributes.drop(columns=['notes'])
+
+    melted = modeled_attributes.melt(id_vars=['province'], var_name='variable', value_name='value')
+    melted['variable'] = melted['variable'].map(mappings)
+    melted = melted.rename(columns={'province': 'region'})
+    return melted
+
+
+if __name__ == '__main__':
+    api_key = ''
+    df = get_data(api_key)

coders2iamc-1.0.0/coders_to_iamc/capacity_factors.py

@@ -0,0 +1,67 @@
+import json
+from urllib.request import urlopen
+import pandas as pd
+
+
+def get_hydro_data(api_key: str, province, year):
+    """
+    This function is used to get the hydro capacity factor data from the CODERS API
+    """
+    with urlopen(f"http://206.12.95.102/hydro_capacity_factor?key={api_key}&province={province}&year={year}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+
+    modeled_attributes = modeled_attributes[
+        ['province', 'local_time', 'capacity_factor']]
+    melted = modeled_attributes.melt(id_vars=['local_time', 'province'], var_name='variable', value_name='value')
+
+    melted['variable'] = 'Hydro Capacity Factor'
+    melted.rename(columns={'province': 'region', 'local_time':'time'}, inplace=True)
+    return melted
+
+def get_wind_solar_data(api_key: str, year):
+    """
+    This function is used to get the VRE capacity factor data from the CODERS API
+    """
+    with urlopen(f"http://206.12.95.102/grid_cell_info?key={api_key}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        grid_cell = pd.json_normalize(json_response)
+        grid_cell = grid_cell[['longitude', 'latitude', 'balancing_area','grid_cell']]
+
+
+    wind = pd.read_csv(f'http://206.12.95.102/wind_capacity_factor?year=2021&key={api_key}&year={year}', index_col=0)
+    wind.index = wind.index-1
+    wind.index = pd.to_datetime(year, format='%Y') + pd.to_timedelta(wind.index, unit='h')
+
+    wind = wind.T
+    wind.index = wind.index.astype(int)
+    wind = pd.merge(wind, grid_cell, left_index=True, right_on='grid_cell')
+    wind['variable'] = 'VRE Capacity Factor|Wind|' + wind['grid_cell'].astype(str) + '|' + wind['latitude'].astype(str) + '_' + wind['longitude'].astype(str)
+    wind = wind.drop(columns=['latitude', 'longitude','grid_cell'])
+    wind.rename(columns={'balancing_area': 'region'}, inplace=True)
+
+    wind_melted = wind.melt(id_vars=['variable', 'region'], var_name='time', value_name='value')
+
+
+    solar = pd.read_csv(f'http://206.12.95.102/solar_capacity_factor?year=2021&key={api_key}&year={year}', index_col=0)
+    solar.index = solar.index-1
+    solar.index = pd.to_datetime(year, format='%Y') + pd.to_timedelta(solar.index, unit='h')
+
+    solar = solar.T
+    solar.index = solar.index.astype(int)
+    solar = pd.merge(solar, grid_cell, left_index=True, right_on='grid_cell')
+    solar['variable'] = 'VRE Capacity Factor|Solar|' + solar['grid_cell'].astype(str) + '|' + solar['latitude'].astype(str) + '_' + solar['longitude'].astype(str)
+    solar = solar.drop(columns=['latitude', 'longitude','grid_cell'])
+    solar.rename(columns={'balancing_area': 'region'}, inplace=True)
+
+    solar_melted = solar.melt(id_vars=['variable', 'region'], var_name='time', value_name='value')
+
+    all_cf = pd.concat([wind_melted, solar_melted], ignore_index=True)
+    return all_cf
+
+if __name__ == '__main__':
+    api_key = 'UcnLMTPYRCAfS9Au'
+    # df = get_hydro_data(api_key, 'AB', 2021)
+    df2 = get_wind_solar_data(api_key, 2021)

coders2iamc-1.0.0/coders_to_iamc/constants.py

@@ -0,0 +1 @@
+CODERS = 'https://api.sesit.ca/'

coders2iamc-1.0.0/coders_to_iamc/cost.py

@@ -0,0 +1,31 @@
+from urllib.request import urlopen
+import pandas as pd
+import json
+
+mappings = {
+    'average_fuel_price_CAD_per_MMBtu': 'Cost|Fuel|',
+    'variable_om_costs': 'Cost|Variable O&M|',
+}
+
+def get_data(api_key: str):
+    with urlopen(f"https://api.sesit.ca/generation_generic?key={api_key}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+
+    modeled_attributes = modeled_attributes[
+        ['variable_om_costs', 'average_fuel_price_CAD_per_MMBtu', 'gen_type_copper']]
+    modeled_attributes['average_fuel_price_CAD_per_MMBtu'] = modeled_attributes[
+                                                                 'average_fuel_price_CAD_per_MMBtu'].astype(float)
+    melted = modeled_attributes.melt(id_vars=['gen_type_copper'], var_name='variable', value_name='value')
+
+    melted['variable'] = melted['variable'].map(mappings)
+    melted['variable'] = melted['variable'] + melted['gen_type_copper'].astype(str)
+    melted = melted.drop(columns=['gen_type_copper'])
+
+    return melted
+
+if __name__ == '__main__':
+    api_key = ''
+    df = get_data(api_key)
+    print(df)

coders2iamc-1.0.0/coders_to_iamc/demand.py

@@ -0,0 +1,62 @@
+import json
+from urllib.request import urlopen
+import pandas as pd
+
+from coders_to_iamc.constants import CODERS
+
+
+def get_canadian_data(api_key: str, province: str, year: int):
+    """
+    This function is used to get the technology parameter data from the CODERS API
+    """
+    with urlopen(f"{CODERS}/provincial_demand?key={api_key}&province={province}&year={year}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+
+    modeled_attributes = modeled_attributes[
+        ['local_time', 'demand_MWh', 'province']]
+    melted = modeled_attributes.melt(id_vars=['local_time', 'province'], var_name='variable', value_name='value')
+
+    melted['variable'] = 'Demand'
+    melted.rename(columns={'province': 'region', 'local_time':'time'}, inplace=True)
+    return melted
+
+def get_us_data(api_key: str, province: str, year: int):
+    """
+    This function is used to get the technology parameter data from the CODERS API
+    """
+    with urlopen(f"{CODERS}/international_transfers?key={api_key}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+
+    states = modeled_attributes[modeled_attributes['province'] == province]['us_state'].unique()
+
+    if len(states) == 0:
+        return pd.DataFrame()
+
+    states_data = []
+    for state in states:
+        with urlopen(f"{CODERS}/international_transfers?key={api_key}&province={province}&us_state={state}&year={year}") as response:
+            response_content = response.read()
+            json_response = json.loads(response_content)
+            modeled_attributes = pd.json_normalize(json_response)
+
+        modeled_attributes = modeled_attributes[
+            ['local_time', 'transfers_MWh', 'province']]
+        melted = modeled_attributes.melt(id_vars=['local_time', 'province'], var_name='variable', value_name='value')
+
+        melted['variable'] = 'US Demand'
+        melted.rename(columns={'province': 'region', 'local_time':'time'}, inplace=True)
+        states_data.append(melted)
+
+    full_df = pd.concat(states_data)
+
+    full_df = full_df.groupby(['time', 'region', 'variable']).sum().reset_index()
+    return full_df
+
+
+if __name__ == '__main__':
+    api_key = ''
+    df = get_canadian_data(api_key, 'AB', 2018)

coders2iamc-1.0.0/coders_to_iamc/forecasted_annual_demand.py

@@ -0,0 +1,34 @@
+import json
+from urllib.request import urlopen
+import pandas as pd
+
+from coders_to_iamc.constants import CODERS
+
+mappings = {
+    'latitude': 'Generators|Latitude|',
+    'longitude': 'Generators|Longitude|',
+    'unit_installed_capacity': 'Generators|Capacity|',
+    'network_node_code': 'Generators|Node Code|',
+}
+
+
+def get_data(api_key: str):
+    """
+    This function is used to get the technology parameter data from the CODERS API
+    """
+    with urlopen(f"http://206.12.95.102/forecasted_annual_demand?key={api_key}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+
+    melted = modeled_attributes.melt(id_vars=['province', 'unit'],
+                                     var_name='time', value_name='value')
+
+    melted['variable'] = 'Forecasted Annual Demand'
+    melted.rename(columns={'province': 'region'}, inplace=True)
+    return melted
+
+
+if __name__ == '__main__':
+    api_key = ''
+    df = get_data(api_key)

coders2iamc-1.0.0/coders_to_iamc/generation_cost_evolution.py

@@ -0,0 +1,36 @@
+import json
+from urllib.request import urlopen
+import pandas as pd
+
+from coders_to_iamc.constants import CODERS
+
+mappings = {
+    'reserve_requirements_percent': 'Reserve Requirements Percentage',
+    'system_line_losses_percent': 'System Line Losses Percentage',
+    'water_rentals_CAD_per_MWh': 'Water Rentals',
+}
+
+
+def get_data(api_key: str):
+    """
+    This function is used to get the technology parameter data from the CODERS API
+    """
+    with urlopen(f"http://206.12.95.102/generation_cost_evolution?key={api_key}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+
+    columns = ['gen_type_copper']
+    # keep any columns that start with a year
+    columns.extend([col for col in modeled_attributes.columns if col.startswith('20')])
+    modeled_attributes = modeled_attributes[columns]
+    melted = modeled_attributes.melt(id_vars=['gen_type_copper'], var_name='time', value_name='value')
+    melted['time'] = melted['time'].apply(lambda x: int(x[:4]))
+    melted['variable'] = 'Generation Cost Evolution' + '|' + melted['gen_type_copper']
+    melted = melted.drop(columns=['gen_type_copper'])
+    return melted
+
+
+if __name__ == '__main__':
+    api_key = ''
+    df = get_data(api_key)

coders2iamc-1.0.0/coders_to_iamc/generation_planning_reserve.py

@@ -0,0 +1,34 @@
+import json
+from urllib.request import urlopen
+import pandas as pd
+
+from coders_to_iamc.constants import CODERS
+
+mappings = {
+    'winter_wind': 'Planning Reserve|Wind|Winter',
+    'winter_solar': 'Planning Reserve|Solar|Winter',
+    'summer_wind': 'Planning Reserve|Wind|Summer',
+    'summer_solar': 'Planning Reserve|Solar|Summer',
+}
+
+
+def get_data(api_key: str):
+    """
+    This function is used to get the technology parameter data from the CODERS API
+    """
+    with urlopen(f"http://206.12.95.102/generation_planning_reserve?key={api_key}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+
+    melted = modeled_attributes.melt(id_vars=['province'],
+                                     var_name='variable', value_name='value')
+
+    melted['variable'] = melted['variable'].map(mappings)
+    melted.rename(columns={'province': 'region'}, inplace=True)
+    return melted
+
+
+if __name__ == '__main__':
+    api_key = ''
+    df = get_data(api_key)

coders2iamc-1.0.0/coders_to_iamc/generators.py

@@ -0,0 +1,43 @@
+import json
+from urllib.request import urlopen
+import pandas as pd
+
+from coders_to_iamc.constants import CODERS
+
+mappings = {
+    'latitude': 'Generators|Latitude|',
+    'longitude': 'Generators|Longitude|',
+    'unit_installed_capacity': 'Generators|Capacity|',
+    'network_node_code': 'Generators|Node Code|',
+    'previous_renewal_year': 'Generators|Previous Renewal Year|',
+    'possible_renewal_year': 'Generators|Possible Renewal Year|',
+    'closure_year': 'Generators|Closure Year|',
+}
+
+
+def get_data(api_key: str):
+    """
+    This function is used to get the technology parameter data from the CODERS API
+    """
+    with urlopen(f"{CODERS}/generators?key={api_key}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+
+    modeled_attributes = modeled_attributes[
+        ['generation_unit_code', 'gen_type_copper', 'copper_balancing_area', 'latitude', 'longitude', 'unit_installed_capacity',
+         'network_node_code', 'start_year', 'previous_renewal_year', 'possible_renewal_year', 'closure_year']]
+    melted = modeled_attributes.melt(id_vars=['gen_type_copper', 'generation_unit_code', 'copper_balancing_area', 'start_year'],
+                                     var_name='variable', value_name='value')
+
+    melted['variable'] = melted['variable'].map(mappings)
+    melted['variable'] = melted['variable'] + melted['gen_type_copper'] + '|' + melted['generation_unit_code'] + '|' + \
+                         melted['start_year'].astype(str)
+    melted = melted.drop(columns=['gen_type_copper', 'generation_unit_code', 'start_year'])
+    melted.rename(columns={'copper_balancing_area': 'region'}, inplace=True)
+    return melted
+
+
+if __name__ == '__main__':
+    api_key = ''
+    df = get_data(api_key)

coders2iamc-1.0.0/coders_to_iamc/grid_cells.py

@@ -0,0 +1,34 @@
+import json
+from urllib.request import urlopen
+import pandas as pd
+
+from coders_to_iamc.constants import CODERS
+
+mappings = {
+    'longitude': 'Grid Cell|Longitude',
+    'latitude': 'Grid Cell|Latitude',
+    'province': 'Grid Cell|Province',
+    'distance_to_grid': 'Grid Cell|Distance to Grid',
+    'population': 'Grid Cell|Population',
+    'surface_area_offshore': 'Grid Cell|Surface Area Offshore',
+    'surface_area_onshore': 'Grid Cell|Surface Area Onshore',
+}
+
+
+def get_data(api_key: str):
+    """
+    This function is used to get the technology parameter data from the CODERS API
+    """
+    with urlopen(f"http://206.12.95.102/grid_cell_info?key={api_key}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+    melted = modeled_attributes.melt(id_vars=['grid_cell', 'balancing_area'], var_name='variable', value_name='value').rename(columns={'balancing_area': 'region'})
+    melted['variable'] = melted['variable'].map(mappings) + '|' + melted['grid_cell'].astype(str)
+    melted = melted.drop(columns=['grid_cell'])
+    return melted
+
+
+if __name__ == '__main__':
+    api_key = ''
+    df = get_data(api_key)

coders2iamc-1.0.0/coders_to_iamc/hydro_greenfield.py

@@ -0,0 +1,46 @@
+import json
+from urllib.request import urlopen
+import pandas as pd
+
+from coders_to_iamc.constants import CODERS
+
+mappings = {
+    'greenfield_facility_code': 'Hydro Greenfield|Facility Code|',
+    'network_node_voltage': 'Hydro Greenfield|Network Node Voltage|',
+    'distance_to_market_grid': 'Hydro Greenfield|Distance to Market Grid|',
+    'facility_installed_capacity': 'Hydro Greenfield|Installed Capacity|',
+    'minimum_generation': 'Hydro Greenfield|Minimum Generation|',
+    'annualized_project_costs': 'Hydro Greenfield|Annualized Project Costs|',
+    'fixed_om_costs': 'Hydro Greenfield|Fixed OM Costs|',
+    'variable_om_costs': 'Hydro Greenfield|Variable OM Costs|',
+    'development_time': 'Hydro Greenfield|Development Time|',
+}
+
+
+def get_data(api_key: str):
+    """
+    This function is used to get the technology parameter data from the CODERS API
+    """
+    with urlopen(f"{CODERS}/hydro_greenfield?key={api_key}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+
+    modeled_attributes = modeled_attributes[
+        ['greenfield_facility_name', 'greenfield_facility_code',
+         'copper_balancing_area', 'network_node_voltage', 'distance_to_market_grid', 'gen_type_copper',
+         'facility_installed_capacity', 'minimum_generation', 'distance_to_market_grid', 'annualized_project_costs',
+         'fixed_om_costs', 'variable_om_costs', 'development_time']
+    ]
+
+    melted = modeled_attributes.melt(id_vars=['gen_type_copper', 'greenfield_facility_name', 'copper_balancing_area'], var_name='variable', value_name='value')
+    melted['variable'] = melted['variable'].map(mappings)
+    melted['variable'] = melted['variable'] + melted['gen_type_copper'] + '|' + melted['greenfield_facility_name']
+    melted = melted.rename(columns={'copper_balancing_area': 'region'})
+    melted = melted.drop(columns=['gen_type_copper', 'greenfield_facility_name'])
+    return melted
+
+
+if __name__ == '__main__':
+    api_key = ''
+    df = get_data(api_key)

coders2iamc-1.0.0/coders_to_iamc/hydro_pump_storage.py

@@ -0,0 +1,46 @@
+import json
+from urllib.request import urlopen
+import pandas as pd
+
+from coders_to_iamc.constants import CODERS
+
+mappings = {
+    'storage_facility_code': 'Hydro Pumped Storage|Facility Code|',
+    'network_node_voltage': 'Hydro Pumped Storage|Network Node Voltage|',
+    'distance_to_market_grid': 'Hydro Pumped Storage|Distance to Market Grid|',
+    'facility_installed_capacity': 'Hydro Pumped Storage|Installed Capacity|',
+    'minimum_generation': 'Hydro Pumped Storage|Minimum Generation|',
+    'annualized_project_costs': 'Hydro Pumped Storage|Annualized Project Costs|',
+    'fixed_om_costs': 'Hydro Pumped Storage|Fixed OM Costs|',
+    'variable_om_costs': 'Hydro Pumped Storage|Variable OM Costs|',
+    'development_time': 'Hydro Pumped Storage|Development Time|',
+}
+
+
+def get_data(api_key: str):
+    """
+    This function is used to get the technology parameter data from the CODERS API
+    """
+    with urlopen(f"{CODERS}/hydro_pumped_storage?key={api_key}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+
+    modeled_attributes = modeled_attributes[
+        ['storage_facility_name', 'storage_facility_code',
+         'copper_balancing_area', 'network_node_voltage', 'distance_to_market_grid', 'storage_type_copper',
+         'facility_installed_capacity', 'minimum_generation', 'distance_to_market_grid', 'annualized_project_costs',
+         'fixed_om_costs', 'variable_om_costs', 'development_time']
+    ]
+
+    melted = modeled_attributes.melt(id_vars=['storage_type_copper', 'storage_facility_name', 'copper_balancing_area'], var_name='variable', value_name='value')
+    melted['variable'] = melted['variable'].map(mappings)
+    melted['variable'] = melted['variable'] + melted['storage_type_copper'] + '|' + melted['storage_facility_name']
+    melted = melted.rename(columns={'copper_balancing_area': 'region'})
+    melted = melted.drop(columns=['storage_type_copper', 'storage_facility_name'])
+    return melted
+
+
+if __name__ == '__main__':
+    api_key = ''
+    df = get_data(api_key)

coders2iamc-1.0.0/coders_to_iamc/hydro_renewal.py

@@ -0,0 +1,46 @@
+import json
+from urllib.request import urlopen
+import pandas as pd
+
+from coders_to_iamc.constants import CODERS
+
+mappings = {
+    'renewal_facility_code': 'Hydro Renewal|Facility Code|',
+    'network_node_voltage': 'Hydro Renewal|Network Node Voltage|',
+    'distance_to_market_grid': 'Hydro Renewal|Distance to Market Grid|',
+    'facility_installed_capacity': 'Hydro Renewal|Installed Capacity|',
+    'minimum_generation': 'Hydro Renewal|Minimum Generation|',
+    'annualized_project_costs': 'Hydro Renewal|Annualized Project Costs|',
+    'fixed_om_costs': 'Hydro Renewal|Fixed OM Costs|',
+    'variable_om_costs': 'Hydro Renewal|Variable OM Costs|',
+    'development_time': 'Hydro Renewal|Development Time|',
+}
+
+
+def get_data(api_key: str):
+    """
+    This function is used to get the technology parameter data from the CODERS API
+    """
+    with urlopen(f"{CODERS}/hydro_renewal?key={api_key}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+
+    modeled_attributes = modeled_attributes[
+        ['renewal_facility_name', 'renewal_facility_code',
+         'copper_balancing_area', 'network_node_voltage', 'distance_to_market_grid', 'gen_type_copper',
+         'facility_installed_capacity', 'minimum_generation', 'distance_to_market_grid', 'annualized_project_costs',
+         'fixed_om_costs', 'variable_om_costs', 'development_time','facility_installed_capacity']
+    ]
+
+    melted = modeled_attributes.melt(id_vars=['gen_type_copper', 'renewal_facility_name', 'copper_balancing_area'], var_name='variable', value_name='value')
+    melted['variable'] = melted['variable'].map(mappings)
+    melted['variable'] = melted['variable'] + melted['gen_type_copper'] + '|' + melted['renewal_facility_name']
+    melted = melted.rename(columns={'copper_balancing_area': 'region'})
+    melted = melted.drop(columns=['gen_type_copper', 'renewal_facility_name'])
+    return melted
+
+
+if __name__ == '__main__':
+    api_key = ''
+    df = get_data(api_key)

coders2iamc-1.0.0/coders_to_iamc/nodes.py

@@ -0,0 +1,36 @@
+import json
+from urllib.request import urlopen
+import pandas as pd
+
+from coders_to_iamc.constants import CODERS
+
+mappings = {
+    'latitude': 'Nodes|Latitude|',
+    'longitude': 'Nodes|Longitude|',
+}
+
+
+
+def get_data(api_key: str):
+    """
+    This function is used to get the technology parameter data from the CODERS API
+    """
+    with urlopen(f"{CODERS}/nodes?key={api_key}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+
+    modeled_attributes = modeled_attributes[
+        ['node_code', 'latitude', 'longitude', 'copper_balancing_area']]
+    melted = modeled_attributes.melt(id_vars=['node_code', 'copper_balancing_area'], var_name='variable', value_name='value')
+
+    melted['variable'] = melted['variable'].map(mappings)
+    melted['variable'] = melted['variable'] + melted['node_code']
+    melted = melted.drop(columns=['node_code'])
+    melted.rename(columns={'copper_balancing_area': 'region'}, inplace=True)
+    return melted
+
+
+if __name__ == '__main__':
+    api_key = ''
+    df = get_data(api_key)

coders2iamc-1.0.0/coders_to_iamc/provincial_transfers.py

@@ -0,0 +1,31 @@
+import json
+from urllib.request import urlopen
+import pandas as pd
+
+from coders_to_iamc.constants import CODERS
+
+
+
+def get_data(api_key: str):
+    """
+    This function is used to get the technology parameter data from the CODERS API
+    """
+    with urlopen(f"{CODERS}/transfer_capacities_copper?key={api_key}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+
+    modeled_attributes = modeled_attributes[
+        ['from_balancing_area', 'to_balancing_area', 'ttc_winter']
+    ].rename(columns={'from_balancing_area': 'region', 'to_balancing_area': 'variable', 'ttc_winter': 'value'})
+
+    modeled_attributes['region'] = modeled_attributes['region'].str.rstrip('.')
+    modeled_attributes['variable'] = modeled_attributes['variable'].str.rstrip('.')
+
+    modeled_attributes['variable'] = 'Inter-Provincial Transmission|Capacity|' + modeled_attributes['variable']
+    return modeled_attributes
+
+
+if __name__ == '__main__':
+    api_key = ''
+    df = get_data(api_key)

coders2iamc-1.0.0/coders_to_iamc/storage.py

@@ -0,0 +1,43 @@
+import json
+from urllib.request import urlopen
+import pandas as pd
+
+from coders_to_iamc.constants import CODERS
+
+mappings = {
+    'latitude': 'Generators|Latitude|',
+    'longitude': 'Generators|Longitude|',
+    'storage_capacity': 'Generators|Capacity|',
+    'storage_energy': 'Generators|Storage Energy|',
+    'network_node_code': 'Generators|Node Code|',
+}
+
+def get_data(api_key: str):
+    """
+    This function is used to get the technology parameter data from the CODERS API
+    """
+    with urlopen(f"{CODERS}/storage?key={api_key}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+
+    modeled_attributes = modeled_attributes[
+        ['storage_facility_code', 'storage_type_copper', 'storage_capacity', 'storage_energy', 'network_node_code',
+         'copper_balancing_area', 'latitude', 'longitude', 'start_year']]
+
+    melted = modeled_attributes.melt(id_vars=['storage_type_copper', 'storage_facility_code', 'copper_balancing_area', 'start_year'],
+                                     var_name='variable', value_name='value')
+
+    
+    melted['variable'] = melted['variable'].map(mappings)
+    melted['variable'] = melted['variable'] + melted['storage_type_copper'] + '|' + melted[
+        'storage_facility_code'] + '|' + melted['start_year'].astype(str)
+    melted = melted.drop(columns=['storage_type_copper', 'storage_facility_code', 'start_year'])
+    melted.rename(columns={'copper_balancing_area': 'region'}, inplace=True)
+
+    return melted
+
+
+if __name__ == '__main__':
+    api_key = ''
+    df = get_data(api_key)

coders2iamc-1.0.0/coders_to_iamc/technology_parameters.py

@@ -0,0 +1,47 @@
+import json
+from urllib.request import urlopen
+import pandas as pd
+
+from coders_to_iamc.constants import CODERS
+
+mappings = {
+    'startup_cost': 'Technology Parameter|Start Up Cost|',
+    'shutdown_cost': 'Technology Parameter|Shut Down Cost|',
+    'min_up_time_hours': 'Technology Parameter|Minimum Up Time|',
+    'min_down_time_hours': 'Technology Parameter|Minimum Down Time|',
+    'ramp_rate_percent_per_min': 'Technology Parameter|Ramp Rate|',
+    'carbon_emissions': 'Technology Parameter|Carbon Intensity|',
+    'min_plant_load': 'Technology Parameter|Minimum Plant Load|',
+    'min_capacity_factor': 'Technology Parameter|Minimum Capacity Factor|',
+    'max_capacity_factor': 'Technology Parameter|Maximum Capacity Factor|',
+    'efficiency': 'Technology Parameter|Efficiency|',
+    'fixed_om_costs': 'Technology Parameter|Fixed O&M Costs|',
+    'variable_om_costs': 'Technology Parameter|Variable O&M Costs|',
+    'annualized_capital_cost_CAD_per_MWyear': 'Technology Parameter|Annualized Capital Cost|',
+    'average_fuel_price_CAD_per_MMBtu': 'Technology Parameter|Average Fuel Price|'
+}
+
+def get_data(api_key:str):
+    """
+    This function is used to get the technology parameter data from the CODERS API
+    """
+    with urlopen(f"{CODERS}/generation_generic?key={api_key}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+
+    modeled_attributes = modeled_attributes[
+        ['gen_type_copper', 'startup_cost', 'shutdown_cost', 'min_up_time_hours', 'min_down_time_hours',
+         'ramp_rate_percent_per_min', 'carbon_emissions', 'min_plant_load', 'min_capacity_factor', 'max_capacity_factor',
+         'efficiency', 'fixed_om_costs', 'variable_om_costs', 'annualized_capital_cost_CAD_per_MWyear', 'average_fuel_price_CAD_per_MMBtu']]
+
+    melted = modeled_attributes.melt(id_vars=['gen_type_copper'], var_name='variable', value_name='value')
+    melted['variable'] = melted['variable'].map(mappings)
+    melted['variable'] = melted['variable'] + melted['gen_type_copper']
+    melted = melted.drop(columns='gen_type_copper')
+    return melted
+
+
+if __name__ == '__main__':
+    api_key = ''
+    df = get_data(api_key)

coders2iamc-1.0.0/coders_to_iamc/transmission.py

@@ -0,0 +1,39 @@
+import json
+from urllib.request import urlopen
+import pandas as pd
+
+from coders_to_iamc.constants import CODERS
+
+mappings = {
+    'network_node_code_starting': 'Intra-Provincial Transmission|Start Node|',
+    'network_node_code_ending': 'Intra-Provincial Transmission|End Node|',
+    'ttc_winter': 'Intra-Provincial Transmission|Capacity|',
+    'reactance': 'Intra-Provincial Transmission|Reactance|',
+}
+
+
+
+def get_data(api_key: str):
+    """
+    This function is used to get the technology parameter data from the CODERS API
+    """
+    with urlopen(f"{CODERS}/transmission_lines?key={api_key}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+
+    modeled_attributes = modeled_attributes[
+        ['transmission_line_id', 'network_node_code_starting', 'network_node_code_ending', 'ttc_winter', 'reactance',
+         'province']]
+    melted = modeled_attributes.melt(id_vars=['transmission_line_id', 'province'], var_name='variable', value_name='value')
+
+    melted['variable'] = melted['variable'].map(mappings)
+    melted['variable'] = melted['variable'] + melted['transmission_line_id'].astype(str)
+    melted = melted.drop(columns=['transmission_line_id'])
+    melted.rename(columns={'province': 'region'}, inplace=True)
+    return melted
+
+
+if __name__ == '__main__':
+    api_key = ''
+    df = get_data(api_key)

coders2iamc-1.0.0/coders_to_iamc/transmission_generic.py

@@ -0,0 +1,32 @@
+import json
+from urllib.request import urlopen
+import pandas as pd
+
+from coders_to_iamc.constants import CODERS
+
+mappings = {
+    'reserve_requirements_percent': 'Reserve Requirements Percentage',
+    'system_line_losses_percent': 'System Line Losses Percentage',
+    'water_rentals_CAD_per_MWh': 'Water Rentals',
+}
+
+
+def get_data(api_key: str):
+    """
+    This function is used to get the technology parameter data from the CODERS API
+    """
+    with urlopen(f"{CODERS}/transmission_generic?key={api_key}") as response:
+        response_content = response.read()
+        json_response = json.loads(response_content)
+        modeled_attributes = pd.json_normalize(json_response)
+
+    modeled_attributes = modeled_attributes[
+        ['annualized_project_cost_CAD_per_MWkmyear', 'transmission_type']
+    ].rename(columns={'annualized_project_cost_CAD_per_MWkmyear': 'value', 'transmission_type': 'variable'})
+    modeled_attributes['variable'] = 'Annualized Project Cost|' + modeled_attributes['variable']
+    return modeled_attributes
+
+
+if __name__ == '__main__':
+    api_key = ''
+    df = get_data(api_key)

coders2iamc-1.0.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

coders2iamc-1.0.0/setup.py

@@ -0,0 +1,35 @@
+# coders-to-iamc/setup.py
+
+from os.path import abspath, dirname, join
+
+from setuptools import find_packages, setup
+
+# Define the directory containing this file
+this_dir = abspath(dirname(__file__))
+
+# Read the long description from README.md
+with open(join(this_dir, "README.md"), encoding="utf-8") as f:
+    long_description = f.read()
+
+# Read the global requirements.txt
+with open(join(this_dir, "requirements.txt"), encoding="utf-8") as f:
+    requirements = f.read().splitlines()
+
+
+setup(
+    name="coders2iamc",
+    version="1.0.0",
+    description="Scripts that pull data from the CODERS database and format it for use in the IAMC format",
+    long_description=long_description,
+    long_description_content_type="text/markdown",
+    url="https://gitlab.com/sesit/coders-to-iamc",
+    install_requires=requirements,
+    packages=find_packages(include=["coders_to_iamc"]),
+    include_package_data=True,
+    classifiers=[
+        "Programming Language :: Python :: 3",
+        "Operating System :: OS Independent",
+    ],
+    python_requires=">=3.9",  # Specify the Python versions you support
+    package_data={"": ["*.yaml"]},
+)