That seems like a reasonable approach, it does indeed have some complicated
history ownership-wise
Cheers,
Torben
On Tue, Jul 26, 2022 at 3:55 AM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:
> Hi Torben,
> yup, I was aware of the effort in that repo, and keeping an eye on it.
> I'm ho
Hi Torben,
yup, I was aware of the effort in that repo, and keeping an eye on it.
I'm however being careful not to copy bits from it, as I'm also aware of
the history of the module before it landed in that public repo and...
well it seems a bit of a code ownership minefield.
Cheers
Andrea
On Tue
+1
I think you may already be aware, but Josh Fix did a lot of work on
something similar a couple years back, and it looks like the code is still
available here: https://github.com/joshfix/imagemosaic-stac
I'm not sure if it'll be at all useful (I expect largely not, given that
its been unmaintain
+1
Ian
On Wed, 13 Jul 2022 at 13:38, Andrea Aime
wrote:
>
> Hi all,
> I'm writing to ask permission for a new community module, a datastore that
> would
> talk to a STAC API, and return features accordingly.
>
> The module would be used as a simple vector store, to display where assets
> (imag
Hi all,
I'm writing to ask permission for a new community module, a datastore that
would
talk to a STAC API, and return features accordingly.
The module would be used as a simple vector store, to display where assets
(images) are located, but it's also meant to be used as a image mosaic
index, so
