0.0
The project is in a healthy, maintained state
A client for using the IQAir_AirVisual API in Ruby. This is an unofficial project.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 2.1.0
~> 0.14.2
~> 13.1.0
~> 0.9.8
~> 3.19.1
~> 2.5.5
~> 5.21.2

Runtime

~> 0.16.0
~> 0.21.0
 Project Readme

IQAir_AirVisual

A client for the IQAir AirVisual API.

This is an unofficial project and still a work in progress (WIP) ... more to come soon.

For API documentation see: https://api-docs.iqair.com/?version=latest

Installation

Add this line to your application's Gemfile:

gem 'iqair_airvisual'

And then execute:

$ bundle

Or install it yourself as:

$ gem install iqair_airvisual

Usage

  require 'iqair_airvisual'
  client  = IQAir_AirVisual::Client.new(api_key: 'API key from website')

  client.countries()

Endpoints

Community

  • Countries
  • States
  • Cities
  • Nearest City (IP Geo-locate)
  • Nearest City (GPS Coordinates)
  • Nearest City (Name)

Other endpoints have not been implemented.

Development

After checking out the repo, run bin/setup to install dependencies. Then, run rake test to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.

Tests

To run tests execute:

$ rake test

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/trex22/iqair_airvisual. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.

License

The gem is available as open source under the terms of the MIT License.

Code of Conduct

Everyone interacting in the IQAir_AirVisual: project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.