npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

cdojs

v1.4.0

Published

JS wrapper for NCEI's Climate Data Online API

Downloads

27

Readme

cdojs

Node+browser package for Climate Data Online (CDO) API

Installation

$ npm install --save cdojs

Usage+examples

cdojs should support all params and endpoints found on NCEI/NCDC's documentation for the CDO API.

Init the client:

var CDO = require('cdojs')
var client = new CDO('mytoken')

To retrieve the first page of queryable datasets, your code might look something like this:

client
  .datasets()
  .then(console.log)

Retrieve all 56 kinds of queryable temperature measurements, 25 per page (montly mean, daily minimum/maximum, etc):

client.all('datatypes', {datacategoryid: 'TEMP'}, console.log) // calls console.log once per page

Alternatively, if you want to page manually:

function getTempTypes (params) {
  if (!params) params = {datacategoryid: 'TEMP'}
  return client
    .datatypes(params)
    .then(page => (
      page.results.length
        ? getTempTypes(CDO.paramsForNextPage(params)).then(pages => [page, ...pages])
        : [page]
    ))
}
getTempTypes().then(console.log)

Typical usage: fetch all stations for ZIP code, then fetch daily temperatures between 2000 and 2001 for the first returned station

// init client with some default query params
var client = new CDO('mytoken', {params: { // set some default params
  datasetid: 'GHCND', // "Daily Summaries"
  datatypeid: 'TOBS', // "Temperature at the time of observation", one of the TEMP datatypes returned by the above query
  startdate: '2000-01-01',
  enddate: '2001-01-01'
}})

// fetch all stations for ZIP code
var results = []
client
  .stations({locationid: 'ZIP:00002'}) // "Yukon Flats Nat Wildlife, AK 00002". Not all ZIPs have a station
  .then(stations => (
    client.all('data', {stationid: stations.results[0].id}, page => {
      results = results.concat(page.results)
      return false // return true to stop paging
    })
  ))
  .then(() => { console.log(results) })