-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Output point locations from geemap.extract_values_to_points doesn’t match input #610
Comments
Thanks for reporting! This bug has been fixed. Please update the package using |
Thank you for the quick fix. I updated and tried without specifying the scale and projection: geemap.extract_values_to_points(points, clay, outShapefile) |
What basemap are you using in QGIS? Try using the same Google basemap in both QGIS and GEE. If the points appear to be at the same locations, then it might be the problem with the basemap you used. |
I am using geemap.extract_values_to_points to extract pixel values under points from a Shapefile (EPSG: 4326) and outputting to a Shapefile. This is the raster image I’m using:
ee.Image("projects/soilgrids-isric/clay_mean")
When I checked the results in QGIS the points in the output Shapefile did not align with the input Shapefile. They were displaced ~200m and therefore extracts data from a neighboring pixel. To fix that I specified scale = 10, projection = 'EPSG:4326'. This moved the output points so they were nearly identical, however, the values for the points correspond to the raster value of the original point location. In other words, the location is (more or less) correct the but data value is from the neighboring pixel.
I attached the Shapefile I'm using.
I’m running this on Ubuntu 20.04 with version 0.8.18 of geemap
points_carbon_sequestration_gisel.zip
The text was updated successfully, but these errors were encountered: