Stronger App Architecture Using Maps
summary
Shows a concrete stack and what actually worked: an Ember app (Zola) rendering lots of civic layers with GeoJSON for small sets and vector tiles for fast styling, using an Ember binding to mapbox-gl; roughly 1,000 daily users and monthly data updates. Describes running Carto-like tile services in-house then switching to hosted, keeping layer state in the URL, stubbing the map instance for tests, and preferring SVG (Leaflet) for accessibility over raw WebGL canvas.
AI-written summary · about
chapters (22)
- 0:00Start
- 1:29Who Am I
- 3:14Plan for the Future of New York City
- 3:56Nyc Planning Labs
- 6:52Urban Planners
- 9:20History of Maps
- 12:54What Is a Web Map
- 13:20Data Layers
- 13:49Recent Technologies
- 14:14Mapquest Launched Its Web Service
- 15:02Google Maps
- 16:03Image Based Tiles Have Limitations
- 17:48How Are Tiles Made
- 18:00Map Projection
- 19:36Geo Json
- 23:34Netflix Ability
- 24:33Case Study
- 25:22Outer Map Box Component
- 28:02Anatomy of the Map Component
- 28:21Draft of the Map Component
- 32:31How Do You Set Up a Map Dependency Injection
- 38:16Augmenting a Message through Maps
related talks
17mBoosting Map Performance with Mapbox and Flutter
01h 34mBuild a Web Map with Open Source Tools
46mDev Stories: Show & Tell
32m"A Developer's Guide to Open Source Web Mapping Libraries"
15mMaking maps work on mobile
27mCartography on the Web
51mWays to get data into Mapbox maps
49mWhen maps are mission-critical: How Watch Duty powers wildfire safety with Mapbox