google / weather-tools

Tools to make weather data accessible and useful.

Home Page:https://weather-tools.readthedocs.io/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Create example JSON config(s)

CillianFn opened this issue · comments

Similar to the *.cfg configuration file examples found in /configs, create example JSON config(s)

Hi, I am new to open source and I would like to work on this issue. Please guide me further on what needs to be done.

Hey @pranay101 ! More information can be found about what configuration files are used for here

As outlined, Configuration files can be written in *.cfg or *.json. However the examples in the config directory only contains examples of *.cfg files.

It would be useful to have some *.json examples also. I suggest creating json versions of some of the cfg examples. These can then be tested locally to ensure the same behaviour is observed e.g.

weather-dl configs/era5_example_config_local_run.cfg --local-run
should work the same as,
weather-dl configs/era5_example_config_local_run.json--local-run

I like the idea of having JSON configs. It's worth noting that the JSON representation will not be as full featured as the ConfigParser. See: https://github.com/google/weather-tools/blob/main/weather_dl/download_pipeline/parsers.py#L72

I think we can still create JSON example configs; however, these will have to be more verbose for the time being.

xref: #48

Hey @pranay101 ! More information can be found about what configuration files are used for here

As outlined, Configuration files can be written in *.cfg or *.json. However the examples in the config directory only contains examples of *.cfg files.

It would be useful to have some *.json examples also. I suggest creating json versions of some of the cfg examples. These can then be tested locally to ensure the same behaviour is observed e.g.

weather-dl configs/era5_example_config_local_run.cfg --local-run should work the same as, weather-dl configs/era5_example_config_local_run.json--local-run

how should I structure the project then?. creating separate folders for .CFG and .JSON inside config. or should I place json file along with the cfg files.

I'm a fan of flat file structures. So, json next to cfg sounds good to me.