Vague ideas omnibus

[lfborjas]

• Move transit calculation to postgres -- could allow usage of the distance operator (given a GiST index), maybe some fancier queries, too? (to use the distance operator, we need a compatible data type, e.g.

select point(1,0) <-> point(2.2,0);
      ?column?      
--------------------
 1.2000000000000002)

-- could be part of introducing a DB for optional persistence of charts, as per #38 -- which would also require a good effects system, as per #54

• use geocode.city as an algolia replacement (addresses Replace Algolia Places #31)
• introduce a purescript-based "experiments" page, for more dynamic features like switching up house systems, or composite charts; also allows to provide a bona-fide "api"
• update retrograde glyph, and chart graphics to render the name of a house, vs. just the number
• fix collisions in rendering