Final Project Pre-production document
by Lucas Smith
Directory with Placeholders
Landing Page Mockup
Transitions & Interactions
- Nav arrows trigger removal of day’s points, addition of next day’s points
- Points enter sequentially with some amount of delay between points
- Point markers have static labels, rollover labels, or clickable popups with information
- Image markers trigger image lightbox
- Stats cards enter and exit gracefully (for geo-dependent stats)
- Stats increment gracefully
Javascript plug-ins / add-ons
jQuery for animations (or maybe just CSS)
leaflet.js for all mapping functions
leaflet.awesome-markers extension for category icons on markers
TBD leaflet extensions for functionality
Scope and production plan:
Milestones:
Creation of point geoJSON files - By 11/11
Creation of line geoJSON files - By 11/11
Date - Geofile(s) - Stats array - By 11/17
HTML / CSS framework - By 11/17
Javascript interaction - Week of 11/17 - 11/24
Polish - 11/24 - 12/5
[Reading] Analysis and Rationale for Leaflet.js
Leaflet is the javascript library I plan to use todo the heavy lifting of creating the slippy webmap at the core of my final project. I first encountered Leaflet in use in the Los Angeles Times’ Mapping L.A. and other map projects. It is an open-source library with an ecosystem of extensions. Some other alternatives would have been the Google Maps API, Mapbox.js, or others. I chose to use Leaflet because it is open source (in fitting with the ethos of this course) and because I have seen it employed in the wild in ways that make me think it’s robust enough for my project. I also have used it (kludgingly) in the past, so I have at least a basic concept of how it works.