This repository has been archived by the owner on Dec 8, 2022. It is now read-only.
Identify pixel value on click #357
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stazrad
reviewed
Nov 11, 2021
src/Popup/utils.js
Outdated
| // handle non vector tile wfs layers | ||
| wfsSelector(layer) | ||
| } else if (!layer.getProperties()._ol_kit_basemap) { | ||
| promises.push({ features: [getPixelValue(layer, event)] }) |
There was a problem hiding this comment.
add comment that this checking for pixel value on raster
PatchesMaps
added
team reviewed 👀
stazrad
approved these changes
Nov 16, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves: attach_gh_issue_here
PR Safety Checklist:
package.json&package-lock.jsonversion numbers to appropriate releasenpm run docsQuick Description of Changes (+ screenshots for ui changes):