-
Notifications
You must be signed in to change notification settings - Fork 410
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Persistence of COG layer's metadata info in catalog service #10083
Comments
dsuren1
added
enhancement
Internal
BackportNeeded
Commits provided for an issue need to be backported to the milestone's stable branch
labels
Mar 19, 2024
tdipisa
changed the title
Save COG layer's metadata info in catalog service on saving map
Persistence of COG layer's metadata info in catalog service
Mar 19, 2024
dsuren1
added a commit
to dsuren1/MapStore2
that referenced
this issue
Mar 19, 2024
6 tasks
6 tasks
6 tasks
offtherailz
pushed a commit
that referenced
this issue
Mar 19, 2024
dsuren1
added a commit
to dsuren1/MapStore2
that referenced
this issue
Mar 21, 2024
…talog service (geosolutions-it#10089) (cherry picked from commit 847c130)
ElenaGallo
removed
the
BackportNeeded
Commits provided for an issue need to be backported to the milestone's stable branch
label
Mar 21, 2024
tdipisa
pushed a commit
that referenced
this issue
Mar 21, 2024
offtherailz
pushed a commit
to offtherailz/MapStore2
that referenced
this issue
Apr 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Currently, the COG metadata is fetched on saving the service. However this proves to be not enough in some cases resulting in an inconsistent behavior when searching and adding the COG layer to map, like:
Acceptance criteria
What kind of improvement you want to add? (check one with "x", remove the others)
Ref issues
#10072 (comment)
The text was updated successfully, but these errors were encountered: