Comments (6)
Yes, simply appending additional columns could be feasible @l-kotzur. I will put this on the backlog and investigate if we can add it.
Also, @adriesse is right regarding the meta data. Meteostat is currently losing some valuable meta data for the sake of simplicity. It's something we'll need to change. But this can only be done as part of the v2 rewrite.
from meteostat-python.
Let's continue this conversation here.
As mentioned by @l-kotzur, solar radiation data has already been added to some of the import routines. So Meteostat is presently collecting this data. However, it is not redistributed through our interfaces atm.
The reason is mainly a planned re-structuring of Meteostat's architecture which will put this Python library in the center of the architecture. This is going to be a completely new version which requires most code to be rewritten.
Before any work on the new version of the library can begin, I'd like to get feedback on the idea. Therefore, I will soon open a new issue which describes the concept. I will also need to talk to a few people to create a stronger foundation for the project - so it doesn't rely as much on myself as a maintainer.
from meteostat-python.
Hey @clampr
Thank you for the information!
This sounds interesting but is also a little bit frustrating to wait for this feature until the new architecture is finished. Would this be that much additional effort, especially when the data is already queried?
Otherwise, I am happy to support this package. So let me know when you make the proposal.
from meteostat-python.
I already thought about this.
The problem is that the current architecture isn't very flexible when it comes to adding new variables, changing the structure or data format. Meteostat Python relies entirely on the data provided through the bulk data interface. This uses CSV files with a static structure. Adding the solar radiation parameter would require a new version of these bulk data files. And every new version of the bulk data requires a temporal parallel export to ensure older versions don't stop working immediately.
I would vote for investing all capacity in the new architecture. This will not only add solar radiation, but also other parameters like cloud cover, visibility, etc.
from meteostat-python.
But isn't the bulk data interface working with NaN/sparse values anyway? So, would the addition of new columns destroy old interfaces? I understand it though for the modification of existing parameter names...
I hope you don't misunderstand my persistence. I just want to use this awesome package. :)
from meteostat-python.
I would perhaps add a comment that adding these parameters would be very attractive, but additional meta data would make them more valuable. I know solar radiation data, and it is certainly not all created equal. Of course the sky is the limit with meta data, but to take a German metaphor that seems somewhat similar but is not: "there is some air overhead" w.r.t. metadata in meteostat.
(To be taken as encouragement rather than criticism!)
from meteostat-python.
Related Issues (20)
- android: SSL certificate issues HOT 2
- No "tsun" values and month values for Jan., Feb. 2023 HOT 2
- station data error? HOT 3
- proposing requests as download data method for mobile, due to issues with certificates verification in pandas HOT 2
- "wpgt" does not populate. HOT 4
- Missing Data Frame Values
- interpolation error "ValueError: The name station occurs multiple times, use a level number" HOT 3
- `Hourly` attempts to fetch data of next year HOT 1
- Hacktoberfest? HOT 1
- DeprecationWarning
- Data from ISD datasource no longer included? HOT 7
- Data from METAR missing for some stations? HOT 2
- Support for proxies HOT 2
- NaN discrepancy between older versions (<=1.5.11) and newer versions (>=1.6.0) HOT 2
- Got Different Results in Local and AzureML
- Point interpolation weighted method error
- Stations and Hourly data availability times don't match
- README Example Faisl With [SSL: CERTIFICATE_VERIFY_FAILED] HOT 1
- Bug in Stations module
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from meteostat-python.