Skip to content
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

[BUG] 3 - Landcover query issues [OSDP-1801] (3 layers) #2603

Closed
1 task done
MLAuger opened this issue Nov 18, 2024 · 2 comments
Closed
1 task done

[BUG] 3 - Landcover query issues [OSDP-1801] (3 layers) #2603

MLAuger opened this issue Nov 18, 2024 · 2 comments

Comments

@MLAuger
Copy link

MLAuger commented Nov 18, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

The 3 land cover layers can't be queried in RAMP. They can in GeoView but return a strange value: "band-0-pixel-value"

image

Concerned UUIDs:
ee1580ab-a23d-4f86-a09b-79763677eb47
c688b87f-e85f-4842-b0e1-a8f79ebf1133
4e615eae-b90c-420b-adee-2ca35896caf6

Expected Behavior

No response

Steps To Reproduce

Load any of the three UUIDs and click on the data to query once loaded.

Anything else?

No response

@jolevesq jolevesq changed the title [BUG] Landcover query issues [BUG] 3 - Landcover query issues Nov 20, 2024
@MLAuger MLAuger changed the title [BUG] 3 - Landcover query issues [BUG] 3 - Landcover query issues [OSDP-1801] (3 layers) Nov 25, 2024
@jolevesq
Copy link
Member

This is returning the WMS value, field name and value. If we do not want it we need to set not query able. I do not think this is a layer issue. Can we close?

<FeatureCollection xmlns="http://www.opengis.net/wfs" xmlns:gml="http://www.opengis.net/gml" xmlns:ows="http://www.opengis.net/ows/1.1" xmlns:ogc="http://www.opengis.net/ogc" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><gml:featureMember
><Geometry>
…
</Geometry
><band-0-pixel-value>15.0</band-0-pixel-value></gml:featureMember></FeatureCollection>

@MLAuger
Copy link
Author

MLAuger commented Jan 14, 2025

You are right, this is not an issue. I had a talk with the Data Cube team this week about this and it does behaves as expected. It's RAMP that did not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants