Open wildintellect opened 1 year ago
Generally we should defer the STAC portion to https://stacspec.org/en/tutorials/ with the exception if STAC results are the input to the loading (e.g. stackstac
). So we should start with knowing the URL to the item we want to read.
Also depth examples that do more than just read parts of a file should find similar appropriate homes like https://projectpythia.org/ Maybe R depth examples can go to https://r-spatial.org
Quick check, we're looking at up to 72 code examples with the proposed options (not all may be valid) 9 languages(across 2 use types) * 8 = 72
Note for R examples:
vsi=TRUE
to trigger vsicurl usage
There are 2 main users stories: Data Producers and Data Users
The matrix of Producer/User Language Format = number of code samples
Level 2 would be to also include various common authentication issues, also in all the languages.
As pointed out in https://github.com/cloudnativegeo/cloud-optimized-geospatial-formats-guide/discussions/83 using quarto tabsets would be a nice way to keep adding languages as people make examples for the same thing.