drewbo

// filters the initial geojson "xView_train.geojson" into separate files matching each training tif
// use like `node index.js`

const fs = require('fs')
const _ = require('lodash')
const gs = require('geojson-stream')
const through2 = require('through2')
const log = require('single-line-log').stdout

const IMAGES = 3000

drewbo

var sniff = require('mapbox-file-sniff')

drewbo

var sniff = require('mapbox-file-sniff')

drewbo

var union = require('turf-union')

var feature1 = {
  "type": "Feature",
  "geometry": {
    "type": "Polygon",
    "coordinates": 
      [
        [
          [

drewbo

Standouts

• Chris Natali: Maybe more R focused but does have experience across the board + OSM + "domain knowledge of the power sector"
• Eleonore Mayola: Biomedical research background, self-guided GIS + code experience, has hit a lot of pieces, good communicator
• João Figueiredo: Good experience across the board
• Vincent Saragos: Has hit lots of different pieces + uses our tools + remote sensing experience.

Got back to me quickly/often, on the fence otherwise

• Mark Delcambre: Code for DC, less experience but self-learner

drewbo

Existing Site

• What type of feedback have you received on the original site? What goals did it accomplish (or not)?
• Do you have any analytics from the original site?
• Are there any specific policy actions, publications, etc. that took place as a result of the original site? Is this what you are/were looking to accomplish?
• What were the biggest blockers for the original site achieving its goals?

Phase 2

• What type of users are you expecting to visit the site? What do you want them to accomplish or take away from the visit?

drewbo

Existing Site

• What type of feedback have you received on the original site? What goals did it accomplish (or not)?
• Do you have any analytics from the original site?
• Are there any specific policy actions, publications, etc. that took place as a result of the original site? Is this what you are/were looking to accomplish?

drewbo

Accesible via the API and the front-end (maps tab)

For people who want to do their own analysis

Allow for all raw file downloading (let's just use the tarballs from google for easy "one-click" downloading)

they don't need processed tiffs because they can perform the analysis how they want

For people who want another form of media (for printing/static embed/etc.)

drewbo

Allow for all raw file downloading (let's just use the tarballs from google unless we think it's important to allow for single band downloads)

drewbo

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console