WorldbankAsDataframe
A wrapper for the World Bank's Development Indicators API. This API was initially developed and sponsored by Code for America, and later updated by Alexander Auritt.
Please see the World Bank's data [developer's page] for more info on the data sources.
Usage
require 'worldbank_as_dataframe'
WorldbankAsDataframe::Source.all.fetch
WorldbankAsDataframe::IncomeLevel..all.fetch
WorldbankAsDataframe::LendingType.all.fetch
WorldbankAsDataframe::Topic.all.fetch
WorldbankAsDataframe::Region.all.fetch
WorldbankAsDataframe::Country.all.fetch
WorldbankAsDataframe::Indicator.all.fetch
WorldbankAsDataframe::Indicator.featured
WorldbankAsDataframe::Topic.all.fetch
include WorldbankAsDataframe
@environment = Topic.find(6).fetch
@environment.id
@environment.name
@environment.note
@brazil = Country.find('br').fetch
@brazil = Country.find('bra').fetch
@brazil.name
@brazil.region
@brazil.capital
@brazil.lending_type
@tractors = Indicator.find('AG.AGR.TRAC.NO').fetch
@tractors.id
@tractors.name
@tractors.source
@results = WorldbankAsDataframe::Data.country('brazil').indicator('NY.GDP.MKTP.CD').dates('2000:2008').fetch
puts @results.first.name
@results.each {|d| puts d.date + ': $' + d.value }
WorldbankAsDataframe::Commodities.new.fetch
WorldbankAsDataframe::Commodities.new('crude').fetch
WorldbankAsDataframe::Commodities.new('gold').fetch(start: '1980-01-01', fin: '2000-12-31')
Contributing
In the spirit of free
software,
everyone is encouraged to help improve this project.
Here are some ways you can contribute:
- by using alpha, beta, and prerelease versions
- by reporting bugs
- by suggesting new features
- by writing or editing documentation
- by writing specifications
- by writing code (no patch is too small: fix typos, add comments,
clean up inconsistent whitespace)
- by refactoring code
- by resolving issues
- by reviewing patches
Submitting an Issue
We use the GitHub issue
tracker to track bugs and
features. Before submitting a bug report or feature request, check to
make sure it hasn't already
been submitted. You can indicate support for an existing issuse by
voting it up. When submitting a
bug report, please include a Gist that
includes a stack trace and any
details that may be necessary to reproduce the bug, including your gem
version, Ruby version, and
operating system. Ideally, a bug report should include a pull request
with failing specs.
Submitting a Pull Request
- Fork the project.
- Create a topic branch.
- Implement your feature or bug fix.
- Add documentation for your feature or bug fix.
- Run bundle exec rake doc:yard. If your changes are not 100%
documented, go back to step 4.
- Add specs for your feature or bug fix.
- Run bundle exec rake spec. If your changes are not 100%
covered, go back to step 6.
- Commit and push your changes.
- Submit a pull request. Please do not include changes to the gemspec,
version, or history file. (If you want to create your own version for
some reason, please do so in a separate commit.)
Copyright
Copyright (c) 2011 Code for America
See
LICENSE
for details.