Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom Airport Data #1235

Merged
merged 3 commits into from
Dec 15, 2024
Merged

Conversation

GbotemiB
Copy link
Contributor

Closes #1225 .

Changes proposed in this Pull Request

This PR aims to address the use of custom data for airports data. This PR is a follow-up from #1225

Checklist

  • I consent to the release of this PR's code under the AGPLv3 license and non-code contributions under CC0-1.0 and CC-BY-4.0.
  • I tested my contribution locally and it seems to work fine.
  • Code and workflow changes are sufficiently documented.
  • Newly introduced dependencies are added to envs/environment.yaml and doc/requirements.txt.
  • Changes in configuration options are added in all of config.default.yaml and config.tutorial.yaml.
  • Add a test config or line additions to test/ (note tests are changing the config.tutorial.yaml)
  • Changes in configuration options are also documented in doc/configtables/*.csv and line references are adjusted in doc/configuration.rst and doc/tutorial.rst.
  • A note for the release notes doc/release_notes.rst is amended in the format of previous release notes, including reference to the requested PR.

@GbotemiB GbotemiB marked this pull request as ready for review December 11, 2024 11:22
@ekatef
Copy link
Member

ekatef commented Dec 11, 2024

Super @GbotemiB! Thank you for the implementation. On the first glance, looks perfectly reasonable. Would be great to discuss the details tomorrow, also with the experts on sector-coupled modeling

@@ -0,0 +1,2 @@
,ident,type,airport_size_nr,name,y,x,elevation_ft,continent,country,iso_region,municipality,scheduled_service,iata_code,length_ft,width_ft,surface,lighted,closed,Total_airport_size_nr,fraction
0,5A8,medium_airport,1,Aleknagik / New Airport,59.2826004028,-158.617996216,66.0,,US,US-AK,Aleknagik,yes,WKK,2040.0,80.0,GRVL-DIRT-F,0.0,0.0,633,0.001579778830963665
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @GbotemiB. Was the second line given as a example?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah you are right, the second line is supposed to be as an example.

@Eddy-JV
Copy link
Collaborator

Eddy-JV commented Dec 15, 2024

Good work @GbotemiB . Thank you for implementing that. Sadly,I could not find passenger information for all airports globally. But for now, this is a good solution for countries who have such more realistic data for consumption.

I will merge now.

@Eddy-JV Eddy-JV merged commit 8212659 into pypsa-meets-earth:main Dec 15, 2024
6 checks passed
@ekatef
Copy link
Member

ekatef commented Dec 15, 2024

@GbotemiB @Eddy-JV @yerbol-akhmetov perfect 😄 Great work!! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow option for custom airport data
4 participants