jcblw / geode Goto Github PK

View Code? Open in Web Editor NEW

57.0 10.0 19.0 55 KB

:earth_americas: wrapper for www.geonames.org written in javascript as a node module

JavaScript 100.00%

geonames api

geode's Introduction

Geode

Locations API in node from www.geonames.org

Install

npm install geode

Use

You will need an account ~ its free (signup).

//include
var geo = new geode('username', {language: 'en', countryCode : 'US'})

geo.search({name :'Riverside'}, function(err, results){
	console.log([err, results])
})

Demo

Here is a simple Express App throwing up an API. (see demo).

The express code is just

var api = new Geode('username', {countryCode: "US", language: 'en'});

app.get('/:collection.:format', function(req, res){
  if(req.params.collection && req.params.format){
    api[req.params.collection](req.query, function(err, collection){
      res[req.params.format]({status : 200, results : collection});
    });
  }else{
    res.send('404');
  }
})

Testing

Make sure to install the development dependecies npm install --dev and then run.

USER=yourusername npm test

geode's People

Contributors

Stargazers

Watchers

Forkers

clixsoftware peter-henning ianscrivener jfuehner wprater ajmalsaid petrkotek kenany estephany sans0r pbihler shailendra9 erichedstrom appsflare landsurveyorsunited thegoat530 pmelopereira palmerabollo teebo

geode's Issues

Single Quote Consistency

in the spec file for testing there is still alot of double quotes, lets switch that over to be consistent.

An in-range update of request is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.84.0 of request was just published.

Branch	Build failing 🚨
Dependency	request
Current Version	2.83.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

request is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 6 commits.

d77c839 Update changelog
4b46a13 2.84.0
0b807c6 Merge pull request #2793 from dvishniakov/2792-oauth_body_hash
cfd2307 Update hawk to 7.0.7 (#2880)
efeaf00 Fixed calculation of oauth_body_hash, issue #2792
253c5e5 2.83.1

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

npm publish new version

Latest version published to npm is 0.0.2, which doesn't work when no local is passed

add to travis.ci

we already have the test setup this should be super simple to setup.

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

Added the new Node.js version to your .travis.yml
The engines config in 1 of your package.json files was too ambiguous to be updated automatically

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