OSGeo - User contributions [en]

Talk:TorchGeo Code Provenance

2026-01-09T09:50:03Z

Ominiverdi:

'''Note''': AI LLM assistance was employed in the production of this document.

{| class="wikitable"
|+ LLM Engine contributions by operator
|-
! Operator !! Tool !! Model 1 !! Model 2
|-
| '''omniverdi''' || opencode || claude-opus || devstral2-2512
|-
| '''darkblueb''' || qwen3-coder || gemma3:12b || ollama local-only
|}

Talk:TorchGeo Code Provenance

2026-01-09T09:49:29Z

Ominiverdi:

Talk:TorchGeo Code Provenance

2026-01-09T09:30:11Z

Ominiverdi:

'''Note''': AI LLM assistance was employed in the production of this document.

{|
|+ LLM Engine contributions by operator
|-
| '''ominverdi''' || opencode || claude-opus || devstral2-2512
|-
| '''darkblueb''' || qwen3-coder || gemma3:12b || ollama local-only
|}

TorchGeo Code Provenance

2026-01-08T16:16:56Z

Ominiverdi: /* TorchGeo Application Questionnaire */

=Code Provenance Review Process=

TorchGeo project
'''refer : https://www.osgeo.org/about/committees/incubation/graduation/'''

==Document Status==

{| class="wikitable"
|-
| '''Version:''' || 0.3
|-
| '''Status:''' || Updated
|-
| '''Last Edited:''' || 08 Jan 2026
|}

==Purpose==

Show to "reasonable comfort level" that TorchGeo
does not have improperly contributed code, and that the code is all under the Project license.

Notice: ''It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly. The onus is not on the OSGeo Incubation Committee to prove there are no problems. However, OSGeo Incubation Committee does need to ensure that OSGeo does not officially endorse code with provenance issues that could have identified and corrected with a reasonable effort.''

=TorchGeo Provenance Review=

== Project History ==

TorchGeo started as an internship project at Microsoft's AI for Good Lab in 2021, with continued support and funding from the University of Illinois Urbana-Champaign and the National Center for Supercomputing Applications. Since then, TorchGeo has been adopted by a diverse community of researchers from academia, industry, and government research institutions who have contributed to the success of the library. In 2025, we founded a new TorchGeo Organization to manage the TorchGeo Project, with the support of members from the above organizations.

Key milestones:

- 2021-05-11: Initial commit (2330aad) by Adam J. Stewart

- 2021-2024: Organic growth to 120+ contributors

- 2025: Formation of TorchGeo Organization with formal governance structure

- 2026: OSGeo incubation application submitted

==Libraries==

All dependencies are external (not bundled in source tree). All licenses are OSI-approved and compatible with MIT.

{| class="wikitable" border="1"
|-
! Library !! License !! Compatible? !! In Core? !! Issues? !! Ok? !! Comments
|-
| einops || MIT || Yes || External || - || Yes || Tensor operations
|-
| geopandas || BSD-3-Clause || Yes || External || - || Yes || Geospatial dataframes
|-
| jsonargparse || MIT || Yes || External || - || Yes || CLI argument parsing
|-
| kornia || Apache-2.0 || Yes || External || - || Yes || Computer vision ops
|-
| lightly || MIT || Yes || External || - || Yes || Self-supervised learning
|-
| lightning || Apache-2.0 || Yes || External || - || Yes || Training framework
|-
| matplotlib || PSF || Yes || External || - || Yes || Plotting
|-
| numpy || BSD-3-Clause || Yes || External || - || Yes || Numerical computing
|-
| pandas || BSD-3-Clause || Yes || External || - || Yes || Data manipulation
|-
| pillow || HPND || Yes || External || - || Yes || Image I/O
|-
| pyproj || MIT || Yes || External || - || Yes || Cartographic projections
|-
| rasterio || BSD-3-Clause || Yes || External || - || Yes || Geospatial raster I/O
|-
| segmentation-models-pytorch || MIT || Yes || External || - || Yes || Segmentation architectures
|-
| shapely || BSD-3-Clause || Yes || External || - || Yes || Geometric operations
|-
| timm || Apache-2.0 || Yes || External || - || Yes || Vision model zoo
|-
| torch || BSD-3-Clause || Yes || External || - || Yes || PyTorch core
|-
| torchmetrics || Apache-2.0 || Yes || External || - || Yes || Metrics computation
|-
| torchvision || BSD-3-Clause || Yes || External || - || Yes || Vision utilities
|}

==Copyright Holders==
{| class="wikitable" border="1"
|-
! Copyright Holder !! Contact !! Issues !! Comments
|-
| TorchGeo Contributors || N/A (collective) || None || Per LICENSE file
|}

The MIT License file states: "Copyright (c) TorchGeo Contributors."

This is a collective copyright model - individual contributors retain copyright but license under MIT.

== Committers ==
'''Total human contributors:''' 122

'''Total commits:''' 2778 (excluding bots)

'''Top contributors''' (PSC members marked with *):

{| class="wikitable" border="1"
|-
! Committer !! Email !! Affiliation !! Agreement Signed?
|-
| Adam J. Stewart * || ajstewart426@gmail.com || TUM / UIUC || TBD
|-
| Caleb Robinson * || calebrob6@gmail.com || Microsoft AI for Good || TBD
|-
| Isaac Corley * || isaac.corley@proton.me || Wherobots || TBD
|-
| Nils Lehmann * || nils.lehmann24@gmail.com || TUM || TBD
|-
| Ashwin Nair * || ashnair0007@gmail.com || Space42 || TBD
|-
| Anthony Ortiz * || Anthony.Ortiz@microsoft.com || Microsoft || TBD
|-
| Robin Cole || robmarkcole@gmail.com || - || TBD
|-
| Yi Wang || wangyi111@users.noreply.github.com || - || TBD
|-
| Yi-Chia Chang || yichiac@users.noreply.github.com || - || TBD
|-
| Burak || burakekim@users.noreply.github.com || - || TBD
|-
| Blaz Rolih || blaz-r@users.noreply.github.com || - || TBD
|-
| Maciej Kilian || iejMac@users.noreply.github.com || - || TBD
|-
| Qiusheng Wu || giswqs@gmail.com || - || TBD
|}

'''Note:''' 122 total contributors. Full list available via <code>git shortlog -sne --all</code>.

==Source Files==
'''Total Python files:''' 557

'''Files with copyright header:''' 557 (100%) - ''after PR #3262 merged''

'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.

{| class="wikitable" border="1"
|-
! File !! License !! Copyright Holder !! Header? !! Issues? !! Ok? !! Comments
|-
| docs/user/metrics/update_timeline.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|-
| tests/data/landcoverai/split.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|}

'''Note:''' PR https://github.com/torchgeo/torchgeo/pull/3262 adds copyright headers to the 2 files that were missing them.

==Further Issues ==
'''Resolved:'''
* Copyright headers added to 2 missing files via PR #3262: https://github.com/torchgeo/torchgeo/pull/3262

'''Pending:'''
* Contributor agreement status needs confirmation from PSC members

== TorchGeo Application Questionnaire ==
See the main application questionnaire for additional project details:
https://trac.osgeo.org/osgeo/wiki/TorchGeo

==Process==

