Search Results

You should basically never use ee.Algorithms.If. If that's the tool you're reaching for, you should rethink what you're doing. In this case, separate the reduceRegion and the unmask into separate fun …

Your code is incomplete so it's not possible to check on things, however You're manually creating a collection from a bunch of what looks like geoJSON. If that collection is large, then the manual c …

Your first quote is in the wrong place. It should be outside the parentheses. '(0.6 * slopereclass) + (0.4 * elevationreclass)'

The documentation for the eigen function states: This implementation uses DecompositionFactory.eig() from https://ejml.org, so the source code, modulo any version differences, is here: https://github. …

Assume for a second that you could have a pixel with a string in it; what would you then do with that? If the answer is: "I'd display it so I knew what day the pixel came from", or something like tha …

I can't tell what you're really trying to do, but there are no situations where you can use both map and iterate where you should choose iterate. You should also avoid converting to list when possibl …

getAsset just gets metadata about the asset; it doesn't actually load it. In order to use it, you use the FeatureCollection constructor with the asset's ID/path. ee.FeatureCollection("projects/ee-alen …

It's no big deal if you call it twice. Most of the library notices that it's already been initialized once and skips doing unnecessary work.

You can figure out which of the operations is too big by trying to print the size of each of the point samples, and the classifier.explain(), and seeing which one barfs first. Most likely, you are sam …

reduceRegions just copies the input feature and adds some properties to it, so in order to have empty geometries, you had to start out with them that way. Buffering something with no geometry results …

You can skip the If() by just merging the collections and taking the first().

When passed a Geometry, Feature or FeatureCollection, Map.addLayer uses collection.draw() to create the layer. There aren't a lot of options to draw, so instead, you should make your own call to col …

No, there's nothing built in for that. It would make a good feature request though.

You simply misspelled the function's name. It's normalizedDifference

This function (and all the other neighborhood operations like GLCMTexture, slope, aspect, etc) operates in units of "output pixels". So if you zoom in, you're working on pixels that are ultimately sm …