Problem
- OAM upload rates are relatively low.
- It's quite unique to find both (a) a person with capabilities to generate a datasets (b) a person with a mindset to want to upload the data for public access.
- It has been suggested that an onboarding pathway for users that produce private datasets would be beneficial, such as NGOs, governments, etc.
Suggested Solutions
These solutions would require adding extra database + API functions to hide specific datasets / make them private.
This probably quite difficult to implement with STAC...
- One suggestion was to have an 'expiry' on the private data. Apparently people do this when the data is commercially useful for say 30 days, but then afterwards isn't commercially useful, so the data could automatically switch over to 'public' after the time has elapsed.
- Another option is to have entirely private datasets hosted on OAM - this would benefit NGOs etc, likely working doing valuable work, but not for general public good.
Should we even consider this idea? After all, OAM was envisioned as a fully open-data repository for open licensed imagery.
Problem
Suggested Solutions
These solutions would require adding extra database + API functions to hide specific datasets / make them private.
This probably quite difficult to implement with STAC...
Should we even consider this idea? After all, OAM was envisioned as a fully open-data repository for open licensed imagery.