Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with raster
Search options not deleted
user 121563
Raster is a data format consisting of regular grids of values, usually stored in an image-like format.
1
vote
1
answer
232
views
Unexpected results for area calculation on two datasets in Google Earth Engine
I'm seeing a very strange result using .pixelArea() on two different layers that should yield identical results.
Code within GEE is here, also reproduced below:
var states = ee.FeatureCollection("ft: …
- 113
5
votes
1
answer
885
views
When is a projected coordinate system needed for analysis (with rasters)?
Take another raster from a different data source, which may have a projected coordinate system and/or a different geographic coordinate system, and use my base data to extract the cells in this other raster … While I'm mainly interested in having the correct theoretical understanding (and keeping my base data in WGS84 as-is), it's also notable that some of ArcGIS's Spatial Analyst raster algebra tools (e.g. …
- 113