Putting Complex Location Data on the Map in Drupal 8
summary
Case study of the Chicago Park District migration handling 600 parks and over 2,000 facility locations, using Migrate and Migrate Tools with a custom source plugin to pull an unsupported SOAP service and CSV supplements, running daily imports and updating existing nodes, geocoding addresses via Google (paid quota) into Geolocation Field and Geocoder, storing polylines for park boundaries, and exposing a custom REST resource that exactly matches the old app’s API — migration and feeds work under those constraints.
AI-written summary · about
chapters (9)
- 0:00Introduction and project overview
- 5:15Project requirements and challenges
- 11:20Importing dynamic and static data
- 17:51Geolocation and geocoding setup
- 25:24Daily imports and cron jobs
- 28:05Displaying location data in lists and maps
- 33:32Creating RESTful feeds for mobile apps
- 36:09Common migration and geocoding problems
- 43:04Q&A on maps and geolocation
related talks
31mCustom Drupal data migration: a Georgia GovHub story
24mGeo+Django: Geo beyond the Django
50m–Mom, can we have G**gle Maps? –We have G**gle Maps at home
24m"Good luck with that": Tag Teaming Civic Data
05mSimplifying access to OpenStreetMap data for urban planning
24mAdding Geo into your Django
22mMaps with Django (and PostGIS)
05mGetting to Know SimpleGeo