MySQL 5.7, 8.0 and MongoDB: Geospatial Introduction
summary
Quick, concrete takeaways: MySQL 5.7 adds InnoDB R‑Tree spatial indexes and ST_ functions which cut a sample query from ~60 seconds and ~33,000 handler ops to under 0.01s and 4 ops, a demo loads ~5,300 GPX points from a 200‑mile drive and maps distances per county, and MySQL 8.0 adds geographic SRID support so ST_Distance works on the globe instead of a flat plane. MongoDB uses 2dsphere indexes and $near (geoNear) queries that were 0.17s vs MySQL 0.21s* for a simple radius lookup; OpenStreetMap data converts and loads into both systems.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 0:35Overview
- 0:58Geo Data
- 1:20Common Questions
- 1:50Other Industries
- 2:15Hammer Sign Formula
- 4:24Traditional Zip Code Table
- 5:45Bounding Box
- 6:38Spatial Data Types
- 7:34Spatial Table Structure
- 8:10Spatial Objects
- 9:56Polygons
- 10:25StContains
- 12:37Indexes
- 13:06No Spatial Key
- 13:47New Spatial Functions
- 15:40Demo
- 20:34Open Street Map
- 21:25Point Table
- 22:35Treat Envelope
- 25:02MongoDB
- 27:06Export JSON to MySQL
- 27:32Load JSON into MySQL
- 27:57Create an index
- 28:24Create an index on lines
- 29:23Remove bad data
- 30:09Dynamic bounding boxes
