Based on 3 Users
Grade distributions are collected using data from the UCLA Registrar’s Office.
Sorry, no enrollment data is available.
Technically I took GEOG 415, which is similar to the one listed here. I didn't have what should have been a predecessor under my belt, GEOG 411 Spatial Imaging, so a chunk of the content was hard for me to understand. I think this is the only course that uses Google Earth Engine, which I loved. It's a lot of coding, so brush up on your coding and also on understanding new syntax - that was the key part of GEE, knowing how to find and understand the weird syntax in this program. The content itself was interesting, the workload was harder than I anticipated, but what was most helpful was attending office hours and asking for help! Bo was a very responsive professor and helpful with my questions at all hours of the day. Having discussions with him on the content was incredibly helpful in understanding what we were doing each week. He also offers plenty of opportunities for extra credit.
Cool but hard class overall, looking forward to exploring GEE further in the future.
Bo is a very involved professor. He genuinely wants the best for his students, and expects a lot. If you put in the work and ask questions when you're struggling, this will be a very rewarding class (it looks good on a resume too). Definitely don't come in expecting a straightforward extension of ENVI/ArcMap based GIS classes you've taken previously; be ready to learn a whole new program.
For a first-time class, during a pandemic no less, it turned out pretty good. There were a few hiccups, including a lack of student participation and an extremely rushed first couple weeks (if you don't have coding experience, you might have a hard time. However, Bo is really helpful during office hours if you ask for help). Ultimately, because this course is so packed with material, I learned a lot. But you definitely have to put in the time, especially if you don't know any coding.