Anyway, as I mentioned, we base product decisions around customer feedback, which is why I'd like to better understand your use case. For example, what is it exactly that you would like to do with your data?
I'd like to be able to store the weather data to a local database on my vineyard so I build a smart system to intelligently control my irrigation.
If I can see how much rainfall has occurred in the previous period, say 7 days, then I might decide to not automatically turn on my irrigation. This saves valuable water resources in a restricted aquifer by not watering when my vines don't need watering. It is environmentally friendly by not using electricity to pump water unnecessarily and saves money because I have to pay per volume of water (around $10,000 annually for the water and also $10,000 annually for the electricity costs).
Making an API with JSON data format weather data (as previously mentioned in this thread) would be ideal to be able to easily handle the data with Internet of Things (IOT) automation hardware and software systems, such as Node Red an IBM developed automation platform that has been provided freely to the Open Source community.
If AcuRite opened up the data there could be whole eco-systems built around their sensors connecting it to IOT automation. AcuRite doesn't have to provide an end to end solution for this and it's probably best if they don't because a one size fits all approach won't cover the multitude of use cases people may have. Here is a link to some of the work IBM has been doing in this area
https://www.ibm.com/watson/stories/ejgallo/ If IBM are investing in this type of technology then the use cases are real and serve a broad community and environmental function.
Would be great if AcuRite came on board, with a JSON based API that could be quickly integrated into the ever expanding IOT automation systems. Everybody else has already done the heavy lifting with open standards and hardware on the automation side, we just need access to quality local weather data to feed into the system. Having to reverse engineer RF signals, can be done, but this limits the main-stream adoption of weather collection stations to people who can get out a soldering iron and build custom hardware.
A single 100 acre vineyard might have as many as 4 or 5 weather stations monitoring very specific weather conditions in each sub-zone. A Node Red automation system might be able to do so many useful things like monitor wind speed in each specific block and send a email / SMS/ Text Msg alert to a tractor driver if the wind speed has got too high for the area they are spraying, or also alert the driver if they are applying a chemical that can not be sprayed on the vines over a certain temperature.
As an added bonus having the ability to mount custom antenna to expand the range of devices would save having to pull the weather data for each site locally and then using a custom solution to get the data back to the central data logging device. On the hardware side of things the Xbee platform are an example of a range of devices with different RF solutions that are already used for custom environmental data logging solutions
https://www.sparkfun.com/pages/xbee_guide