pypsa-meets-earth/pypsa-earth

Polish license information in documentation

Open

#1,747 opened on Mar 5, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (349 forks)auto 404
bugdocumentationgood first issue

Repository metrics

Stars
 (351 stars)
PR merge metrics
 (PR metrics pending)

Description

Checklist

  • I am using the current main branch or the latest release. Please indicate.
  • I am running on an up-to-date pypsa-earth environment. Update via conda env update -f envs/environment.yaml.

Describe the Bug

For licenses, we have a summary here in the documentation but it may need some cross-checking and polishes. In particular:

  • A link to Copernicus land coverage dataset is outdated and must be replaced with a newer one https://cds.climate.copernicus.eu/cdsapp/#!/terms/licence-to-use-copernicus-products -> https://zenodo.org/records/3939050
  • There is a mistake for GADM whose license is by no means CC4.0, and conditions of use contain a direct restriction of re-distribution >The data are freely available for academic use and other non-commercial use. Redistribution, or commercial use is not allowed without prior permission.
  • eez and copernicus landcover datasets don't have restrictions on commercial usage (since they are licensed by a standart CC4.0)

Contributor guide

Research direction
Update the documentation by replacing the outdated Copernicus link, correcting the GADM license description, and verifying the CC4.0 statements for eez and Copernicus landcover datasets.
Tech stack
python
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90