I just released a gem to help interactions with fusion tables.
It’s on github, or you can install with a straight:
gem install fusion_tables
The main rationale behind making this gem was to make it easy to upload geospatial data to make quick exploratory maps of large datasets. As an example, here are the results of sampling georeferenced tweets from the live twitter streaming API around several major cities (click the points!):
Tokyo
London
New York
Fusion Tables also lets you generate live visualisation from the same data you’re displaying in the map. Here’s a comparison of the counts in all the cities I sampled:
Title says it all really. I finally got tired of importing the ipinfodb into postgreSQL via CSV (the SQL they provide on their site targets MySQL), and have made a dump available on S3. Knock yourself out.
I love DHH’s Tolk. For those that don’t know, it’s a rails engine that makes translating your base locale in your Rails app really easy . While I was translating, I was getting bored with doing simple things like translating the days of the week and so on, and sometimes needed help with more complex sentences. This is my fork of Tolk that autotranslates your translation string with google translate to give you a sensible starting point rather than a white box.
The vanilla method of storing view translations in an i18n’d Rails project is to maintain a huge locale yaml file. A step forwards is to maintain many yaml files split into folders mirroring your controller or view structure. Splitting is better for maintenance, however many tools and services, like DHH’s Tolk which can help with the actual translation of your site currently rely on your locale being in one place.
I wanted both. I’d like to maintain my base locale files in a nice split structure, whilst at the same time being able to use tools like Tolk to maintain my translations.
With your base locales arranged as described by the Rails Guides simply use the following rake task to generate an aggregated locale YAML file. To ensure no keys are overwritten, be sure to maintain your translations in their own namespaces.
There are times we want our Rails apps to have some sort of spatial capability. Recording lat long point locations and displaying them in a google map is fine, but increasingly we want to do more with our spatial data.
We want to be able to import data from a wide range of existing spatial [...]
