New proposed function: getWeather
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- data-visualization
Research direction
The proposed function is linked from the issue as a standalone getWeather repository; begin by reviewing that repository and its current implementation. The issue describes weather data retrieval, anomaly detection, indicators, and visualization, but does not define a specific change or completion criteria.
Written by the indexing model from the issue text.
Description
Hi everybody,
Today I am showing a new utility function, getWeather, designed to bring robust statistical analysis and advanced visualization to meteorological data within the FSDA "mind".
Inspired by the workflow and the interactive design of getYahoo, this function provides an end-to-end pipeline: from data retrieval (via Open-Meteo API) to robust anomaly detection and visualization. Given the recent meteorological shifts and the growing need for climate data quality checks, this function is intended to be a reliable "first-look" tool for time-series meteorological assessment.
Screenshot produced by: getWeather("Parma","lastperiod","1mo")
Key Features
-
Pipeline Design: One-step retrieval, cleaning, and structuring of surface weather variables (Temperature, Humidity, Pressure, Wind, Precipitation) into a timetable.
-
Robust Statistics: Implements multivariate anomaly detection using Robust Covariance (robustcov) and Mahalanobis distances, allowing users to spot outliers (e.g., sensor malfunctions or extreme micro-climatic events) without being misled by non-Gaussian noise.
-
Technical Indicators: Uses Exponential Moving Averages (EMA) to identify structural trends in temperature and provides linear regression fitting between Wind Speed and Gusts to assess correlation stability.
-
Advanced Visualization: A custom three-panel diagnostic layout featuring a dark-themed UI, interactive datatips (implemented via DataTipTemplate for optimal performance), and automatic figure exportation.
Next integrations:
I am actively planning to expand this function's capabilities to align with FSDA’s core philosophy:
like integrate MahalFS for a more granular identification of outliers and potential statistical depth also a spatial visualization: Implementing geoplotFS to visualize weather stations or event paths on maps.
Also, am actively exploring API sources or calculation methods to integrate CAPE (Convective Available Potential Energy) and SWT (Severe Weather Threat) indices to enhance forecasting diagnostic power. Also a lot things are now missing (like a proper documentation) but I am going to add on this type of things, as soon as I can.
I am open to every tipe of suggestion, also if you want to try the code or propose some changes, this is the standalone repository of this beta code:
getWeather
- Dominant language
- MATLAB
- Stars
- 30
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from UniprJRC/DSwithMATLAB
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
UniprJRC/DSwithMATLAB#243 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
UniprJRC/DSwithMATLAB#242 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
UniprJRC/DSwithMATLAB#241 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
UniprJRC/DSwithMATLAB#240 ·
-
Suggestion for the next edition
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
UniprJRC/DSwithMATLAB#238 · 2 comments ·
All issues in UniprJRC/DSwithMATLAB
Similar issues
-
bug priority: p3 size: xs
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Ax/Atb trim the caller's GpuIds in place, so blocksize-1 solvers run on one GPU after the first anglePossibly taken @AnderBiguri claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
mathworks/MATLAB-Coding-Guidelines#7 · 3 comments ·