How did you enjoy the UC - have any takeaways from it? I only attended the virtual 2021 UC. The workshops I've seen come out of it are invaluable... well, they are probably tangibly valuable to ESRI given they are word-of-mouth ads... other than those, they seem well-made and exciting on the whole. I'm a single part of GIS community, but I was described as wider at my latest doctor visit - so that's gotta count for something. On a surface level, it's a great entry point for GIS. Maybe even a good learning tool for younger audiences or laymen. The customizability is lacking, which can lead more interested users down a loooooooong rabbit hole (that in turn would lead more invested users to ESRI - or worse, opensource). To the creator's point, that's kind of the appeal behind Felt tho, no? Simplicity. Willing to bet there's a fair amount of opensource tech running on the back end. Exciting to see where it goes. Might be a nice tool to send to my brother for easy learning of the basics. My brother and I have had an on-going discussion for the past few years on how cool he believes the GIS work can be based on what I've worked on, plus where there's an theoretically small leap from his skillset (SQL/Datamining) to mine (Cartography). Up until recently, my limited purview - not connecting the dots between PostGIS and our discussions - had me saying: "Take a GIS certificate course I guess?" Which would, what, qualify his "GIS" skills for an imagery analyst at best? With a laaaaaaaaaaaaaarge gap between "I know what vector and raster data are (smiley face)" and "I know how to tinker on the dev-end of a WCS," the question has been whether it’s worth it for an early-30s professional with a masters degree to go back to rudimentary technical schooling for the bare-bones basics of anther profession entirely. Enter: PostGIS. Taking the time off from work to dive deeper into SQL since the progression of learning seems to be “GIS -> PostgreSQL -> PostGIS.” And those are probably medium-level learning curves at best. My hope is I can use this time to learn via Coursera/Udemy, then apply the learnings to some form of passion projects. Either sustainable energy or reviving some of my grad-school projects but taking a different approach. Don’t know how long this will take, but ideally it will be something to showcase to the next employer(s) long term. Visual warning if you’re on a browser: see second graph. This has been on my mind since reading it (grain of salt given for Medium article). Would venture that me applying my GIS knowledge to spatial SQL vs. my brother applying his SQL knowledge to spatial SQL would net him higher pay/title/etc… curious to see how it will turn out.
As a whole the GIS world is...surprisingly shallow. There are some technical niches for sure, but compared to what I've seen in other domains of engineering, one can get incredibly fast to a point where one can do 80% of all GIS work. Really, a basic GIS course combined with a modicum of data-wrangling chops and Google skills can get you very far. To speak from personal experience; I had 2 mandatory GIS courses at uni, took one Python+GIS elective, and learned enough on the job the past 4 years (all of ArcGIS Online + PostGIS + ArcPy) that I can prolly apply for most senior GIS jobs out there. A lot of GIS work is just about getting the right input into the right GIS tool(s) and ✨presenting✨the result. I know people who have done nothing more than "load data into GIS, apply pre-made tools, visualize" for decades. Which for sure is reflected to a degree in salary. A shockingly small niche (over here at least) is the people who are good at writing queries and half-decent at GIS. PostGIS legitimately can replace 95% of the individual pre-made tools QGIS and ArcGIS has to offer. You can do much more complex things much faster. My largest project the past year ended up being 2300 lines of PostGIS/SQL code I wrote on my own. The first 30% is just data prep written in code - "make sure I properly join tables A thru G in the data type I want it to be without ever having to touch Field Mappings ever again". The rest is a bunch of clever geo-joins and a bunch of not clever regular joins of tables and features. Nothing special to anyone who already knows how to handle semi-long SQL queries; PostGIS is really just one new column type and a bunch of functions to do stuff with it. For many in the GIS world, once they start seeing the benefit of PostGIS, they often don't go back. It really is objectively better to get shit done. Which means that a lot of skilled GIS people have made a lot of PostGIS code that only a small subset of GIS people can work with. Which means that if you're the kind of person whose brain can be wrapped around the core concepts of SQL and GIS, it's an easy ticket into advanced GIS work. For me it took a 2-day (intense) course plus a week of actually working with it under a deadline to go from "I can do most anything I want with Arc" to "no wait actually this PostGIS thing rawks". YMMV - I know in the US, the GIS world is much more imagery heavy, and imagery does not gell well with PG. But I can get so* much more work done these days by doing 95% of it in PG from the QGIS Database Manager that it's an easy recommendation.