HDG-52 Make it clearer when to use STAC API#134
Open
asteiner-swisstopo wants to merge 1 commit intomasterfrom
Open
HDG-52 Make it clearer when to use STAC API#134asteiner-swisstopo wants to merge 1 commit intomasterfrom
asteiner-swisstopo wants to merge 1 commit intomasterfrom
Conversation
According to support, people are often confused whether they should use feature-based API endpoints or the file-based STAC API. See [this recent Google group thread](https://groups.google.com/g/geoadmin-api/c/3fSpRamiF2c/m/aW6yn49mCAAJ) for example. This change aims to improve clarity by changing these two sections: - Page "Identify Features": Redirect to STAC API in the warning box about the maximum number of features. - Page "STAC API" > "Overview": Add a section to clarify how STAC is different from the other service endpoints (api3).
Comment on lines
7
to
10
| ::: warning | ||
| No more than 200 features can be retrieved per request. | ||
| A maximum of 200 features can be retrieved per request. | ||
| To download a larger number of features or entire datasets, use the file-based [STAC API](/download-data/stac-api/overview.md). | ||
| ::: |
Contributor
Author
There was a problem hiding this comment.
@ltclm Is this the only service endpoint with that limitation or should we also add that warning to other pages?
Luke252
reviewed
May 4, 2026
|
|
||
| This documentation provides tutorials on how to use the STAC API of [data.geo.admin.ch](https://data.geo.admin.ch/). | ||
|
|
||
| While other geo.admin.ch service endpoints are tailored for querying individual records and targeted vector features, the STAC API is optimized for discovering and downloading file-based data, typically entire datasets or specific spatial or temporal tiles. |
Luke252
approved these changes
May 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
According to support, people are often confused whether they should use feature-based API endpoints or the file-based STAC API. See this recent Google group thread for example.
This change aims to improve clarity by changing these two sections:
CC @faselm
Test link