You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Think about batch embedding processing. Have a way to generate embeddings at the start of the project. Select AOI -> tile -> prepare embeddings -> store them somewhere (perhaps S3) as /z/x/y.embedding
Currently, DS-Annotate supports map view embedding, which can be easily stored in S3 and loaded when starting a project. However, there is an issue when loading the map views: if someone loads the embedded images in a different browser size, the embedding doesn't work anymore, because the positions of the bounding box and points will be incorrect.
I believe tile supports will work much better, such as embedding all tiles in an area or map view. In this way, we can store as many tiles as we want. what do you think @willemarcel ?
From: https://github.com/developmentseed/labs/issues/327#issuecomment-1629049057
Currently, DS-Annotate supports map view embedding, which can be easily stored in S3 and loaded when starting a project. However, there is an issue when loading the map views: if someone loads the embedded images in a different browser size, the embedding doesn't work anymore, because the positions of the bounding box and points will be incorrect.
I believe tile supports will work much better, such as embedding all tiles in an area or map view. In this way, we can store as many tiles as we want. what do you think @willemarcel ?
cc. @geohacker @batpad @rbavery
The text was updated successfully, but these errors were encountered: