New answers tagged

3

Chart.image.byClass is just calling a grouped reduceRegion. Probably easiest to just build your own data table, so you can then configure the rest of the charting any way you want. var palette = ee.List(["#006400","#00ff00","#687537","#935132","#45c2a5","#b8af4f","#f1c232","#ffd966&...


1

Dictionaries (and Feature properties) aren't ordered, so you have to jump through some hoops to convert them into something that has an order first. Get the importance keys and values as lists, sort them, convert to a Chart API DataTable and plot that: https://code.earthengine.google.com/4ae6b783c20dc09aed826a358b94552f var importance = ee.Dictionary(exp.get(...


1

I would use an ui.Chart.feature.groups chart. That requires you to rearrange your data a bit. Here's one way to do that: var labelByCode = ee.Dictionary({ 1: 'Air', 2: 'Vegetation', 3: 'Urban', }) var features = ee .FeatureCollection([ ee.Feature(null, {year: 2000, data: area_2000}), ee.Feature(null, {year: 2010, data: area_2010}), ee....


0

Worked when specificying the crs field in .reduceRegion so that the two images are in a common projection. Example: var pixelValsY = data.reduceRegion( {reducer: ee.Reducer.toList(), geometry: geometry, scale: 30}); var pixelValsX = dem.reduceRegion( {reducer: ee.Reducer.toList(), geometry: geometry, scale: 30, crs: data.projection()}); ...


Top 50 recent answers are included