Map XML (within tilelive bridge)

<Map srs="+proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 +x_0=0.0 +y_0=0.0 +k=1.0 +units=m +nadgrids=@null +wktext +no_defs +over" buffer-size="256" base="/Users/mapsam/mapbox/tilelive-bridge/" maximum-extent="-20037508.34,-20037508.34,20037508.34,20037508.34">
  <Parameters>
    <Parameter name="bounds">-71.547459,42.834546,-71.534092,42.845709</Parameter>
    <Parameter name="center">-71.5407755,42.8401275,0</Parameter>
    <Parameter name="format">pbf</Parameter>

/**
 * A `LngLatBounds` object represents a geographical bounding box,
 * defined by its southwest and northeast points in longitude and latitude.
 *
 * If no arguments are provided to the constructor, a `null` bounding box is created.
 *
 * Note that any Mapbox GL method that accepts a `LngLatBounds` object as an argument or option
 * can also accept an `Array` of two [`LngLatLike`](#LngLatLike) constructs and will perform an implicit conversion.
 * This flexible type is documented as [`LngLatBoundsLike`](#LngLatBoundsLike).

There's a bug in npm that doesn't dedup Git URLs in package.json dependencies: npm/npm#3081

Node Mapnik dependents

• happytiff
  • mapnik-omnivore
• mapbox-geostats
• mapbox-map-metadata
  • tilelive-omnivore
  • tilelive-vector

The website is jekyll-based (which you know plenty about!). The resume page at mapsam.com/resume uses these key files:

1. _layouts/resume.html: this is template for the resume page. You'll notice a few different for loops on this page that look for jobs, cv items, and extras formally declared as "things" because I couldn't come up with a better word 😄
2. resume/index.md: this is the meat of the potato, where all of the "data" for the resume exist. Notice in the YAML (the syntax for the top part of the file between the --- triple dashes) there are sections for jobs

We are going to jump into Git, the version control system behind GitHub. Many projects, geospatial or otherwise, rely on git to track changes made to source code and documentation so people can work collaboratively without accidental code deletions.

1. Git vocabulary quest
2. GitHub and social coding
3. Introduction to the command line
4. Standard Git workflow
5. Maps & GitHub
6. Websites with GitHub pages (if time permits)