Hello Everyone,
After a good time gap i tried to generate an AMY file for a city. I accessed the NOAA website (https://gis.ncdc.noaa.gov/maps/ncei/cdo/hourly) to generate the required txt files as the modified AMY component requires .txt file as input.
But the NOAA format has again changed the way we used to download by clicking on access button (now add to cart option popping out).
hello @Asisnath
You know this plugin for creating AMY file has bug
even old data type of NOAA couldnāt work !!!
me and my friends try in different versions and systems.
but it didnāt work.
i hope @chris fix this issue soon.
we really need this ability of dragonfly
Iām sorry for such a late response here but Iām very glad that you found a temporary solution. Iāll try to add methods to handle the new NOAA format soon but, if anyone is feeling brave enough, you should be able to get it to work with < 100 lines of Python code using the ladybug-core Python library that is already being used in the current AMY component.
Hereās the full SDK documentation for the ladybug-core library, which lists all of the available modules and classes (probably the most important one here is the datacollection module): https://www.ladybug.tools/ladybug/docs/ladybug.html
And you can work with the ladybug library either with native python (installing it with ladybug-core) or you can simply type import ladybug in a GHPython component if you already have honeybee[+] installed.
I havenāt changed the AMY-data-importing component yet and I probably wonāt be able to get to it for another couple of weeks. So the opportunity is open if anyone wants to tackle it. Itās a good task if anyoneās looking to learn how to use the ladybug Python SDK.
I tried to find a way to download the data from this website but didnāt find the txt file. It would be grateful if you can provide some instructions of downloading the NOAA data.
Hello @chris. I tested the file but an error popped up with DF_Creat_EPW_Component. I have attached the screenshot and the updated file with latest LBT components to keep files similar for testing. Please have a look.
Thanks for catching the bug, @Asisnath . Those pesky SI/IP unit conversions. Glad that NOAA moved to officially using SI with this recent update. I just pushed a bug fix:
Hey @Asisnath ,
As I was falling asleep last night, I realized that thereās a bug in how I was interpreting the new AMY data. Iām 99% sure that all of the datetimes in the csv file are in GMT now instead of the time zone of the location recording the data. Iāll push a fix this morning (that is, morning in EDT and not GMT) and verify that itās correct. Glad that I caught this one before the release.