Joining Weather Data to Event Tables with {weatherjoin}8 months ago
Overview | Basic usage | Time handling in detail | What tz means | Single-column time input | Multi-column time input | Daily vs hourly data (time_api) | Daily timestamps and the dummy hour | Spatial handling and representative locations | Efficient time-range planning (splitting sparse ranges) | Local caching | Cache locations | User-level cache (default): persists across projects and sessions. | Project-level cache: stored in a .weatherjoin/ directory inside the project. This is useful for reproducible analyses and shared projects. | Cache maintenance | Advanced cache policy | Elevation handling (site_elevation) | Joining weather data back to events | Handling missing inputs | Summary