NOTE: I started to create these tutorials when I was a PhD student. I decided to continue, but it has nothing to do with my current affiliation/employer.
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>10 top tweet tips to become an expert in #EarthEngine #visualizations from @Keiko_geo.
— Google Earth (@googleearth) February 5, 2020
#1 - find out how adjusting color from satellite images can help you magnify and study objects such as buildings or vegetation ➵ https://t.co/mjoNKv1MQO pic.twitter.com/RoceWb62Wz
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>#EarthEngine tip 56: It's about time! Use #SegmentGeospatial #samgeo developed by @giswqs & Lucas Osco for your remote sensing questions. Did you know @samapriyaroy recently ingested @ESA_EO
— Keiko (@Keiko_geo) July 8, 2023
CCI Biomass? #geemap is fully utilised in this tip too! pic.twitter.com/LiS4KCDpsm
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Google #EarthEngine tip 26: inspired by @annamaria_84 #NDVI time-series composite in #RGB - you can see when trees or crops were cleared or have grown by colour (May 2017, 2018, and 2019). Red = cleared; blue = grown using #GoogleEarthEngine pic.twitter.com/qqotIzqIPt
— Keiko (@Keiko_geo) October 27, 2019
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Google #EarthEngine tip 40: How to do 'loop' (actually 'map') on #GoogleEarthEngine with different #RandomForest parameters. Nested loop? No problem... #MachineLearning #FeatureImportance #EarthEngineSG pic.twitter.com/nOS0i0PvEB
— Keiko (@Keiko_geo) September 15, 2021
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Google #EarthEngine tip 28: too lazy for machine learning? Identify objects using #NDVI. Low costs, low power, and elementary math. #ForYourInspiration #GoogleEarthEngine pic.twitter.com/alu1WteKJC
— Keiko (@Keiko_geo) November 16, 2019
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Google #EarthEngine tip 44: Are you using 'aside()'? It can save you a lot of time and lines! #Landsat9 pic.twitter.com/uhhh3OUDj0
— Keiko (@Keiko_geo) February 15, 2022
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Google #EarthEngine tip 33: Doing #SAR in the right way. Not-so-deadly (or is it?) consequence of averaging dBs. #Sentinel1 #GoogleEarthEngine pic.twitter.com/gnqISjRiPU
— Keiko (@Keiko_geo) June 23, 2020
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Google #EarthEngine tip 41: Test the #GEDI test. Due to so many requests, I can't ignore. But please remember, the dataset is not final... Anyway here is the very introduction of GEDI on EE (or my feedback to the amazing Google Earth Engine team, with many thanks!) pic.twitter.com/PKZRz2QGdV
— Keiko (@Keiko_geo) December 18, 2021
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Google #EarthEngine tip 29: Looking for timely #forestLoss #alert? Discover the hidden GLAD Alert dataset in #GoogleEarthEngine pic.twitter.com/azmrDD64jJ
— Keiko (@Keiko_geo) December 7, 2019
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Finally I got around to make a simple #GoogleEarthEngine app for #PalmOil and #Rubber plantations in Tanintharyi #Myanmnar - part of my PhD project: https://t.co/uYvtkDQ2UR Feel free to use the code: https://t.co/grWobbONed
— Keiko (@Keiko_geo) March 22, 2020
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>A #Jupyter notebook example for interactive mapping with #EarthEngine, #ipyleaflet, and #ipywidgets. Thanks to @Keiko_geo for the JS code. Try it with binder now: https://t.co/QERw7GKttX #Python @gartn001 @davidbrochart @SylvainCorlay @ProjectJupyter @googleearth @jstnbraaten https://t.co/wpFvWespYE pic.twitter.com/jDzuCU6sFp
— Qiusheng Wu (@giswqs) March 22, 2020
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Something different this time. "Interactive #maps on #python #JupyterNotebook" #folium #ipyleaflet What else is out there? Do you use #gmaps, #mapbox, #bokeh? what's your favourite? pic.twitter.com/M0ODlcwKdI
— Keiko (@Keiko_geo) March 7, 2020
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Google #EarthEngine tip 48: Unique values in Earth Engine - it's 'distinct()' #Lucas pic.twitter.com/bRTQ38pCBM
— @Keiko_geo@fediscience.org (@Keiko_geo) September 12, 2022
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Google #EarthEngine tip 36: Do you share your code with others? Do you talk to yourself when coding? These may be useful. You can force the user (or yourself) to read your message! alert, prompt, confirm #GoogleEarthEngine unofficial pic.twitter.com/E5xLqmVVVm
— Keiko (@Keiko_geo) October 4, 2020
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>I contributed to #GoogleEarthEngine community #tutorial - showing how to display and estimate forest area based on forest definitions using connectedPixelCount, reproject and atScale, for reporting, #REDD+ #FREL etc with any data source (example uses GFC) https://t.co/4mxGnvmBHd
— Keiko (@Keiko_geo) October 3, 2019
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Google #EarthEngine tip 35: Pythonise #GoogleEarthEngine with @giswqs's #geemap #ee_to_numpy. Go crazy with all the python packages like #pandas_profiling pic.twitter.com/gDgjLBoaDP
— Keiko (@Keiko_geo) August 2, 2020
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Google #EarthEngine tip 39: a quick and easy way to compare maps with sampling. #esri #modis #copernicus #landcover #GoogleEarthEngine unofficial. Apologies in advance - I didn't have a lot of time making this! So it was done in haste as you can probably see pic.twitter.com/QjXQFMjTjD
— Keiko (@Keiko_geo) June 28, 2021
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Google #EarthEngine tip 38: aside(), loop, client vs server (again), what's your favourite way of displaying an image collection? Here is an example of the last 14 days available #Maastricht melting #snow #GoogleEarthEngine unofficial pic.twitter.com/ia638KA0R2
— Keiko (@Keiko_geo) February 21, 2021
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Google #EarthEngine tip 15: I made an app that shows #deforestation in #protectedAreas (see tip 14) globally https://t.co/j828H2twqA Feel free to improve! code-> https://t.co/3Kch4hHnpM pic.twitter.com/ahm5U4Sh58
— Keiko (@Keiko_geo) June 3, 2019
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>I'm not sure who needs to know this but here you go.
— Keiko (@Keiko_geo) February 21, 2021
Google #EarthEngine tip 37: Data types, client vs server side functions. #GoogleEarthEngine unofficial pic.twitter.com/Pwv3ubIo4C
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Google #EarthEngine tip 51 with @RangeSpatialist: Do you like to create #EarthEngine assets but live in low-level fear of the day you’ll have to move or delete them? 😱 If so, you’ll love this tip, the geeadd CLI by @samapriyaroy pic.twitter.com/YBTMy3LztQ
— @Keiko_geo@fediscience.org (@Keiko_geo) October 18, 2022
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Google #EarthEngine tip 27: can't get enough maps? Use https://t.co/iSqkjalmaC function to add more maps in #console. Following up on the Wednesday's #EarthEngineVirtualMeetUp How would you use this? pic.twitter.com/S4owCi2bcm
— Keiko (@Keiko_geo) November 9, 2019
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Google #EarthEngine tip 19: Visualise #SAR without math on #EarthEngine. Use ee-palettes, made by @gena_d, Fedor and @jstnbraaten 🙏 #GEECommunity #Sentinel1 pic.twitter.com/XVT1d7CZ15
— Keiko (@Keiko_geo) July 3, 2019
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Google #EarthEngine tip 20: Use #plantation maps from @globalforests to visualise harvesting and exclude plantations from tree loss in a country https://t.co/Q20kz4qoDD https://t.co/C84pQ7v2yv pic.twitter.com/yW7Hiw0zdi
— Keiko (@Keiko_geo) July 11, 2019
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Google #EarthEngine tip 12: Use ui.Chart.image.histogram to see the trend and year of tree loss #hansen #treeloss #histogram #papua pic.twitter.com/UXzFk4kajs
— Keiko (@Keiko_geo) May 28, 2019