tmcw

The compiled code - the listing of laws in their most-current state that we could simply call 'The Code', is actually constructed by contractors like Westlaw and LexisNexis, who maintain the technology to manage it and hire people to read PDF-formatted bills from the Council's website and manually edit sections of the law to keep it up to date.

As a result, this contractor keeps the only complete digital copy of the code.

That is, the DC government creates changesets, or diffs, of the code. The code is the

tmcw

Whole Earth Guide

I'm not sure about this; GIS really got burned from being both a 'science' and a 'product' from the beginning, and there are blurry lines between what I think is essential and what I don't know because I never do it and am not a GIS person. Anyway.

A No-Bullshit Intro to Maps and GIS

1. What Maps Are
2. Data
3. Information
4. Transformation

max-mapper

Your API does REST, but can it SLEEP?

SLEEP (Syncable Lightweight Event Emitting Persistence) is an emerging standard for distributed data sync using HTTP and JSON. A generalized version of CouchDB's much lauded built-in replication, SLEEP extends the REST architecture to define a way in which databases can offer syncable JSON APIs that foster open data innovation by allowing developers to replicate entire databases over the net.

---

SLEEP comes from the Apache CouchDB project which is now widely known for it's multi-master streaming HTTP + JSON replication. This is possible in part because of the CouchDB _changes feed, which is a particular API that lets you see if there have been any changes made to the database since last time you synchronized. CouchDB can efficiently implement the _changes feed because of one subtle difference between it and most other databases: it stores a history of all changes that happen to the database, including deletes.

If you synchronize data from a remote source and then the

josephspurrier

// Source: http://nicolasmerouze.com/guide-routers-golang/

// Package httprouterwrapper allows the use of http.HandlerFunc compatible funcs with julienschmidt/httprouter
package httprouterwrapper

import (
	"net/http"

	"github.com/gorilla/context"
	"github.com/julienschmidt/httprouter"

ryanflorence

################################################################################
# script: Base.coffee
# author: Ryan Florence <rpflorence@gmail.com>
# license: MIT-Style License
#
# A surprisingly useful base class for CoffeeScript.  Inspired by my old
# friend, MooTools Class. Provides default options, mixins, and custom events.
class Base

  defaults: {}

schacon

{
  "hands": [
    {
      "direction": [
        0.187837,
        0.097272,
        -0.976745
      ],
      "id": 3,
      "palmNormal": [

hugooliveirad

# Sync fork with original repository
#
# Requires an "upstream" remote, pointing to original repo
# e.g. `git remote add upstream git@github.com:user/repo.git`

alias git-sync-fork="git fetch upstream; git checkout master; git merge upstream/master"

inokappa

package main

import (
    "fmt"
    "log"
    "flag"
    "os"
    "os/exec"
    "encoding/json"
    "github.com/aws/aws-sdk-go/service/sfn"

shesek

##########
### Moved to https://github.com/shesek/callable-klass
##########


"use strict"
# without strict mode, `this` defaults to window, so `(this?obj)`
# would always return window.

callable = (ctor) ->

mbostock

license: gpl-3.0