Change announcements for collections ch.blw* and ch.bafu*

[mariokeusen]

Test link

[faselm]

👍

[asteiner-swisstopo]

Nice, has the right amount of detail. I would put in a bit more structure to make it easier to read than one long sentence.

[asteiner-swisstopo]

I have the following concerns:

1. I find these long sentences a bit difficult to read.
2. There is a typo: "timestand"
3. Don't we have to write that it is a "STAC collection" instead of just "collection" to make it clear what the context is?
4. It's not clear if only ch.bafu.gewaesserschutz-nawa is going to be released on March 18th - what about ch.blw.ursprungsbezeichnungen?

How about this simpler version?

[2026-02-26] Migration of STAC collections ch.blw.ursprungsbezeichnungen* and update to ch.bafu.gewaesserschutz-nawa

The upcoming release on March 18th 2026 will introduce the following changes:

• New collection ch.blw.ursprungsbezeichnungen. This collection replaces the five previous collections:

  • ch.blw.ursprungsbezeichnungen-fleisch
  • ch.blw.ursprungsbezeichnungen-kaese
  • ch.blw.ursprungsbezeichnungen-konditoreiwaren
  • ch.blw.ursprungsbezeichnungen-pflanzen
  • ch.blw.ursprungsbezeichnungen-spirituosen

• Updated items in ch.bafu.gewaesserschutz-nawa. The existing STAC item gewaesserschutz-nawa will be replaced by two new items with updated content and timestamps:

  • gewaesserschutz-nawa_biologie
  • gewaesserschutz-nawa_chemie

[mariokeusen]

Tried to bring this in an updated proposal while considering the facts about the changes. Merci fürs re-review...

[asteiner-swisstopo]

Cool thanks. Very long title but I can live with that 🙃

For your info @mariokeusen, our guidelines state that we should rebase, not merge in case of a merge conflict (as you did):

When merging a personal branch into a shared branch (e.g. feat-my-feature into develop), we should never have conflict as the head branch should be always rebased on top of the base branch. Due to this conflict always happens during the rebase and needs to be fixed during the rebase step on the personal branch.

You can do this in GitHub easily:

[mariokeusen]

@asteiner-swisstopo thanks for that hint, this is due to the fact, I only very rarely merge pr's myself. In this case, anyways currently nothing can be merged, because of some aws code build test failing (and I am totally lost there). Therefore glad if you or someone who can handle that, could take over the merging here (from the content side, for me this can be published)

[asteiner-swisstopo]

@asteiner-swisstopo thanks for that hint, this is due to the fact, I only very rarely merge pr's myself. In this case, anyways currently nothing can be merged, because of some aws code build test failing (and I am totally lost there). Therefore glad if you or someone who can handle that, could take over the merging here (from the content side, for me this can be published)

@mariokeusen When building the website for the test link, AWS CodeBuild runs a program to check for inconsistencies in the Markdown documents (prettier). In this case, there were several small issues, so the corresponding pipeline in AWS CodeBuild failed. For example, there was no blank line after the list.

For this time, I fixed the issue, merged the branch to master and released to https://docs.geo.admin.ch.

I can show you how to do that yourself for another time, feel free to reach out.