'''This Code Provenance Review followed the OSGeo Incubation process:'''
{| class="wikitable"
|-
! Step !! Status !! Date !! Notes
|-
| 1. Create Provenance Review Document || Complete || 06 Jan 2026 || Document created from [https://wiki.osgeo.org/wiki/Provenance_Review_Template Provenance Review Template]
|-
| 2. Library/Component Review || Complete || 08 Jan 2026 || 18 dependencies reviewed, no issues found
|-
| 3. Code Copyright Review || Complete || 08 Jan 2026 || 557 files reviewed, no issues found
|-
| 4. Submit to Project Mentor || Complete || 08 Jan 2026 || Brian M Hamlin (Mentor)
|}
=== Review Summary ===
{| class="wikitable"
|-
| '''Components in source tree:''' || None (all external dependencies)
|-
| '''Problematic licenses:''' || None identified
|-
| '''License conflicts:''' || None identified
|-
| '''Files reviewed:''' || 557 Python files
|-
| '''Files with headers:''' || 557 (100%)
|-
| '''External code derivations:''' || 2 files (both MIT licensed, properly attributed)
|-
| '''Copyright model:''' || Collective ("TorchGeo Contributors")
|}
=== Outstanding Items ===
* '''Pending merge:''' [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262] - adds copyright headers to 2 files
* '''NEEDS PSC INPUT:''' CLA/DCO status confirmation
* '''NEEDS PSC INPUT:''' Contributor agreement status for PSC members
=== Conclusion ===
'''The TorchGeo codebase passes the Code Provenance Review''' with no blocking issues identified. The project demonstrates good license hygiene and is ready for OSGeo incubation from a code provenance perspective.

==Library/Component Review Process==

'''Review completed:''' 08 Jan 2026
=== 1. Components in Source Tree ===
'''Finding:''' '''None'''
TorchGeo does '''not''' bundle any third-party libraries in its source tree. Unlike projects like GDAL (which includes copies of libtiff, libjpeg, etc.), TorchGeo treats all dependencies as external packages installed via pip/conda.
* No <code>vendor/</code> directory
* No <code>third_party/</code> directory
* No <code>external/</code> directory
* No embedded library copies
This is the recommended approach and simplifies license management.
=== 2. External Dependencies ===
'''Total required dependencies:''' 18
'''All licenses are OSI-approved and compatible with MIT.'''
{| class="wikitable"
|-
! Package !! License !! Compatible? !! Potentially Problematic?
|-
| einops || MIT || Yes || No
|-
| geopandas || BSD-3-Clause || Yes || No
|-
| jsonargparse || MIT || Yes || No
|-
| kornia || Apache-2.0 || Yes || No
|-
| lightly || MIT || Yes || No
|-
| lightning || Apache-2.0 || Yes || No
|-
| matplotlib || PSF (BSD-style) || Yes || No
|-
| numpy || BSD-3-Clause || Yes || No
|-
| pandas || BSD-3-Clause || Yes || No
|-
| pillow || HPND (permissive) || Yes || No
|-
| pyproj || MIT || Yes || No
|-
| rasterio || BSD-3-Clause || Yes || No
|-
| segmentation-models-pytorch || MIT || Yes || No
|-
| shapely || BSD-3-Clause || Yes || No
|-
| timm || Apache-2.0 || Yes || No
|-
| torch || BSD-3-Clause || Yes || No
|-
| torchmetrics || Apache-2.0 || Yes || No
|-
| torchvision || BSD-3-Clause || Yes || No
|}
=== 3. License Distribution ===
{| class="wikitable"
|-
! License Type !! Count !! Notes
|-
| MIT || 6 || Permissive, fully compatible
|-
| BSD-3-Clause || 7 || Permissive, fully compatible
|-
| Apache-2.0 || 4 || Permissive, fully compatible
|-
| PSF || 1 || Python Software Foundation, BSD-style
|-
| HPND || 1 || Historical Permission Notice and Disclaimer, permissive
|}
=== 4. Potentially Problematic Licenses ===
'''Finding:''' '''None identified'''
* No GPL or LGPL dependencies (no copyleft)
* No AGPL dependencies
* No proprietary or non-free dependencies
* No "viral" license concerns
=== 5. License Conflicts ===
'''Finding:''' '''None identified'''
All dependency licenses are permissive and compatible with each other and with TorchGeo's MIT license. There are no conflicts analogous to GDAL's use of GPL'ed GRASS libraries.
=== 6. Optional Dependencies ===
TorchGeo has optional dependencies for the <code>datasets</code> extra. All use permissive licenses:
{| class="wikitable"
|-
! Package !! License
|-
| h5py || BSD-3-Clause
|-
| laspy || BSD-2-Clause
|-
| netcdf4 || MIT
|-
| opencv-python || Apache-2.0
|-
| pycocotools || BSD-2-Clause
|-
| rioxarray || Apache-2.0
|-
| scikit-image || BSD-3-Clause
|-
| scipy || BSD-3-Clause
|-
| xarray || Apache-2.0
|}
=== 7. Conclusion ===
'''Overall assessment:''' No library/component issues identified
* No bundled code in source tree
* All 18 required dependencies use permissive OSI-approved licenses
* No GPL/copyleft dependencies
* No license conflicts
* Clean dependency model suitable for OSGeo incubation

== Code Copyright Review ==
'''Review completed:''' 08 Jan 2026
'''Reviewer:''' Brian M Hamlin (Mentor), with assistance from automated tooling
'''Scope:''' All 557 Python source files in the TorchGeo repository
=== 1. License Headers ===
{| class="wikitable"
|-
| '''Total Python files:''' || 557
|-
| '''Files with standard header:''' || 557 (100%)
|-
| '''Files missing header:''' || 0 (after [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262])
|}
'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.
'''Finding:''' All source files include the standard license header. Two utility scripts (<code>docs/user/metrics/update_timeline.py</code> and <code>tests/data/landcoverai/split.py</code>) were identified as missing headers during this review and fixed via [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262].
=== 2. License Consistency ===
'''Finding:''' All files are under the '''MIT License'''. No files use a different or conflicting license.
* No GPL, LGPL, or copyleft licenses found
* No Apache-only or BSD-only files found
* All code consistently uses MIT
=== 3. Code Origins ===
Two files contain code derived from external sources. Both are properly attributed and both original sources use MIT License (compatible):
{| class="wikitable"
|-
! File !! Source !! Source License !! Compatible? !! Attribution in File?
|-
| <code>torchgeo/models/btc.py</code> || [https://github.com/blaz-r/BTC-change-detection blaz-r/BTC-change-detection] || MIT || Yes || Yes
|-
| <code>torchgeo/models/croma.py</code> || [https://github.com/antofuller/CROMA antofuller/CROMA] || MIT || Yes || Yes
|}
'''Finding:''' Both external code sources are MIT licensed, which is fully compatible with TorchGeo's MIT license. Attribution is properly documented in the source file headers.
=== 4. Vendored/Bundled Code ===
'''Finding:''' No vendored or bundled third-party code exists in the source tree. All dependencies are external and installed via pip/conda.
* No <code>vendor/</code>, <code>third_party/</code>, or <code>external/</code> directories
* No embedded copies of libraries (unlike GDAL which bundles libtiff, libjpeg, etc.)
* All 18 dependencies are fetched externally at install time
=== 5. Copyright Holders ===
{| class="wikitable"
|-
! Copyright Holder !! Type !! Notes
|-
| TorchGeo Contributors || Collective || Single copyright holder for all files
|}
'''Finding:''' The project uses a '''collective copyright model'''. All files use "Copyright (c) TorchGeo Contributors" rather than individual contributor names.
'''Implications for relicensing:'''
* Simplified model - no need to contact 122 individual contributors
* Contributors implicitly agree to collective copyright by submitting PRs
* '''NEEDS CLARIFICATION:''' Does the project have a Contributor License Agreement (CLA) or Developer Certificate of Origin (DCO)?
=== 6. Outstanding Issues ===
'''Resolved:'''
* Copyright headers added to 2 missing files: [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262]
'''Pending:'''
* '''NEEDS PSC INPUT:''' Confirm whether a CLA/DCO is in place or planned
* '''NEEDS PSC INPUT:''' Contributor agreement status for PSC members (currently all marked TBD)
=== 7. Conclusion ===
'''Overall assessment:''' No provenance issues identified
The TorchGeo codebase demonstrates good copyright hygiene:
* 100% of source files have proper license headers
* All code is consistently MIT licensed
* External code derivations are properly attributed and license-compatible
* No vendored code complicates the license picture
* Collective copyright model simplifies governance
The codebase is ready for OSGeo incubation from a code provenance perspective, pending confirmation of contributor agreement procedures from the PSC.

TorchGeo Code Provenance

2026-01-08T16:16:22Z

Ominiverdi: /* Document Status */

=Code Provenance Review Process=

TorchGeo project
'''refer : https://www.osgeo.org/about/committees/incubation/graduation/'''

==Document Status==

{| class="wikitable"
|-
| '''Version:''' || 0.3
|-
| '''Status:''' || Updated
|-
| '''Last Edited:''' || 08 Jan 2026
|}

==Purpose==

Show to "reasonable comfort level" that TorchGeo
does not have improperly contributed code, and that the code is all under the Project license.

Notice: ''It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly. The onus is not on the OSGeo Incubation Committee to prove there are no problems. However, OSGeo Incubation Committee does need to ensure that OSGeo does not officially endorse code with provenance issues that could have identified and corrected with a reasonable effort.''

=TorchGeo Provenance Review=

== Project History ==

TorchGeo started as an internship project at Microsoft's AI for Good Lab in 2021, with continued support and funding from the University of Illinois Urbana-Champaign and the National Center for Supercomputing Applications. Since then, TorchGeo has been adopted by a diverse community of researchers from academia, industry, and government research institutions who have contributed to the success of the library. In 2025, we founded a new TorchGeo Organization to manage the TorchGeo Project, with the support of members from the above organizations.

Key milestones:

- 2021-05-11: Initial commit (2330aad) by Adam J. Stewart

- 2021-2024: Organic growth to 120+ contributors

- 2025: Formation of TorchGeo Organization with formal governance structure

- 2026: OSGeo incubation application submitted

==Libraries==

All dependencies are external (not bundled in source tree). All licenses are OSI-approved and compatible with MIT.

{| class="wikitable" border="1"
|-
! Library !! License !! Compatible? !! In Core? !! Issues? !! Ok? !! Comments
|-
| einops || MIT || Yes || External || - || Yes || Tensor operations
|-
| geopandas || BSD-3-Clause || Yes || External || - || Yes || Geospatial dataframes
|-
| jsonargparse || MIT || Yes || External || - || Yes || CLI argument parsing
|-
| kornia || Apache-2.0 || Yes || External || - || Yes || Computer vision ops
|-
| lightly || MIT || Yes || External || - || Yes || Self-supervised learning
|-
| lightning || Apache-2.0 || Yes || External || - || Yes || Training framework
|-
| matplotlib || PSF || Yes || External || - || Yes || Plotting
|-
| numpy || BSD-3-Clause || Yes || External || - || Yes || Numerical computing
|-
| pandas || BSD-3-Clause || Yes || External || - || Yes || Data manipulation
|-
| pillow || HPND || Yes || External || - || Yes || Image I/O
|-
| pyproj || MIT || Yes || External || - || Yes || Cartographic projections
|-
| rasterio || BSD-3-Clause || Yes || External || - || Yes || Geospatial raster I/O
|-
| segmentation-models-pytorch || MIT || Yes || External || - || Yes || Segmentation architectures
|-
| shapely || BSD-3-Clause || Yes || External || - || Yes || Geometric operations
|-
| timm || Apache-2.0 || Yes || External || - || Yes || Vision model zoo
|-
| torch || BSD-3-Clause || Yes || External || - || Yes || PyTorch core
|-
| torchmetrics || Apache-2.0 || Yes || External || - || Yes || Metrics computation
|-
| torchvision || BSD-3-Clause || Yes || External || - || Yes || Vision utilities
|}

==Copyright Holders==
{| class="wikitable" border="1"
|-
! Copyright Holder !! Contact !! Issues !! Comments
|-
| TorchGeo Contributors || N/A (collective) || None || Per LICENSE file
|}

The MIT License file states: "Copyright (c) TorchGeo Contributors."

This is a collective copyright model - individual contributors retain copyright but license under MIT.

== Committers ==
'''Total human contributors:''' 122

'''Total commits:''' 2778 (excluding bots)

'''Top contributors''' (PSC members marked with *):

{| class="wikitable" border="1"
|-
! Committer !! Email !! Affiliation !! Agreement Signed?
|-
| Adam J. Stewart * || ajstewart426@gmail.com || TUM / UIUC || TBD
|-
| Caleb Robinson * || calebrob6@gmail.com || Microsoft AI for Good || TBD
|-
| Isaac Corley * || isaac.corley@proton.me || Wherobots || TBD
|-
| Nils Lehmann * || nils.lehmann24@gmail.com || TUM || TBD
|-
| Ashwin Nair * || ashnair0007@gmail.com || Space42 || TBD
|-
| Anthony Ortiz * || Anthony.Ortiz@microsoft.com || Microsoft || TBD
|-
| Robin Cole || robmarkcole@gmail.com || - || TBD
|-
| Yi Wang || wangyi111@users.noreply.github.com || - || TBD
|-
| Yi-Chia Chang || yichiac@users.noreply.github.com || - || TBD
|-
| Burak || burakekim@users.noreply.github.com || - || TBD
|-
| Blaz Rolih || blaz-r@users.noreply.github.com || - || TBD
|-
| Maciej Kilian || iejMac@users.noreply.github.com || - || TBD
|-
| Qiusheng Wu || giswqs@gmail.com || - || TBD
|}

'''Note:''' 122 total contributors. Full list available via <code>git shortlog -sne --all</code>.

==Source Files==
'''Total Python files:''' 557

'''Files with copyright header:''' 557 (100%) - ''after PR #3262 merged''

'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.

{| class="wikitable" border="1"
|-
! File !! License !! Copyright Holder !! Header? !! Issues? !! Ok? !! Comments
|-
| docs/user/metrics/update_timeline.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|-
| tests/data/landcoverai/split.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|}

'''Note:''' PR https://github.com/torchgeo/torchgeo/pull/3262 adds copyright headers to the 2 files that were missing them.

==Further Issues ==
'''Resolved:'''
* Copyright headers added to 2 missing files via PR #3262: https://github.com/torchgeo/torchgeo/pull/3262

'''Pending:'''
* Contributor agreement status needs confirmation from PSC members

== TorchGeo Application Questionnaire ==

https://trac.osgeo.org/osgeo/wiki/TorchGeo

==Process==

'''This Code Provenance Review followed the OSGeo Incubation process:'''
{| class="wikitable"
|-
! Step !! Status !! Date !! Notes
|-
| 1. Create Provenance Review Document || Complete || 06 Jan 2026 || Document created from [https://wiki.osgeo.org/wiki/Provenance_Review_Template Provenance Review Template]
|-
| 2. Library/Component Review || Complete || 08 Jan 2026 || 18 dependencies reviewed, no issues found
|-
| 3. Code Copyright Review || Complete || 08 Jan 2026 || 557 files reviewed, no issues found
|-
| 4. Submit to Project Mentor || Complete || 08 Jan 2026 || Brian M Hamlin (Mentor)
|}
=== Review Summary ===
{| class="wikitable"
|-
| '''Components in source tree:''' || None (all external dependencies)
|-
| '''Problematic licenses:''' || None identified
|-
| '''License conflicts:''' || None identified
|-
| '''Files reviewed:''' || 557 Python files
|-
| '''Files with headers:''' || 557 (100%)
|-
| '''External code derivations:''' || 2 files (both MIT licensed, properly attributed)
|-
| '''Copyright model:''' || Collective ("TorchGeo Contributors")
|}
=== Outstanding Items ===
* '''Pending merge:''' [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262] - adds copyright headers to 2 files
* '''NEEDS PSC INPUT:''' CLA/DCO status confirmation
* '''NEEDS PSC INPUT:''' Contributor agreement status for PSC members
=== Conclusion ===
'''The TorchGeo codebase passes the Code Provenance Review''' with no blocking issues identified. The project demonstrates good license hygiene and is ready for OSGeo incubation from a code provenance perspective.

==Library/Component Review Process==

'''Review completed:''' 08 Jan 2026
=== 1. Components in Source Tree ===
'''Finding:''' '''None'''
TorchGeo does '''not''' bundle any third-party libraries in its source tree. Unlike projects like GDAL (which includes copies of libtiff, libjpeg, etc.), TorchGeo treats all dependencies as external packages installed via pip/conda.
* No <code>vendor/</code> directory
* No <code>third_party/</code> directory
* No <code>external/</code> directory
* No embedded library copies
This is the recommended approach and simplifies license management.
=== 2. External Dependencies ===
'''Total required dependencies:''' 18
'''All licenses are OSI-approved and compatible with MIT.'''
{| class="wikitable"
|-
! Package !! License !! Compatible? !! Potentially Problematic?
|-
| einops || MIT || Yes || No
|-
| geopandas || BSD-3-Clause || Yes || No
|-
| jsonargparse || MIT || Yes || No
|-
| kornia || Apache-2.0 || Yes || No
|-
| lightly || MIT || Yes || No
|-
| lightning || Apache-2.0 || Yes || No
|-
| matplotlib || PSF (BSD-style) || Yes || No
|-
| numpy || BSD-3-Clause || Yes || No
|-
| pandas || BSD-3-Clause || Yes || No
|-
| pillow || HPND (permissive) || Yes || No
|-
| pyproj || MIT || Yes || No
|-
| rasterio || BSD-3-Clause || Yes || No
|-
| segmentation-models-pytorch || MIT || Yes || No
|-
| shapely || BSD-3-Clause || Yes || No
|-
| timm || Apache-2.0 || Yes || No
|-
| torch || BSD-3-Clause || Yes || No
|-
| torchmetrics || Apache-2.0 || Yes || No
|-
| torchvision || BSD-3-Clause || Yes || No
|}
=== 3. License Distribution ===
{| class="wikitable"
|-
! License Type !! Count !! Notes
|-
| MIT || 6 || Permissive, fully compatible
|-
| BSD-3-Clause || 7 || Permissive, fully compatible
|-
| Apache-2.0 || 4 || Permissive, fully compatible
|-
| PSF || 1 || Python Software Foundation, BSD-style
|-
| HPND || 1 || Historical Permission Notice and Disclaimer, permissive
|}
=== 4. Potentially Problematic Licenses ===
'''Finding:''' '''None identified'''
* No GPL or LGPL dependencies (no copyleft)
* No AGPL dependencies
* No proprietary or non-free dependencies
* No "viral" license concerns
=== 5. License Conflicts ===
'''Finding:''' '''None identified'''
All dependency licenses are permissive and compatible with each other and with TorchGeo's MIT license. There are no conflicts analogous to GDAL's use of GPL'ed GRASS libraries.
=== 6. Optional Dependencies ===
TorchGeo has optional dependencies for the <code>datasets</code> extra. All use permissive licenses:
{| class="wikitable"
|-
! Package !! License
|-
| h5py || BSD-3-Clause
|-
| laspy || BSD-2-Clause
|-
| netcdf4 || MIT
|-
| opencv-python || Apache-2.0
|-
| pycocotools || BSD-2-Clause
|-
| rioxarray || Apache-2.0
|-
| scikit-image || BSD-3-Clause
|-
| scipy || BSD-3-Clause
|-
| xarray || Apache-2.0
|}
=== 7. Conclusion ===
'''Overall assessment:''' No library/component issues identified
* No bundled code in source tree
* All 18 required dependencies use permissive OSI-approved licenses
* No GPL/copyleft dependencies
* No license conflicts
* Clean dependency model suitable for OSGeo incubation

== Code Copyright Review ==
'''Review completed:''' 08 Jan 2026
'''Reviewer:''' Brian M Hamlin (Mentor), with assistance from automated tooling
'''Scope:''' All 557 Python source files in the TorchGeo repository
=== 1. License Headers ===
{| class="wikitable"
|-
| '''Total Python files:''' || 557
|-
| '''Files with standard header:''' || 557 (100%)
|-
| '''Files missing header:''' || 0 (after [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262])
|}
'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.
'''Finding:''' All source files include the standard license header. Two utility scripts (<code>docs/user/metrics/update_timeline.py</code> and <code>tests/data/landcoverai/split.py</code>) were identified as missing headers during this review and fixed via [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262].
=== 2. License Consistency ===
'''Finding:''' All files are under the '''MIT License'''. No files use a different or conflicting license.
* No GPL, LGPL, or copyleft licenses found
* No Apache-only or BSD-only files found
* All code consistently uses MIT
=== 3. Code Origins ===
Two files contain code derived from external sources. Both are properly attributed and both original sources use MIT License (compatible):
{| class="wikitable"
|-
! File !! Source !! Source License !! Compatible? !! Attribution in File?
|-
| <code>torchgeo/models/btc.py</code> || [https://github.com/blaz-r/BTC-change-detection blaz-r/BTC-change-detection] || MIT || Yes || Yes
|-
| <code>torchgeo/models/croma.py</code> || [https://github.com/antofuller/CROMA antofuller/CROMA] || MIT || Yes || Yes
|}
'''Finding:''' Both external code sources are MIT licensed, which is fully compatible with TorchGeo's MIT license. Attribution is properly documented in the source file headers.
=== 4. Vendored/Bundled Code ===
'''Finding:''' No vendored or bundled third-party code exists in the source tree. All dependencies are external and installed via pip/conda.
* No <code>vendor/</code>, <code>third_party/</code>, or <code>external/</code> directories
* No embedded copies of libraries (unlike GDAL which bundles libtiff, libjpeg, etc.)
* All 18 dependencies are fetched externally at install time
=== 5. Copyright Holders ===
{| class="wikitable"
|-
! Copyright Holder !! Type !! Notes
|-
| TorchGeo Contributors || Collective || Single copyright holder for all files
|}
'''Finding:''' The project uses a '''collective copyright model'''. All files use "Copyright (c) TorchGeo Contributors" rather than individual contributor names.
'''Implications for relicensing:'''
* Simplified model - no need to contact 122 individual contributors
* Contributors implicitly agree to collective copyright by submitting PRs
* '''NEEDS CLARIFICATION:''' Does the project have a Contributor License Agreement (CLA) or Developer Certificate of Origin (DCO)?
=== 6. Outstanding Issues ===
'''Resolved:'''
* Copyright headers added to 2 missing files: [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262]
'''Pending:'''
* '''NEEDS PSC INPUT:''' Confirm whether a CLA/DCO is in place or planned
* '''NEEDS PSC INPUT:''' Contributor agreement status for PSC members (currently all marked TBD)
=== 7. Conclusion ===
'''Overall assessment:''' No provenance issues identified
The TorchGeo codebase demonstrates good copyright hygiene:
* 100% of source files have proper license headers
* All code is consistently MIT licensed
* External code derivations are properly attributed and license-compatible
* No vendored code complicates the license picture
* Collective copyright model simplifies governance
The codebase is ready for OSGeo incubation from a code provenance perspective, pending confirmation of contributor agreement procedures from the PSC.

TorchGeo Code Provenance

2026-01-08T16:16:07Z

Ominiverdi: /* Frequently Asked Questions */

=Code Provenance Review Process=

TorchGeo project
'''refer : https://www.osgeo.org/about/committees/incubation/graduation/'''

==Document Status==

{| class="wikitable"
|-
| '''Version:''' || 0.2
|-
| '''Status:''' || Updated
|-
| '''Last Edited:''' || 08 Jan 2026
|}

==Purpose==

Show to "reasonable comfort level" that TorchGeo
does not have improperly contributed code, and that the code is all under the Project license.

Notice: ''It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly. The onus is not on the OSGeo Incubation Committee to prove there are no problems. However, OSGeo Incubation Committee does need to ensure that OSGeo does not officially endorse code with provenance issues that could have identified and corrected with a reasonable effort.''

=TorchGeo Provenance Review=

== Project History ==

TorchGeo started as an internship project at Microsoft's AI for Good Lab in 2021, with continued support and funding from the University of Illinois Urbana-Champaign and the National Center for Supercomputing Applications. Since then, TorchGeo has been adopted by a diverse community of researchers from academia, industry, and government research institutions who have contributed to the success of the library. In 2025, we founded a new TorchGeo Organization to manage the TorchGeo Project, with the support of members from the above organizations.

Key milestones:

- 2021-05-11: Initial commit (2330aad) by Adam J. Stewart

- 2021-2024: Organic growth to 120+ contributors

- 2025: Formation of TorchGeo Organization with formal governance structure

- 2026: OSGeo incubation application submitted

==Libraries==

All dependencies are external (not bundled in source tree). All licenses are OSI-approved and compatible with MIT.

{| class="wikitable" border="1"
|-
! Library !! License !! Compatible? !! In Core? !! Issues? !! Ok? !! Comments
|-
| einops || MIT || Yes || External || - || Yes || Tensor operations
|-
| geopandas || BSD-3-Clause || Yes || External || - || Yes || Geospatial dataframes
|-
| jsonargparse || MIT || Yes || External || - || Yes || CLI argument parsing
|-
| kornia || Apache-2.0 || Yes || External || - || Yes || Computer vision ops
|-
| lightly || MIT || Yes || External || - || Yes || Self-supervised learning
|-
| lightning || Apache-2.0 || Yes || External || - || Yes || Training framework
|-
| matplotlib || PSF || Yes || External || - || Yes || Plotting
|-
| numpy || BSD-3-Clause || Yes || External || - || Yes || Numerical computing
|-
| pandas || BSD-3-Clause || Yes || External || - || Yes || Data manipulation
|-
| pillow || HPND || Yes || External || - || Yes || Image I/O
|-
| pyproj || MIT || Yes || External || - || Yes || Cartographic projections
|-
| rasterio || BSD-3-Clause || Yes || External || - || Yes || Geospatial raster I/O
|-
| segmentation-models-pytorch || MIT || Yes || External || - || Yes || Segmentation architectures
|-
| shapely || BSD-3-Clause || Yes || External || - || Yes || Geometric operations
|-
| timm || Apache-2.0 || Yes || External || - || Yes || Vision model zoo
|-
| torch || BSD-3-Clause || Yes || External || - || Yes || PyTorch core
|-
| torchmetrics || Apache-2.0 || Yes || External || - || Yes || Metrics computation
|-
| torchvision || BSD-3-Clause || Yes || External || - || Yes || Vision utilities
|}

==Copyright Holders==
{| class="wikitable" border="1"
|-
! Copyright Holder !! Contact !! Issues !! Comments
|-
| TorchGeo Contributors || N/A (collective) || None || Per LICENSE file
|}

The MIT License file states: "Copyright (c) TorchGeo Contributors."

This is a collective copyright model - individual contributors retain copyright but license under MIT.

== Committers ==
'''Total human contributors:''' 122

'''Total commits:''' 2778 (excluding bots)

'''Top contributors''' (PSC members marked with *):

{| class="wikitable" border="1"
|-
! Committer !! Email !! Affiliation !! Agreement Signed?
|-
| Adam J. Stewart * || ajstewart426@gmail.com || TUM / UIUC || TBD
|-
| Caleb Robinson * || calebrob6@gmail.com || Microsoft AI for Good || TBD
|-
| Isaac Corley * || isaac.corley@proton.me || Wherobots || TBD
|-
| Nils Lehmann * || nils.lehmann24@gmail.com || TUM || TBD
|-
| Ashwin Nair * || ashnair0007@gmail.com || Space42 || TBD
|-
| Anthony Ortiz * || Anthony.Ortiz@microsoft.com || Microsoft || TBD
|-
| Robin Cole || robmarkcole@gmail.com || - || TBD
|-
| Yi Wang || wangyi111@users.noreply.github.com || - || TBD
|-
| Yi-Chia Chang || yichiac@users.noreply.github.com || - || TBD
|-
| Burak || burakekim@users.noreply.github.com || - || TBD
|-
| Blaz Rolih || blaz-r@users.noreply.github.com || - || TBD
|-
| Maciej Kilian || iejMac@users.noreply.github.com || - || TBD
|-
| Qiusheng Wu || giswqs@gmail.com || - || TBD
|}

'''Note:''' 122 total contributors. Full list available via <code>git shortlog -sne --all</code>.

==Source Files==
'''Total Python files:''' 557

'''Files with copyright header:''' 557 (100%) - ''after PR #3262 merged''

'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.

{| class="wikitable" border="1"
|-
! File !! License !! Copyright Holder !! Header? !! Issues? !! Ok? !! Comments
|-
| docs/user/metrics/update_timeline.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|-
| tests/data/landcoverai/split.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|}

'''Note:''' PR https://github.com/torchgeo/torchgeo/pull/3262 adds copyright headers to the 2 files that were missing them.

==Further Issues ==
'''Resolved:'''
* Copyright headers added to 2 missing files via PR #3262: https://github.com/torchgeo/torchgeo/pull/3262

'''Pending:'''
* Contributor agreement status needs confirmation from PSC members

== TorchGeo Application Questionnaire ==

https://trac.osgeo.org/osgeo/wiki/TorchGeo

==Process==

'''This Code Provenance Review followed the OSGeo Incubation process:'''
{| class="wikitable"
|-
! Step !! Status !! Date !! Notes
|-
| 1. Create Provenance Review Document || Complete || 06 Jan 2026 || Document created from [https://wiki.osgeo.org/wiki/Provenance_Review_Template Provenance Review Template]
|-
| 2. Library/Component Review || Complete || 08 Jan 2026 || 18 dependencies reviewed, no issues found
|-
| 3. Code Copyright Review || Complete || 08 Jan 2026 || 557 files reviewed, no issues found
|-
| 4. Submit to Project Mentor || Complete || 08 Jan 2026 || Brian M Hamlin (Mentor)
|}
=== Review Summary ===
{| class="wikitable"
|-
| '''Components in source tree:''' || None (all external dependencies)
|-
| '''Problematic licenses:''' || None identified
|-
| '''License conflicts:''' || None identified
|-
| '''Files reviewed:''' || 557 Python files
|-
| '''Files with headers:''' || 557 (100%)
|-
| '''External code derivations:''' || 2 files (both MIT licensed, properly attributed)
|-
| '''Copyright model:''' || Collective ("TorchGeo Contributors")
|}
=== Outstanding Items ===
* '''Pending merge:''' [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262] - adds copyright headers to 2 files
* '''NEEDS PSC INPUT:''' CLA/DCO status confirmation
* '''NEEDS PSC INPUT:''' Contributor agreement status for PSC members
=== Conclusion ===
'''The TorchGeo codebase passes the Code Provenance Review''' with no blocking issues identified. The project demonstrates good license hygiene and is ready for OSGeo incubation from a code provenance perspective.

==Library/Component Review Process==

'''Review completed:''' 08 Jan 2026
=== 1. Components in Source Tree ===
'''Finding:''' '''None'''
TorchGeo does '''not''' bundle any third-party libraries in its source tree. Unlike projects like GDAL (which includes copies of libtiff, libjpeg, etc.), TorchGeo treats all dependencies as external packages installed via pip/conda.
* No <code>vendor/</code> directory
* No <code>third_party/</code> directory
* No <code>external/</code> directory
* No embedded library copies
This is the recommended approach and simplifies license management.
=== 2. External Dependencies ===
'''Total required dependencies:''' 18
'''All licenses are OSI-approved and compatible with MIT.'''
{| class="wikitable"
|-
! Package !! License !! Compatible? !! Potentially Problematic?
|-
| einops || MIT || Yes || No
|-
| geopandas || BSD-3-Clause || Yes || No
|-
| jsonargparse || MIT || Yes || No
|-
| kornia || Apache-2.0 || Yes || No
|-
| lightly || MIT || Yes || No
|-
| lightning || Apache-2.0 || Yes || No
|-
| matplotlib || PSF (BSD-style) || Yes || No
|-
| numpy || BSD-3-Clause || Yes || No
|-
| pandas || BSD-3-Clause || Yes || No
|-
| pillow || HPND (permissive) || Yes || No
|-
| pyproj || MIT || Yes || No
|-
| rasterio || BSD-3-Clause || Yes || No
|-
| segmentation-models-pytorch || MIT || Yes || No
|-
| shapely || BSD-3-Clause || Yes || No
|-
| timm || Apache-2.0 || Yes || No
|-
| torch || BSD-3-Clause || Yes || No
|-
| torchmetrics || Apache-2.0 || Yes || No
|-
| torchvision || BSD-3-Clause || Yes || No
|}
=== 3. License Distribution ===
{| class="wikitable"
|-
! License Type !! Count !! Notes
|-
| MIT || 6 || Permissive, fully compatible
|-
| BSD-3-Clause || 7 || Permissive, fully compatible
|-
| Apache-2.0 || 4 || Permissive, fully compatible
|-
| PSF || 1 || Python Software Foundation, BSD-style
|-
| HPND || 1 || Historical Permission Notice and Disclaimer, permissive
|}
=== 4. Potentially Problematic Licenses ===
'''Finding:''' '''None identified'''
* No GPL or LGPL dependencies (no copyleft)
* No AGPL dependencies
* No proprietary or non-free dependencies
* No "viral" license concerns
=== 5. License Conflicts ===
'''Finding:''' '''None identified'''
All dependency licenses are permissive and compatible with each other and with TorchGeo's MIT license. There are no conflicts analogous to GDAL's use of GPL'ed GRASS libraries.
=== 6. Optional Dependencies ===
TorchGeo has optional dependencies for the <code>datasets</code> extra. All use permissive licenses:
{| class="wikitable"
|-
! Package !! License
|-
| h5py || BSD-3-Clause
|-
| laspy || BSD-2-Clause
|-
| netcdf4 || MIT
|-
| opencv-python || Apache-2.0
|-
| pycocotools || BSD-2-Clause
|-
| rioxarray || Apache-2.0
|-
| scikit-image || BSD-3-Clause
|-
| scipy || BSD-3-Clause
|-
| xarray || Apache-2.0
|}
=== 7. Conclusion ===
'''Overall assessment:''' No library/component issues identified
* No bundled code in source tree
* All 18 required dependencies use permissive OSI-approved licenses
* No GPL/copyleft dependencies
* No license conflicts
* Clean dependency model suitable for OSGeo incubation

== Code Copyright Review ==
'''Review completed:''' 08 Jan 2026
'''Reviewer:''' Brian M Hamlin (Mentor), with assistance from automated tooling
'''Scope:''' All 557 Python source files in the TorchGeo repository
=== 1. License Headers ===
{| class="wikitable"
|-
| '''Total Python files:''' || 557
|-
| '''Files with standard header:''' || 557 (100%)
|-
| '''Files missing header:''' || 0 (after [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262])
|}
'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.
'''Finding:''' All source files include the standard license header. Two utility scripts (<code>docs/user/metrics/update_timeline.py</code> and <code>tests/data/landcoverai/split.py</code>) were identified as missing headers during this review and fixed via [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262].
=== 2. License Consistency ===
'''Finding:''' All files are under the '''MIT License'''. No files use a different or conflicting license.
* No GPL, LGPL, or copyleft licenses found
* No Apache-only or BSD-only files found
* All code consistently uses MIT
=== 3. Code Origins ===
Two files contain code derived from external sources. Both are properly attributed and both original sources use MIT License (compatible):
{| class="wikitable"
|-
! File !! Source !! Source License !! Compatible? !! Attribution in File?
|-
| <code>torchgeo/models/btc.py</code> || [https://github.com/blaz-r/BTC-change-detection blaz-r/BTC-change-detection] || MIT || Yes || Yes
|-
| <code>torchgeo/models/croma.py</code> || [https://github.com/antofuller/CROMA antofuller/CROMA] || MIT || Yes || Yes
|}
'''Finding:''' Both external code sources are MIT licensed, which is fully compatible with TorchGeo's MIT license. Attribution is properly documented in the source file headers.
=== 4. Vendored/Bundled Code ===
'''Finding:''' No vendored or bundled third-party code exists in the source tree. All dependencies are external and installed via pip/conda.
* No <code>vendor/</code>, <code>third_party/</code>, or <code>external/</code> directories
* No embedded copies of libraries (unlike GDAL which bundles libtiff, libjpeg, etc.)
* All 18 dependencies are fetched externally at install time
=== 5. Copyright Holders ===
{| class="wikitable"
|-
! Copyright Holder !! Type !! Notes
|-
| TorchGeo Contributors || Collective || Single copyright holder for all files
|}
'''Finding:''' The project uses a '''collective copyright model'''. All files use "Copyright (c) TorchGeo Contributors" rather than individual contributor names.
'''Implications for relicensing:'''
* Simplified model - no need to contact 122 individual contributors
* Contributors implicitly agree to collective copyright by submitting PRs
* '''NEEDS CLARIFICATION:''' Does the project have a Contributor License Agreement (CLA) or Developer Certificate of Origin (DCO)?
=== 6. Outstanding Issues ===
'''Resolved:'''
* Copyright headers added to 2 missing files: [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262]
'''Pending:'''
* '''NEEDS PSC INPUT:''' Confirm whether a CLA/DCO is in place or planned
* '''NEEDS PSC INPUT:''' Contributor agreement status for PSC members (currently all marked TBD)
=== 7. Conclusion ===
'''Overall assessment:''' No provenance issues identified
The TorchGeo codebase demonstrates good copyright hygiene:
* 100% of source files have proper license headers
* All code is consistently MIT licensed
* External code derivations are properly attributed and license-compatible
* No vendored code complicates the license picture
* Collective copyright model simplifies governance
The codebase is ready for OSGeo incubation from a code provenance perspective, pending confirmation of contributor agreement procedures from the PSC.

TorchGeo Code Provenance

2026-01-08T16:12:17Z

Ominiverdi: /* Process */

=Code Provenance Review Process=

TorchGeo project
'''refer : https://www.osgeo.org/about/committees/incubation/graduation/'''

==Document Status==

{| class="wikitable"
|-
| '''Version:''' || 0.2
|-
| '''Status:''' || Updated
|-
| '''Last Edited:''' || 08 Jan 2026
|}

==Purpose==

Show to "reasonable comfort level" that TorchGeo
does not have improperly contributed code, and that the code is all under the Project license.

Notice: ''It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly. The onus is not on the OSGeo Incubation Committee to prove there are no problems. However, OSGeo Incubation Committee does need to ensure that OSGeo does not officially endorse code with provenance issues that could have identified and corrected with a reasonable effort.''

=TorchGeo Provenance Review=

== Project History ==

TorchGeo started as an internship project at Microsoft's AI for Good Lab in 2021, with continued support and funding from the University of Illinois Urbana-Champaign and the National Center for Supercomputing Applications. Since then, TorchGeo has been adopted by a diverse community of researchers from academia, industry, and government research institutions who have contributed to the success of the library. In 2025, we founded a new TorchGeo Organization to manage the TorchGeo Project, with the support of members from the above organizations.

Key milestones:

- 2021-05-11: Initial commit (2330aad) by Adam J. Stewart

- 2021-2024: Organic growth to 120+ contributors

- 2025: Formation of TorchGeo Organization with formal governance structure

- 2026: OSGeo incubation application submitted

==Libraries==

All dependencies are external (not bundled in source tree). All licenses are OSI-approved and compatible with MIT.

{| class="wikitable" border="1"
|-
! Library !! License !! Compatible? !! In Core? !! Issues? !! Ok? !! Comments
|-
| einops || MIT || Yes || External || - || Yes || Tensor operations
|-
| geopandas || BSD-3-Clause || Yes || External || - || Yes || Geospatial dataframes
|-
| jsonargparse || MIT || Yes || External || - || Yes || CLI argument parsing
|-
| kornia || Apache-2.0 || Yes || External || - || Yes || Computer vision ops
|-
| lightly || MIT || Yes || External || - || Yes || Self-supervised learning
|-
| lightning || Apache-2.0 || Yes || External || - || Yes || Training framework
|-
| matplotlib || PSF || Yes || External || - || Yes || Plotting
|-
| numpy || BSD-3-Clause || Yes || External || - || Yes || Numerical computing
|-
| pandas || BSD-3-Clause || Yes || External || - || Yes || Data manipulation
|-
| pillow || HPND || Yes || External || - || Yes || Image I/O
|-
| pyproj || MIT || Yes || External || - || Yes || Cartographic projections
|-
| rasterio || BSD-3-Clause || Yes || External || - || Yes || Geospatial raster I/O
|-
| segmentation-models-pytorch || MIT || Yes || External || - || Yes || Segmentation architectures
|-
| shapely || BSD-3-Clause || Yes || External || - || Yes || Geometric operations
|-
| timm || Apache-2.0 || Yes || External || - || Yes || Vision model zoo
|-
| torch || BSD-3-Clause || Yes || External || - || Yes || PyTorch core
|-
| torchmetrics || Apache-2.0 || Yes || External || - || Yes || Metrics computation
|-
| torchvision || BSD-3-Clause || Yes || External || - || Yes || Vision utilities
|}

==Copyright Holders==
{| class="wikitable" border="1"
|-
! Copyright Holder !! Contact !! Issues !! Comments
|-
| TorchGeo Contributors || N/A (collective) || None || Per LICENSE file
|}

The MIT License file states: "Copyright (c) TorchGeo Contributors."

This is a collective copyright model - individual contributors retain copyright but license under MIT.

== Committers ==
'''Total human contributors:''' 122

'''Total commits:''' 2778 (excluding bots)

'''Top contributors''' (PSC members marked with *):

{| class="wikitable" border="1"
|-
! Committer !! Email !! Affiliation !! Agreement Signed?
|-
| Adam J. Stewart * || ajstewart426@gmail.com || TUM / UIUC || TBD
|-
| Caleb Robinson * || calebrob6@gmail.com || Microsoft AI for Good || TBD
|-
| Isaac Corley * || isaac.corley@proton.me || Wherobots || TBD
|-
| Nils Lehmann * || nils.lehmann24@gmail.com || TUM || TBD
|-
| Ashwin Nair * || ashnair0007@gmail.com || Space42 || TBD
|-
| Anthony Ortiz * || Anthony.Ortiz@microsoft.com || Microsoft || TBD
|-
| Robin Cole || robmarkcole@gmail.com || - || TBD
|-
| Yi Wang || wangyi111@users.noreply.github.com || - || TBD
|-
| Yi-Chia Chang || yichiac@users.noreply.github.com || - || TBD
|-
| Burak || burakekim@users.noreply.github.com || - || TBD
|-
| Blaz Rolih || blaz-r@users.noreply.github.com || - || TBD
|-
| Maciej Kilian || iejMac@users.noreply.github.com || - || TBD
|-
| Qiusheng Wu || giswqs@gmail.com || - || TBD
|}

'''Note:''' 122 total contributors. Full list available via <code>git shortlog -sne --all</code>.

==Source Files==
'''Total Python files:''' 557

'''Files with copyright header:''' 557 (100%) - ''after PR #3262 merged''

'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.

{| class="wikitable" border="1"
|-
! File !! License !! Copyright Holder !! Header? !! Issues? !! Ok? !! Comments
|-
| docs/user/metrics/update_timeline.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|-
| tests/data/landcoverai/split.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|}

'''Note:''' PR https://github.com/torchgeo/torchgeo/pull/3262 adds copyright headers to the 2 files that were missing them.

==Further Issues ==
'''Resolved:'''
* Copyright headers added to 2 missing files via PR #3262: https://github.com/torchgeo/torchgeo/pull/3262

'''Pending:'''
* Contributor agreement status needs confirmation from PSC members

== TorchGeo Application Questionnaire ==

https://trac.osgeo.org/osgeo/wiki/TorchGeo

==Process==

'''This Code Provenance Review followed the OSGeo Incubation process:'''
{| class="wikitable"
|-
! Step !! Status !! Date !! Notes
|-
| 1. Create Provenance Review Document || Complete || 06 Jan 2026 || Document created from [https://wiki.osgeo.org/wiki/Provenance_Review_Template Provenance Review Template]
|-
| 2. Library/Component Review || Complete || 08 Jan 2026 || 18 dependencies reviewed, no issues found
|-
| 3. Code Copyright Review || Complete || 08 Jan 2026 || 557 files reviewed, no issues found
|-
| 4. Submit to Project Mentor || Complete || 08 Jan 2026 || Brian M Hamlin (Mentor)
|}
=== Review Summary ===
{| class="wikitable"
|-
| '''Components in source tree:''' || None (all external dependencies)
|-
| '''Problematic licenses:''' || None identified
|-
| '''License conflicts:''' || None identified
|-
| '''Files reviewed:''' || 557 Python files
|-
| '''Files with headers:''' || 557 (100%)
|-
| '''External code derivations:''' || 2 files (both MIT licensed, properly attributed)
|-
| '''Copyright model:''' || Collective ("TorchGeo Contributors")
|}
=== Outstanding Items ===
* '''Pending merge:''' [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262] - adds copyright headers to 2 files
* '''NEEDS PSC INPUT:''' CLA/DCO status confirmation
* '''NEEDS PSC INPUT:''' Contributor agreement status for PSC members
=== Conclusion ===
'''The TorchGeo codebase passes the Code Provenance Review''' with no blocking issues identified. The project demonstrates good license hygiene and is ready for OSGeo incubation from a code provenance perspective.

==Library/Component Review Process==

'''Review completed:''' 08 Jan 2026
=== 1. Components in Source Tree ===
'''Finding:''' '''None'''
TorchGeo does '''not''' bundle any third-party libraries in its source tree. Unlike projects like GDAL (which includes copies of libtiff, libjpeg, etc.), TorchGeo treats all dependencies as external packages installed via pip/conda.
* No <code>vendor/</code> directory
* No <code>third_party/</code> directory
* No <code>external/</code> directory
* No embedded library copies
This is the recommended approach and simplifies license management.
=== 2. External Dependencies ===
'''Total required dependencies:''' 18
'''All licenses are OSI-approved and compatible with MIT.'''
{| class="wikitable"
|-
! Package !! License !! Compatible? !! Potentially Problematic?
|-
| einops || MIT || Yes || No
|-
| geopandas || BSD-3-Clause || Yes || No
|-
| jsonargparse || MIT || Yes || No
|-
| kornia || Apache-2.0 || Yes || No
|-
| lightly || MIT || Yes || No
|-
| lightning || Apache-2.0 || Yes || No
|-
| matplotlib || PSF (BSD-style) || Yes || No
|-
| numpy || BSD-3-Clause || Yes || No
|-
| pandas || BSD-3-Clause || Yes || No
|-
| pillow || HPND (permissive) || Yes || No
|-
| pyproj || MIT || Yes || No
|-
| rasterio || BSD-3-Clause || Yes || No
|-
| segmentation-models-pytorch || MIT || Yes || No
|-
| shapely || BSD-3-Clause || Yes || No
|-
| timm || Apache-2.0 || Yes || No
|-
| torch || BSD-3-Clause || Yes || No
|-
| torchmetrics || Apache-2.0 || Yes || No
|-
| torchvision || BSD-3-Clause || Yes || No
|}
=== 3. License Distribution ===
{| class="wikitable"
|-
! License Type !! Count !! Notes
|-
| MIT || 6 || Permissive, fully compatible
|-
| BSD-3-Clause || 7 || Permissive, fully compatible
|-
| Apache-2.0 || 4 || Permissive, fully compatible
|-
| PSF || 1 || Python Software Foundation, BSD-style
|-
| HPND || 1 || Historical Permission Notice and Disclaimer, permissive
|}
=== 4. Potentially Problematic Licenses ===
'''Finding:''' '''None identified'''
* No GPL or LGPL dependencies (no copyleft)
* No AGPL dependencies
* No proprietary or non-free dependencies
* No "viral" license concerns
=== 5. License Conflicts ===
'''Finding:''' '''None identified'''
All dependency licenses are permissive and compatible with each other and with TorchGeo's MIT license. There are no conflicts analogous to GDAL's use of GPL'ed GRASS libraries.
=== 6. Optional Dependencies ===
TorchGeo has optional dependencies for the <code>datasets</code> extra. All use permissive licenses:
{| class="wikitable"
|-
! Package !! License
|-
| h5py || BSD-3-Clause
|-
| laspy || BSD-2-Clause
|-
| netcdf4 || MIT
|-
| opencv-python || Apache-2.0
|-
| pycocotools || BSD-2-Clause
|-
| rioxarray || Apache-2.0
|-
| scikit-image || BSD-3-Clause
|-
| scipy || BSD-3-Clause
|-
| xarray || Apache-2.0
|}
=== 7. Conclusion ===
'''Overall assessment:''' No library/component issues identified
* No bundled code in source tree
* All 18 required dependencies use permissive OSI-approved licenses
* No GPL/copyleft dependencies
* No license conflicts
* Clean dependency model suitable for OSGeo incubation

== Code Copyright Review ==
'''Review completed:''' 08 Jan 2026
'''Reviewer:''' Brian M Hamlin (Mentor), with assistance from automated tooling
'''Scope:''' All 557 Python source files in the TorchGeo repository
=== 1. License Headers ===
{| class="wikitable"
|-
| '''Total Python files:''' || 557
|-
| '''Files with standard header:''' || 557 (100%)
|-
| '''Files missing header:''' || 0 (after [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262])
|}
'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.
'''Finding:''' All source files include the standard license header. Two utility scripts (<code>docs/user/metrics/update_timeline.py</code> and <code>tests/data/landcoverai/split.py</code>) were identified as missing headers during this review and fixed via [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262].
=== 2. License Consistency ===
'''Finding:''' All files are under the '''MIT License'''. No files use a different or conflicting license.
* No GPL, LGPL, or copyleft licenses found
* No Apache-only or BSD-only files found
* All code consistently uses MIT
=== 3. Code Origins ===
Two files contain code derived from external sources. Both are properly attributed and both original sources use MIT License (compatible):
{| class="wikitable"
|-
! File !! Source !! Source License !! Compatible? !! Attribution in File?
|-
| <code>torchgeo/models/btc.py</code> || [https://github.com/blaz-r/BTC-change-detection blaz-r/BTC-change-detection] || MIT || Yes || Yes
|-
| <code>torchgeo/models/croma.py</code> || [https://github.com/antofuller/CROMA antofuller/CROMA] || MIT || Yes || Yes
|}
'''Finding:''' Both external code sources are MIT licensed, which is fully compatible with TorchGeo's MIT license. Attribution is properly documented in the source file headers.
=== 4. Vendored/Bundled Code ===
'''Finding:''' No vendored or bundled third-party code exists in the source tree. All dependencies are external and installed via pip/conda.
* No <code>vendor/</code>, <code>third_party/</code>, or <code>external/</code> directories
* No embedded copies of libraries (unlike GDAL which bundles libtiff, libjpeg, etc.)
* All 18 dependencies are fetched externally at install time
=== 5. Copyright Holders ===
{| class="wikitable"
|-
! Copyright Holder !! Type !! Notes
|-
| TorchGeo Contributors || Collective || Single copyright holder for all files
|}
'''Finding:''' The project uses a '''collective copyright model'''. All files use "Copyright (c) TorchGeo Contributors" rather than individual contributor names.
'''Implications for relicensing:'''
* Simplified model - no need to contact 122 individual contributors
* Contributors implicitly agree to collective copyright by submitting PRs
* '''NEEDS CLARIFICATION:''' Does the project have a Contributor License Agreement (CLA) or Developer Certificate of Origin (DCO)?
=== 6. Outstanding Issues ===
'''Resolved:'''
* Copyright headers added to 2 missing files: [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262]
'''Pending:'''
* '''NEEDS PSC INPUT:''' Confirm whether a CLA/DCO is in place or planned
* '''NEEDS PSC INPUT:''' Contributor agreement status for PSC members (currently all marked TBD)
=== 7. Conclusion ===
'''Overall assessment:''' No provenance issues identified
The TorchGeo codebase demonstrates good copyright hygiene:
* 100% of source files have proper license headers
* All code is consistently MIT licensed
* External code derivations are properly attributed and license-compatible
* No vendored code complicates the license picture
* Collective copyright model simplifies governance
The codebase is ready for OSGeo incubation from a code provenance perspective, pending confirmation of contributor agreement procedures from the PSC.

==Frequently Asked Questions==

;Do we need to ensure there is a copyright and licence headers in every file?
:Projects are expected to embed a copyright and license header in every source file (.cpp and .h for instance). Machine generated files (such as lex or yacc output for instance) does not require a header if it is inconvenient to embed one, but then an effort should be made to embed a header in the original source file (ie. .l or .y). There is no need to embed copyright and license headers in build files (ie. Makefiles, Visual Studio project files), nor in small documentation fragments (like READMEs). Copyright/license headers should be included in substantial bodies of documentation if it can be done in such a way that it doesn't interfere with the document.

;Do I really need to embed the whole license agreement in every file?
:No, it is sufficient to refer to a single copy of the license agreement for the project, but each file should include an indication of what the license is, and the location of the full license document. For example:
/*
* Copyright (C) 2004-2005 Autodesk, Inc.
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of version 2.1 of the GNU Lesser
* General Public License as published by the Free Software Foundation.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this library; if not, write to the Free Software
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*/

or:

* COPYRIGHT: (C) 2001 by the GRASS Development Team
*
* This program is free software under the GNU General Public
* License (>=v2). Read the file COPYING that comes with GRASS
* for details.

;Can I just write a script to check everything?
:No. The point of a human review is to ensure that human eyes have looked at the header of each file, looking for any anomalies. For instance it is not uncommon to have additional messages written in headers about the original source of particular code, but not necessarily in a way that a script could recognise.

; But I just did a review similar to this a few months ago, do I really need to do it again?
: If you believe you have already met or exceeded the rigor described in this review document, then you can present the results of your previous analysis along with an explanation of why you think it still applies. You will need to manually review additions since that earlier review. It will be up to the Incubator (and ultimately the foundation board) to determine if they are satisfied with any review.

;Do I need to track down every contributor and ask for permission to use their code?
:No. As long as code was knowingly provided by contributors to the project while it was under a clear licensing policy then it is reasonable to assume the project licensing arrangements are accepted unless there is some reason to have doubts. If code was brought into the project from outside sources under ambiguous circumstances then it may be necessary to contact the copyright holder for a legal release, or at least a statement of permission.

;Some project code was adapted from other sources with ambiguous copyrights, what do I do?
:First, document such concerns in the review document and within the source files themselves. Second, try to obtain a release to use the provide code. An email statement of permission should be sufficient, but pertinant details of such an email should be included in the source file in questions (eg. date, identification of releasing person, text of the release). If no release is possible, but the code isn't very necessary, consider removing or replacing it to simplify things. Otherwise the issue will need to be discussed in the incubator to assess risk.

; Should I be looking for patent problems?
: No. However, if the code review turns up notes about patent issues - or if there are known patent issues for the project, then these should be noted in the review document. Generally speaking a proper patent review is very difficult and may increase, rather than decrease, legal liability.

; Should I be looking for trademark conflicts?
: Possibly. It may be prudent to check for trademark conflicts for the project name, or the name of public packages within the project. If issues are found they should be noted in the review document.

--

[[Category: Incubation]]

TorchGeo Code Provenance

2026-01-08T16:11:26Z

Ominiverdi: /* Library/Component Review Process */

=Code Provenance Review Process=

TorchGeo project
'''refer : https://www.osgeo.org/about/committees/incubation/graduation/'''

==Document Status==

{| class="wikitable"
|-
| '''Version:''' || 0.2
|-
| '''Status:''' || Updated
|-
| '''Last Edited:''' || 08 Jan 2026
|}

==Purpose==

Show to "reasonable comfort level" that TorchGeo
does not have improperly contributed code, and that the code is all under the Project license.

Notice: ''It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly. The onus is not on the OSGeo Incubation Committee to prove there are no problems. However, OSGeo Incubation Committee does need to ensure that OSGeo does not officially endorse code with provenance issues that could have identified and corrected with a reasonable effort.''

=TorchGeo Provenance Review=

== Project History ==

TorchGeo started as an internship project at Microsoft's AI for Good Lab in 2021, with continued support and funding from the University of Illinois Urbana-Champaign and the National Center for Supercomputing Applications. Since then, TorchGeo has been adopted by a diverse community of researchers from academia, industry, and government research institutions who have contributed to the success of the library. In 2025, we founded a new TorchGeo Organization to manage the TorchGeo Project, with the support of members from the above organizations.

Key milestones:

- 2021-05-11: Initial commit (2330aad) by Adam J. Stewart

- 2021-2024: Organic growth to 120+ contributors

- 2025: Formation of TorchGeo Organization with formal governance structure

- 2026: OSGeo incubation application submitted

==Libraries==

All dependencies are external (not bundled in source tree). All licenses are OSI-approved and compatible with MIT.

{| class="wikitable" border="1"
|-
! Library !! License !! Compatible? !! In Core? !! Issues? !! Ok? !! Comments
|-
| einops || MIT || Yes || External || - || Yes || Tensor operations
|-
| geopandas || BSD-3-Clause || Yes || External || - || Yes || Geospatial dataframes
|-
| jsonargparse || MIT || Yes || External || - || Yes || CLI argument parsing
|-
| kornia || Apache-2.0 || Yes || External || - || Yes || Computer vision ops
|-
| lightly || MIT || Yes || External || - || Yes || Self-supervised learning
|-
| lightning || Apache-2.0 || Yes || External || - || Yes || Training framework
|-
| matplotlib || PSF || Yes || External || - || Yes || Plotting
|-
| numpy || BSD-3-Clause || Yes || External || - || Yes || Numerical computing
|-
| pandas || BSD-3-Clause || Yes || External || - || Yes || Data manipulation
|-
| pillow || HPND || Yes || External || - || Yes || Image I/O
|-
| pyproj || MIT || Yes || External || - || Yes || Cartographic projections
|-
| rasterio || BSD-3-Clause || Yes || External || - || Yes || Geospatial raster I/O
|-
| segmentation-models-pytorch || MIT || Yes || External || - || Yes || Segmentation architectures
|-
| shapely || BSD-3-Clause || Yes || External || - || Yes || Geometric operations
|-
| timm || Apache-2.0 || Yes || External || - || Yes || Vision model zoo
|-
| torch || BSD-3-Clause || Yes || External || - || Yes || PyTorch core
|-
| torchmetrics || Apache-2.0 || Yes || External || - || Yes || Metrics computation
|-
| torchvision || BSD-3-Clause || Yes || External || - || Yes || Vision utilities
|}

==Copyright Holders==
{| class="wikitable" border="1"
|-
! Copyright Holder !! Contact !! Issues !! Comments
|-
| TorchGeo Contributors || N/A (collective) || None || Per LICENSE file
|}

The MIT License file states: "Copyright (c) TorchGeo Contributors."

This is a collective copyright model - individual contributors retain copyright but license under MIT.

== Committers ==
'''Total human contributors:''' 122

'''Total commits:''' 2778 (excluding bots)

'''Top contributors''' (PSC members marked with *):

{| class="wikitable" border="1"
|-
! Committer !! Email !! Affiliation !! Agreement Signed?
|-
| Adam J. Stewart * || ajstewart426@gmail.com || TUM / UIUC || TBD
|-
| Caleb Robinson * || calebrob6@gmail.com || Microsoft AI for Good || TBD
|-
| Isaac Corley * || isaac.corley@proton.me || Wherobots || TBD
|-
| Nils Lehmann * || nils.lehmann24@gmail.com || TUM || TBD
|-
| Ashwin Nair * || ashnair0007@gmail.com || Space42 || TBD
|-
| Anthony Ortiz * || Anthony.Ortiz@microsoft.com || Microsoft || TBD
|-
| Robin Cole || robmarkcole@gmail.com || - || TBD
|-
| Yi Wang || wangyi111@users.noreply.github.com || - || TBD
|-
| Yi-Chia Chang || yichiac@users.noreply.github.com || - || TBD
|-
| Burak || burakekim@users.noreply.github.com || - || TBD
|-
| Blaz Rolih || blaz-r@users.noreply.github.com || - || TBD
|-
| Maciej Kilian || iejMac@users.noreply.github.com || - || TBD
|-
| Qiusheng Wu || giswqs@gmail.com || - || TBD
|}

'''Note:''' 122 total contributors. Full list available via <code>git shortlog -sne --all</code>.

==Source Files==
'''Total Python files:''' 557

'''Files with copyright header:''' 557 (100%) - ''after PR #3262 merged''

'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.

{| class="wikitable" border="1"
|-
! File !! License !! Copyright Holder !! Header? !! Issues? !! Ok? !! Comments
|-
| docs/user/metrics/update_timeline.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|-
| tests/data/landcoverai/split.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|}

'''Note:''' PR https://github.com/torchgeo/torchgeo/pull/3262 adds copyright headers to the 2 files that were missing them.

==Further Issues ==
'''Resolved:'''
* Copyright headers added to 2 missing files via PR #3262: https://github.com/torchgeo/torchgeo/pull/3262

'''Pending:'''
* Contributor agreement status needs confirmation from PSC members

== TorchGeo Application Questionnaire ==

https://trac.osgeo.org/osgeo/wiki/TorchGeo

==Process==

The Code Provenance Review is separated into two sections, each with a slightly different process:
# Create a Provenance Review Document by copying the [[Provenance Review Template]].
# Complete the Library/Component Review Process.
# Complete the Code Copyright Review.
# Submit the completed Provenance Review Document to the Project Mentor for review.

==Library/Component Review Process==

'''Review completed:''' 08 Jan 2026
=== 1. Components in Source Tree ===
'''Finding:''' '''None'''
TorchGeo does '''not''' bundle any third-party libraries in its source tree. Unlike projects like GDAL (which includes copies of libtiff, libjpeg, etc.), TorchGeo treats all dependencies as external packages installed via pip/conda.
* No <code>vendor/</code> directory
* No <code>third_party/</code> directory
* No <code>external/</code> directory
* No embedded library copies
This is the recommended approach and simplifies license management.
=== 2. External Dependencies ===
'''Total required dependencies:''' 18
'''All licenses are OSI-approved and compatible with MIT.'''
{| class="wikitable"
|-
! Package !! License !! Compatible? !! Potentially Problematic?
|-
| einops || MIT || Yes || No
|-
| geopandas || BSD-3-Clause || Yes || No
|-
| jsonargparse || MIT || Yes || No
|-
| kornia || Apache-2.0 || Yes || No
|-
| lightly || MIT || Yes || No
|-
| lightning || Apache-2.0 || Yes || No
|-
| matplotlib || PSF (BSD-style) || Yes || No
|-
| numpy || BSD-3-Clause || Yes || No
|-
| pandas || BSD-3-Clause || Yes || No
|-
| pillow || HPND (permissive) || Yes || No
|-
| pyproj || MIT || Yes || No
|-
| rasterio || BSD-3-Clause || Yes || No
|-
| segmentation-models-pytorch || MIT || Yes || No
|-
| shapely || BSD-3-Clause || Yes || No
|-
| timm || Apache-2.0 || Yes || No
|-
| torch || BSD-3-Clause || Yes || No
|-
| torchmetrics || Apache-2.0 || Yes || No
|-
| torchvision || BSD-3-Clause || Yes || No
|}
=== 3. License Distribution ===
{| class="wikitable"
|-
! License Type !! Count !! Notes
|-
| MIT || 6 || Permissive, fully compatible
|-
| BSD-3-Clause || 7 || Permissive, fully compatible
|-
| Apache-2.0 || 4 || Permissive, fully compatible
|-
| PSF || 1 || Python Software Foundation, BSD-style
|-
| HPND || 1 || Historical Permission Notice and Disclaimer, permissive
|}
=== 4. Potentially Problematic Licenses ===
'''Finding:''' '''None identified'''
* No GPL or LGPL dependencies (no copyleft)
* No AGPL dependencies
* No proprietary or non-free dependencies
* No "viral" license concerns
=== 5. License Conflicts ===
'''Finding:''' '''None identified'''
All dependency licenses are permissive and compatible with each other and with TorchGeo's MIT license. There are no conflicts analogous to GDAL's use of GPL'ed GRASS libraries.
=== 6. Optional Dependencies ===
TorchGeo has optional dependencies for the <code>datasets</code> extra. All use permissive licenses:
{| class="wikitable"
|-
! Package !! License
|-
| h5py || BSD-3-Clause
|-
| laspy || BSD-2-Clause
|-
| netcdf4 || MIT
|-
| opencv-python || Apache-2.0
|-
| pycocotools || BSD-2-Clause
|-
| rioxarray || Apache-2.0
|-
| scikit-image || BSD-3-Clause
|-
| scipy || BSD-3-Clause
|-
| xarray || Apache-2.0
|}
=== 7. Conclusion ===
'''Overall assessment:''' No library/component issues identified
* No bundled code in source tree
* All 18 required dependencies use permissive OSI-approved licenses
* No GPL/copyleft dependencies
* No license conflicts
* Clean dependency model suitable for OSGeo incubation

== Code Copyright Review ==
'''Review completed:''' 08 Jan 2026
'''Reviewer:''' Brian M Hamlin (Mentor), with assistance from automated tooling
'''Scope:''' All 557 Python source files in the TorchGeo repository
=== 1. License Headers ===
{| class="wikitable"
|-
| '''Total Python files:''' || 557
|-
| '''Files with standard header:''' || 557 (100%)
|-
| '''Files missing header:''' || 0 (after [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262])
|}
'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.
'''Finding:''' All source files include the standard license header. Two utility scripts (<code>docs/user/metrics/update_timeline.py</code> and <code>tests/data/landcoverai/split.py</code>) were identified as missing headers during this review and fixed via [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262].
=== 2. License Consistency ===
'''Finding:''' All files are under the '''MIT License'''. No files use a different or conflicting license.
* No GPL, LGPL, or copyleft licenses found
* No Apache-only or BSD-only files found
* All code consistently uses MIT
=== 3. Code Origins ===
Two files contain code derived from external sources. Both are properly attributed and both original sources use MIT License (compatible):
{| class="wikitable"
|-
! File !! Source !! Source License !! Compatible? !! Attribution in File?
|-
| <code>torchgeo/models/btc.py</code> || [https://github.com/blaz-r/BTC-change-detection blaz-r/BTC-change-detection] || MIT || Yes || Yes
|-
| <code>torchgeo/models/croma.py</code> || [https://github.com/antofuller/CROMA antofuller/CROMA] || MIT || Yes || Yes
|}
'''Finding:''' Both external code sources are MIT licensed, which is fully compatible with TorchGeo's MIT license. Attribution is properly documented in the source file headers.
=== 4. Vendored/Bundled Code ===
'''Finding:''' No vendored or bundled third-party code exists in the source tree. All dependencies are external and installed via pip/conda.
* No <code>vendor/</code>, <code>third_party/</code>, or <code>external/</code> directories
* No embedded copies of libraries (unlike GDAL which bundles libtiff, libjpeg, etc.)
* All 18 dependencies are fetched externally at install time
=== 5. Copyright Holders ===
{| class="wikitable"
|-
! Copyright Holder !! Type !! Notes
|-
| TorchGeo Contributors || Collective || Single copyright holder for all files
|}
'''Finding:''' The project uses a '''collective copyright model'''. All files use "Copyright (c) TorchGeo Contributors" rather than individual contributor names.
'''Implications for relicensing:'''
* Simplified model - no need to contact 122 individual contributors
* Contributors implicitly agree to collective copyright by submitting PRs
* '''NEEDS CLARIFICATION:''' Does the project have a Contributor License Agreement (CLA) or Developer Certificate of Origin (DCO)?
=== 6. Outstanding Issues ===
'''Resolved:'''
* Copyright headers added to 2 missing files: [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262]
'''Pending:'''
* '''NEEDS PSC INPUT:''' Confirm whether a CLA/DCO is in place or planned
* '''NEEDS PSC INPUT:''' Contributor agreement status for PSC members (currently all marked TBD)
=== 7. Conclusion ===
'''Overall assessment:''' No provenance issues identified
The TorchGeo codebase demonstrates good copyright hygiene:
* 100% of source files have proper license headers
* All code is consistently MIT licensed
* External code derivations are properly attributed and license-compatible
* No vendored code complicates the license picture
* Collective copyright model simplifies governance
The codebase is ready for OSGeo incubation from a code provenance perspective, pending confirmation of contributor agreement procedures from the PSC.

==Frequently Asked Questions==

;Do we need to ensure there is a copyright and licence headers in every file?
:Projects are expected to embed a copyright and license header in every source file (.cpp and .h for instance). Machine generated files (such as lex or yacc output for instance) does not require a header if it is inconvenient to embed one, but then an effort should be made to embed a header in the original source file (ie. .l or .y). There is no need to embed copyright and license headers in build files (ie. Makefiles, Visual Studio project files), nor in small documentation fragments (like READMEs). Copyright/license headers should be included in substantial bodies of documentation if it can be done in such a way that it doesn't interfere with the document.

;Do I really need to embed the whole license agreement in every file?
:No, it is sufficient to refer to a single copy of the license agreement for the project, but each file should include an indication of what the license is, and the location of the full license document. For example:
/*
* Copyright (C) 2004-2005 Autodesk, Inc.
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of version 2.1 of the GNU Lesser
* General Public License as published by the Free Software Foundation.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this library; if not, write to the Free Software
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*/

or:

* COPYRIGHT: (C) 2001 by the GRASS Development Team
*
* This program is free software under the GNU General Public
* License (>=v2). Read the file COPYING that comes with GRASS
* for details.

;Can I just write a script to check everything?
:No. The point of a human review is to ensure that human eyes have looked at the header of each file, looking for any anomalies. For instance it is not uncommon to have additional messages written in headers about the original source of particular code, but not necessarily in a way that a script could recognise.

; But I just did a review similar to this a few months ago, do I really need to do it again?
: If you believe you have already met or exceeded the rigor described in this review document, then you can present the results of your previous analysis along with an explanation of why you think it still applies. You will need to manually review additions since that earlier review. It will be up to the Incubator (and ultimately the foundation board) to determine if they are satisfied with any review.

;Do I need to track down every contributor and ask for permission to use their code?
:No. As long as code was knowingly provided by contributors to the project while it was under a clear licensing policy then it is reasonable to assume the project licensing arrangements are accepted unless there is some reason to have doubts. If code was brought into the project from outside sources under ambiguous circumstances then it may be necessary to contact the copyright holder for a legal release, or at least a statement of permission.

;Some project code was adapted from other sources with ambiguous copyrights, what do I do?
:First, document such concerns in the review document and within the source files themselves. Second, try to obtain a release to use the provide code. An email statement of permission should be sufficient, but pertinant details of such an email should be included in the source file in questions (eg. date, identification of releasing person, text of the release). If no release is possible, but the code isn't very necessary, consider removing or replacing it to simplify things. Otherwise the issue will need to be discussed in the incubator to assess risk.

; Should I be looking for patent problems?
: No. However, if the code review turns up notes about patent issues - or if there are known patent issues for the project, then these should be noted in the review document. Generally speaking a proper patent review is very difficult and may increase, rather than decrease, legal liability.

; Should I be looking for trademark conflicts?
: Possibly. It may be prudent to check for trademark conflicts for the project name, or the name of public packages within the project. If issues are found they should be noted in the review document.

--

[[Category: Incubation]]

TorchGeo Code Provenance

2026-01-08T16:10:39Z

Ominiverdi: /* Code Copyright Review */

=Code Provenance Review Process=

TorchGeo project
'''refer : https://www.osgeo.org/about/committees/incubation/graduation/'''

==Document Status==

{| class="wikitable"
|-
| '''Version:''' || 0.2
|-
| '''Status:''' || Updated
|-
| '''Last Edited:''' || 08 Jan 2026
|}

==Purpose==

Show to "reasonable comfort level" that TorchGeo
does not have improperly contributed code, and that the code is all under the Project license.

Notice: ''It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly. The onus is not on the OSGeo Incubation Committee to prove there are no problems. However, OSGeo Incubation Committee does need to ensure that OSGeo does not officially endorse code with provenance issues that could have identified and corrected with a reasonable effort.''

=TorchGeo Provenance Review=

== Project History ==

TorchGeo started as an internship project at Microsoft's AI for Good Lab in 2021, with continued support and funding from the University of Illinois Urbana-Champaign and the National Center for Supercomputing Applications. Since then, TorchGeo has been adopted by a diverse community of researchers from academia, industry, and government research institutions who have contributed to the success of the library. In 2025, we founded a new TorchGeo Organization to manage the TorchGeo Project, with the support of members from the above organizations.

Key milestones:

- 2021-05-11: Initial commit (2330aad) by Adam J. Stewart

- 2021-2024: Organic growth to 120+ contributors

- 2025: Formation of TorchGeo Organization with formal governance structure

- 2026: OSGeo incubation application submitted

==Libraries==

All dependencies are external (not bundled in source tree). All licenses are OSI-approved and compatible with MIT.

{| class="wikitable" border="1"
|-
! Library !! License !! Compatible? !! In Core? !! Issues? !! Ok? !! Comments
|-
| einops || MIT || Yes || External || - || Yes || Tensor operations
|-
| geopandas || BSD-3-Clause || Yes || External || - || Yes || Geospatial dataframes
|-
| jsonargparse || MIT || Yes || External || - || Yes || CLI argument parsing
|-
| kornia || Apache-2.0 || Yes || External || - || Yes || Computer vision ops
|-
| lightly || MIT || Yes || External || - || Yes || Self-supervised learning
|-
| lightning || Apache-2.0 || Yes || External || - || Yes || Training framework
|-
| matplotlib || PSF || Yes || External || - || Yes || Plotting
|-
| numpy || BSD-3-Clause || Yes || External || - || Yes || Numerical computing
|-
| pandas || BSD-3-Clause || Yes || External || - || Yes || Data manipulation
|-
| pillow || HPND || Yes || External || - || Yes || Image I/O
|-
| pyproj || MIT || Yes || External || - || Yes || Cartographic projections
|-
| rasterio || BSD-3-Clause || Yes || External || - || Yes || Geospatial raster I/O
|-
| segmentation-models-pytorch || MIT || Yes || External || - || Yes || Segmentation architectures
|-
| shapely || BSD-3-Clause || Yes || External || - || Yes || Geometric operations
|-
| timm || Apache-2.0 || Yes || External || - || Yes || Vision model zoo
|-
| torch || BSD-3-Clause || Yes || External || - || Yes || PyTorch core
|-
| torchmetrics || Apache-2.0 || Yes || External || - || Yes || Metrics computation
|-
| torchvision || BSD-3-Clause || Yes || External || - || Yes || Vision utilities
|}

==Copyright Holders==
{| class="wikitable" border="1"
|-
! Copyright Holder !! Contact !! Issues !! Comments
|-
| TorchGeo Contributors || N/A (collective) || None || Per LICENSE file
|}

The MIT License file states: "Copyright (c) TorchGeo Contributors."

This is a collective copyright model - individual contributors retain copyright but license under MIT.

== Committers ==
'''Total human contributors:''' 122

'''Total commits:''' 2778 (excluding bots)

'''Top contributors''' (PSC members marked with *):

{| class="wikitable" border="1"
|-
! Committer !! Email !! Affiliation !! Agreement Signed?
|-
| Adam J. Stewart * || ajstewart426@gmail.com || TUM / UIUC || TBD
|-
| Caleb Robinson * || calebrob6@gmail.com || Microsoft AI for Good || TBD
|-
| Isaac Corley * || isaac.corley@proton.me || Wherobots || TBD
|-
| Nils Lehmann * || nils.lehmann24@gmail.com || TUM || TBD
|-
| Ashwin Nair * || ashnair0007@gmail.com || Space42 || TBD
|-
| Anthony Ortiz * || Anthony.Ortiz@microsoft.com || Microsoft || TBD
|-
| Robin Cole || robmarkcole@gmail.com || - || TBD
|-
| Yi Wang || wangyi111@users.noreply.github.com || - || TBD
|-
| Yi-Chia Chang || yichiac@users.noreply.github.com || - || TBD
|-
| Burak || burakekim@users.noreply.github.com || - || TBD
|-
| Blaz Rolih || blaz-r@users.noreply.github.com || - || TBD
|-
| Maciej Kilian || iejMac@users.noreply.github.com || - || TBD
|-
| Qiusheng Wu || giswqs@gmail.com || - || TBD
|}

'''Note:''' 122 total contributors. Full list available via <code>git shortlog -sne --all</code>.

==Source Files==
'''Total Python files:''' 557

'''Files with copyright header:''' 557 (100%) - ''after PR #3262 merged''

'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.

{| class="wikitable" border="1"
|-
! File !! License !! Copyright Holder !! Header? !! Issues? !! Ok? !! Comments
|-
| docs/user/metrics/update_timeline.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|-
| tests/data/landcoverai/split.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|}

'''Note:''' PR https://github.com/torchgeo/torchgeo/pull/3262 adds copyright headers to the 2 files that were missing them.

==Further Issues ==
'''Resolved:'''
* Copyright headers added to 2 missing files via PR #3262: https://github.com/torchgeo/torchgeo/pull/3262

'''Pending:'''
* Contributor agreement status needs confirmation from PSC members

== TorchGeo Application Questionnaire ==

https://trac.osgeo.org/osgeo/wiki/TorchGeo

==Process==

The Code Provenance Review is separated into two sections, each with a slightly different process:
# Create a Provenance Review Document by copying the [[Provenance Review Template]].
# Complete the Library/Component Review Process.
# Complete the Code Copyright Review.
# Submit the completed Provenance Review Document to the Project Mentor for review.

==Library/Component Review Process==

For the overall project, document potential Library/Component issues by:
# Listing any external components that are included "in the source tree" for the project. For instance, GDAL includes a copy of libtiff, libjpeg, etc in the source tree. It is necessary to be able to identify things like that in the source tree that are under their own distinct license, and are not explicitly vetted by the project team. If practical, it is desirable to remove these internal components and treat them as external dependencies. If kept internal, notes on the licenses of the components should be documented using the Provenance Review Template.
# Listing all external dependencies with:
## Potentially problematic license terms (all non-free libraries, for instance).
## All libraries with licenses that might conflict (for instance GDAL's use of GPL'ed GRASS libraries in the non-GPL GDAL).

== Code Copyright Review ==
'''Review completed:''' 08 Jan 2026
'''Reviewer:''' Brian M Hamlin (Mentor), with assistance from automated tooling
'''Scope:''' All 557 Python source files in the TorchGeo repository
=== 1. License Headers ===
{| class="wikitable"
|-
| '''Total Python files:''' || 557
|-
| '''Files with standard header:''' || 557 (100%)
|-
| '''Files missing header:''' || 0 (after [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262])
|}
'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.
'''Finding:''' All source files include the standard license header. Two utility scripts (<code>docs/user/metrics/update_timeline.py</code> and <code>tests/data/landcoverai/split.py</code>) were identified as missing headers during this review and fixed via [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262].
=== 2. License Consistency ===
'''Finding:''' All files are under the '''MIT License'''. No files use a different or conflicting license.
* No GPL, LGPL, or copyleft licenses found
* No Apache-only or BSD-only files found
* All code consistently uses MIT
=== 3. Code Origins ===
Two files contain code derived from external sources. Both are properly attributed and both original sources use MIT License (compatible):
{| class="wikitable"
|-
! File !! Source !! Source License !! Compatible? !! Attribution in File?
|-
| <code>torchgeo/models/btc.py</code> || [https://github.com/blaz-r/BTC-change-detection blaz-r/BTC-change-detection] || MIT || Yes || Yes
|-
| <code>torchgeo/models/croma.py</code> || [https://github.com/antofuller/CROMA antofuller/CROMA] || MIT || Yes || Yes
|}
'''Finding:''' Both external code sources are MIT licensed, which is fully compatible with TorchGeo's MIT license. Attribution is properly documented in the source file headers.
=== 4. Vendored/Bundled Code ===
'''Finding:''' No vendored or bundled third-party code exists in the source tree. All dependencies are external and installed via pip/conda.
* No <code>vendor/</code>, <code>third_party/</code>, or <code>external/</code> directories
* No embedded copies of libraries (unlike GDAL which bundles libtiff, libjpeg, etc.)
* All 18 dependencies are fetched externally at install time
=== 5. Copyright Holders ===
{| class="wikitable"
|-
! Copyright Holder !! Type !! Notes
|-
| TorchGeo Contributors || Collective || Single copyright holder for all files
|}
'''Finding:''' The project uses a '''collective copyright model'''. All files use "Copyright (c) TorchGeo Contributors" rather than individual contributor names.
'''Implications for relicensing:'''
* Simplified model - no need to contact 122 individual contributors
* Contributors implicitly agree to collective copyright by submitting PRs
* '''NEEDS CLARIFICATION:''' Does the project have a Contributor License Agreement (CLA) or Developer Certificate of Origin (DCO)?
=== 6. Outstanding Issues ===
'''Resolved:'''
* Copyright headers added to 2 missing files: [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262]
'''Pending:'''
* '''NEEDS PSC INPUT:''' Confirm whether a CLA/DCO is in place or planned
* '''NEEDS PSC INPUT:''' Contributor agreement status for PSC members (currently all marked TBD)
=== 7. Conclusion ===
'''Overall assessment:''' No provenance issues identified
The TorchGeo codebase demonstrates good copyright hygiene:
* 100% of source files have proper license headers
* All code is consistently MIT licensed
* External code derivations are properly attributed and license-compatible
* No vendored code complicates the license picture
* Collective copyright model simplifies governance
The codebase is ready for OSGeo incubation from a code provenance perspective, pending confirmation of contributor agreement procedures from the PSC.

==Frequently Asked Questions==

;Do we need to ensure there is a copyright and licence headers in every file?
:Projects are expected to embed a copyright and license header in every source file (.cpp and .h for instance). Machine generated files (such as lex or yacc output for instance) does not require a header if it is inconvenient to embed one, but then an effort should be made to embed a header in the original source file (ie. .l or .y). There is no need to embed copyright and license headers in build files (ie. Makefiles, Visual Studio project files), nor in small documentation fragments (like READMEs). Copyright/license headers should be included in substantial bodies of documentation if it can be done in such a way that it doesn't interfere with the document.

;Do I really need to embed the whole license agreement in every file?
:No, it is sufficient to refer to a single copy of the license agreement for the project, but each file should include an indication of what the license is, and the location of the full license document. For example:
/*
* Copyright (C) 2004-2005 Autodesk, Inc.
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of version 2.1 of the GNU Lesser
* General Public License as published by the Free Software Foundation.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this library; if not, write to the Free Software
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*/

or:

* COPYRIGHT: (C) 2001 by the GRASS Development Team
*
* This program is free software under the GNU General Public
* License (>=v2). Read the file COPYING that comes with GRASS
* for details.

;Can I just write a script to check everything?
:No. The point of a human review is to ensure that human eyes have looked at the header of each file, looking for any anomalies. For instance it is not uncommon to have additional messages written in headers about the original source of particular code, but not necessarily in a way that a script could recognise.

; But I just did a review similar to this a few months ago, do I really need to do it again?
: If you believe you have already met or exceeded the rigor described in this review document, then you can present the results of your previous analysis along with an explanation of why you think it still applies. You will need to manually review additions since that earlier review. It will be up to the Incubator (and ultimately the foundation board) to determine if they are satisfied with any review.

;Do I need to track down every contributor and ask for permission to use their code?
:No. As long as code was knowingly provided by contributors to the project while it was under a clear licensing policy then it is reasonable to assume the project licensing arrangements are accepted unless there is some reason to have doubts. If code was brought into the project from outside sources under ambiguous circumstances then it may be necessary to contact the copyright holder for a legal release, or at least a statement of permission.

;Some project code was adapted from other sources with ambiguous copyrights, what do I do?
:First, document such concerns in the review document and within the source files themselves. Second, try to obtain a release to use the provide code. An email statement of permission should be sufficient, but pertinant details of such an email should be included in the source file in questions (eg. date, identification of releasing person, text of the release). If no release is possible, but the code isn't very necessary, consider removing or replacing it to simplify things. Otherwise the issue will need to be discussed in the incubator to assess risk.

; Should I be looking for patent problems?
: No. However, if the code review turns up notes about patent issues - or if there are known patent issues for the project, then these should be noted in the review document. Generally speaking a proper patent review is very difficult and may increase, rather than decrease, legal liability.

; Should I be looking for trademark conflicts?
: Possibly. It may be prudent to check for trademark conflicts for the project name, or the name of public packages within the project. If issues are found they should be noted in the review document.

--

[[Category: Incubation]]

TorchGeo Code Provenance

2026-01-08T16:10:17Z

Ominiverdi: /* Code Copyright Review */

=Code Provenance Review Process=

TorchGeo project
'''refer : https://www.osgeo.org/about/committees/incubation/graduation/'''

==Document Status==

{| class="wikitable"
|-
| '''Version:''' || 0.2
|-
| '''Status:''' || Updated
|-
| '''Last Edited:''' || 08 Jan 2026
|}

==Purpose==

Show to "reasonable comfort level" that TorchGeo
does not have improperly contributed code, and that the code is all under the Project license.

Notice: ''It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly. The onus is not on the OSGeo Incubation Committee to prove there are no problems. However, OSGeo Incubation Committee does need to ensure that OSGeo does not officially endorse code with provenance issues that could have identified and corrected with a reasonable effort.''

=TorchGeo Provenance Review=

== Project History ==

TorchGeo started as an internship project at Microsoft's AI for Good Lab in 2021, with continued support and funding from the University of Illinois Urbana-Champaign and the National Center for Supercomputing Applications. Since then, TorchGeo has been adopted by a diverse community of researchers from academia, industry, and government research institutions who have contributed to the success of the library. In 2025, we founded a new TorchGeo Organization to manage the TorchGeo Project, with the support of members from the above organizations.

Key milestones:

- 2021-05-11: Initial commit (2330aad) by Adam J. Stewart

- 2021-2024: Organic growth to 120+ contributors

- 2025: Formation of TorchGeo Organization with formal governance structure

- 2026: OSGeo incubation application submitted

==Libraries==

All dependencies are external (not bundled in source tree). All licenses are OSI-approved and compatible with MIT.

{| class="wikitable" border="1"
|-
! Library !! License !! Compatible? !! In Core? !! Issues? !! Ok? !! Comments
|-
| einops || MIT || Yes || External || - || Yes || Tensor operations
|-
| geopandas || BSD-3-Clause || Yes || External || - || Yes || Geospatial dataframes
|-
| jsonargparse || MIT || Yes || External || - || Yes || CLI argument parsing
|-
| kornia || Apache-2.0 || Yes || External || - || Yes || Computer vision ops
|-
| lightly || MIT || Yes || External || - || Yes || Self-supervised learning
|-
| lightning || Apache-2.0 || Yes || External || - || Yes || Training framework
|-
| matplotlib || PSF || Yes || External || - || Yes || Plotting
|-
| numpy || BSD-3-Clause || Yes || External || - || Yes || Numerical computing
|-
| pandas || BSD-3-Clause || Yes || External || - || Yes || Data manipulation
|-
| pillow || HPND || Yes || External || - || Yes || Image I/O
|-
| pyproj || MIT || Yes || External || - || Yes || Cartographic projections
|-
| rasterio || BSD-3-Clause || Yes || External || - || Yes || Geospatial raster I/O
|-
| segmentation-models-pytorch || MIT || Yes || External || - || Yes || Segmentation architectures
|-
| shapely || BSD-3-Clause || Yes || External || - || Yes || Geometric operations
|-
| timm || Apache-2.0 || Yes || External || - || Yes || Vision model zoo
|-
| torch || BSD-3-Clause || Yes || External || - || Yes || PyTorch core
|-
| torchmetrics || Apache-2.0 || Yes || External || - || Yes || Metrics computation
|-
| torchvision || BSD-3-Clause || Yes || External || - || Yes || Vision utilities
|}

==Copyright Holders==
{| class="wikitable" border="1"
|-
! Copyright Holder !! Contact !! Issues !! Comments
|-
| TorchGeo Contributors || N/A (collective) || None || Per LICENSE file
|}

The MIT License file states: "Copyright (c) TorchGeo Contributors."

This is a collective copyright model - individual contributors retain copyright but license under MIT.

== Committers ==
'''Total human contributors:''' 122

'''Total commits:''' 2778 (excluding bots)

'''Top contributors''' (PSC members marked with *):

{| class="wikitable" border="1"
|-
! Committer !! Email !! Affiliation !! Agreement Signed?
|-
| Adam J. Stewart * || ajstewart426@gmail.com || TUM / UIUC || TBD
|-
| Caleb Robinson * || calebrob6@gmail.com || Microsoft AI for Good || TBD
|-
| Isaac Corley * || isaac.corley@proton.me || Wherobots || TBD
|-
| Nils Lehmann * || nils.lehmann24@gmail.com || TUM || TBD
|-
| Ashwin Nair * || ashnair0007@gmail.com || Space42 || TBD
|-
| Anthony Ortiz * || Anthony.Ortiz@microsoft.com || Microsoft || TBD
|-
| Robin Cole || robmarkcole@gmail.com || - || TBD
|-
| Yi Wang || wangyi111@users.noreply.github.com || - || TBD
|-
| Yi-Chia Chang || yichiac@users.noreply.github.com || - || TBD
|-
| Burak || burakekim@users.noreply.github.com || - || TBD
|-
| Blaz Rolih || blaz-r@users.noreply.github.com || - || TBD
|-
| Maciej Kilian || iejMac@users.noreply.github.com || - || TBD
|-
| Qiusheng Wu || giswqs@gmail.com || - || TBD
|}

'''Note:''' 122 total contributors. Full list available via <code>git shortlog -sne --all</code>.

==Source Files==
'''Total Python files:''' 557

'''Files with copyright header:''' 557 (100%) - ''after PR #3262 merged''

'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.

{| class="wikitable" border="1"
|-
! File !! License !! Copyright Holder !! Header? !! Issues? !! Ok? !! Comments
|-
| docs/user/metrics/update_timeline.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|-
| tests/data/landcoverai/split.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|}

'''Note:''' PR https://github.com/torchgeo/torchgeo/pull/3262 adds copyright headers to the 2 files that were missing them.

==Further Issues ==
'''Resolved:'''
* Copyright headers added to 2 missing files via PR #3262: https://github.com/torchgeo/torchgeo/pull/3262

'''Pending:'''
* Contributor agreement status needs confirmation from PSC members

== TorchGeo Application Questionnaire ==

https://trac.osgeo.org/osgeo/wiki/TorchGeo

==Process==

The Code Provenance Review is separated into two sections, each with a slightly different process:
# Create a Provenance Review Document by copying the [[Provenance Review Template]].
# Complete the Library/Component Review Process.
# Complete the Code Copyright Review.
# Submit the completed Provenance Review Document to the Project Mentor for review.

==Library/Component Review Process==

For the overall project, document potential Library/Component issues by:
# Listing any external components that are included "in the source tree" for the project. For instance, GDAL includes a copy of libtiff, libjpeg, etc in the source tree. It is necessary to be able to identify things like that in the source tree that are under their own distinct license, and are not explicitly vetted by the project team. If practical, it is desirable to remove these internal components and treat them as external dependencies. If kept internal, notes on the licenses of the components should be documented using the Provenance Review Template.
# Listing all external dependencies with:
## Potentially problematic license terms (all non-free libraries, for instance).
## All libraries with licenses that might conflict (for instance GDAL's use of GPL'ed GRASS libraries in the non-GPL GDAL).

==Code Copyright Review==

== Code Copyright Review ==
'''Review completed:''' 08 Jan 2026
'''Reviewer:''' Brian M Hamlin (Mentor), with assistance from automated tooling
'''Scope:''' All 557 Python source files in the TorchGeo repository
=== 1. License Headers ===
{| class="wikitable"
|-
| '''Total Python files:''' || 557
|-
| '''Files with standard header:''' || 557 (100%)
|-
| '''Files missing header:''' || 0 (after [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262])
|}
'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.
'''Finding:''' All source files include the standard license header. Two utility scripts (<code>docs/user/metrics/update_timeline.py</code> and <code>tests/data/landcoverai/split.py</code>) were identified as missing headers during this review and fixed via [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262].
=== 2. License Consistency ===
'''Finding:''' All files are under the '''MIT License'''. No files use a different or conflicting license.
* No GPL, LGPL, or copyleft licenses found
* No Apache-only or BSD-only files found
* All code consistently uses MIT
=== 3. Code Origins ===
Two files contain code derived from external sources. Both are properly attributed and both original sources use MIT License (compatible):
{| class="wikitable"
|-
! File !! Source !! Source License !! Compatible? !! Attribution in File?
|-
| <code>torchgeo/models/btc.py</code> || [https://github.com/blaz-r/BTC-change-detection blaz-r/BTC-change-detection] || MIT || Yes || Yes
|-
| <code>torchgeo/models/croma.py</code> || [https://github.com/antofuller/CROMA antofuller/CROMA] || MIT || Yes || Yes
|}
'''Finding:''' Both external code sources are MIT licensed, which is fully compatible with TorchGeo's MIT license. Attribution is properly documented in the source file headers.
=== 4. Vendored/Bundled Code ===
'''Finding:''' No vendored or bundled third-party code exists in the source tree. All dependencies are external and installed via pip/conda.
* No <code>vendor/</code>, <code>third_party/</code>, or <code>external/</code> directories
* No embedded copies of libraries (unlike GDAL which bundles libtiff, libjpeg, etc.)
* All 18 dependencies are fetched externally at install time
=== 5. Copyright Holders ===
{| class="wikitable"
|-
! Copyright Holder !! Type !! Notes
|-
| TorchGeo Contributors || Collective || Single copyright holder for all files
|}
'''Finding:''' The project uses a '''collective copyright model'''. All files use "Copyright (c) TorchGeo Contributors" rather than individual contributor names.
'''Implications for relicensing:'''
* Simplified model - no need to contact 122 individual contributors
* Contributors implicitly agree to collective copyright by submitting PRs
* '''NEEDS CLARIFICATION:''' Does the project have a Contributor License Agreement (CLA) or Developer Certificate of Origin (DCO)?
=== 6. Outstanding Issues ===
'''Resolved:'''
* Copyright headers added to 2 missing files: [https://github.com/torchgeo/torchgeo/pull/3262 PR #3262]
'''Pending:'''
* '''NEEDS PSC INPUT:''' Confirm whether a CLA/DCO is in place or planned
* '''NEEDS PSC INPUT:''' Contributor agreement status for PSC members (currently all marked TBD)
=== 7. Conclusion ===
'''Overall assessment:''' No provenance issues identified
The TorchGeo codebase demonstrates good copyright hygiene:
* 100% of source files have proper license headers
* All code is consistently MIT licensed
* External code derivations are properly attributed and license-compatible
* No vendored code complicates the license picture
* Collective copyright model simplifies governance
The codebase is ready for OSGeo incubation from a code provenance perspective, pending confirmation of contributor agreement procedures from the PSC.

==Frequently Asked Questions==

;Do we need to ensure there is a copyright and licence headers in every file?
:Projects are expected to embed a copyright and license header in every source file (.cpp and .h for instance). Machine generated files (such as lex or yacc output for instance) does not require a header if it is inconvenient to embed one, but then an effort should be made to embed a header in the original source file (ie. .l or .y). There is no need to embed copyright and license headers in build files (ie. Makefiles, Visual Studio project files), nor in small documentation fragments (like READMEs). Copyright/license headers should be included in substantial bodies of documentation if it can be done in such a way that it doesn't interfere with the document.

;Do I really need to embed the whole license agreement in every file?
:No, it is sufficient to refer to a single copy of the license agreement for the project, but each file should include an indication of what the license is, and the location of the full license document. For example:
/*
* Copyright (C) 2004-2005 Autodesk, Inc.
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of version 2.1 of the GNU Lesser
* General Public License as published by the Free Software Foundation.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this library; if not, write to the Free Software
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*/

or:

* COPYRIGHT: (C) 2001 by the GRASS Development Team
*
* This program is free software under the GNU General Public
* License (>=v2). Read the file COPYING that comes with GRASS
* for details.

;Can I just write a script to check everything?
:No. The point of a human review is to ensure that human eyes have looked at the header of each file, looking for any anomalies. For instance it is not uncommon to have additional messages written in headers about the original source of particular code, but not necessarily in a way that a script could recognise.

; But I just did a review similar to this a few months ago, do I really need to do it again?
: If you believe you have already met or exceeded the rigor described in this review document, then you can present the results of your previous analysis along with an explanation of why you think it still applies. You will need to manually review additions since that earlier review. It will be up to the Incubator (and ultimately the foundation board) to determine if they are satisfied with any review.

;Do I need to track down every contributor and ask for permission to use their code?
:No. As long as code was knowingly provided by contributors to the project while it was under a clear licensing policy then it is reasonable to assume the project licensing arrangements are accepted unless there is some reason to have doubts. If code was brought into the project from outside sources under ambiguous circumstances then it may be necessary to contact the copyright holder for a legal release, or at least a statement of permission.

;Some project code was adapted from other sources with ambiguous copyrights, what do I do?
:First, document such concerns in the review document and within the source files themselves. Second, try to obtain a release to use the provide code. An email statement of permission should be sufficient, but pertinant details of such an email should be included in the source file in questions (eg. date, identification of releasing person, text of the release). If no release is possible, but the code isn't very necessary, consider removing or replacing it to simplify things. Otherwise the issue will need to be discussed in the incubator to assess risk.

; Should I be looking for patent problems?
: No. However, if the code review turns up notes about patent issues - or if there are known patent issues for the project, then these should be noted in the review document. Generally speaking a proper patent review is very difficult and may increase, rather than decrease, legal liability.

; Should I be looking for trademark conflicts?
: Possibly. It may be prudent to check for trademark conflicts for the project name, or the name of public packages within the project. If issues are found they should be noted in the review document.

--

[[Category: Incubation]]

TorchGeo Code Provenance

2026-01-08T16:04:41Z

Ominiverdi: /* Frequently Asked Questions */

TorchGeo Code Provenance

2026-01-08T16:02:54Z

Ominiverdi: /* Document Status */

=Code Provenance Review Process=

TorchGeo project
'''refer : https://www.osgeo.org/about/committees/incubation/graduation/'''

==Document Status==

{| class="wikitable"
|-
| '''Version:''' || 0.2
|-
| '''Status:''' || Updated
|-
| '''Last Edited:''' || 08 Jan 2026
|}

==Purpose==

Show to "reasonable comfort level" that TorchGeo
does not have improperly contributed code, and that the code is all under the Project license.

Notice: ''It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly. The onus is not on the OSGeo Incubation Committee to prove there are no problems. However, OSGeo Incubation Committee does need to ensure that OSGeo does not officially endorse code with provenance issues that could have identified and corrected with a reasonable effort.''

=TorchGeo Provenance Review=

== Project History ==

TorchGeo started as an internship project at Microsoft's AI for Good Lab in 2021, with continued support and funding from the University of Illinois Urbana-Champaign and the National Center for Supercomputing Applications. Since then, TorchGeo has been adopted by a diverse community of researchers from academia, industry, and government research institutions who have contributed to the success of the library. In 2025, we founded a new TorchGeo Organization to manage the TorchGeo Project, with the support of members from the above organizations.

Key milestones:

- 2021-05-11: Initial commit (2330aad) by Adam J. Stewart

- 2021-2024: Organic growth to 120+ contributors

- 2025: Formation of TorchGeo Organization with formal governance structure

- 2026: OSGeo incubation application submitted

==Libraries==

All dependencies are external (not bundled in source tree). All licenses are OSI-approved and compatible with MIT.

{| class="wikitable" border="1"
|-
! Library !! License !! Compatible? !! In Core? !! Issues? !! Ok? !! Comments
|-
| einops || MIT || Yes || External || - || Yes || Tensor operations
|-
| geopandas || BSD-3-Clause || Yes || External || - || Yes || Geospatial dataframes
|-
| jsonargparse || MIT || Yes || External || - || Yes || CLI argument parsing
|-
| kornia || Apache-2.0 || Yes || External || - || Yes || Computer vision ops
|-
| lightly || MIT || Yes || External || - || Yes || Self-supervised learning
|-
| lightning || Apache-2.0 || Yes || External || - || Yes || Training framework
|-
| matplotlib || PSF || Yes || External || - || Yes || Plotting
|-
| numpy || BSD-3-Clause || Yes || External || - || Yes || Numerical computing
|-
| pandas || BSD-3-Clause || Yes || External || - || Yes || Data manipulation
|-
| pillow || HPND || Yes || External || - || Yes || Image I/O
|-
| pyproj || MIT || Yes || External || - || Yes || Cartographic projections
|-
| rasterio || BSD-3-Clause || Yes || External || - || Yes || Geospatial raster I/O
|-
| segmentation-models-pytorch || MIT || Yes || External || - || Yes || Segmentation architectures
|-
| shapely || BSD-3-Clause || Yes || External || - || Yes || Geometric operations
|-
| timm || Apache-2.0 || Yes || External || - || Yes || Vision model zoo
|-
| torch || BSD-3-Clause || Yes || External || - || Yes || PyTorch core
|-
| torchmetrics || Apache-2.0 || Yes || External || - || Yes || Metrics computation
|-
| torchvision || BSD-3-Clause || Yes || External || - || Yes || Vision utilities
|}

==Copyright Holders==
{| class="wikitable" border="1"
|-
! Copyright Holder !! Contact !! Issues !! Comments
|-
| TorchGeo Contributors || N/A (collective) || None || Per LICENSE file
|}

The MIT License file states: "Copyright (c) TorchGeo Contributors."

This is a collective copyright model - individual contributors retain copyright but license under MIT.

== Committers ==
'''Total human contributors:''' 122

'''Total commits:''' 2778 (excluding bots)

'''Top contributors''' (PSC members marked with *):

{| class="wikitable" border="1"
|-
! Committer !! Email !! Affiliation !! Agreement Signed?
|-
| Adam J. Stewart * || ajstewart426@gmail.com || TUM / UIUC || TBD
|-
| Caleb Robinson * || calebrob6@gmail.com || Microsoft AI for Good || TBD
|-
| Isaac Corley * || isaac.corley@proton.me || Wherobots || TBD
|-
| Nils Lehmann * || nils.lehmann24@gmail.com || TUM || TBD
|-
| Ashwin Nair * || ashnair0007@gmail.com || Space42 || TBD
|-
| Anthony Ortiz * || Anthony.Ortiz@microsoft.com || Microsoft || TBD
|-
| Robin Cole || robmarkcole@gmail.com || - || TBD
|-
| Yi Wang || wangyi111@users.noreply.github.com || - || TBD
|-
| Yi-Chia Chang || yichiac@users.noreply.github.com || - || TBD
|-
| Burak || burakekim@users.noreply.github.com || - || TBD
|-
| Blaz Rolih || blaz-r@users.noreply.github.com || - || TBD
|-
| Maciej Kilian || iejMac@users.noreply.github.com || - || TBD
|-
| Qiusheng Wu || giswqs@gmail.com || - || TBD
|}

'''Note:''' 122 total contributors. Full list available via <code>git shortlog -sne --all</code>.

==Source Files==
'''Total Python files:''' 557

'''Files with copyright header:''' 557 (100%) - ''after PR #3262 merged''

'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.

{| class="wikitable" border="1"
|-
! File !! License !! Copyright Holder !! Header? !! Issues? !! Ok? !! Comments
|-
| docs/user/metrics/update_timeline.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|-
| tests/data/landcoverai/split.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|}

'''Note:''' PR https://github.com/torchgeo/torchgeo/pull/3262 adds copyright headers to the 2 files that were missing them.

==Further Issues ==
'''Resolved:'''
* Copyright headers added to 2 missing files via PR #3262: https://github.com/torchgeo/torchgeo/pull/3262

'''Pending:'''
* Contributor agreement status needs confirmation from PSC members

== TorchGeo Application Questionnaire ==

https://trac.osgeo.org/osgeo/wiki/TorchGeo

==Process==

The Code Provenance Review is separated into two sections, each with a slightly different process:
# Create a Provenance Review Document by copying the [[Provenance Review Template]].
# Complete the Library/Component Review Process.
# Complete the Code Copyright Review.
# Submit the completed Provenance Review Document to the Project Mentor for review.

==Library/Component Review Process==

For the overall project, document potential Library/Component issues by:
# Listing any external components that are included "in the source tree" for the project. For instance, GDAL includes a copy of libtiff, libjpeg, etc in the source tree. It is necessary to be able to identify things like that in the source tree that are under their own distinct license, and are not explicitly vetted by the project team. If practical, it is desirable to remove these internal components and treat them as external dependencies. If kept internal, notes on the licenses of the components should be documented using the Provenance Review Template.
# Listing all external dependencies with:
## Potentially problematic license terms (all non-free libraries, for instance).
## All libraries with licenses that might conflict (for instance GDAL's use of GPL'ed GRASS libraries in the non-GPL GDAL).

==Code Copyright Review==

For each project source file, perform the following:
# Does the file include the license information? If not, add it if there there is no ambiguity about whether the standard project license applies. If that is not obvious, make notes in the review document.
# Is the file under the normal project license? If not, make notes in the review document.
# Is there anything obviously unusual about the origin of the code? Does this pose any conflicts? Is the issue properly described in the source file? For instance, in GDAL, the gdal/port/cpl_strtod.cpp file is closely derived from external code that was placed in the public domain. cpl_strtod.cpp is placed under the normal GDAL MIT/X license, but detailed notes are kept in the header text on it's origin, the fact that this was public domain and so the fact that it is ok to relicense it. Oddities should be noted in the source file itself and in the review document.
# Maintain a list of all copyright holders identified in the Provenance Review Document. This list is essentially everyone who would need to agree to relicense the project. It may be desirable to seek copyright assignment to a "project lead", or to the foundation to reduce the number of copyright holders for the project, although this is not required.

==Frequently Asked Questions==

;Do we need to ensure there is a copyright and licence headers in every file?
:Projects are expected to embed a copyright and license header in every source file (.cpp and .h for instance). Machine generated files (such as lex or yacc output for instance) does not require a header if it is inconvenient to embed one, but then an effort should be made to embed a header in the original source file (ie. .l or .y). There is no need to embed copyright and license headers in build files (ie. Makefiles, Visual Studio project files), nor in small documentation fragments (like READMEs). Copyright/license headers should be included in substantial bodies of documentation if it can be done in such a way that it doesn't interfere with the document.

;Do I really need to embed the whole license agreement in every file?
:No, it is sufficient to refer to a single copy of the license agreement for the project, but each file should include an indication of what the license is, and the location of the full license document. For example:
/*
* Copyright (C) 2004-2005 Autodesk, Inc.
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of version 2.1 of the GNU Lesser
* General Public License as published by the Free Software Foundation.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this library; if not, write to the Free Software
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*/

or:

* COPYRIGHT: (C) 2001 by the GRASS Development Team
*
* This program is free software under the GNU General Public
* License (>=v2). Read the file COPYING that comes with GRASS
* for details.

;Can I just write a script to check everything?
:No. The point of a human review is to ensure that human eyes have looked at the header of each file, looking for any anomalies. For instance it is not uncommon to have additional messages written in headers about the original source of particular code, but not necessarily in a way that a script could recognise.

; But I just did a review similar to this a few months ago, do I really need to do it again?
: If you believe you have already met or exceeded the rigor described in this review document, then you can present the results of your previous analysis along with an explanation of why you think it still applies. You will need to manually review additions since that earlier review. It will be up to the Incubator (and ultimately the foundation board) to determine if they are satisfied with any review.

;Do I need to track down every contributor and ask for permission to use their code?
:No. As long as code was knowingly provided by contributors to the project while it was under a clear licensing policy then it is reasonable to assume the project licensing arrangements are accepted unless there is some reason to have doubts. If code was brought into the project from outside sources under ambiguous circumstances then it may be necessary to contact the copyright holder for a legal release, or at least a statement of permission.

;Some project code was adapted from other sources with ambiguous copyrights, what do I do?
:First, document such concerns in the review document and within the source files themselves. Second, try to obtain a release to use the provide code. An email statement of permission should be sufficient, but pertinant details of such an email should be included in the source file in questions (eg. date, identification of releasing person, text of the release). If no release is possible, but the code isn't very necessary, consider removing or replacing it to simplify things. Otherwise the issue will need to be discussed in the incubator to assess risk.

; Should I be looking for patent problems?
: No. However, if the code review turns up notes about patent issues - or if there are known patent issues for the project, then these should be noted in the review document. Generally speaking a proper patent review is very difficult and may increase, rather than decrease, legal liability.

; Should I be looking for trademark conflicts?
: Possibly. It may be prudent to check for trademark conflicts for the project name, or the name of public packages within the project. If issues are found they should be noted in the review document.

--
(generated by Claud-code and tools)

{| class="wikitable"
|-
! Committer !! Username !! Affiliation !! Agreement
|-
| Adam J. Stewart * || ajstewart426@gmail.com || UIUC/Microsoft || TBD
|-
| Caleb Robinson * || calebrob6@gmail.com || Microsoft AI for Good || TBD
|-
| Isaac Corley * || isaaccorley@users.noreply.github.com || Wherobots || TBD
|-
| Nils Lehmann * || nilsleh@users.noreply.github.com || TUM || TBD
|-
| Ashwin Nair * || ash1995@gmail.com || - || TBD
|-
| Robin Cole || robmarkcole@gmail.com || - || TBD
|-
| Yi Wang || wangyi111@users.noreply.github.com || - || TBD
|-
| Yi-Chia Chang || yichiac@users.noreply.github.com || - || TBD
|-
| Burak || burakekim@users.noreply.github.com || - || TBD
|-
| Blaz Rolih || blaz-r@users.noreply.github.com || - || TBD
|-
| Maciej Kilian || iejMac@users.noreply.github.com || - || TBD
|-
| Qiusheng Wu || giswqs@gmail.com || - || TBD
|}

[[Category: Incubation]]

TorchGeo Code Provenance

2026-01-08T16:02:40Z

Ominiverdi: /* Further Issues */

=Code Provenance Review Process=

TorchGeo project
'''refer : https://www.osgeo.org/about/committees/incubation/graduation/'''

==Document Status==

'''Version:''' 0.1

'''Status:''' init

'''Last Edited:''' 06 Jan 2026

==Purpose==

Show to "reasonable comfort level" that TorchGeo
does not have improperly contributed code, and that the code is all under the Project license.

Notice: ''It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly. The onus is not on the OSGeo Incubation Committee to prove there are no problems. However, OSGeo Incubation Committee does need to ensure that OSGeo does not officially endorse code with provenance issues that could have identified and corrected with a reasonable effort.''

=TorchGeo Provenance Review=

== Project History ==

TorchGeo started as an internship project at Microsoft's AI for Good Lab in 2021, with continued support and funding from the University of Illinois Urbana-Champaign and the National Center for Supercomputing Applications. Since then, TorchGeo has been adopted by a diverse community of researchers from academia, industry, and government research institutions who have contributed to the success of the library. In 2025, we founded a new TorchGeo Organization to manage the TorchGeo Project, with the support of members from the above organizations.

Key milestones:

- 2021-05-11: Initial commit (2330aad) by Adam J. Stewart

- 2021-2024: Organic growth to 120+ contributors

- 2025: Formation of TorchGeo Organization with formal governance structure

- 2026: OSGeo incubation application submitted

==Libraries==

All dependencies are external (not bundled in source tree). All licenses are OSI-approved and compatible with MIT.

{| class="wikitable" border="1"
|-
! Library !! License !! Compatible? !! In Core? !! Issues? !! Ok? !! Comments
|-
| einops || MIT || Yes || External || - || Yes || Tensor operations
|-
| geopandas || BSD-3-Clause || Yes || External || - || Yes || Geospatial dataframes
|-
| jsonargparse || MIT || Yes || External || - || Yes || CLI argument parsing
|-
| kornia || Apache-2.0 || Yes || External || - || Yes || Computer vision ops
|-
| lightly || MIT || Yes || External || - || Yes || Self-supervised learning
|-
| lightning || Apache-2.0 || Yes || External || - || Yes || Training framework
|-
| matplotlib || PSF || Yes || External || - || Yes || Plotting
|-
| numpy || BSD-3-Clause || Yes || External || - || Yes || Numerical computing
|-
| pandas || BSD-3-Clause || Yes || External || - || Yes || Data manipulation
|-
| pillow || HPND || Yes || External || - || Yes || Image I/O
|-
| pyproj || MIT || Yes || External || - || Yes || Cartographic projections
|-
| rasterio || BSD-3-Clause || Yes || External || - || Yes || Geospatial raster I/O
|-
| segmentation-models-pytorch || MIT || Yes || External || - || Yes || Segmentation architectures
|-
| shapely || BSD-3-Clause || Yes || External || - || Yes || Geometric operations
|-
| timm || Apache-2.0 || Yes || External || - || Yes || Vision model zoo
|-
| torch || BSD-3-Clause || Yes || External || - || Yes || PyTorch core
|-
| torchmetrics || Apache-2.0 || Yes || External || - || Yes || Metrics computation
|-
| torchvision || BSD-3-Clause || Yes || External || - || Yes || Vision utilities
|}

==Copyright Holders==
{| class="wikitable" border="1"
|-
! Copyright Holder !! Contact !! Issues !! Comments
|-
| TorchGeo Contributors || N/A (collective) || None || Per LICENSE file
|}

The MIT License file states: "Copyright (c) TorchGeo Contributors."

This is a collective copyright model - individual contributors retain copyright but license under MIT.

== Committers ==
'''Total human contributors:''' 122

'''Total commits:''' 2778 (excluding bots)

'''Top contributors''' (PSC members marked with *):

{| class="wikitable" border="1"
|-
! Committer !! Email !! Affiliation !! Agreement Signed?
|-
| Adam J. Stewart * || ajstewart426@gmail.com || TUM / UIUC || TBD
|-
| Caleb Robinson * || calebrob6@gmail.com || Microsoft AI for Good || TBD
|-
| Isaac Corley * || isaac.corley@proton.me || Wherobots || TBD
|-
| Nils Lehmann * || nils.lehmann24@gmail.com || TUM || TBD
|-
| Ashwin Nair * || ashnair0007@gmail.com || Space42 || TBD
|-
| Anthony Ortiz * || Anthony.Ortiz@microsoft.com || Microsoft || TBD
|-
| Robin Cole || robmarkcole@gmail.com || - || TBD
|-
| Yi Wang || wangyi111@users.noreply.github.com || - || TBD
|-
| Yi-Chia Chang || yichiac@users.noreply.github.com || - || TBD
|-
| Burak || burakekim@users.noreply.github.com || - || TBD
|-
| Blaz Rolih || blaz-r@users.noreply.github.com || - || TBD
|-
| Maciej Kilian || iejMac@users.noreply.github.com || - || TBD
|-
| Qiusheng Wu || giswqs@gmail.com || - || TBD
|}

'''Note:''' 122 total contributors. Full list available via <code>git shortlog -sne --all</code>.

==Source Files==
'''Total Python files:''' 557

'''Files with copyright header:''' 557 (100%) - ''after PR #3262 merged''

'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.

{| class="wikitable" border="1"
|-
! File !! License !! Copyright Holder !! Header? !! Issues? !! Ok? !! Comments
|-
| docs/user/metrics/update_timeline.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|-
| tests/data/landcoverai/split.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|}

'''Note:''' PR https://github.com/torchgeo/torchgeo/pull/3262 adds copyright headers to the 2 files that were missing them.

==Further Issues ==
'''Resolved:'''
* Copyright headers added to 2 missing files via PR #3262: https://github.com/torchgeo/torchgeo/pull/3262

'''Pending:'''
* Contributor agreement status needs confirmation from PSC members

== TorchGeo Application Questionnaire ==

https://trac.osgeo.org/osgeo/wiki/TorchGeo

==Process==

The Code Provenance Review is separated into two sections, each with a slightly different process:
# Create a Provenance Review Document by copying the [[Provenance Review Template]].
# Complete the Library/Component Review Process.
# Complete the Code Copyright Review.
# Submit the completed Provenance Review Document to the Project Mentor for review.

==Library/Component Review Process==

For the overall project, document potential Library/Component issues by:
# Listing any external components that are included "in the source tree" for the project. For instance, GDAL includes a copy of libtiff, libjpeg, etc in the source tree. It is necessary to be able to identify things like that in the source tree that are under their own distinct license, and are not explicitly vetted by the project team. If practical, it is desirable to remove these internal components and treat them as external dependencies. If kept internal, notes on the licenses of the components should be documented using the Provenance Review Template.
# Listing all external dependencies with:
## Potentially problematic license terms (all non-free libraries, for instance).
## All libraries with licenses that might conflict (for instance GDAL's use of GPL'ed GRASS libraries in the non-GPL GDAL).

==Code Copyright Review==

For each project source file, perform the following:
# Does the file include the license information? If not, add it if there there is no ambiguity about whether the standard project license applies. If that is not obvious, make notes in the review document.
# Is the file under the normal project license? If not, make notes in the review document.
# Is there anything obviously unusual about the origin of the code? Does this pose any conflicts? Is the issue properly described in the source file? For instance, in GDAL, the gdal/port/cpl_strtod.cpp file is closely derived from external code that was placed in the public domain. cpl_strtod.cpp is placed under the normal GDAL MIT/X license, but detailed notes are kept in the header text on it's origin, the fact that this was public domain and so the fact that it is ok to relicense it. Oddities should be noted in the source file itself and in the review document.
# Maintain a list of all copyright holders identified in the Provenance Review Document. This list is essentially everyone who would need to agree to relicense the project. It may be desirable to seek copyright assignment to a "project lead", or to the foundation to reduce the number of copyright holders for the project, although this is not required.

==Frequently Asked Questions==

;Do we need to ensure there is a copyright and licence headers in every file?
:Projects are expected to embed a copyright and license header in every source file (.cpp and .h for instance). Machine generated files (such as lex or yacc output for instance) does not require a header if it is inconvenient to embed one, but then an effort should be made to embed a header in the original source file (ie. .l or .y). There is no need to embed copyright and license headers in build files (ie. Makefiles, Visual Studio project files), nor in small documentation fragments (like READMEs). Copyright/license headers should be included in substantial bodies of documentation if it can be done in such a way that it doesn't interfere with the document.

;Do I really need to embed the whole license agreement in every file?
:No, it is sufficient to refer to a single copy of the license agreement for the project, but each file should include an indication of what the license is, and the location of the full license document. For example:
/*
* Copyright (C) 2004-2005 Autodesk, Inc.
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of version 2.1 of the GNU Lesser
* General Public License as published by the Free Software Foundation.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this library; if not, write to the Free Software
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*/

or:

* COPYRIGHT: (C) 2001 by the GRASS Development Team
*
* This program is free software under the GNU General Public
* License (>=v2). Read the file COPYING that comes with GRASS
* for details.

;Can I just write a script to check everything?
:No. The point of a human review is to ensure that human eyes have looked at the header of each file, looking for any anomalies. For instance it is not uncommon to have additional messages written in headers about the original source of particular code, but not necessarily in a way that a script could recognise.

; But I just did a review similar to this a few months ago, do I really need to do it again?
: If you believe you have already met or exceeded the rigor described in this review document, then you can present the results of your previous analysis along with an explanation of why you think it still applies. You will need to manually review additions since that earlier review. It will be up to the Incubator (and ultimately the foundation board) to determine if they are satisfied with any review.

;Do I need to track down every contributor and ask for permission to use their code?
:No. As long as code was knowingly provided by contributors to the project while it was under a clear licensing policy then it is reasonable to assume the project licensing arrangements are accepted unless there is some reason to have doubts. If code was brought into the project from outside sources under ambiguous circumstances then it may be necessary to contact the copyright holder for a legal release, or at least a statement of permission.

;Some project code was adapted from other sources with ambiguous copyrights, what do I do?
:First, document such concerns in the review document and within the source files themselves. Second, try to obtain a release to use the provide code. An email statement of permission should be sufficient, but pertinant details of such an email should be included in the source file in questions (eg. date, identification of releasing person, text of the release). If no release is possible, but the code isn't very necessary, consider removing or replacing it to simplify things. Otherwise the issue will need to be discussed in the incubator to assess risk.

; Should I be looking for patent problems?
: No. However, if the code review turns up notes about patent issues - or if there are known patent issues for the project, then these should be noted in the review document. Generally speaking a proper patent review is very difficult and may increase, rather than decrease, legal liability.

; Should I be looking for trademark conflicts?
: Possibly. It may be prudent to check for trademark conflicts for the project name, or the name of public packages within the project. If issues are found they should be noted in the review document.

--
(generated by Claud-code and tools)

{| class="wikitable"
|-
! Committer !! Username !! Affiliation !! Agreement
|-
| Adam J. Stewart * || ajstewart426@gmail.com || UIUC/Microsoft || TBD
|-
| Caleb Robinson * || calebrob6@gmail.com || Microsoft AI for Good || TBD
|-
| Isaac Corley * || isaaccorley@users.noreply.github.com || Wherobots || TBD
|-
| Nils Lehmann * || nilsleh@users.noreply.github.com || TUM || TBD
|-
| Ashwin Nair * || ash1995@gmail.com || - || TBD
|-
| Robin Cole || robmarkcole@gmail.com || - || TBD
|-
| Yi Wang || wangyi111@users.noreply.github.com || - || TBD
|-
| Yi-Chia Chang || yichiac@users.noreply.github.com || - || TBD
|-
| Burak || burakekim@users.noreply.github.com || - || TBD
|-
| Blaz Rolih || blaz-r@users.noreply.github.com || - || TBD
|-
| Maciej Kilian || iejMac@users.noreply.github.com || - || TBD
|-
| Qiusheng Wu || giswqs@gmail.com || - || TBD
|}

[[Category: Incubation]]

TorchGeo Code Provenance

2026-01-08T16:02:12Z

Ominiverdi: /* Committers */

=Code Provenance Review Process=

TorchGeo project
'''refer : https://www.osgeo.org/about/committees/incubation/graduation/'''

==Document Status==

'''Version:''' 0.1

'''Status:''' init

'''Last Edited:''' 06 Jan 2026

==Purpose==

Show to "reasonable comfort level" that TorchGeo
does not have improperly contributed code, and that the code is all under the Project license.

Notice: ''It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly. The onus is not on the OSGeo Incubation Committee to prove there are no problems. However, OSGeo Incubation Committee does need to ensure that OSGeo does not officially endorse code with provenance issues that could have identified and corrected with a reasonable effort.''

=TorchGeo Provenance Review=

== Project History ==

TorchGeo started as an internship project at Microsoft's AI for Good Lab in 2021, with continued support and funding from the University of Illinois Urbana-Champaign and the National Center for Supercomputing Applications. Since then, TorchGeo has been adopted by a diverse community of researchers from academia, industry, and government research institutions who have contributed to the success of the library. In 2025, we founded a new TorchGeo Organization to manage the TorchGeo Project, with the support of members from the above organizations.

Key milestones:

- 2021-05-11: Initial commit (2330aad) by Adam J. Stewart

- 2021-2024: Organic growth to 120+ contributors

- 2025: Formation of TorchGeo Organization with formal governance structure

- 2026: OSGeo incubation application submitted

==Libraries==

All dependencies are external (not bundled in source tree). All licenses are OSI-approved and compatible with MIT.

{| class="wikitable" border="1"
|-
! Library !! License !! Compatible? !! In Core? !! Issues? !! Ok? !! Comments
|-
| einops || MIT || Yes || External || - || Yes || Tensor operations
|-
| geopandas || BSD-3-Clause || Yes || External || - || Yes || Geospatial dataframes
|-
| jsonargparse || MIT || Yes || External || - || Yes || CLI argument parsing
|-
| kornia || Apache-2.0 || Yes || External || - || Yes || Computer vision ops
|-
| lightly || MIT || Yes || External || - || Yes || Self-supervised learning
|-
| lightning || Apache-2.0 || Yes || External || - || Yes || Training framework
|-
| matplotlib || PSF || Yes || External || - || Yes || Plotting
|-
| numpy || BSD-3-Clause || Yes || External || - || Yes || Numerical computing
|-
| pandas || BSD-3-Clause || Yes || External || - || Yes || Data manipulation
|-
| pillow || HPND || Yes || External || - || Yes || Image I/O
|-
| pyproj || MIT || Yes || External || - || Yes || Cartographic projections
|-
| rasterio || BSD-3-Clause || Yes || External || - || Yes || Geospatial raster I/O
|-
| segmentation-models-pytorch || MIT || Yes || External || - || Yes || Segmentation architectures
|-
| shapely || BSD-3-Clause || Yes || External || - || Yes || Geometric operations
|-
| timm || Apache-2.0 || Yes || External || - || Yes || Vision model zoo
|-
| torch || BSD-3-Clause || Yes || External || - || Yes || PyTorch core
|-
| torchmetrics || Apache-2.0 || Yes || External || - || Yes || Metrics computation
|-
| torchvision || BSD-3-Clause || Yes || External || - || Yes || Vision utilities
|}

==Copyright Holders==
{| class="wikitable" border="1"
|-
! Copyright Holder !! Contact !! Issues !! Comments
|-
| TorchGeo Contributors || N/A (collective) || None || Per LICENSE file
|}

The MIT License file states: "Copyright (c) TorchGeo Contributors."

This is a collective copyright model - individual contributors retain copyright but license under MIT.

== Committers ==
'''Total human contributors:''' 122

'''Total commits:''' 2778 (excluding bots)

'''Top contributors''' (PSC members marked with *):

{| class="wikitable" border="1"
|-
! Committer !! Email !! Affiliation !! Agreement Signed?
|-
| Adam J. Stewart * || ajstewart426@gmail.com || TUM / UIUC || TBD
|-
| Caleb Robinson * || calebrob6@gmail.com || Microsoft AI for Good || TBD
|-
| Isaac Corley * || isaac.corley@proton.me || Wherobots || TBD
|-
| Nils Lehmann * || nils.lehmann24@gmail.com || TUM || TBD
|-
| Ashwin Nair * || ashnair0007@gmail.com || Space42 || TBD
|-
| Anthony Ortiz * || Anthony.Ortiz@microsoft.com || Microsoft || TBD
|-
| Robin Cole || robmarkcole@gmail.com || - || TBD
|-
| Yi Wang || wangyi111@users.noreply.github.com || - || TBD
|-
| Yi-Chia Chang || yichiac@users.noreply.github.com || - || TBD
|-
| Burak || burakekim@users.noreply.github.com || - || TBD
|-
| Blaz Rolih || blaz-r@users.noreply.github.com || - || TBD
|-
| Maciej Kilian || iejMac@users.noreply.github.com || - || TBD
|-
| Qiusheng Wu || giswqs@gmail.com || - || TBD
|}

'''Note:''' 122 total contributors. Full list available via <code>git shortlog -sne --all</code>.

==Source Files==
'''Total Python files:''' 557

'''Files with copyright header:''' 557 (100%) - ''after PR #3262 merged''

'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.

{| class="wikitable" border="1"
|-
! File !! License !! Copyright Holder !! Header? !! Issues? !! Ok? !! Comments
|-
| docs/user/metrics/update_timeline.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|-
| tests/data/landcoverai/split.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|}

'''Note:''' PR https://github.com/torchgeo/torchgeo/pull/3262 adds copyright headers to the 2 files that were missing them.

==Further Issues ==
''List or reference a list of any outstanding issues not already listed above. Typically link to issues in project's issue tracker.''

Action: Add copyright headers to these 2 files.
---

## Action Items for Brian

1. [ ] Add copyright headers to 2 missing files (or confirm they are trivial/auto-generated)

2. [ ] Confirm contributor agreement status for top maintainers

3. [ ] Copy sections above to wiki, adjusting table formatting for MediaWiki syntax

---

== TorchGeo Application Questionnaire

https://trac.osgeo.org/osgeo/wiki/TorchGeo

==Process==

The Code Provenance Review is separated into two sections, each with a slightly different process:
# Create a Provenance Review Document by copying the [[Provenance Review Template]].
# Complete the Library/Component Review Process.
# Complete the Code Copyright Review.
# Submit the completed Provenance Review Document to the Project Mentor for review.

==Library/Component Review Process==

For the overall project, document potential Library/Component issues by:
# Listing any external components that are included "in the source tree" for the project. For instance, GDAL includes a copy of libtiff, libjpeg, etc in the source tree. It is necessary to be able to identify things like that in the source tree that are under their own distinct license, and are not explicitly vetted by the project team. If practical, it is desirable to remove these internal components and treat them as external dependencies. If kept internal, notes on the licenses of the components should be documented using the Provenance Review Template.
# Listing all external dependencies with:
## Potentially problematic license terms (all non-free libraries, for instance).
## All libraries with licenses that might conflict (for instance GDAL's use of GPL'ed GRASS libraries in the non-GPL GDAL).

==Code Copyright Review==

For each project source file, perform the following:
# Does the file include the license information? If not, add it if there there is no ambiguity about whether the standard project license applies. If that is not obvious, make notes in the review document.
# Is the file under the normal project license? If not, make notes in the review document.
# Is there anything obviously unusual about the origin of the code? Does this pose any conflicts? Is the issue properly described in the source file? For instance, in GDAL, the gdal/port/cpl_strtod.cpp file is closely derived from external code that was placed in the public domain. cpl_strtod.cpp is placed under the normal GDAL MIT/X license, but detailed notes are kept in the header text on it's origin, the fact that this was public domain and so the fact that it is ok to relicense it. Oddities should be noted in the source file itself and in the review document.
# Maintain a list of all copyright holders identified in the Provenance Review Document. This list is essentially everyone who would need to agree to relicense the project. It may be desirable to seek copyright assignment to a "project lead", or to the foundation to reduce the number of copyright holders for the project, although this is not required.

==Frequently Asked Questions==

;Do we need to ensure there is a copyright and licence headers in every file?
:Projects are expected to embed a copyright and license header in every source file (.cpp and .h for instance). Machine generated files (such as lex or yacc output for instance) does not require a header if it is inconvenient to embed one, but then an effort should be made to embed a header in the original source file (ie. .l or .y). There is no need to embed copyright and license headers in build files (ie. Makefiles, Visual Studio project files), nor in small documentation fragments (like READMEs). Copyright/license headers should be included in substantial bodies of documentation if it can be done in such a way that it doesn't interfere with the document.

;Do I really need to embed the whole license agreement in every file?
:No, it is sufficient to refer to a single copy of the license agreement for the project, but each file should include an indication of what the license is, and the location of the full license document. For example:
/*
* Copyright (C) 2004-2005 Autodesk, Inc.
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of version 2.1 of the GNU Lesser
* General Public License as published by the Free Software Foundation.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this library; if not, write to the Free Software
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*/

or:

* COPYRIGHT: (C) 2001 by the GRASS Development Team
*
* This program is free software under the GNU General Public
* License (>=v2). Read the file COPYING that comes with GRASS
* for details.

;Can I just write a script to check everything?
:No. The point of a human review is to ensure that human eyes have looked at the header of each file, looking for any anomalies. For instance it is not uncommon to have additional messages written in headers about the original source of particular code, but not necessarily in a way that a script could recognise.

; But I just did a review similar to this a few months ago, do I really need to do it again?
: If you believe you have already met or exceeded the rigor described in this review document, then you can present the results of your previous analysis along with an explanation of why you think it still applies. You will need to manually review additions since that earlier review. It will be up to the Incubator (and ultimately the foundation board) to determine if they are satisfied with any review.

;Do I need to track down every contributor and ask for permission to use their code?
:No. As long as code was knowingly provided by contributors to the project while it was under a clear licensing policy then it is reasonable to assume the project licensing arrangements are accepted unless there is some reason to have doubts. If code was brought into the project from outside sources under ambiguous circumstances then it may be necessary to contact the copyright holder for a legal release, or at least a statement of permission.

;Some project code was adapted from other sources with ambiguous copyrights, what do I do?
:First, document such concerns in the review document and within the source files themselves. Second, try to obtain a release to use the provide code. An email statement of permission should be sufficient, but pertinant details of such an email should be included in the source file in questions (eg. date, identification of releasing person, text of the release). If no release is possible, but the code isn't very necessary, consider removing or replacing it to simplify things. Otherwise the issue will need to be discussed in the incubator to assess risk.

; Should I be looking for patent problems?
: No. However, if the code review turns up notes about patent issues - or if there are known patent issues for the project, then these should be noted in the review document. Generally speaking a proper patent review is very difficult and may increase, rather than decrease, legal liability.

; Should I be looking for trademark conflicts?
: Possibly. It may be prudent to check for trademark conflicts for the project name, or the name of public packages within the project. If issues are found they should be noted in the review document.

--
(generated by Claud-code and tools)

{| class="wikitable"
|-
! Committer !! Username !! Affiliation !! Agreement
|-
| Adam J. Stewart * || ajstewart426@gmail.com || UIUC/Microsoft || TBD
|-
| Caleb Robinson * || calebrob6@gmail.com || Microsoft AI for Good || TBD
|-
| Isaac Corley * || isaaccorley@users.noreply.github.com || Wherobots || TBD
|-
| Nils Lehmann * || nilsleh@users.noreply.github.com || TUM || TBD
|-
| Ashwin Nair * || ash1995@gmail.com || - || TBD
|-
| Robin Cole || robmarkcole@gmail.com || - || TBD
|-
| Yi Wang || wangyi111@users.noreply.github.com || - || TBD
|-
| Yi-Chia Chang || yichiac@users.noreply.github.com || - || TBD
|-
| Burak || burakekim@users.noreply.github.com || - || TBD
|-
| Blaz Rolih || blaz-r@users.noreply.github.com || - || TBD
|-
| Maciej Kilian || iejMac@users.noreply.github.com || - || TBD
|-
| Qiusheng Wu || giswqs@gmail.com || - || TBD
|}

[[Category: Incubation]]

TorchGeo Code Provenance

2026-01-08T16:01:52Z

Ominiverdi: /* Copyright Holders */

=Code Provenance Review Process=

TorchGeo project
'''refer : https://www.osgeo.org/about/committees/incubation/graduation/'''

==Document Status==

'''Version:''' 0.1

'''Status:''' init

'''Last Edited:''' 06 Jan 2026

==Purpose==

Show to "reasonable comfort level" that TorchGeo
does not have improperly contributed code, and that the code is all under the Project license.

Notice: ''It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly. The onus is not on the OSGeo Incubation Committee to prove there are no problems. However, OSGeo Incubation Committee does need to ensure that OSGeo does not officially endorse code with provenance issues that could have identified and corrected with a reasonable effort.''

=TorchGeo Provenance Review=

== Project History ==

TorchGeo started as an internship project at Microsoft's AI for Good Lab in 2021, with continued support and funding from the University of Illinois Urbana-Champaign and the National Center for Supercomputing Applications. Since then, TorchGeo has been adopted by a diverse community of researchers from academia, industry, and government research institutions who have contributed to the success of the library. In 2025, we founded a new TorchGeo Organization to manage the TorchGeo Project, with the support of members from the above organizations.

Key milestones:

- 2021-05-11: Initial commit (2330aad) by Adam J. Stewart

- 2021-2024: Organic growth to 120+ contributors

- 2025: Formation of TorchGeo Organization with formal governance structure

- 2026: OSGeo incubation application submitted

==Libraries==

All dependencies are external (not bundled in source tree). All licenses are OSI-approved and compatible with MIT.

{| class="wikitable" border="1"
|-
! Library !! License !! Compatible? !! In Core? !! Issues? !! Ok? !! Comments
|-
| einops || MIT || Yes || External || - || Yes || Tensor operations
|-
| geopandas || BSD-3-Clause || Yes || External || - || Yes || Geospatial dataframes
|-
| jsonargparse || MIT || Yes || External || - || Yes || CLI argument parsing
|-
| kornia || Apache-2.0 || Yes || External || - || Yes || Computer vision ops
|-
| lightly || MIT || Yes || External || - || Yes || Self-supervised learning
|-
| lightning || Apache-2.0 || Yes || External || - || Yes || Training framework
|-
| matplotlib || PSF || Yes || External || - || Yes || Plotting
|-
| numpy || BSD-3-Clause || Yes || External || - || Yes || Numerical computing
|-
| pandas || BSD-3-Clause || Yes || External || - || Yes || Data manipulation
|-
| pillow || HPND || Yes || External || - || Yes || Image I/O
|-
| pyproj || MIT || Yes || External || - || Yes || Cartographic projections
|-
| rasterio || BSD-3-Clause || Yes || External || - || Yes || Geospatial raster I/O
|-
| segmentation-models-pytorch || MIT || Yes || External || - || Yes || Segmentation architectures
|-
| shapely || BSD-3-Clause || Yes || External || - || Yes || Geometric operations
|-
| timm || Apache-2.0 || Yes || External || - || Yes || Vision model zoo
|-
| torch || BSD-3-Clause || Yes || External || - || Yes || PyTorch core
|-
| torchmetrics || Apache-2.0 || Yes || External || - || Yes || Metrics computation
|-
| torchvision || BSD-3-Clause || Yes || External || - || Yes || Vision utilities
|}

==Copyright Holders==
{| class="wikitable" border="1"
|-
! Copyright Holder !! Contact !! Issues !! Comments
|-
| TorchGeo Contributors || N/A (collective) || None || Per LICENSE file
|}

The MIT License file states: "Copyright (c) TorchGeo Contributors."

This is a collective copyright model - individual contributors retain copyright but license under MIT.

== Committers ==

<pre>
TorchGeo Repository Statistics
==============================================================
commit 6995642a4b03ae03834f599dd58a47a04fc91608
Author: Isaac Corley <isaac.corley@proton.me>
Date: Sat Jan 3 16:40:34 2026 -0600

-
commit 2330aad537f09ae93e2fa3283d1c25a3e0230703
Author: Adam J. Stewart <ajstewart426@gmail.com>
Date: Tue May 11 14:46:50 2021 -0500

Initial commit
------------------------------------------------
Total Commits: 3357

Contributors:
1068 Adam J. Stewart
947 dependabot[bot]
217 Caleb Robinson
104 Isaac Corley
101 Nils Lehmann
77 Ashwin Nair
30 isaac
17 Robin Cole
15 Yi Wang
12 Yi-Chia Chang
10 Burak
9 Maciej Kilian
6 Blaž Rolih
5 Amri Rasyidi,Qiusheng Wu,Ritwik Gupta,Sieger Falkena
4 Copilot,Daniele Rege Cambrin,Harald Kristen,gatienc
3 Adrian Tofting,George Huber,Hitesh Tolani,Luca Colomba,Pablo Mandiola,Zhuo Zheng
2 Blanchon,Buğra,Can Michael Hucko,Data Philosopher,Favyen Bastani,Gaétan Bahl,Janne Mäyrä,Jingtong
2 Kaustav Mukherjee,SpontaneousDuck,Wei Ji,Yang Mu,estherrolf,remtav,shreyakannan1205
1 Adrian Boguszewski,Al-Ekram Elahee Hridoy,Aleksey Morozov,Alexandre Lacoste,Alhassan Sahad,Arianna Sole
1 Bianca Zadrozny,Boe Zhou,Byeong-Hyeok Yu,Codruț Diaconu,Daiki Kimura,David Meaux,Dimitris Mantas
1 Dominik K,Dylan Stewart,Ethan White (he/him),Federico Bessi,Forrest Williams,Georgia Manou,Giacomo Caria
1 Heng Fang,HeshamHM28,Ikko Eltociear Ashimine,Inderpreet Singh Parmar,JDilger,Jakub,Kaleb Crans,Kamil Raczycki
1 Keenan Eves,Kendall Smith,Kiran S,Konrad Heidler,Konstantin Klemmer,Krishnagopal Halder
1 Laurențiu Nicola,Leonard Waldmann,Mathias Baumgartinger, Matt Gibson,Mauricio Cordeiro,Mehmet Cem Gunturkun
1 MengluTao,Michael Nolde,Michiaki Tatsubori,Nassim AIT ALI BRAHAM,Night-dev,Odd Eirik Igland,Ohad Nir
1 Oluwabusayo Jacobs,Piero Toffanin,Piper Wolters,Pitchaporn Likitpanjamanon,Reslan Tinawi,Rijul Dahiya,Rémi Cresson
1 Rémi Tavon,Saumya Sinha,Shradha Sehgal,Slawek Bierwiaczonek,Tarandeep Singh,Taylor Denouden,Teo Cherici
1 Veronika Buchauer,XShadow,nands,iejMac,kaybe20, lhackel-tub,lns-lns,lucastao,mdchuc,nsutezo,ntw-au,tritolol

File Changes Summary:
Added lines: 215314
Removed lines: 101198
Total lines changed: 114116
</pre>

==Source Files==
'''Total Python files:''' 557

'''Files with copyright header:''' 557 (100%) - ''after PR #3262 merged''

'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.

{| class="wikitable" border="1"
|-
! File !! License !! Copyright Holder !! Header? !! Issues? !! Ok? !! Comments
|-
| docs/user/metrics/update_timeline.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|-
| tests/data/landcoverai/split.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|}

'''Note:''' PR https://github.com/torchgeo/torchgeo/pull/3262 adds copyright headers to the 2 files that were missing them.

==Further Issues ==
''List or reference a list of any outstanding issues not already listed above. Typically link to issues in project's issue tracker.''

Action: Add copyright headers to these 2 files.
---

## Action Items for Brian

1. [ ] Add copyright headers to 2 missing files (or confirm they are trivial/auto-generated)

2. [ ] Confirm contributor agreement status for top maintainers

3. [ ] Copy sections above to wiki, adjusting table formatting for MediaWiki syntax

---

== TorchGeo Application Questionnaire

https://trac.osgeo.org/osgeo/wiki/TorchGeo

==Process==

The Code Provenance Review is separated into two sections, each with a slightly different process:
# Create a Provenance Review Document by copying the [[Provenance Review Template]].
# Complete the Library/Component Review Process.
# Complete the Code Copyright Review.
# Submit the completed Provenance Review Document to the Project Mentor for review.

==Library/Component Review Process==

For the overall project, document potential Library/Component issues by:
# Listing any external components that are included "in the source tree" for the project. For instance, GDAL includes a copy of libtiff, libjpeg, etc in the source tree. It is necessary to be able to identify things like that in the source tree that are under their own distinct license, and are not explicitly vetted by the project team. If practical, it is desirable to remove these internal components and treat them as external dependencies. If kept internal, notes on the licenses of the components should be documented using the Provenance Review Template.
# Listing all external dependencies with:
## Potentially problematic license terms (all non-free libraries, for instance).
## All libraries with licenses that might conflict (for instance GDAL's use of GPL'ed GRASS libraries in the non-GPL GDAL).

==Code Copyright Review==

For each project source file, perform the following:
# Does the file include the license information? If not, add it if there there is no ambiguity about whether the standard project license applies. If that is not obvious, make notes in the review document.
# Is the file under the normal project license? If not, make notes in the review document.
# Is there anything obviously unusual about the origin of the code? Does this pose any conflicts? Is the issue properly described in the source file? For instance, in GDAL, the gdal/port/cpl_strtod.cpp file is closely derived from external code that was placed in the public domain. cpl_strtod.cpp is placed under the normal GDAL MIT/X license, but detailed notes are kept in the header text on it's origin, the fact that this was public domain and so the fact that it is ok to relicense it. Oddities should be noted in the source file itself and in the review document.
# Maintain a list of all copyright holders identified in the Provenance Review Document. This list is essentially everyone who would need to agree to relicense the project. It may be desirable to seek copyright assignment to a "project lead", or to the foundation to reduce the number of copyright holders for the project, although this is not required.

==Frequently Asked Questions==

;Do we need to ensure there is a copyright and licence headers in every file?
:Projects are expected to embed a copyright and license header in every source file (.cpp and .h for instance). Machine generated files (such as lex or yacc output for instance) does not require a header if it is inconvenient to embed one, but then an effort should be made to embed a header in the original source file (ie. .l or .y). There is no need to embed copyright and license headers in build files (ie. Makefiles, Visual Studio project files), nor in small documentation fragments (like READMEs). Copyright/license headers should be included in substantial bodies of documentation if it can be done in such a way that it doesn't interfere with the document.

;Do I really need to embed the whole license agreement in every file?
:No, it is sufficient to refer to a single copy of the license agreement for the project, but each file should include an indication of what the license is, and the location of the full license document. For example:
/*
* Copyright (C) 2004-2005 Autodesk, Inc.
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of version 2.1 of the GNU Lesser
* General Public License as published by the Free Software Foundation.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this library; if not, write to the Free Software
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*/

or:

* COPYRIGHT: (C) 2001 by the GRASS Development Team
*
* This program is free software under the GNU General Public
* License (>=v2). Read the file COPYING that comes with GRASS
* for details.

;Can I just write a script to check everything?
:No. The point of a human review is to ensure that human eyes have looked at the header of each file, looking for any anomalies. For instance it is not uncommon to have additional messages written in headers about the original source of particular code, but not necessarily in a way that a script could recognise.

; But I just did a review similar to this a few months ago, do I really need to do it again?
: If you believe you have already met or exceeded the rigor described in this review document, then you can present the results of your previous analysis along with an explanation of why you think it still applies. You will need to manually review additions since that earlier review. It will be up to the Incubator (and ultimately the foundation board) to determine if they are satisfied with any review.

;Do I need to track down every contributor and ask for permission to use their code?
:No. As long as code was knowingly provided by contributors to the project while it was under a clear licensing policy then it is reasonable to assume the project licensing arrangements are accepted unless there is some reason to have doubts. If code was brought into the project from outside sources under ambiguous circumstances then it may be necessary to contact the copyright holder for a legal release, or at least a statement of permission.

;Some project code was adapted from other sources with ambiguous copyrights, what do I do?
:First, document such concerns in the review document and within the source files themselves. Second, try to obtain a release to use the provide code. An email statement of permission should be sufficient, but pertinant details of such an email should be included in the source file in questions (eg. date, identification of releasing person, text of the release). If no release is possible, but the code isn't very necessary, consider removing or replacing it to simplify things. Otherwise the issue will need to be discussed in the incubator to assess risk.

; Should I be looking for patent problems?
: No. However, if the code review turns up notes about patent issues - or if there are known patent issues for the project, then these should be noted in the review document. Generally speaking a proper patent review is very difficult and may increase, rather than decrease, legal liability.

; Should I be looking for trademark conflicts?
: Possibly. It may be prudent to check for trademark conflicts for the project name, or the name of public packages within the project. If issues are found they should be noted in the review document.

--
(generated by Claud-code and tools)

{| class="wikitable"
|-
! Committer !! Username !! Affiliation !! Agreement
|-
| Adam J. Stewart * || ajstewart426@gmail.com || UIUC/Microsoft || TBD
|-
| Caleb Robinson * || calebrob6@gmail.com || Microsoft AI for Good || TBD
|-
| Isaac Corley * || isaaccorley@users.noreply.github.com || Wherobots || TBD
|-
| Nils Lehmann * || nilsleh@users.noreply.github.com || TUM || TBD
|-
| Ashwin Nair * || ash1995@gmail.com || - || TBD
|-
| Robin Cole || robmarkcole@gmail.com || - || TBD
|-
| Yi Wang || wangyi111@users.noreply.github.com || - || TBD
|-
| Yi-Chia Chang || yichiac@users.noreply.github.com || - || TBD
|-
| Burak || burakekim@users.noreply.github.com || - || TBD
|-
| Blaz Rolih || blaz-r@users.noreply.github.com || - || TBD
|-
| Maciej Kilian || iejMac@users.noreply.github.com || - || TBD
|-
| Qiusheng Wu || giswqs@gmail.com || - || TBD
|}

[[Category: Incubation]]

TorchGeo Code Provenance

2026-01-08T16:01:17Z

Ominiverdi: /* Source Files */

=Code Provenance Review Process=

TorchGeo project
'''refer : https://www.osgeo.org/about/committees/incubation/graduation/'''

==Document Status==

'''Version:''' 0.1

'''Status:''' init

'''Last Edited:''' 06 Jan 2026

==Purpose==

Show to "reasonable comfort level" that TorchGeo
does not have improperly contributed code, and that the code is all under the Project license.

Notice: ''It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly. The onus is not on the OSGeo Incubation Committee to prove there are no problems. However, OSGeo Incubation Committee does need to ensure that OSGeo does not officially endorse code with provenance issues that could have identified and corrected with a reasonable effort.''

=TorchGeo Provenance Review=

== Project History ==

TorchGeo started as an internship project at Microsoft's AI for Good Lab in 2021, with continued support and funding from the University of Illinois Urbana-Champaign and the National Center for Supercomputing Applications. Since then, TorchGeo has been adopted by a diverse community of researchers from academia, industry, and government research institutions who have contributed to the success of the library. In 2025, we founded a new TorchGeo Organization to manage the TorchGeo Project, with the support of members from the above organizations.

Key milestones:

- 2021-05-11: Initial commit (2330aad) by Adam J. Stewart

- 2021-2024: Organic growth to 120+ contributors

- 2025: Formation of TorchGeo Organization with formal governance structure

- 2026: OSGeo incubation application submitted

==Libraries==

All dependencies are external (not bundled in source tree). All licenses are OSI-approved and compatible with MIT.

{| class="wikitable" border="1"
|-
! Library !! License !! Compatible? !! In Core? !! Issues? !! Ok? !! Comments
|-
| einops || MIT || Yes || External || - || Yes || Tensor operations
|-
| geopandas || BSD-3-Clause || Yes || External || - || Yes || Geospatial dataframes
|-
| jsonargparse || MIT || Yes || External || - || Yes || CLI argument parsing
|-
| kornia || Apache-2.0 || Yes || External || - || Yes || Computer vision ops
|-
| lightly || MIT || Yes || External || - || Yes || Self-supervised learning
|-
| lightning || Apache-2.0 || Yes || External || - || Yes || Training framework
|-
| matplotlib || PSF || Yes || External || - || Yes || Plotting
|-
| numpy || BSD-3-Clause || Yes || External || - || Yes || Numerical computing
|-
| pandas || BSD-3-Clause || Yes || External || - || Yes || Data manipulation
|-
| pillow || HPND || Yes || External || - || Yes || Image I/O
|-
| pyproj || MIT || Yes || External || - || Yes || Cartographic projections
|-
| rasterio || BSD-3-Clause || Yes || External || - || Yes || Geospatial raster I/O
|-
| segmentation-models-pytorch || MIT || Yes || External || - || Yes || Segmentation architectures
|-
| shapely || BSD-3-Clause || Yes || External || - || Yes || Geometric operations
|-
| timm || Apache-2.0 || Yes || External || - || Yes || Vision model zoo
|-
| torch || BSD-3-Clause || Yes || External || - || Yes || PyTorch core
|-
| torchmetrics || Apache-2.0 || Yes || External || - || Yes || Metrics computation
|-
| torchvision || BSD-3-Clause || Yes || External || - || Yes || Vision utilities
|}

==Copyright Holders==

Copyright (c) TorchGeo Contributors. All rights reserved.

== Committers ==

<pre>
TorchGeo Repository Statistics
==============================================================
commit 6995642a4b03ae03834f599dd58a47a04fc91608
Author: Isaac Corley <isaac.corley@proton.me>
Date: Sat Jan 3 16:40:34 2026 -0600

-
commit 2330aad537f09ae93e2fa3283d1c25a3e0230703
Author: Adam J. Stewart <ajstewart426@gmail.com>
Date: Tue May 11 14:46:50 2021 -0500

Initial commit
------------------------------------------------
Total Commits: 3357

Contributors:
1068 Adam J. Stewart
947 dependabot[bot]
217 Caleb Robinson
104 Isaac Corley
101 Nils Lehmann
77 Ashwin Nair
30 isaac
17 Robin Cole
15 Yi Wang
12 Yi-Chia Chang
10 Burak
9 Maciej Kilian
6 Blaž Rolih
5 Amri Rasyidi,Qiusheng Wu,Ritwik Gupta,Sieger Falkena
4 Copilot,Daniele Rege Cambrin,Harald Kristen,gatienc
3 Adrian Tofting,George Huber,Hitesh Tolani,Luca Colomba,Pablo Mandiola,Zhuo Zheng
2 Blanchon,Buğra,Can Michael Hucko,Data Philosopher,Favyen Bastani,Gaétan Bahl,Janne Mäyrä,Jingtong
2 Kaustav Mukherjee,SpontaneousDuck,Wei Ji,Yang Mu,estherrolf,remtav,shreyakannan1205
1 Adrian Boguszewski,Al-Ekram Elahee Hridoy,Aleksey Morozov,Alexandre Lacoste,Alhassan Sahad,Arianna Sole
1 Bianca Zadrozny,Boe Zhou,Byeong-Hyeok Yu,Codruț Diaconu,Daiki Kimura,David Meaux,Dimitris Mantas
1 Dominik K,Dylan Stewart,Ethan White (he/him),Federico Bessi,Forrest Williams,Georgia Manou,Giacomo Caria
1 Heng Fang,HeshamHM28,Ikko Eltociear Ashimine,Inderpreet Singh Parmar,JDilger,Jakub,Kaleb Crans,Kamil Raczycki
1 Keenan Eves,Kendall Smith,Kiran S,Konrad Heidler,Konstantin Klemmer,Krishnagopal Halder
1 Laurențiu Nicola,Leonard Waldmann,Mathias Baumgartinger, Matt Gibson,Mauricio Cordeiro,Mehmet Cem Gunturkun
1 MengluTao,Michael Nolde,Michiaki Tatsubori,Nassim AIT ALI BRAHAM,Night-dev,Odd Eirik Igland,Ohad Nir
1 Oluwabusayo Jacobs,Piero Toffanin,Piper Wolters,Pitchaporn Likitpanjamanon,Reslan Tinawi,Rijul Dahiya,Rémi Cresson
1 Rémi Tavon,Saumya Sinha,Shradha Sehgal,Slawek Bierwiaczonek,Tarandeep Singh,Taylor Denouden,Teo Cherici
1 Veronika Buchauer,XShadow,nands,iejMac,kaybe20, lhackel-tub,lns-lns,lucastao,mdchuc,nsutezo,ntw-au,tritolol

File Changes Summary:
Added lines: 215314
Removed lines: 101198
Total lines changed: 114116
</pre>

==Source Files==
'''Total Python files:''' 557

'''Files with copyright header:''' 557 (100%) - ''after PR #3262 merged''

'''Standard header format:'''
# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.

{| class="wikitable" border="1"
|-
! File !! License !! Copyright Holder !! Header? !! Issues? !! Ok? !! Comments
|-
| docs/user/metrics/update_timeline.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|-
| tests/data/landcoverai/split.py || MIT || TorchGeo Contributors || Yes || None || Yes || Fixed in PR #3262
|}

'''Note:''' PR https://github.com/torchgeo/torchgeo/pull/3262 adds copyright headers to the 2 files that were missing them.

==Further Issues ==
''List or reference a list of any outstanding issues not already listed above. Typically link to issues in project's issue tracker.''

Action: Add copyright headers to these 2 files.
---

## Action Items for Brian

1. [ ] Add copyright headers to 2 missing files (or confirm they are trivial/auto-generated)

2. [ ] Confirm contributor agreement status for top maintainers

3. [ ] Copy sections above to wiki, adjusting table formatting for MediaWiki syntax

---

== TorchGeo Application Questionnaire

https://trac.osgeo.org/osgeo/wiki/TorchGeo

==Process==

The Code Provenance Review is separated into two sections, each with a slightly different process:
# Create a Provenance Review Document by copying the [[Provenance Review Template]].
# Complete the Library/Component Review Process.
# Complete the Code Copyright Review.
# Submit the completed Provenance Review Document to the Project Mentor for review.

==Library/Component Review Process==

For the overall project, document potential Library/Component issues by:
# Listing any external components that are included "in the source tree" for the project. For instance, GDAL includes a copy of libtiff, libjpeg, etc in the source tree. It is necessary to be able to identify things like that in the source tree that are under their own distinct license, and are not explicitly vetted by the project team. If practical, it is desirable to remove these internal components and treat them as external dependencies. If kept internal, notes on the licenses of the components should be documented using the Provenance Review Template.
# Listing all external dependencies with:
## Potentially problematic license terms (all non-free libraries, for instance).
## All libraries with licenses that might conflict (for instance GDAL's use of GPL'ed GRASS libraries in the non-GPL GDAL).

==Code Copyright Review==

For each project source file, perform the following:
# Does the file include the license information? If not, add it if there there is no ambiguity about whether the standard project license applies. If that is not obvious, make notes in the review document.
# Is the file under the normal project license? If not, make notes in the review document.
# Is there anything obviously unusual about the origin of the code? Does this pose any conflicts? Is the issue properly described in the source file? For instance, in GDAL, the gdal/port/cpl_strtod.cpp file is closely derived from external code that was placed in the public domain. cpl_strtod.cpp is placed under the normal GDAL MIT/X license, but detailed notes are kept in the header text on it's origin, the fact that this was public domain and so the fact that it is ok to relicense it. Oddities should be noted in the source file itself and in the review document.
# Maintain a list of all copyright holders identified in the Provenance Review Document. This list is essentially everyone who would need to agree to relicense the project. It may be desirable to seek copyright assignment to a "project lead", or to the foundation to reduce the number of copyright holders for the project, although this is not required.

==Frequently Asked Questions==

;Do we need to ensure there is a copyright and licence headers in every file?
:Projects are expected to embed a copyright and license header in every source file (.cpp and .h for instance). Machine generated files (such as lex or yacc output for instance) does not require a header if it is inconvenient to embed one, but then an effort should be made to embed a header in the original source file (ie. .l or .y). There is no need to embed copyright and license headers in build files (ie. Makefiles, Visual Studio project files), nor in small documentation fragments (like READMEs). Copyright/license headers should be included in substantial bodies of documentation if it can be done in such a way that it doesn't interfere with the document.

;Do I really need to embed the whole license agreement in every file?
:No, it is sufficient to refer to a single copy of the license agreement for the project, but each file should include an indication of what the license is, and the location of the full license document. For example:
/*
* Copyright (C) 2004-2005 Autodesk, Inc.
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of version 2.1 of the GNU Lesser
* General Public License as published by the Free Software Foundation.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this library; if not, write to the Free Software
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*/

or:

* COPYRIGHT: (C) 2001 by the GRASS Development Team
*
* This program is free software under the GNU General Public
* License (>=v2). Read the file COPYING that comes with GRASS
* for details.

;Can I just write a script to check everything?
:No. The point of a human review is to ensure that human eyes have looked at the header of each file, looking for any anomalies. For instance it is not uncommon to have additional messages written in headers about the original source of particular code, but not necessarily in a way that a script could recognise.

; But I just did a review similar to this a few months ago, do I really need to do it again?
: If you believe you have already met or exceeded the rigor described in this review document, then you can present the results of your previous analysis along with an explanation of why you think it still applies. You will need to manually review additions since that earlier review. It will be up to the Incubator (and ultimately the foundation board) to determine if they are satisfied with any review.

;Do I need to track down every contributor and ask for permission to use their code?
:No. As long as code was knowingly provided by contributors to the project while it was under a clear licensing policy then it is reasonable to assume the project licensing arrangements are accepted unless there is some reason to have doubts. If code was brought into the project from outside sources under ambiguous circumstances then it may be necessary to contact the copyright holder for a legal release, or at least a statement of permission.

;Some project code was adapted from other sources with ambiguous copyrights, what do I do?
:First, document such concerns in the review document and within the source files themselves. Second, try to obtain a release to use the provide code. An email statement of permission should be sufficient, but pertinant details of such an email should be included in the source file in questions (eg. date, identification of releasing person, text of the release). If no release is possible, but the code isn't very necessary, consider removing or replacing it to simplify things. Otherwise the issue will need to be discussed in the incubator to assess risk.

; Should I be looking for patent problems?
: No. However, if the code review turns up notes about patent issues - or if there are known patent issues for the project, then these should be noted in the review document. Generally speaking a proper patent review is very difficult and may increase, rather than decrease, legal liability.

; Should I be looking for trademark conflicts?
: Possibly. It may be prudent to check for trademark conflicts for the project name, or the name of public packages within the project. If issues are found they should be noted in the review document.

--
(generated by Claud-code and tools)

{| class="wikitable"
|-
! Committer !! Username !! Affiliation !! Agreement
|-
| Adam J. Stewart * || ajstewart426@gmail.com || UIUC/Microsoft || TBD
|-
| Caleb Robinson * || calebrob6@gmail.com || Microsoft AI for Good || TBD
|-
| Isaac Corley * || isaaccorley@users.noreply.github.com || Wherobots || TBD
|-
| Nils Lehmann * || nilsleh@users.noreply.github.com || TUM || TBD
|-
| Ashwin Nair * || ash1995@gmail.com || - || TBD
|-
| Robin Cole || robmarkcole@gmail.com || - || TBD
|-
| Yi Wang || wangyi111@users.noreply.github.com || - || TBD
|-
| Yi-Chia Chang || yichiac@users.noreply.github.com || - || TBD
|-
| Burak || burakekim@users.noreply.github.com || - || TBD
|-
| Blaz Rolih || blaz-r@users.noreply.github.com || - || TBD
|-
| Maciej Kilian || iejMac@users.noreply.github.com || - || TBD
|-
| Qiusheng Wu || giswqs@gmail.com || - || TBD
|}

[[Category: Incubation]]

TorchGeo Code Provenance

2026-01-08T16:00:29Z

Ominiverdi: /* Committers */

=Code Provenance Review Process=

TorchGeo project
'''refer : https://www.osgeo.org/about/committees/incubation/graduation/'''

==Document Status==

'''Version:''' 0.1

'''Status:''' init

'''Last Edited:''' 06 Jan 2026

==Purpose==

Show to "reasonable comfort level" that TorchGeo
does not have improperly contributed code, and that the code is all under the Project license.

Notice: ''It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly. The onus is not on the OSGeo Incubation Committee to prove there are no problems. However, OSGeo Incubation Committee does need to ensure that OSGeo does not officially endorse code with provenance issues that could have identified and corrected with a reasonable effort.''

=TorchGeo Provenance Review=

== Project History ==

TorchGeo started as an internship project at Microsoft's AI for Good Lab in 2021, with continued support and funding from the University of Illinois Urbana-Champaign and the National Center for Supercomputing Applications. Since then, TorchGeo has been adopted by a diverse community of researchers from academia, industry, and government research institutions who have contributed to the success of the library. In 2025, we founded a new TorchGeo Organization to manage the TorchGeo Project, with the support of members from the above organizations.

Key milestones:

- 2021-05-11: Initial commit (2330aad) by Adam J. Stewart

- 2021-2024: Organic growth to 120+ contributors

- 2025: Formation of TorchGeo Organization with formal governance structure

- 2026: OSGeo incubation application submitted

==Libraries==

All dependencies are external (not bundled in source tree). All licenses are OSI-approved and compatible with MIT.

{| class="wikitable" border="1"
|-
! Library !! License !! Compatible? !! In Core? !! Issues? !! Ok? !! Comments
|-
| einops || MIT || Yes || External || - || Yes || Tensor operations
|-
| geopandas || BSD-3-Clause || Yes || External || - || Yes || Geospatial dataframes
|-
| jsonargparse || MIT || Yes || External || - || Yes || CLI argument parsing
|-
| kornia || Apache-2.0 || Yes || External || - || Yes || Computer vision ops
|-
| lightly || MIT || Yes || External || - || Yes || Self-supervised learning
|-
| lightning || Apache-2.0 || Yes || External || - || Yes || Training framework
|-
| matplotlib || PSF || Yes || External || - || Yes || Plotting
|-
| numpy || BSD-3-Clause || Yes || External || - || Yes || Numerical computing
|-
| pandas || BSD-3-Clause || Yes || External || - || Yes || Data manipulation
|-
| pillow || HPND || Yes || External || - || Yes || Image I/O
|-
| pyproj || MIT || Yes || External || - || Yes || Cartographic projections
|-
| rasterio || BSD-3-Clause || Yes || External || - || Yes || Geospatial raster I/O
|-
| segmentation-models-pytorch || MIT || Yes || External || - || Yes || Segmentation architectures
|-
| shapely || BSD-3-Clause || Yes || External || - || Yes || Geometric operations
|-
| timm || Apache-2.0 || Yes || External || - || Yes || Vision model zoo
|-
| torch || BSD-3-Clause || Yes || External || - || Yes || PyTorch core
|-
| torchmetrics || Apache-2.0 || Yes || External || - || Yes || Metrics computation
|-
| torchvision || BSD-3-Clause || Yes || External || - || Yes || Vision utilities
|}

==Copyright Holders==

Copyright (c) TorchGeo Contributors. All rights reserved.

== Committers ==

<pre>
TorchGeo Repository Statistics
==============================================================
commit 6995642a4b03ae03834f599dd58a47a04fc91608
Author: Isaac Corley <isaac.corley@proton.me>
Date: Sat Jan 3 16:40:34 2026 -0600

-
commit 2330aad537f09ae93e2fa3283d1c25a3e0230703
Author: Adam J. Stewart <ajstewart426@gmail.com>
Date: Tue May 11 14:46:50 2021 -0500

Initial commit
------------------------------------------------
Total Commits: 3357

Contributors:
1068 Adam J. Stewart
947 dependabot[bot]
217 Caleb Robinson
104 Isaac Corley
101 Nils Lehmann
77 Ashwin Nair
30 isaac
17 Robin Cole
15 Yi Wang
12 Yi-Chia Chang
10 Burak
9 Maciej Kilian
6 Blaž Rolih
5 Amri Rasyidi,Qiusheng Wu,Ritwik Gupta,Sieger Falkena
4 Copilot,Daniele Rege Cambrin,Harald Kristen,gatienc
3 Adrian Tofting,George Huber,Hitesh Tolani,Luca Colomba,Pablo Mandiola,Zhuo Zheng
2 Blanchon,Buğra,Can Michael Hucko,Data Philosopher,Favyen Bastani,Gaétan Bahl,Janne Mäyrä,Jingtong
2 Kaustav Mukherjee,SpontaneousDuck,Wei Ji,Yang Mu,estherrolf,remtav,shreyakannan1205
1 Adrian Boguszewski,Al-Ekram Elahee Hridoy,Aleksey Morozov,Alexandre Lacoste,Alhassan Sahad,Arianna Sole
1 Bianca Zadrozny,Boe Zhou,Byeong-Hyeok Yu,Codruț Diaconu,Daiki Kimura,David Meaux,Dimitris Mantas
1 Dominik K,Dylan Stewart,Ethan White (he/him),Federico Bessi,Forrest Williams,Georgia Manou,Giacomo Caria
1 Heng Fang,HeshamHM28,Ikko Eltociear Ashimine,Inderpreet Singh Parmar,JDilger,Jakub,Kaleb Crans,Kamil Raczycki
1 Keenan Eves,Kendall Smith,Kiran S,Konrad Heidler,Konstantin Klemmer,Krishnagopal Halder
1 Laurențiu Nicola,Leonard Waldmann,Mathias Baumgartinger, Matt Gibson,Mauricio Cordeiro,Mehmet Cem Gunturkun
1 MengluTao,Michael Nolde,Michiaki Tatsubori,Nassim AIT ALI BRAHAM,Night-dev,Odd Eirik Igland,Ohad Nir
1 Oluwabusayo Jacobs,Piero Toffanin,Piper Wolters,Pitchaporn Likitpanjamanon,Reslan Tinawi,Rijul Dahiya,Rémi Cresson
1 Rémi Tavon,Saumya Sinha,Shradha Sehgal,Slawek Bierwiaczonek,Tarandeep Singh,Taylor Denouden,Teo Cherici
1 Veronika Buchauer,XShadow,nands,iejMac,kaybe20, lhackel-tub,lns-lns,lucastao,mdchuc,nsutezo,ntw-au,tritolol

File Changes Summary:
Added lines: 215314
Removed lines: 101198
Total lines changed: 114116
</pre>

==Source Files==

currently, 2 of 557 python files lack a copyright line

./docs/user/metrics/update_timeline.py ; ./tests/data/landcoverai/split.py

$ `find . -name "*.py" -exec grep -li "Copyright" {} \;`

{| class="wikitable" border="1"
! File !! Licence !! Copyright Holder !! Licenced? !! Issue(s)? !! Ok? !! Comments
|-
| File || Licence || <org/person> || yes|| n/a || yes ||
|}

Primarily in Python : 593 dot-py files in 1283 directories

Most Changed Files:
2769
435 requirements/required.txt
206 .github/workflows/tests.yaml
179 requirements/style.txt
166 torchgeo/datasets/__init__.py
156 setup.cfg
156 pyproject.toml
140 requirements/datasets.txt
137 docs/api/datasets.rst
136 torchgeo/datasets/geo.py

</pre>

{| class="wikitable" border="1"
! Committer !! Username !! Affiliation !! Contribution Agrement Signed? !! Ok?
|-
| Name || Username || Company || Yes || Yes
|}

Standard header format:

# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.

==Further Issues ==
''List or reference a list of any outstanding issues not already listed above. Typically link to issues in project's issue tracker.''

Action: Add copyright headers to these 2 files.
---

## Action Items for Brian

1. [ ] Add copyright headers to 2 missing files (or confirm they are trivial/auto-generated)

2. [ ] Confirm contributor agreement status for top maintainers

3. [ ] Copy sections above to wiki, adjusting table formatting for MediaWiki syntax

---

== TorchGeo Application Questionnaire

https://trac.osgeo.org/osgeo/wiki/TorchGeo

==Process==

The Code Provenance Review is separated into two sections, each with a slightly different process:
# Create a Provenance Review Document by copying the [[Provenance Review Template]].
# Complete the Library/Component Review Process.
# Complete the Code Copyright Review.
# Submit the completed Provenance Review Document to the Project Mentor for review.

==Library/Component Review Process==

For the overall project, document potential Library/Component issues by:
# Listing any external components that are included "in the source tree" for the project. For instance, GDAL includes a copy of libtiff, libjpeg, etc in the source tree. It is necessary to be able to identify things like that in the source tree that are under their own distinct license, and are not explicitly vetted by the project team. If practical, it is desirable to remove these internal components and treat them as external dependencies. If kept internal, notes on the licenses of the components should be documented using the Provenance Review Template.
# Listing all external dependencies with:
## Potentially problematic license terms (all non-free libraries, for instance).
## All libraries with licenses that might conflict (for instance GDAL's use of GPL'ed GRASS libraries in the non-GPL GDAL).

==Code Copyright Review==

For each project source file, perform the following:
# Does the file include the license information? If not, add it if there there is no ambiguity about whether the standard project license applies. If that is not obvious, make notes in the review document.
# Is the file under the normal project license? If not, make notes in the review document.
# Is there anything obviously unusual about the origin of the code? Does this pose any conflicts? Is the issue properly described in the source file? For instance, in GDAL, the gdal/port/cpl_strtod.cpp file is closely derived from external code that was placed in the public domain. cpl_strtod.cpp is placed under the normal GDAL MIT/X license, but detailed notes are kept in the header text on it's origin, the fact that this was public domain and so the fact that it is ok to relicense it. Oddities should be noted in the source file itself and in the review document.
# Maintain a list of all copyright holders identified in the Provenance Review Document. This list is essentially everyone who would need to agree to relicense the project. It may be desirable to seek copyright assignment to a "project lead", or to the foundation to reduce the number of copyright holders for the project, although this is not required.

==Frequently Asked Questions==

;Do we need to ensure there is a copyright and licence headers in every file?
:Projects are expected to embed a copyright and license header in every source file (.cpp and .h for instance). Machine generated files (such as lex or yacc output for instance) does not require a header if it is inconvenient to embed one, but then an effort should be made to embed a header in the original source file (ie. .l or .y). There is no need to embed copyright and license headers in build files (ie. Makefiles, Visual Studio project files), nor in small documentation fragments (like READMEs). Copyright/license headers should be included in substantial bodies of documentation if it can be done in such a way that it doesn't interfere with the document.

;Do I really need to embed the whole license agreement in every file?
:No, it is sufficient to refer to a single copy of the license agreement for the project, but each file should include an indication of what the license is, and the location of the full license document. For example:
/*
* Copyright (C) 2004-2005 Autodesk, Inc.
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of version 2.1 of the GNU Lesser
* General Public License as published by the Free Software Foundation.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this library; if not, write to the Free Software
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*/

or:

* COPYRIGHT: (C) 2001 by the GRASS Development Team
*
* This program is free software under the GNU General Public
* License (>=v2). Read the file COPYING that comes with GRASS
* for details.

;Can I just write a script to check everything?
:No. The point of a human review is to ensure that human eyes have looked at the header of each file, looking for any anomalies. For instance it is not uncommon to have additional messages written in headers about the original source of particular code, but not necessarily in a way that a script could recognise.

; But I just did a review similar to this a few months ago, do I really need to do it again?
: If you believe you have already met or exceeded the rigor described in this review document, then you can present the results of your previous analysis along with an explanation of why you think it still applies. You will need to manually review additions since that earlier review. It will be up to the Incubator (and ultimately the foundation board) to determine if they are satisfied with any review.

;Do I need to track down every contributor and ask for permission to use their code?
:No. As long as code was knowingly provided by contributors to the project while it was under a clear licensing policy then it is reasonable to assume the project licensing arrangements are accepted unless there is some reason to have doubts. If code was brought into the project from outside sources under ambiguous circumstances then it may be necessary to contact the copyright holder for a legal release, or at least a statement of permission.

;Some project code was adapted from other sources with ambiguous copyrights, what do I do?
:First, document such concerns in the review document and within the source files themselves. Second, try to obtain a release to use the provide code. An email statement of permission should be sufficient, but pertinant details of such an email should be included in the source file in questions (eg. date, identification of releasing person, text of the release). If no release is possible, but the code isn't very necessary, consider removing or replacing it to simplify things. Otherwise the issue will need to be discussed in the incubator to assess risk.

; Should I be looking for patent problems?
: No. However, if the code review turns up notes about patent issues - or if there are known patent issues for the project, then these should be noted in the review document. Generally speaking a proper patent review is very difficult and may increase, rather than decrease, legal liability.

; Should I be looking for trademark conflicts?
: Possibly. It may be prudent to check for trademark conflicts for the project name, or the name of public packages within the project. If issues are found they should be noted in the review document.

--
(generated by Claud-code and tools)

{| class="wikitable"
|-
! Committer !! Username !! Affiliation !! Agreement
|-
| Adam J. Stewart * || ajstewart426@gmail.com || UIUC/Microsoft || TBD
|-
| Caleb Robinson * || calebrob6@gmail.com || Microsoft AI for Good || TBD
|-
| Isaac Corley * || isaaccorley@users.noreply.github.com || Wherobots || TBD
|-
| Nils Lehmann * || nilsleh@users.noreply.github.com || TUM || TBD
|-
| Ashwin Nair * || ash1995@gmail.com || - || TBD
|-
| Robin Cole || robmarkcole@gmail.com || - || TBD
|-
| Yi Wang || wangyi111@users.noreply.github.com || - || TBD
|-
| Yi-Chia Chang || yichiac@users.noreply.github.com || - || TBD
|-
| Burak || burakekim@users.noreply.github.com || - || TBD
|-
| Blaz Rolih || blaz-r@users.noreply.github.com || - || TBD
|-
| Maciej Kilian || iejMac@users.noreply.github.com || - || TBD
|-
| Qiusheng Wu || giswqs@gmail.com || - || TBD
|}

[[Category: Incubation]]

TorchGeo Code Provenance

2026-01-08T15:58:47Z

Ominiverdi: /* Libraries */

=Code Provenance Review Process=

TorchGeo project
'''refer : https://www.osgeo.org/about/committees/incubation/graduation/'''

==Document Status==

'''Version:''' 0.1

'''Status:''' init

'''Last Edited:''' 06 Jan 2026

==Purpose==

Show to "reasonable comfort level" that TorchGeo
does not have improperly contributed code, and that the code is all under the Project license.

Notice: ''It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly. The onus is not on the OSGeo Incubation Committee to prove there are no problems. However, OSGeo Incubation Committee does need to ensure that OSGeo does not officially endorse code with provenance issues that could have identified and corrected with a reasonable effort.''

=TorchGeo Provenance Review=

== Project History ==

TorchGeo started as an internship project at Microsoft's AI for Good Lab in 2021, with continued support and funding from the University of Illinois Urbana-Champaign and the National Center for Supercomputing Applications. Since then, TorchGeo has been adopted by a diverse community of researchers from academia, industry, and government research institutions who have contributed to the success of the library. In 2025, we founded a new TorchGeo Organization to manage the TorchGeo Project, with the support of members from the above organizations.

Key milestones:

- 2021-05-11: Initial commit (2330aad) by Adam J. Stewart

- 2021-2024: Organic growth to 120+ contributors

- 2025: Formation of TorchGeo Organization with formal governance structure

- 2026: OSGeo incubation application submitted

==Libraries==

All dependencies are external (not bundled in source tree). All licenses are OSI-approved and compatible with MIT.

{| class="wikitable" border="1"
|-
! Library !! License !! Compatible? !! In Core? !! Issues? !! Ok? !! Comments
|-
| einops || MIT || Yes || External || - || Yes || Tensor operations
|-
| geopandas || BSD-3-Clause || Yes || External || - || Yes || Geospatial dataframes
|-
| jsonargparse || MIT || Yes || External || - || Yes || CLI argument parsing
|-
| kornia || Apache-2.0 || Yes || External || - || Yes || Computer vision ops
|-
| lightly || MIT || Yes || External || - || Yes || Self-supervised learning
|-
| lightning || Apache-2.0 || Yes || External || - || Yes || Training framework
|-
| matplotlib || PSF || Yes || External || - || Yes || Plotting
|-
| numpy || BSD-3-Clause || Yes || External || - || Yes || Numerical computing
|-
| pandas || BSD-3-Clause || Yes || External || - || Yes || Data manipulation
|-
| pillow || HPND || Yes || External || - || Yes || Image I/O
|-
| pyproj || MIT || Yes || External || - || Yes || Cartographic projections
|-
| rasterio || BSD-3-Clause || Yes || External || - || Yes || Geospatial raster I/O
|-
| segmentation-models-pytorch || MIT || Yes || External || - || Yes || Segmentation architectures
|-
| shapely || BSD-3-Clause || Yes || External || - || Yes || Geometric operations
|-
| timm || Apache-2.0 || Yes || External || - || Yes || Vision model zoo
|-
| torch || BSD-3-Clause || Yes || External || - || Yes || PyTorch core
|-
| torchmetrics || Apache-2.0 || Yes || External || - || Yes || Metrics computation
|-
| torchvision || BSD-3-Clause || Yes || External || - || Yes || Vision utilities
|}

==Copyright Holders==

Copyright (c) TorchGeo Contributors. All rights reserved.

== Committers ==

<pre>
TorchGeo Repository Statistics
==============================================================
commit 6995642a4b03ae03834f599dd58a47a04fc91608
Author: Isaac Corley <isaac.corley@proton.me>
Date: Sat Jan 3 16:40:34 2026 -0600

-
commit 2330aad537f09ae93e2fa3283d1c25a3e0230703
Author: Adam J. Stewart <ajstewart426@gmail.com>
Date: Tue May 11 14:46:50 2021 -0500

Initial commit
------------------------------------------------
Total Commits: 3357

Contributors:
1068 Adam J. Stewart
947 dependabot[bot]
217 Caleb Robinson
104 Isaac Corley
101 Nils Lehmann
77 Ashwin Nair
30 isaac
17 Robin Cole
15 Yi Wang
12 Yi-Chia Chang
10 Burak
9 Maciej Kilian
6 Blaž Rolih
5 Amri Rasyidi,Qiusheng Wu,Ritwik Gupta,Sieger Falkena
4 Copilot,Daniele Rege Cambrin,Harald Kristen,gatienc
3 Adrian Tofting,George Huber,Hitesh Tolani,Luca Colomba,Pablo Mandiola,Zhuo Zheng
2 Blanchon,Buğra,Can Michael Hucko,Data Philosopher,Favyen Bastani,Gaétan Bahl,Janne Mäyrä,Jingtong
2 Kaustav Mukherjee,SpontaneousDuck,Wei Ji,Yang Mu,estherrolf,remtav,shreyakannan1205
1 Adrian Boguszewski,Al-Ekram Elahee Hridoy,Aleksey Morozov,Alexandre Lacoste,Alhassan Sahad,Arianna Sole
1 Bianca Zadrozny,Boe Zhou,Byeong-Hyeok Yu,Codruț Diaconu,Daiki Kimura,David Meaux,Dimitris Mantas
1 Dominik K,Dylan Stewart,Ethan White (he/him),Federico Bessi,Forrest Williams,Georgia Manou,Giacomo Caria
1 Heng Fang,HeshamHM28,Ikko Eltociear Ashimine,Inderpreet Singh Parmar,JDilger,Jakub,Kaleb Crans,Kamil Raczycki
1 Keenan Eves,Kendall Smith,Kiran S,Konrad Heidler,Konstantin Klemmer,Krishnagopal Halder
1 Laurențiu Nicola,Leonard Waldmann,Mathias Baumgartinger, Matt Gibson,Mauricio Cordeiro,Mehmet Cem Gunturkun
1 MengluTao,Michael Nolde,Michiaki Tatsubori,Nassim AIT ALI BRAHAM,Night-dev,Odd Eirik Igland,Ohad Nir
1 Oluwabusayo Jacobs,Piero Toffanin,Piper Wolters,Pitchaporn Likitpanjamanon,Reslan Tinawi,Rijul Dahiya,Rémi Cresson
1 Rémi Tavon,Saumya Sinha,Shradha Sehgal,Slawek Bierwiaczonek,Tarandeep Singh,Taylor Denouden,Teo Cherici
1 Veronika Buchauer,XShadow,nands,iejMac,kaybe20, lhackel-tub,lns-lns,lucastao,mdchuc,nsutezo,ntw-au,tritolol

File Changes Summary:
Added lines: 215314
Removed lines: 101198
Total lines changed: 114116

==Source Files==

currently, 2 of 557 python files lack a copyright line

./docs/user/metrics/update_timeline.py ; ./tests/data/landcoverai/split.py

$ `find . -name "*.py" -exec grep -li "Copyright" {} \;`

{| class="wikitable" border="1"
! File !! Licence !! Copyright Holder !! Licenced? !! Issue(s)? !! Ok? !! Comments
|-
| File || Licence || <org/person> || yes|| n/a || yes ||
|}

Primarily in Python : 593 dot-py files in 1283 directories

Most Changed Files:
2769
435 requirements/required.txt
206 .github/workflows/tests.yaml
179 requirements/style.txt
166 torchgeo/datasets/__init__.py
156 setup.cfg
156 pyproject.toml
140 requirements/datasets.txt
137 docs/api/datasets.rst
136 torchgeo/datasets/geo.py

</pre>

{| class="wikitable" border="1"
! Committer !! Username !! Affiliation !! Contribution Agrement Signed? !! Ok?
|-
| Name || Username || Company || Yes || Yes
|}

Standard header format:

# Copyright (c) TorchGeo Contributors. All rights reserved.
# Licensed under the MIT License.

==Further Issues ==
''List or reference a list of any outstanding issues not already listed above. Typically link to issues in project's issue tracker.''

Action: Add copyright headers to these 2 files.
---

## Action Items for Brian

1. [ ] Add copyright headers to 2 missing files (or confirm they are trivial/auto-generated)

2. [ ] Confirm contributor agreement status for top maintainers

3. [ ] Copy sections above to wiki, adjusting table formatting for MediaWiki syntax

---

== TorchGeo Application Questionnaire

https://trac.osgeo.org/osgeo/wiki/TorchGeo

==Process==

The Code Provenance Review is separated into two sections, each with a slightly different process:
# Create a Provenance Review Document by copying the [[Provenance Review Template]].
# Complete the Library/Component Review Process.
# Complete the Code Copyright Review.
# Submit the completed Provenance Review Document to the Project Mentor for review.

==Library/Component Review Process==

For the overall project, document potential Library/Component issues by:
# Listing any external components that are included "in the source tree" for the project. For instance, GDAL includes a copy of libtiff, libjpeg, etc in the source tree. It is necessary to be able to identify things like that in the source tree that are under their own distinct license, and are not explicitly vetted by the project team. If practical, it is desirable to remove these internal components and treat them as external dependencies. If kept internal, notes on the licenses of the components should be documented using the Provenance Review Template.
# Listing all external dependencies with:
## Potentially problematic license terms (all non-free libraries, for instance).
## All libraries with licenses that might conflict (for instance GDAL's use of GPL'ed GRASS libraries in the non-GPL GDAL).

==Code Copyright Review==

For each project source file, perform the following:
# Does the file include the license information? If not, add it if there there is no ambiguity about whether the standard project license applies. If that is not obvious, make notes in the review document.
# Is the file under the normal project license? If not, make notes in the review document.
# Is there anything obviously unusual about the origin of the code? Does this pose any conflicts? Is the issue properly described in the source file? For instance, in GDAL, the gdal/port/cpl_strtod.cpp file is closely derived from external code that was placed in the public domain. cpl_strtod.cpp is placed under the normal GDAL MIT/X license, but detailed notes are kept in the header text on it's origin, the fact that this was public domain and so the fact that it is ok to relicense it. Oddities should be noted in the source file itself and in the review document.
# Maintain a list of all copyright holders identified in the Provenance Review Document. This list is essentially everyone who would need to agree to relicense the project. It may be desirable to seek copyright assignment to a "project lead", or to the foundation to reduce the number of copyright holders for the project, although this is not required.

==Frequently Asked Questions==

;Do we need to ensure there is a copyright and licence headers in every file?
:Projects are expected to embed a copyright and license header in every source file (.cpp and .h for instance). Machine generated files (such as lex or yacc output for instance) does not require a header if it is inconvenient to embed one, but then an effort should be made to embed a header in the original source file (ie. .l or .y). There is no need to embed copyright and license headers in build files (ie. Makefiles, Visual Studio project files), nor in small documentation fragments (like READMEs). Copyright/license headers should be included in substantial bodies of documentation if it can be done in such a way that it doesn't interfere with the document.

;Do I really need to embed the whole license agreement in every file?
:No, it is sufficient to refer to a single copy of the license agreement for the project, but each file should include an indication of what the license is, and the location of the full license document. For example:
/*
* Copyright (C) 2004-2005 Autodesk, Inc.
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of version 2.1 of the GNU Lesser
* General Public License as published by the Free Software Foundation.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this library; if not, write to the Free Software
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*/

or:

* COPYRIGHT: (C) 2001 by the GRASS Development Team
*
* This program is free software under the GNU General Public
* License (>=v2). Read the file COPYING that comes with GRASS
* for details.

;Can I just write a script to check everything?
:No. The point of a human review is to ensure that human eyes have looked at the header of each file, looking for any anomalies. For instance it is not uncommon to have additional messages written in headers about the original source of particular code, but not necessarily in a way that a script could recognise.

; But I just did a review similar to this a few months ago, do I really need to do it again?
: If you believe you have already met or exceeded the rigor described in this review document, then you can present the results of your previous analysis along with an explanation of why you think it still applies. You will need to manually review additions since that earlier review. It will be up to the Incubator (and ultimately the foundation board) to determine if they are satisfied with any review.

;Do I need to track down every contributor and ask for permission to use their code?
:No. As long as code was knowingly provided by contributors to the project while it was under a clear licensing policy then it is reasonable to assume the project licensing arrangements are accepted unless there is some reason to have doubts. If code was brought into the project from outside sources under ambiguous circumstances then it may be necessary to contact the copyright holder for a legal release, or at least a statement of permission.

;Some project code was adapted from other sources with ambiguous copyrights, what do I do?
:First, document such concerns in the review document and within the source files themselves. Second, try to obtain a release to use the provide code. An email statement of permission should be sufficient, but pertinant details of such an email should be included in the source file in questions (eg. date, identification of releasing person, text of the release). If no release is possible, but the code isn't very necessary, consider removing or replacing it to simplify things. Otherwise the issue will need to be discussed in the incubator to assess risk.

; Should I be looking for patent problems?
: No. However, if the code review turns up notes about patent issues - or if there are known patent issues for the project, then these should be noted in the review document. Generally speaking a proper patent review is very difficult and may increase, rather than decrease, legal liability.

; Should I be looking for trademark conflicts?
: Possibly. It may be prudent to check for trademark conflicts for the project name, or the name of public packages within the project. If issues are found they should be noted in the review document.

--
(generated by Claud-code and tools)

{| class="wikitable"
|-
! Committer !! Username !! Affiliation !! Agreement
|-
| Adam J. Stewart * || ajstewart426@gmail.com || UIUC/Microsoft || TBD
|-
| Caleb Robinson * || calebrob6@gmail.com || Microsoft AI for Good || TBD
|-
| Isaac Corley * || isaaccorley@users.noreply.github.com || Wherobots || TBD
|-
| Nils Lehmann * || nilsleh@users.noreply.github.com || TUM || TBD
|-
| Ashwin Nair * || ash1995@gmail.com || - || TBD
|-
| Robin Cole || robmarkcole@gmail.com || - || TBD
|-
| Yi Wang || wangyi111@users.noreply.github.com || - || TBD
|-
| Yi-Chia Chang || yichiac@users.noreply.github.com || - || TBD
|-
| Burak || burakekim@users.noreply.github.com || - || TBD
|-
| Blaz Rolih || blaz-r@users.noreply.github.com || - || TBD
|-
| Maciej Kilian || iejMac@users.noreply.github.com || - || TBD
|-
| Qiusheng Wu || giswqs@gmail.com || - || TBD
|}

[[Category: Incubation]]

SAC Service Status

2025-12-18T07:48:37Z

Ominiverdi: /* gallery */

Infrastructure of OSGeo System Administration Committee ([[SAC]])

For emergency plans see: [[SAC:Admin and Troubleshooting]]

= Servers at OSL =
[[OSL | Open Source Labs]] - 6 physical machines that are lxd hosts containing ''x'' virtual machines/containers. 1 is currently shutdown

history:
* 7 physical machines of which 5 ar lxd hosts containing ''x'' virtual machines/containers.
* As part of migration of data center 2025)
** 2 machines: [[SAC_Service_Status#Backup_.28osgeo5.29| backup]], [[SAC_Service_Status#osgeo3|osgeo3]] are historical servers.

== Logging into Physical Machines ==

Currently we do not have physical machines under LDAP control.<del>

All [[SAC#Members|SAC administrators]] have LDAP auth to the OSL Machines.

<del>To ssh into a server using your LDAP account, you can do the following replacing '''your_osgeo_login''' with your OSGeo login and '''vmname''' with the vm name of the server at OSL.<del>

<del>ssh '''your_osgeo_login'''@'''servername'''.osgeo.osuosl.org<del>

<del>When prompted for password, use your OSGeo Login password.<del>

<del>[[SAC:Primary Administrators]] also have ssh key access in case LDAP is down and that will also apply to the physical machines. Worst case scenario use the information on [[OSL | Open Source Labs]] to file a ticket (SAC members only). Direct connection to virtual machines is by appending it's vm alias to .osgeo.osuosl.org.<del>

== Logging into LXD Hosts ==

[[SAC_Service_Status#osgeo4|osgeo4]], [[SAC_Service_Status#osgeo7|osgeo7]], [[SAC_Service_Status#osgeo8|osgeo8]], and [[SAC_Service_Status#osgeo9|osgeo9]] are all Ubuntu servers running LXD.
LXD is a management system for LXC containers and QEMU VMS. LXD has a [https://www.youtube.com/channel/UCuP6xPt0WTeZu32CkQPpbvA channel] that covers its features.

To directly access the host, you go thru port 2222

ssh tech_dev@''server_name''.osgeo.osuosl.org -p 2222

Only [[SAC:Primary Administrators]] have their ssh key installed under that account. In order to access via KVM of these in event servers do not come up on a reboot, you need to go thru OSU OSL OpenVPN. To get an OpenVPN account, you need to put in a support ticket to support@osuosl.org. In order to qualify for an OpenVPN account, you need to be an OSGeo SAC administrator. You will also need to install [https://openvpn.net/community-downloads/ OpenVPN client]) to use your OpenVPN account.

Each host on the private KVM side is named https://'''osgeo8'''.osuosl.oob -- where replace '''osgeo8''' with the relevant host. The .oob is the private network, so doesn't work unless you are connected to via OpenVPN.

The browser interface is sometimes clunky, so you might want to use '''ipmitool''' installable on linux/unix or wsl using relevant package manager. KVM passwords are stored in [https://git.osgeo.org/gitea/sac/password-store SAC password-store].

A convenient block to add to your ~/.ssh/config to easily login to osgeo's LXD hosts follows:

Host osgeo?
User tech_dev
HostName %h.osgeo.osuosl.org
Port 2222

Then you would be able to log into those hosts with commands like:

ssh osgeo7

== Logging into LXD Containers and VMs ==

A convenient block to add to your ~/.ssh/config to easily login to osgeo's LXD hosted containers and vms is the following:

# This stanza is only needed if you have an IdentityFile configured below.
# The IdentityFile from a target host is not automatically applied to the hop host, so we need to make it explicit:
Host hop.*.osgeo.org
IdentityFile "path/to/your/private/key"

Host osgeo*-*
ProxyCommand ssh hop.$(sed -e "s/-.*//" <<< "%h").osgeo.org -W $(sed -e "s/^osgeo[^-*]-//;s/$/.lxd/" <<< "%h"):%p
# this is only needed if you you use different private keys for different servers
IdentityFile "path/to/your/private/key"

Then you'll be able to access a LXC Container or QEMU VM on machine `osgeo9` with:

ssh yourusername@osgeo9-matrix

And one on machine `osgeo7` with:

ssh yourusername@osgeo7-download

Note you still need to know where each LXC host is hosted... See successive sections to know what's on which machine.

'''Troubleshooting:''' In case of "Permission denied (publickey)." after an update to a modern openSSH version, it might well be that your ssh key (RSH key) is disabled in your client in favour of more modern cyphers.

Ugly workaround: add one line `PubkeyAcceptedKeyTypes ...` in `.ssh/config`, to re-enable RSA keys for now (consider to generate a new key):

vim .ssh/config
...
Host *
...
PubkeyAcceptedKeyTypes +ssh-rsa

... but better read e.g. [https://dev.to/bowmanjd/upgrade-ssh-client-keys-and-remote-servers-after-fedora-33-s-new-crypto-policy-47ag here]!

== osgeo 8 ==
Server added April 2021, donated by OpenStreetMap project.

Likely machine: https://web.archive.org/web/20191112203036/https://hardware.openstreetmap.org/servers/stormfly-01.openstreetmap.org/

Intended to provide additional LXD capacity and backup.

[[osgeo8|Configuration Details]]

=== Services running on osgeo8 ===

==== hop ====
hop.osgeo8.osgeo.org - jump host for accessing containers/vms on osgeo8

==== nginx ====
http, https Proxy for all containers on osgeo8 and also provides mirror proxy for download.osgeo.org

==== centtie-7-pgrouting ====
Centos 7 running PostgreSQL 15, PostGIS 3.3.2, gcc-4.8.5, cmake 3
Configured to be a github self-hosted runner for testing centos for pgrouting project

[https://github.com/pgRouting/admin/wiki/CI%3A-Centos-7-GHA-runner Details of Github Action runner setup]

==== download8 ====

Replica of download that is on osgeo7.
Mirrors download and home folders from osgeo7.
https://download-cache.osgeo.org

See [[Download Server]]

==== dronie-client ====
a ci bot for dronie.osgeo.org which is used for git.osgeo.org/gitea ci jobs

==== geoserver-cite ====
Houses OGC site certification for geoserver https://cite.geoserver.org

==== grass-wiki ====

See [[SAC:GrassWiki]]

==== grass ====
https://grass.osgeo.org upgraded to Bullseye debian 11.

GRASS GIS server

Current DNS name: grass.osgeo.org

Debian 11 Bullseye

Web: Apache + Hugo (generated through cronjob from https://github.com/OSGeo/grass-website/), see https://github.com/OSGeo/grass-addons/tree/grass8/utils/cronjobs_osgeo_lxd

`unattended-upgrades` for automatic installation of security upgrades is installed and running

ssh: reachable via jumphost.

==== meshcentral ====
https://remote.osgeo.org
This is a remoting tool currently setup to test livecd vms via a web browser.

4 VMS currently set up on osgeo8 accessible from this. Currently based on livecd 16rc1 snapshots, with wm install script run.

==== pgrouting-dev ====
For pgrouting development use to do things like pushing docker images on a scheduled basis.
Perhaps later for demo sites. WIP.

==== woodie-client-vm ====

Separate agent for woodie-server, this one is a true VM rather than container.

==== woodie-server ====

See [[Woodie]]

== osgeo 9 ==
Server added April 2021, donated by OpenStreetMap project.

Likely machine: https://web.archive.org/web/20191112203042/https://hardware.openstreetmap.org/servers/stormfly-02.openstreetmap.org/

Is an LXD host. Also Stores lxd images used by other lxd hosts.

[[osgeo9|Configuration Details]]

=== Services running on osgeo9 ===
==== hop ====
hop.osgeo9.osgeo.org. For LDAP users allows them to hop thru to get to other containers.

==== Secure (LDAP ) ====
[https://git.osgeo.org/gitea/sac/osgeo9/wiki/secure-container secure] -- ldap.osgeo.org [[SAC:LDAP]] used for ldap service (a rebuild of old secure.osgeo.osuosl.org) now on Debian 11
Moved from osgeo7

==== ldap-web ====

Currently housing https://id.osgeo.org/ for LDAP management.
Deployed via ansible
Moved from osgeo9

* id.osgeo.org

==== jitsi ====

See [[SAC:Jitsi]] (for video meetings)

==== nextcloud ====
https://nextcloud.osgeo.org

Ubuntu 22.04 LXD/nginx/postgresql 14 container for document sharing similar to dropbox/google drive - nextcloud.lxd - https://nextcloud.osgeo.org [https://git.osgeo.org/gitea/sac/osgeo9/wiki/Nextcloud-container Nextcloud Setup]

home of https://nextcloud.osgeo.org
This server does not use ssh osgeo-ldap as it was the first container built. However nextcloud.osgeo.org does authenticate with osgeo ldap.

TODO: add special page for this

==== nginx ====
nginx (for web proxy of traffic of osgeo9 containers) additional mirror proxy for download.osgeo.org

==== adventure (WIP)====
https://adventure.osgeo.org runs https://github.com/thecodingmachine/workadventure software

==== dronie-client ====
a ci bot for dronie.osgeo.org which is used for git.osgeo.org/gitea ci jobs

==== limesurvey ====
Debian 10, PostgreSQL 13, PHP 8 with ldap/ssh. https://limesurvey.osgeo.org
Setup detailed on [https://git.osgeo.org/gitea/sac/osgeo3/wiki/limesurvey-container limesurvey container]

==== mail ====
mailman: lists.osgeo.org
mail.osgeo.org
tilechache web: tilecache.osgeo.org
mailserver: postfix

==== matrix ====
'''Container Name:''' matrix - lxd container with ldap/ssh.
Hosts [[Matrix]] homeserver ([[SAC:MatrixSynapse]]) and IRC bridges ([[SAC:Heisenbridge]])

https://gitea.osgeo.org/sac/osgeo9/wiki/matrix-container for full detail on how the container is setup

==== pixelfed ====

SHUT OFF (both container and website) cause of lack of interest. Container is still there.
[[Pixelfed]] instance reachable on https://photo.osgeo.org to house community photos

==== peertube ====

[[Peertube]] instance reachable on https://video.osgeo.org

==== pretalx ====
Ubuntu 20.04 with OSGeo LDAP and Docker installed. pretalx software runs in Docker.
https://talks.osgeo.org - for OSGeo Talk collection and voting See [[Pretalx]]

==== weblate ====
'''Container Name:''' weblate (for doc translation)

Houses: https://weblate.osgeo.org (for document translation to different languages)

For further details refer to [[SAC:Weblate]]

==== wordpress ====

See [[SAC:Wordpress]]

==== geo-docs container ====

Houses:
* https://blog.geoserver.org
* https://geos.osgeo.org
* https://geotools.org
* https://geowebcache.osgeo.org
* https://lastools.osgeo.org
* https://planet.osgeo.org

==== wiki ====

See [[OSGeo Wiki]]

==== discourse ====

See [[SAC:Discourse]]

==== mail ====

Hosts: lists.osgeo.org, mail.osgeo.org and a few other services.
See [[Mail server]] for more details.

== osgeo 7 ==

Server added June 2018. Intended to replace [[SAC_Service_Status#osgeo3|osgeo3]] and old osgeo4 (before reformat).
See [[Osgeo7]] for configuration details.

[https://git.osgeo.org/gitea/sac/osgeo7/wiki/_pages Container setup of all the osgeo7 servers is located in https://git.osgeo.org/gitea/sac/osgeo7/wiki/_pages]

Running LXD 3 snap based container management -- LXD version 3.17 as of 2019-09-15

=== Accessing osgeo7 containers via ssh ===

Only the download.osgeo.org is directly exposed ssh via port 22. To access the other containers, you can tunnel thru
download.osgeo.org -- You need to be in the shell group to be able to access download and the other servers. If you are not already put in a [https://trac.osgeo.org/osgeo/newticket SAC Ticket Request]. You also need to have your public key registered. To do so edit your profile [https://id.osgeo.org/ldap/edit] (and put in your public key)

A convenient block to add to your own `.ssh/config` file follows:

Host osgeo7-*
ProxyCommand ssh your_osgeo_id@hop.osgeo7.osgeo.org -W $(sed -e "s/^osgeo7-//;s/$/.lxd/" <<< "%h"):%p
IdentityFile "path/to/your/private/key"

With the above in place, you can connect to any container using:

ssh your_id@osgeo7-<container_name>

'''Troubleshooting:''' In case of "Permission denied (publickey)." after an update to a modern openSSH version, it might well be that your ssh key (RSH key) is disabled in your client in favour of more modern cyphers.

Ugly workaround: add one line `PubkeyAcceptedKeyTypes ...` in `.ssh/config`, to re-enable RSA keys for now (consider to generate a new key):

vim .ssh/config
...
Host *
...
PubkeyAcceptedKeyTypes +ssh-rsa

... but better read e.g. [https://dev.to/bowmanjd/upgrade-ssh-client-keys-and-remote-servers-after-fedora-33-s-new-crypto-policy-47ag here]!

=== Services on osgeo7 ===

==== Monitor ====

debian10 lxd container with ldap/ssh. https://monitor.osgeo.org (houses grafana dashboard (for all servers) and prometheus server for <del>[[SAC_Service_Status#osgeo3|osgeo3]]<del> containers and pulls basic container metrics using node exporters pulled via prometheus servers. Requirs ldap to log into the web console.

Configuring servers for monitoring is detailed [https://git.osgeo.org/gitea/sac/prometheus-config Git Prometheus Config]

==== Download ====

See [[Download Server]]

==== dronie-client-osgeo3 ====
STOPPED See [https://trac.osgeo.org/osgeo/ticket/3415 #3415]
Its a copy of dronie-client that was on [[SAC_Service_Status#osgeo3|osgeo3]] which has been shutdown
This is a debian 10 lxd container running docker. Currently has just one running docker osgeo-drone-agent to serve as a client for dronie-server (dronie.osgeo.org running on osgeo7)

==== gallery ====
Debian 12 (bookworm) container for AI/ML services, media, and experimental applications.

'''Resources:''' 8 vCPUs, 12GB RAM
'''System services:''' nginx, redis, PostgreSQL 17, turnserver, php-fpm

'''Brian's services (darkblueb):'''
* GalleryVM media library
* llamafile experiments
* photoprism configuration

'''Lorenzo's services (ominiverdi):'''
* '''matrix-llmagent''' - Matrix chat bot with LLM integration (uses OpenRouter API)
** GitHub: https://github.com/ominiverdi/matrix-llmagent
* '''BGE-M3 Embedding Server''' - Semantic search embeddings via llama.cpp
** Port: 8094 (localhost only), Model: bge-m3-Q8_0.gguf
* '''osgeo-library''' - PDF figure/table/equation extraction and semantic search
** GitHub: https://github.com/ominiverdi/osgeo-library
** CLI command: <code>osgeo-library</code> (as ominiverdi user)
* '''osgeo_wiki_bot''' - Automated wiki/WordPress/Planet content sync and processing
** GitHub: https://github.com/ominiverdi/osgeo_wiki_bot
** Cron: wiki (6h), WordPress (daily), Planet (4h), chunk processing (hourly)

The embedding model running on osgeo7-gallery is BGE-M3 (bge-m3-Q8_0.gguf), a multilingual model from BAAI supporting 100+ languages. It produces 1024-dimensional vectors and runs via llama-server on port 8094 (localhost only). The Q8_0 quantization keeps it light: 606 MB on disk, ~457 MB RAM, ~12ms per query.

'''Contact:''' darkblueb (Brian Hamlin), ominiverdi (Lorenzo Becchi) or SAC channel

==== live ====
Home of [http://live.osgeo.org live.osgeo.org] ;
Running Ubuntu 24.04.3 LTS with OSGeo LDAP SSH

==== mapserver ====

See [[MapServer_at_osgeo7]]

==== nexus (repo.osgeo.org, docker.osgeo.org) ====
See [[SAC:Repo]] this is a debian 10 lxd container running docker 19.
It currently has one docker container running within it called nexus -- exposed as repo.osgeo.org on nginx.

Also exposed as project dockers for pushing images: postgis-docker.osgeo.org, geoserver-docker.osgeo.org, geos-docker.osgeo.org, sac-docker.osgeo.org

==== nginx ====
Proxy that routes all http/https traffic for the other containers (can be accessed via osgeo7 host lxc or ubuntu@osgeo7-nginx if your key is installed on ubuntu user).
The nginx container holds the letsencrypt https SSL certs for all the containers and handles the renewal of the letsencrypt certs using certbot renew cronjob.
Prometheus server to collect all monitoring logs from OSGeo7 <del>(only accessible by [[SAC_Service_Status#osgeo3|osgeo3]]), these get queried via monitor.osgeo.org (running on [[SAC_Service_Status#osgeo3|osgeo3]]) via grafana server.<del>

==== tracsvn (trac, svn, git) ====

Home of [[Trac]], [[SAC:Git Service|Git]] and [[Subversion]] services.

See [[TracSVN]] for full details.

==== photoprism ====
Picture gallery. Syncs with https://nextcloud.osgeo.org
But pictures are shown here https://photoprism.osgeo.org

==== old-wiki (stopped) ====
This used to be housed on [[SAC_Service_Status#osgeo3|osgeo3]], and was moved 2019-09-14 to osgeo7 as old-wiki container.
wiki.osgeo.org moved back to [[SAC_Service_Status#osgeo3|osgeo3]] on 2020-05-22 and in wiki container. The wiki container is a complete rebuild with files and database restored and upgraded.
Refer to the [[SAC_Service_Status#osgeo3|osgeo3]] section for more details.

[https://git.osgeo.org/gitea/sac/osgeo7/wiki/old-wiki-container old wiki container] -- used for wiki service (it is an lxd2pc created image of wiki.osgeo.osuosl.org VM that was on [[SAC_Service_Status#osgeo3|osgeo3]])

See [[OSGeo Wiki]]

==== nextcloud-ubuntu (stopped) ====
Moved to osgeo9

==== dronie-server ====

See [[Dronie]]

==== old-projects (stopped) ====
-- this is the old projects.osgeo.osuosl.org migrated from osgeo4 as an lxd container, so more or less the same as it was before, with the exception that all the websites are now proxied thru the nginx container. Websites on it are community-review.foss4g.org and spatialreference.org

To access you need to go thru download.osgeo.org -> old-projects

==== old-web (stopped) ====
The old web.osgeo.osuosl.org (was on [[SAC_Service_Status#osgeo3|osgeo3]])

* mapguide.osgeo.org

==== old-webextra ====
This is a replica of webextra.osgeo.osuosl.org that was hosted on [[SAC_Service_Status#osgeo3|osgeo3]]

Started move on November 29th 2019 and completed December 8th, 2019
* foss4g.org
* europe.foss4g.org
* video.foss4g.org
* planet.osgeo.org
* various old foss4g.org years
* <del>live.osgeo.org</del> moved to dedicated container
* journal.osgeo.org (not sure what this is for, should be retired?)
* <del>vmap0.tiles.osgeo.org</del> #removed site

Information from webextra on [[SAC_Service_Status#osgeo3|osgeo3]]

** Retired December 8th, 2019 -- and moved to osgeo7 as container old-webextra

* See [[WebExtraVM]] for full details (server: http://webextra.osgeo.osuosl.org)
* hosts http://planet.osgeo.org, http://mum03.mapserver.org, http://live.osgeo.org
* http://foss4g.org (main portal) and archive of old sites 2006-2014
* http://conference.osgeo.org - [[Conference System]] (also: [[SAC:Setup_OCS]])
* http://journal.osgeo.org / osgeo.org/ojs - [[Journal System]]
* Redirects for many chapter and other urls handled via /etc/httpd/conf.d/rewrite.conf

==== pycsw ====
'''Container Name:''' pycsw

* https://demo.pycsw.org
* '''OGC CSW Reference Implementation and Server demo'''
* deployment setup at https://github.com/geopython/demo.pycsw.org
* running hourly teardown/setup cron via docker-compose
* migrated from [[AdhocVM#Existing_services_hosted_on_the_Ad-hoc_VM:|Adhoc VM]] thanks to [https://trac.osgeo.org/osgeo/ticket/2452 SAC] (May 2020)

=== osgeo7 decommissioned containers ===

==== <del>old-adhoc</del> ====

'''SHUTOFF as of 2022-01-29'''

[[AdhocVM|old-adhoc]] -- this is the old adhoc.osgeo.osuosl.org migrated 2019-05-08 from osgeo4 as an lxd container.
Used by osgeo-live for there test docs and by grass for earthquake, and mapserver for demo.
Note that there is a new live (container that osgeo-live will more to), there is also a mapserver container (which mapserver have started to move their demo to)

To access via ssh you should go thru download.osgeo.org -> old-adhoc.lxd
It is accessible via https://adhoc.osgeo.org and http://adhoc.osgeo.osuosl.org

* VM used for projects for various adhoc purposes. Risks to system stability that would be unacceptable on the Projects VM may be ok here.
* See [[AdhocVM]] for full details, and some notes on services running here.
* eg http://adhoc.osgeo.osuosl.org/livedvd/docs/en/quickstart/

== osgeo6 ==

See [[osgeo6]]

== osgeo4 ==

osgeo4 is a real server managed by OSUOSL - can be access via ssh tech_dev@osgeo4.osgeo.osuosl.org -p 2222 (only people with their access keys installed can log in and doesn't allow password access) - password for tech_dev is in the secure container (on osgeo7) / access folder.

In August 2019 the server had new power supply put in and replacement disks. It was reformatted with Ubuntu 18.04.3 to serve as secondary LXD host to osgeo7
zfsutils-linux was installed so lxd can use zfs for storage.

=== sshing into osgeo4 containers ===
Note that all the containers are closed off from direct ssh access except for the hop.osgeo4.osgeo.org. To access the other containers, you need to hop through hop.
hop container has port 22 open but requires ssh access so users who’ve been granted rights can hop thru it to other containers using hop.osgeo4.osgeo.org as name.

A convenient block to add to your own .ssh/config file follows where your_id could be your osgeo id or a local account on that container

Host osgeo4-*
ProxyCommand ssh your_osgeo_id@hop.osgeo4.osgeo.org -W $(sed -e "s/^osgeo4-//;s/$/.lxd/" <<< "%h"):%p
IdentityFile "path/to/your/private/key"
User your_id

Then to access say the wordpress-dev container, you'd do the below

ssh osgeo4-wordpress-dev

=== osgeo4 baremetal features ===
It's makeup is as follows:
{| class="wikitable"
|-
! Item !! Settings
|-
| Disks || 6 1.8 TB drives
|-
| Memory || 48 GB
|-
| CPUs || 8 Intel(R) Xeon(R) CPU E5540 @ 2.53GHz (8192kb cache)
|}
<pre>lsblk -i
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1.8T 0 disk
|-sda1 8:1 0 953M 0 part
| `-md0 9:0 0 952M 0 raid1 /boot
`-sda2 8:2 0 46.6G 0 part
`-md1 9:1 0 46.5G 0 raid1
|-lvm-root 253:0 0 37.3G 0 lvm /
`-lvm-swap 253:1 0 7.5G 0 lvm [SWAP]
sdb 8:16 0 1.8T 0 disk
|-sdb1 8:17 0 953M 0 part
| `-md0 9:0 0 952M 0 raid1 /boot
`-sdb2 8:18 0 46.6G 0 part
`-md1 9:1 0 46.5G 0 raid1
|-lvm-root 253:0 0 37.3G 0 lvm /
`-lvm-swap 253:1 0 7.5G 0 lvm [SWAP]
sdc 8:32 0 1.8T 0 disk
sdd 8:48 0 1.8T 0 disk
sde 8:64 0 1.8T 0 disk
sdf 8:80 0 1.8T 0 disk
</pre>

<pre>
sdc,sdd,sde,sdf form a zfs osgeo4_lxd partition (sdc,sdd) mirrors sde,sdf for total lxd capacity of 3.62 TB
</pre>

Nightly backups of osgeo7, and osgeo4 containers are kept here and named <container>-backup and be kept in a stopped state.

=== Services running on osgeo4 ===

==== hop ====
'''Container Name:''' hop - this is the only container with direct ssh access via ssh hop.osgeo4.osgeo.org. To get to other containers, you need to hop thru this one. Requires ssh key access

==== ansible-dev ====
'''Container Name:''' ansible-dev, has ansible 2.9.27 installed and all plugins needed to manage OSGeo ansible infrastructure.
DEPRECATED, use `ansible-dev`

==== ansible-control ====
'''Container Name:''' ansible-control, can be used to deploy OSGeo ansible infrastructure. Replaces `ansible-dev`

==== osgeo4-nginx ====
'''Container Name:''' osgeo4-nginx ->> all web traffick from other containers on osgeo4 get proxied thru here

==== old-web-staging ====
'''Container Name:''' old-web-staging - used primarily for experimenting with changes to id.osgeo.org (old-web on osgeo7) like testing out OS and software upgrade etc, changes to LDAP forms and registration, before applying to id.osgeo.org. - https://id.staging.osgeo.org

==== pretalx-staging ====
'''Container Name:''' pretalx-staging - used primarily for experimenting with changes to talks.osgeo.org (pretalx on [[SAC_Service_Status#osgeo9|osgeo9]]) like testing out Docker builds and software upgrade etc, before applying to talks.osgeo.org. - https://talks.staging.osgeo.org

==== wordpress-dev ====
'''Container Name:''' wordpress-dev - used primarily for osgeo.org main website development - https://staging.www.osgeo.org, https://dev.www.osgeo.org

==== wiki-dev ====
'''Container Name:''' wiki-dev - used primarily for experimenting with changes to wiki.osgeo.org like testing out OS and software upgrade etc before appying to wiki.osgeo.org. - https://dev.wiki.osgeo.org

==== wiki-staging ====
'''Container Name:''' wiki-staging - used primarily for upgrade changes to wiki.osgeo.org like testing out OS and software upgrade etc before applying to wiki.osgeo.org. - https://staging.wiki.osgeo.org. The construction of this container is managed by sac ansible-deployment.

==== tracsvn-dev ====
'''Container Name:''' tracsvn-dev - This is a 2019-09-05 lxd2pc image of tracsvn.osgeo.osuosl.org (now on osgeo7 as tracsvn) used primarily for experimenting like testing out OS, git and software upgrade etc before appying to production. -- https://dev.git.osgeo.org, https://dev.tracsvn.osgeo.org Has the following sites: https://dev.trac.osgeo.org, https://dev.git.osgeo.org/gitea, https://dev.svn.osgeo.org.

It was upgraded to Debian 11 on 2024-08-21.

==== dronie-client ====
'''Container Name:''' dronie-client - This is a debian 10 machine, with OSGeo LDAP authentication and a drone-agent docker running. To be used with https://dronie.osgeo.org

= Cloud Hosted Servers and other external under SAC Control =

== Future Hosting Plans for Windows / Mac Building ==

[[SAC_Shared_Building_Services|SAC Shared Building Services]]

== Atlantic.net ==

* host.postgis.net -p 2222 is an LXD Ubuntu 18.04 16GB RAM/ 6 vCPU, 350GB data, 250GB block storage
* Currenlty running two lxd containers:
debbie: debian 10 postgis.net, planet.postgis.net, debbie.postgis.net (jenkins build bot)
debbie-docker.host.postgis.net - runs docker and serves as a 1.0 agent for dronie.osgeo.org

= QGIS off OSGeo =
Services on separated machines rented and managed by the QGIS project at hetzner

* website including documentation http://www.qgis.org
* website building, documentation building, debian/ubuntu nightlies, plugins.qgis.org
* issues.qgis.org: redmine

= Historical servers (not more in use) =

- [[Telascience Blades (Historical)]]

== web18a.osgeo.osuosl.org ==
NO LONGER USED - turned off
'''2019-09-03 Production services www.osgeo.org, 2018.foss4g.org moved to wordpress container on [[osgeo7]]
Staging services (staging.www.osgeo.org, dev.www.osgeo.org move to wordpress-dev container on [[osgeo4]]
Grass wordpress is disabled as grass decided to go with another solution, so have grass container on osgeo7'''
(Cloud hosted server on OSUOSL hardware (not ours) )
* Debian 9.3 4GB server, host name: web18a.osgeo.osuosl.org require ssh key to log in.
* Hosts wordpress sites staging.www.osgeo.org,www.osgeo.org, staging.grass.osgeo.org, foss4g2018.osgeo.org
* Setup details on [https://git.osgeo.org/gitea/osgeo/www_apache_configs/wiki/Web18a-setup Web18a setup]

== OSGeo funtoo ==

For lxd experimentation it's an lxd container running other lxd containers and provided by funtoo.org.

OSGeo is paying funtoo via treasurer at osgeo.org.

* [https://git.osgeo.org/gitea/sac/osgeo_funtoo OSGeo Funtoo] osgeo.host.funtoo.org

* funtoo LXDs currently running:
** <del>[https://limesurvey.osgeo.org LimeSurvey] -this may be in future migrated to osgeo7 or osgeo3</del>
Migrated to [[SAC_Service_Status#osgeo3|osgeo3]] 2020-11-28 -- see [[https://trac.osgeo.org/osgeo/ticket/2362|#2362]]

== osgeo3 ==

osgeo3 physical server refer to [[osgeo3|Configuration Details]] for hardware specs. It was used to run production, but moderately risky things. Refer to [[SAC:Old-osgeo3]] for past history before osgeo3 was rebuilt.
osgeo3 was a hosted by OSUOSL - No longer accessible <del>can be accessed via ssh tech_dev@osgeo3.osgeo.osuosl.org -p 2222 (only people with their access keys installed can log in and doesn't allow password access) - password for tech_dev is in the secure container (on osgeo7) / access folder.<del>

== Backup (osgeo5) ==

* <del>Backup now runs on dedicated hardware<del>
* <del>Provides Rsync backups of download.osgeo.org<del>
* <del>Provides Bacula backups of various VMs.<del>
* See [[SAC:Backups]] for details.

[[Category:Infrastructure]]
[[Category:Services]]

SAC Service Status

2025-12-17T21:36:28Z

Ominiverdi: /* gallery */

Infrastructure of OSGeo System Administration Committee ([[SAC]])

For emergency plans see: [[SAC:Admin and Troubleshooting]]

= Servers at OSL =
[[OSL | Open Source Labs]] - 6 physical machines that are lxd hosts containing ''x'' virtual machines/containers. 1 is currently shutdown

history:
* 7 physical machines of which 5 ar lxd hosts containing ''x'' virtual machines/containers.
* As part of migration of data center 2025)
** 2 machines: [[SAC_Service_Status#Backup_.28osgeo5.29| backup]], [[SAC_Service_Status#osgeo3|osgeo3]] are historical servers.

== Logging into Physical Machines ==

Currently we do not have physical machines under LDAP control.<del>

All [[SAC#Members|SAC administrators]] have LDAP auth to the OSL Machines.

<del>To ssh into a server using your LDAP account, you can do the following replacing '''your_osgeo_login''' with your OSGeo login and '''vmname''' with the vm name of the server at OSL.<del>

<del>ssh '''your_osgeo_login'''@'''servername'''.osgeo.osuosl.org<del>

<del>When prompted for password, use your OSGeo Login password.<del>

<del>[[SAC:Primary Administrators]] also have ssh key access in case LDAP is down and that will also apply to the physical machines. Worst case scenario use the information on [[OSL | Open Source Labs]] to file a ticket (SAC members only). Direct connection to virtual machines is by appending it's vm alias to .osgeo.osuosl.org.<del>

== Logging into LXD Hosts ==

[[SAC_Service_Status#osgeo4|osgeo4]], [[SAC_Service_Status#osgeo7|osgeo7]], [[SAC_Service_Status#osgeo8|osgeo8]], and [[SAC_Service_Status#osgeo9|osgeo9]] are all Ubuntu servers running LXD.
LXD is a management system for LXC containers and QEMU VMS. LXD has a [https://www.youtube.com/channel/UCuP6xPt0WTeZu32CkQPpbvA channel] that covers its features.

To directly access the host, you go thru port 2222

ssh tech_dev@''server_name''.osgeo.osuosl.org -p 2222

Only [[SAC:Primary Administrators]] have their ssh key installed under that account. In order to access via KVM of these in event servers do not come up on a reboot, you need to go thru OSU OSL OpenVPN. To get an OpenVPN account, you need to put in a support ticket to support@osuosl.org. In order to qualify for an OpenVPN account, you need to be an OSGeo SAC administrator. You will also need to install [https://openvpn.net/community-downloads/ OpenVPN client]) to use your OpenVPN account.

Each host on the private KVM side is named https://'''osgeo8'''.osuosl.oob -- where replace '''osgeo8''' with the relevant host. The .oob is the private network, so doesn't work unless you are connected to via OpenVPN.

The browser interface is sometimes clunky, so you might want to use '''ipmitool''' installable on linux/unix or wsl using relevant package manager. KVM passwords are stored in [https://git.osgeo.org/gitea/sac/password-store SAC password-store].

A convenient block to add to your ~/.ssh/config to easily login to osgeo's LXD hosts follows:

Host osgeo?
User tech_dev
HostName %h.osgeo.osuosl.org
Port 2222

Then you would be able to log into those hosts with commands like:

ssh osgeo7

== Logging into LXD Containers and VMs ==

A convenient block to add to your ~/.ssh/config to easily login to osgeo's LXD hosted containers and vms is the following:

# This stanza is only needed if you have an IdentityFile configured below.
# The IdentityFile from a target host is not automatically applied to the hop host, so we need to make it explicit:
Host hop.*.osgeo.org
IdentityFile "path/to/your/private/key"

Host osgeo*-*
ProxyCommand ssh hop.$(sed -e "s/-.*//" <<< "%h").osgeo.org -W $(sed -e "s/^osgeo[^-*]-//;s/$/.lxd/" <<< "%h"):%p
# this is only needed if you you use different private keys for different servers
IdentityFile "path/to/your/private/key"

Then you'll be able to access a LXC Container or QEMU VM on machine `osgeo9` with:

ssh yourusername@osgeo9-matrix

And one on machine `osgeo7` with:

ssh yourusername@osgeo7-download

Note you still need to know where each LXC host is hosted... See successive sections to know what's on which machine.

'''Troubleshooting:''' In case of "Permission denied (publickey)." after an update to a modern openSSH version, it might well be that your ssh key (RSH key) is disabled in your client in favour of more modern cyphers.

Ugly workaround: add one line `PubkeyAcceptedKeyTypes ...` in `.ssh/config`, to re-enable RSA keys for now (consider to generate a new key):

vim .ssh/config
...
Host *
...
PubkeyAcceptedKeyTypes +ssh-rsa

... but better read e.g. [https://dev.to/bowmanjd/upgrade-ssh-client-keys-and-remote-servers-after-fedora-33-s-new-crypto-policy-47ag here]!

== osgeo 8 ==
Server added April 2021, donated by OpenStreetMap project.

Likely machine: https://web.archive.org/web/20191112203036/https://hardware.openstreetmap.org/servers/stormfly-01.openstreetmap.org/

Intended to provide additional LXD capacity and backup.

[[osgeo8|Configuration Details]]

=== Services running on osgeo8 ===

==== hop ====
hop.osgeo8.osgeo.org - jump host for accessing containers/vms on osgeo8

==== nginx ====
http, https Proxy for all containers on osgeo8 and also provides mirror proxy for download.osgeo.org

==== centtie-7-pgrouting ====
Centos 7 running PostgreSQL 15, PostGIS 3.3.2, gcc-4.8.5, cmake 3
Configured to be a github self-hosted runner for testing centos for pgrouting project

[https://github.com/pgRouting/admin/wiki/CI%3A-Centos-7-GHA-runner Details of Github Action runner setup]

==== download8 ====

Replica of download that is on osgeo7.
Mirrors download and home folders from osgeo7.
https://download-cache.osgeo.org

See [[Download Server]]

==== dronie-client ====
a ci bot for dronie.osgeo.org which is used for git.osgeo.org/gitea ci jobs

==== geoserver-cite ====
Houses OGC site certification for geoserver https://cite.geoserver.org

==== grass-wiki ====

See [[SAC:GrassWiki]]

==== grass ====
https://grass.osgeo.org upgraded to Bullseye debian 11.

GRASS GIS server

Current DNS name: grass.osgeo.org

Debian 11 Bullseye

Web: Apache + Hugo (generated through cronjob from https://github.com/OSGeo/grass-website/), see https://github.com/OSGeo/grass-addons/tree/grass8/utils/cronjobs_osgeo_lxd

`unattended-upgrades` for automatic installation of security upgrades is installed and running

ssh: reachable via jumphost.

==== meshcentral ====
https://remote.osgeo.org
This is a remoting tool currently setup to test livecd vms via a web browser.

4 VMS currently set up on osgeo8 accessible from this. Currently based on livecd 16rc1 snapshots, with wm install script run.

==== pgrouting-dev ====
For pgrouting development use to do things like pushing docker images on a scheduled basis.
Perhaps later for demo sites. WIP.

==== woodie-client-vm ====

Separate agent for woodie-server, this one is a true VM rather than container.

==== woodie-server ====

See [[Woodie]]

== osgeo 9 ==
Server added April 2021, donated by OpenStreetMap project.

Likely machine: https://web.archive.org/web/20191112203042/https://hardware.openstreetmap.org/servers/stormfly-02.openstreetmap.org/

Is an LXD host. Also Stores lxd images used by other lxd hosts.

[[osgeo9|Configuration Details]]

=== Services running on osgeo9 ===
==== hop ====
hop.osgeo9.osgeo.org. For LDAP users allows them to hop thru to get to other containers.

==== Secure (LDAP ) ====
[https://git.osgeo.org/gitea/sac/osgeo9/wiki/secure-container secure] -- ldap.osgeo.org [[SAC:LDAP]] used for ldap service (a rebuild of old secure.osgeo.osuosl.org) now on Debian 11
Moved from osgeo7

==== ldap-web ====

Currently housing https://id.osgeo.org/ for LDAP management.
Deployed via ansible
Moved from osgeo9

* id.osgeo.org

==== jitsi ====

See [[SAC:Jitsi]] (for video meetings)

==== nextcloud ====
https://nextcloud.osgeo.org

Ubuntu 22.04 LXD/nginx/postgresql 14 container for document sharing similar to dropbox/google drive - nextcloud.lxd - https://nextcloud.osgeo.org [https://git.osgeo.org/gitea/sac/osgeo9/wiki/Nextcloud-container Nextcloud Setup]

home of https://nextcloud.osgeo.org
This server does not use ssh osgeo-ldap as it was the first container built. However nextcloud.osgeo.org does authenticate with osgeo ldap.

TODO: add special page for this

==== nginx ====
nginx (for web proxy of traffic of osgeo9 containers) additional mirror proxy for download.osgeo.org

==== adventure (WIP)====
https://adventure.osgeo.org runs https://github.com/thecodingmachine/workadventure software

==== dronie-client ====
a ci bot for dronie.osgeo.org which is used for git.osgeo.org/gitea ci jobs

==== limesurvey ====
Debian 10, PostgreSQL 13, PHP 8 with ldap/ssh. https://limesurvey.osgeo.org
Setup detailed on [https://git.osgeo.org/gitea/sac/osgeo3/wiki/limesurvey-container limesurvey container]

==== mail ====
mailman: lists.osgeo.org
mail.osgeo.org
tilechache web: tilecache.osgeo.org
mailserver: postfix

==== matrix ====
'''Container Name:''' matrix - lxd container with ldap/ssh.
Hosts [[Matrix]] homeserver ([[SAC:MatrixSynapse]]) and IRC bridges ([[SAC:Heisenbridge]])

https://gitea.osgeo.org/sac/osgeo9/wiki/matrix-container for full detail on how the container is setup

==== pixelfed ====

SHUT OFF (both container and website) cause of lack of interest. Container is still there.
[[Pixelfed]] instance reachable on https://photo.osgeo.org to house community photos

==== peertube ====

[[Peertube]] instance reachable on https://video.osgeo.org

==== pretalx ====
Ubuntu 20.04 with OSGeo LDAP and Docker installed. pretalx software runs in Docker.
https://talks.osgeo.org - for OSGeo Talk collection and voting See [[Pretalx]]

==== weblate ====
'''Container Name:''' weblate (for doc translation)

Houses: https://weblate.osgeo.org (for document translation to different languages)

For further details refer to [[SAC:Weblate]]

==== wordpress ====

See [[SAC:Wordpress]]

==== geo-docs container ====

Houses:
* https://blog.geoserver.org
* https://geos.osgeo.org
* https://geotools.org
* https://geowebcache.osgeo.org
* https://lastools.osgeo.org
* https://planet.osgeo.org

==== wiki ====

See [[OSGeo Wiki]]

==== discourse ====

See [[SAC:Discourse]]

==== mail ====

Hosts: lists.osgeo.org, mail.osgeo.org and a few other services.
See [[Mail server]] for more details.

== osgeo 7 ==

Server added June 2018. Intended to replace [[SAC_Service_Status#osgeo3|osgeo3]] and old osgeo4 (before reformat).
See [[Osgeo7]] for configuration details.

[https://git.osgeo.org/gitea/sac/osgeo7/wiki/_pages Container setup of all the osgeo7 servers is located in https://git.osgeo.org/gitea/sac/osgeo7/wiki/_pages]

Running LXD 3 snap based container management -- LXD version 3.17 as of 2019-09-15

=== Accessing osgeo7 containers via ssh ===

Only the download.osgeo.org is directly exposed ssh via port 22. To access the other containers, you can tunnel thru
download.osgeo.org -- You need to be in the shell group to be able to access download and the other servers. If you are not already put in a [https://trac.osgeo.org/osgeo/newticket SAC Ticket Request]. You also need to have your public key registered. To do so edit your profile [https://id.osgeo.org/ldap/edit] (and put in your public key)

A convenient block to add to your own `.ssh/config` file follows:

Host osgeo7-*
ProxyCommand ssh your_osgeo_id@hop.osgeo7.osgeo.org -W $(sed -e "s/^osgeo7-//;s/$/.lxd/" <<< "%h"):%p
IdentityFile "path/to/your/private/key"

With the above in place, you can connect to any container using:

ssh your_id@osgeo7-<container_name>

'''Troubleshooting:''' In case of "Permission denied (publickey)." after an update to a modern openSSH version, it might well be that your ssh key (RSH key) is disabled in your client in favour of more modern cyphers.

Ugly workaround: add one line `PubkeyAcceptedKeyTypes ...` in `.ssh/config`, to re-enable RSA keys for now (consider to generate a new key):

vim .ssh/config
...
Host *
...
PubkeyAcceptedKeyTypes +ssh-rsa

... but better read e.g. [https://dev.to/bowmanjd/upgrade-ssh-client-keys-and-remote-servers-after-fedora-33-s-new-crypto-policy-47ag here]!

=== Services on osgeo7 ===

==== Monitor ====

debian10 lxd container with ldap/ssh. https://monitor.osgeo.org (houses grafana dashboard (for all servers) and prometheus server for <del>[[SAC_Service_Status#osgeo3|osgeo3]]<del> containers and pulls basic container metrics using node exporters pulled via prometheus servers. Requirs ldap to log into the web console.

Configuring servers for monitoring is detailed [https://git.osgeo.org/gitea/sac/prometheus-config Git Prometheus Config]

==== Download ====

See [[Download Server]]

==== dronie-client-osgeo3 ====
STOPPED See [https://trac.osgeo.org/osgeo/ticket/3415 #3415]
Its a copy of dronie-client that was on [[SAC_Service_Status#osgeo3|osgeo3]] which has been shutdown
This is a debian 10 lxd container running docker. Currently has just one running docker osgeo-drone-agent to serve as a client for dronie-server (dronie.osgeo.org running on osgeo7)

==== gallery ====
Debian 12 (bookworm) container for AI/ML services, media, and experimental applications.
'''Resources:''' 8 vCPUs, 12GB RAM
'''System services:''' nginx, redis, PostgreSQL 17, turnserver, php-fpm
'''Brian's services (darkblueb):'''
* GalleryVM media library
* llamafile experiments
* photoprism configuration
'''Lorenzo's services (ominiverdi):'''
* '''matrix-llmagent''' - Matrix chat bot with LLM integration (uses OpenRouter API)
** GitHub: https://github.com/ominiverdi/matrix-llmagent
* '''BGE-M3 Embedding Server''' - Semantic search embeddings via llama.cpp
** Port: 8094 (localhost only), Model: bge-m3-Q8_0.gguf
* '''osgeo-library''' - PDF figure/table/equation extraction and semantic search
** GitHub: https://github.com/ominiverdi/osgeo-library
** CLI command: <code>osgeo-library</code> (as ominiverdi user)
* '''osgeo_wiki_bot''' - Automated wiki/WordPress/Planet content sync and processing
** GitHub: https://github.com/ominiverdi/osgeo_wiki_bot
** Cron: wiki (6h), WordPress (daily), Planet (4h), chunk processing (hourly)
'''Pending SAC actions:'''
* Install postgresql-16-pgvector package (for osgeo-library semantic search)
'''Contact:''' darkblueb (Brian Hamlin), ominiverdi (Lorenzo Becchi) or SAC channel

==== live ====
Home of [http://live.osgeo.org live.osgeo.org] ;
Running Ubuntu 24.04.3 LTS with OSGeo LDAP SSH

==== mapserver ====

See [[MapServer_at_osgeo7]]

==== nexus (repo.osgeo.org, docker.osgeo.org) ====
See [[SAC:Repo]] this is a debian 10 lxd container running docker 19.
It currently has one docker container running within it called nexus -- exposed as repo.osgeo.org on nginx.

Also exposed as project dockers for pushing images: postgis-docker.osgeo.org, geoserver-docker.osgeo.org, geos-docker.osgeo.org, sac-docker.osgeo.org

==== nginx ====
Proxy that routes all http/https traffic for the other containers (can be accessed via osgeo7 host lxc or ubuntu@osgeo7-nginx if your key is installed on ubuntu user).
The nginx container holds the letsencrypt https SSL certs for all the containers and handles the renewal of the letsencrypt certs using certbot renew cronjob.
Prometheus server to collect all monitoring logs from OSGeo7 <del>(only accessible by [[SAC_Service_Status#osgeo3|osgeo3]]), these get queried via monitor.osgeo.org (running on [[SAC_Service_Status#osgeo3|osgeo3]]) via grafana server.<del>

==== tracsvn (trac, svn, git) ====

Home of [[Trac]], [[SAC:Git Service|Git]] and [[Subversion]] services.

See [[TracSVN]] for full details.

==== photoprism ====
Picture gallery. Syncs with https://nextcloud.osgeo.org
But pictures are shown here https://photoprism.osgeo.org

==== old-wiki (stopped) ====
This used to be housed on [[SAC_Service_Status#osgeo3|osgeo3]], and was moved 2019-09-14 to osgeo7 as old-wiki container.
wiki.osgeo.org moved back to [[SAC_Service_Status#osgeo3|osgeo3]] on 2020-05-22 and in wiki container. The wiki container is a complete rebuild with files and database restored and upgraded.
Refer to the [[SAC_Service_Status#osgeo3|osgeo3]] section for more details.

[https://git.osgeo.org/gitea/sac/osgeo7/wiki/old-wiki-container old wiki container] -- used for wiki service (it is an lxd2pc created image of wiki.osgeo.osuosl.org VM that was on [[SAC_Service_Status#osgeo3|osgeo3]])

See [[OSGeo Wiki]]

==== nextcloud-ubuntu (stopped) ====
Moved to osgeo9

==== dronie-server ====

See [[Dronie]]

==== old-projects (stopped) ====
-- this is the old projects.osgeo.osuosl.org migrated from osgeo4 as an lxd container, so more or less the same as it was before, with the exception that all the websites are now proxied thru the nginx container. Websites on it are community-review.foss4g.org and spatialreference.org

To access you need to go thru download.osgeo.org -> old-projects

==== old-web (stopped) ====
The old web.osgeo.osuosl.org (was on [[SAC_Service_Status#osgeo3|osgeo3]])

* mapguide.osgeo.org

==== old-webextra ====
This is a replica of webextra.osgeo.osuosl.org that was hosted on [[SAC_Service_Status#osgeo3|osgeo3]]

Started move on November 29th 2019 and completed December 8th, 2019
* foss4g.org
* europe.foss4g.org
* video.foss4g.org
* planet.osgeo.org
* various old foss4g.org years
* <del>live.osgeo.org</del> moved to dedicated container
* journal.osgeo.org (not sure what this is for, should be retired?)
* <del>vmap0.tiles.osgeo.org</del> #removed site

Information from webextra on [[SAC_Service_Status#osgeo3|osgeo3]]

** Retired December 8th, 2019 -- and moved to osgeo7 as container old-webextra

* See [[WebExtraVM]] for full details (server: http://webextra.osgeo.osuosl.org)
* hosts http://planet.osgeo.org, http://mum03.mapserver.org, http://live.osgeo.org
* http://foss4g.org (main portal) and archive of old sites 2006-2014
* http://conference.osgeo.org - [[Conference System]] (also: [[SAC:Setup_OCS]])
* http://journal.osgeo.org / osgeo.org/ojs - [[Journal System]]
* Redirects for many chapter and other urls handled via /etc/httpd/conf.d/rewrite.conf

==== pycsw ====
'''Container Name:''' pycsw

* https://demo.pycsw.org
* '''OGC CSW Reference Implementation and Server demo'''
* deployment setup at https://github.com/geopython/demo.pycsw.org
* running hourly teardown/setup cron via docker-compose
* migrated from [[AdhocVM#Existing_services_hosted_on_the_Ad-hoc_VM:|Adhoc VM]] thanks to [https://trac.osgeo.org/osgeo/ticket/2452 SAC] (May 2020)

=== osgeo7 decommissioned containers ===

==== <del>old-adhoc</del> ====

'''SHUTOFF as of 2022-01-29'''

[[AdhocVM|old-adhoc]] -- this is the old adhoc.osgeo.osuosl.org migrated 2019-05-08 from osgeo4 as an lxd container.
Used by osgeo-live for there test docs and by grass for earthquake, and mapserver for demo.
Note that there is a new live (container that osgeo-live will more to), there is also a mapserver container (which mapserver have started to move their demo to)

To access via ssh you should go thru download.osgeo.org -> old-adhoc.lxd
It is accessible via https://adhoc.osgeo.org and http://adhoc.osgeo.osuosl.org

* VM used for projects for various adhoc purposes. Risks to system stability that would be unacceptable on the Projects VM may be ok here.
* See [[AdhocVM]] for full details, and some notes on services running here.
* eg http://adhoc.osgeo.osuosl.org/livedvd/docs/en/quickstart/

== osgeo6 ==

See [[osgeo6]]

== osgeo4 ==

osgeo4 is a real server managed by OSUOSL - can be access via ssh tech_dev@osgeo4.osgeo.osuosl.org -p 2222 (only people with their access keys installed can log in and doesn't allow password access) - password for tech_dev is in the secure container (on osgeo7) / access folder.

In August 2019 the server had new power supply put in and replacement disks. It was reformatted with Ubuntu 18.04.3 to serve as secondary LXD host to osgeo7
zfsutils-linux was installed so lxd can use zfs for storage.

=== sshing into osgeo4 containers ===
Note that all the containers are closed off from direct ssh access except for the hop.osgeo4.osgeo.org. To access the other containers, you need to hop through hop.
hop container has port 22 open but requires ssh access so users who’ve been granted rights can hop thru it to other containers using hop.osgeo4.osgeo.org as name.

A convenient block to add to your own .ssh/config file follows where your_id could be your osgeo id or a local account on that container

Host osgeo4-*
ProxyCommand ssh your_osgeo_id@hop.osgeo4.osgeo.org -W $(sed -e "s/^osgeo4-//;s/$/.lxd/" <<< "%h"):%p
IdentityFile "path/to/your/private/key"
User your_id

Then to access say the wordpress-dev container, you'd do the below

ssh osgeo4-wordpress-dev

=== osgeo4 baremetal features ===
It's makeup is as follows:
{| class="wikitable"
|-
! Item !! Settings
|-
| Disks || 6 1.8 TB drives
|-
| Memory || 48 GB
|-
| CPUs || 8 Intel(R) Xeon(R) CPU E5540 @ 2.53GHz (8192kb cache)
|}
<pre>lsblk -i
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1.8T 0 disk
|-sda1 8:1 0 953M 0 part
| `-md0 9:0 0 952M 0 raid1 /boot
`-sda2 8:2 0 46.6G 0 part
`-md1 9:1 0 46.5G 0 raid1
|-lvm-root 253:0 0 37.3G 0 lvm /
`-lvm-swap 253:1 0 7.5G 0 lvm [SWAP]
sdb 8:16 0 1.8T 0 disk
|-sdb1 8:17 0 953M 0 part
| `-md0 9:0 0 952M 0 raid1 /boot
`-sdb2 8:18 0 46.6G 0 part
`-md1 9:1 0 46.5G 0 raid1
|-lvm-root 253:0 0 37.3G 0 lvm /
`-lvm-swap 253:1 0 7.5G 0 lvm [SWAP]
sdc 8:32 0 1.8T 0 disk
sdd 8:48 0 1.8T 0 disk
sde 8:64 0 1.8T 0 disk
sdf 8:80 0 1.8T 0 disk
</pre>

<pre>
sdc,sdd,sde,sdf form a zfs osgeo4_lxd partition (sdc,sdd) mirrors sde,sdf for total lxd capacity of 3.62 TB
</pre>

Nightly backups of osgeo7, and osgeo4 containers are kept here and named <container>-backup and be kept in a stopped state.

=== Services running on osgeo4 ===

==== hop ====
'''Container Name:''' hop - this is the only container with direct ssh access via ssh hop.osgeo4.osgeo.org. To get to other containers, you need to hop thru this one. Requires ssh key access

==== ansible-dev ====
'''Container Name:''' ansible-dev, has ansible 2.9.27 installed and all plugins needed to manage OSGeo ansible infrastructure.
DEPRECATED, use `ansible-dev`

==== ansible-control ====
'''Container Name:''' ansible-control, can be used to deploy OSGeo ansible infrastructure. Replaces `ansible-dev`

==== osgeo4-nginx ====
'''Container Name:''' osgeo4-nginx ->> all web traffick from other containers on osgeo4 get proxied thru here

==== old-web-staging ====
'''Container Name:''' old-web-staging - used primarily for experimenting with changes to id.osgeo.org (old-web on osgeo7) like testing out OS and software upgrade etc, changes to LDAP forms and registration, before applying to id.osgeo.org. - https://id.staging.osgeo.org

==== pretalx-staging ====
'''Container Name:''' pretalx-staging - used primarily for experimenting with changes to talks.osgeo.org (pretalx on [[SAC_Service_Status#osgeo9|osgeo9]]) like testing out Docker builds and software upgrade etc, before applying to talks.osgeo.org. - https://talks.staging.osgeo.org

==== wordpress-dev ====
'''Container Name:''' wordpress-dev - used primarily for osgeo.org main website development - https://staging.www.osgeo.org, https://dev.www.osgeo.org

==== wiki-dev ====
'''Container Name:''' wiki-dev - used primarily for experimenting with changes to wiki.osgeo.org like testing out OS and software upgrade etc before appying to wiki.osgeo.org. - https://dev.wiki.osgeo.org

==== wiki-staging ====
'''Container Name:''' wiki-staging - used primarily for upgrade changes to wiki.osgeo.org like testing out OS and software upgrade etc before applying to wiki.osgeo.org. - https://staging.wiki.osgeo.org. The construction of this container is managed by sac ansible-deployment.

==== tracsvn-dev ====
'''Container Name:''' tracsvn-dev - This is a 2019-09-05 lxd2pc image of tracsvn.osgeo.osuosl.org (now on osgeo7 as tracsvn) used primarily for experimenting like testing out OS, git and software upgrade etc before appying to production. -- https://dev.git.osgeo.org, https://dev.tracsvn.osgeo.org Has the following sites: https://dev.trac.osgeo.org, https://dev.git.osgeo.org/gitea, https://dev.svn.osgeo.org.

It was upgraded to Debian 11 on 2024-08-21.

==== dronie-client ====
'''Container Name:''' dronie-client - This is a debian 10 machine, with OSGeo LDAP authentication and a drone-agent docker running. To be used with https://dronie.osgeo.org

= Cloud Hosted Servers and other external under SAC Control =

== Future Hosting Plans for Windows / Mac Building ==

[[SAC_Shared_Building_Services|SAC Shared Building Services]]

== Atlantic.net ==

* host.postgis.net -p 2222 is an LXD Ubuntu 18.04 16GB RAM/ 6 vCPU, 350GB data, 250GB block storage
* Currenlty running two lxd containers:
debbie: debian 10 postgis.net, planet.postgis.net, debbie.postgis.net (jenkins build bot)
debbie-docker.host.postgis.net - runs docker and serves as a 1.0 agent for dronie.osgeo.org

= QGIS off OSGeo =
Services on separated machines rented and managed by the QGIS project at hetzner

* website including documentation http://www.qgis.org
* website building, documentation building, debian/ubuntu nightlies, plugins.qgis.org
* issues.qgis.org: redmine

= Historical servers (not more in use) =

- [[Telascience Blades (Historical)]]

== web18a.osgeo.osuosl.org ==
NO LONGER USED - turned off
'''2019-09-03 Production services www.osgeo.org, 2018.foss4g.org moved to wordpress container on [[osgeo7]]
Staging services (staging.www.osgeo.org, dev.www.osgeo.org move to wordpress-dev container on [[osgeo4]]
Grass wordpress is disabled as grass decided to go with another solution, so have grass container on osgeo7'''
(Cloud hosted server on OSUOSL hardware (not ours) )
* Debian 9.3 4GB server, host name: web18a.osgeo.osuosl.org require ssh key to log in.
* Hosts wordpress sites staging.www.osgeo.org,www.osgeo.org, staging.grass.osgeo.org, foss4g2018.osgeo.org
* Setup details on [https://git.osgeo.org/gitea/osgeo/www_apache_configs/wiki/Web18a-setup Web18a setup]

== OSGeo funtoo ==

For lxd experimentation it's an lxd container running other lxd containers and provided by funtoo.org.

OSGeo is paying funtoo via treasurer at osgeo.org.

* [https://git.osgeo.org/gitea/sac/osgeo_funtoo OSGeo Funtoo] osgeo.host.funtoo.org

* funtoo LXDs currently running:
** <del>[https://limesurvey.osgeo.org LimeSurvey] -this may be in future migrated to osgeo7 or osgeo3</del>
Migrated to [[SAC_Service_Status#osgeo3|osgeo3]] 2020-11-28 -- see [[https://trac.osgeo.org/osgeo/ticket/2362|#2362]]

== osgeo3 ==

osgeo3 physical server refer to [[osgeo3|Configuration Details]] for hardware specs. It was used to run production, but moderately risky things. Refer to [[SAC:Old-osgeo3]] for past history before osgeo3 was rebuilt.
osgeo3 was a hosted by OSUOSL - No longer accessible <del>can be accessed via ssh tech_dev@osgeo3.osgeo.osuosl.org -p 2222 (only people with their access keys installed can log in and doesn't allow password access) - password for tech_dev is in the secure container (on osgeo7) / access folder.<del>

== Backup (osgeo5) ==

* <del>Backup now runs on dedicated hardware<del>
* <del>Provides Rsync backups of download.osgeo.org<del>
* <del>Provides Bacula backups of various VMs.<del>
* See [[SAC:Backups]] for details.

[[Category:Infrastructure]]
[[Category:Services]]

User:Hospitales

2025-11-09T15:35:57Z

Ominiverdi: Blanked the page

User:Santtuvp

2025-11-09T15:35:26Z

Ominiverdi: Blanked the page

User talk:Jparedesg

2025-11-09T15:34:37Z

Ominiverdi: Blanked the page