background preloader

Tools

Facebook Twitter

Query Language. Find Latitude and Longitude. Fusion Tables - Gather, visualize, and share data tables online. Bust your data out of its silo! Get more from data with Fusion Tables. Fusion Tables is an experimental data visualization web application to gather, visualize, and share data tables. Visualize bigger table data online Filter and summarize across hundreds of thousands of rows. Then try a chart, map, network graph, or custom layout and embed or share it. Collaborate! All your data organization is automatically saved and stored in Google Drive.

Two tables are better than one! Merge two or three tables to generate a single visualization that includes both sets of data. Make a map in minutes Host data online - and stay in control Viewers located anywhere can produce charts or maps from it. Visualize bigger table data online Import your own data Upload data tables from spreadsheets or CSV files, even KML. Visualize it instantly See the data on a map or as a chart immediately.

See how journalists and nonprofits around the world use Fusion Tables Two tables are better than one! Make a map in minutes. A Brief Introduction to REST. You may or may not be aware that there is debate going on about the “right” way to implement heterogeneous application-to-application communication: While the current mainstream clearly focuses on web services based on SOAP, WSDL and the WS-* specification universe, a small, but very vocal minority claims there’s a better way: REST, short for REpresentational State Transfer. In this article, I will try to provide a pragmatic introduction to REST and RESTful HTTP application integration without digressing into this debate. I will go into more detail while explaining those aspects that, in my experience, cause the most discussion when someone is exposed to this approach for the first time.

Key REST principles Most introductions to REST start with the formal definition and background. Give every “thing” an ID I’m using the term “thing” here instead of the formally correct “resource” because this is such a simple principle that it shouldn’t be hidden behind terminology. Link things together. Editing pipe.