Didn’t see that coming (and checked the date three times). From Google:
Today, we’re thrilled to announce the launch of Shapefile and 3D model import support on Google Earth. (…)
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. (…)
Comments … ugh… vary:
“Great to see Google Earth is moving in this direction but shapefiles in 2026? Interesting choice” 😅
“Amazing …!” 🤩
“In 2026 you should ban loading shapefiles instead of allowing it” 🤣
“OMG - an announcement for Shapefile Support in 2026? Seriously?”
“SHP still feels a bit legacy, but native support in Google Earth is a solid step for interoperability. Would be great to see equal focus on modern, cloud-native formats (GeoParquet, FlatGeobuf etc.).”
Sure, it feels odd. And it may be similar to adding an Excel import to a fancy cloud DWH – that is, like building an on-ramp for the unadorned data of millions of users.