-
Notifications
You must be signed in to change notification settings - Fork 409
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
Notify data projection not compatible / available for COG #9589
Closed
1 of 6 tasks
Tracked by
#9593
Comments
6 tasks
tdipisa
changed the title
Notify data projection not compatible / avaliable for COG
Notify data projection not compatible / available for COG
Oct 12, 2023
tdipisa
added
the
BackportNeeded
Commits provided for an issue need to be backported to the milestone's stable branch
label
Nov 3, 2023
Updated acceptance criteria
|
dsuren1
added a commit
to dsuren1/MapStore2
that referenced
this issue
Nov 10, 2023
5 tasks
5 tasks
offtherailz
pushed a commit
that referenced
this issue
Nov 20, 2023
dsuren1
added a commit
to dsuren1/MapStore2
that referenced
this issue
Nov 21, 2023
…le for COG (geosolutions-it#9690) (cherry picked from commit 76207ab)
offtherailz
pushed a commit
that referenced
this issue
Nov 21, 2023
ElenaGallo
removed
the
BackportNeeded
Commits provided for an issue need to be backported to the milestone's stable branch
label
Nov 21, 2023
dsuren1
added a commit
to dsuren1/MapStore2
that referenced
this issue
Nov 23, 2023
5 tasks
offtherailz
pushed a commit
that referenced
this issue
Nov 27, 2023
ElenaGallo
added
the
BackportNeeded
Commits provided for an issue need to be backported to the milestone's stable branch
label
Nov 27, 2023
tdipisa
pushed a commit
that referenced
this issue
Nov 29, 2023
tdipisa
removed
the
BackportNeeded
Commits provided for an issue need to be backported to the milestone's stable branch
label
Nov 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When the download metadata is checked (and it should be by default), we have to check the CRS and notify the user if the CRS definiton is not defined in MapStore, so the layer can not be reporojected in the map CRS.
CRS should be avaliable from
const crs = getProjectionFromGeoKeys(image);
we already query on catalog to get the BBOXAlso if the layer in map is in a projection not compatible, it should be grayed out and notified as for WMTS.
What kind of improvement you want to add? (check one with "x", remove the others)
Other useful information
I don't think is relevant for our implementation,
but we noticed that in this example openlayer do not define any projection for the map or include the tiff projection
https://openlayers.org/en/latest/examples/cog.html
Probably the OL map has some automation to properly target projection
Instead here they are defined
https://openlayers.org/en/latest/examples/multiple-cogs.html
The text was updated successfully, but these errors were encountered: