Page run by a Geospatial Engineer. Spatial Data, GIS & Remote Sensing | Exploring the intersection of ML & AI with spatial Tech 🌍 #GIS#RemoteSensing#AI#ML
Part 1 of a series on SQL for Geospatial Data:Mastering the Basics.
The basics will cover as much as the SQL cookbook covers thus tag along even for non spatial data
https://t.co/rHIDQS6iCE
#SpatialTidbits#100DaysOfSQL#geospatialanalysis#DataEngineer
This is GIM chatbot's name. GIM International is a blog that defines themselves as an independent and high-quality information source for everything the global geomatics industry has to offer, online and offline!
I found the name witty☺️
Mastering SQL for geospatial workflows: A quick guide to updating data
Use the Point-and-Shoot analogy for UPDATE statements, to handling MERGE (Upserts) and correlated subqueries, here is how to keep your spatial tables accurate.
#GIS#SQL#PostgreSQL#Geospatial
Today, we’re thrilled to announce the launch of Shapefile and 3D model import support on Google Earth. Plus, we’ve also added elevation profiles to the measure tool just for… good measure! https://t.co/vpIJA3HCv4
You’ve made it clear. You want to be able to bring more of your data and models to Google Earth’s real-world canvas. We're excited to take the next step in delivering on that promise with these new features:
🔶 Shapefiles (SHP): Render industry-standard geospatial data as performant, cloud-native layers.
💡 3D Models (GLB): Place custom architectural mock-ups, massings, and more in a visually rich context.
🗻 Elevation Profiles: View detailed terrain data in the measure tool you already know and love.
These new features are live now on Google Earth!
Diving into the world of geospatial data and SQL?
The latest blog post in the series on SQL for Geospatial Data: Mastering the Basics - INSERTING is a perfect starting point!
Learn how to insert your spatial data with ease. 🗺️ #GIS#SpatialSQL#Geospatial
The article link ⬇️
Whether you're doing spatial analysis in PostGIS or any geospatial-enabled database, these patterns will save you hours of debugging
Building from Part 1 & Part 2, perfect for leveling up your geospatial SQL skills & Scripts are available on Github
⬇️⬇️
https://t.co/uyZtzrR5Np
New in the SQL for Geospatial Data series! Mastering the Basics :Joins(Part 3) is live.
This one dives deep into the real-world headaches of working with multiple tables: countries (master) + polygons, lines, and points detail tables
https://t.co/NqUFWfDDz1
Practical solutions :
-Pre-aggregate with CTEs before joining
- Smart use of DISTINCT and set operations like EXCEPT to compare tables
- Handling NULLs cleanly with COALESCE in LEFT JOINs for reliable reporting
New on Spatial Tidbits: Master SQL Joins & PostGIS! 🌍
In this part, I break down:
- Activating the PostGIS extension
- Equi-joins vs. INTERSECT
- Using CTEs (Common Table Expressions) to keep your spatial logic clean and readable
#PostGIS#SQL#Geospatial
@NodeNBO It's really exciting to see land cover/land use change maps like this. It makes reality more tangible and easier to act on.
Satellite embeddings are changing remote sensing allowing retrieval of LU/LC insights faster and more easily than ever before
GitHub scripts → https://t.co/e0StSPaLMm
What’s your biggest headache when hunting data gaps in PostGIS?
→ NULLs in spatial joins?
→ Performance on large layers?
→ Chaining multiple joins?
Drop your thoughts below ⬇️
#GeoAI#DataEngineer#100DaysOfSQL
Struggling with data gaps in your geospatial layers?
Here’s how to find missing records gracefully using:
→ SET DIFFERENCE with EXCEPT (clean & NULL-safe)
→ ANTI-JOINS with NOT IN
#PostgreSQL#GIS#SQL