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 🙏

© 2026 – Pkg Stats / Ryan Hefner

grads-queryable

v1.0.0

Published

Queryable instance of grads data for predictors and stuff

Downloads

8

Readme

grads-queryable

This is a queryable instance of my grads software. The intension is to make flight path predictions easier for you (and for NOAA) by reducing the amount of weather data requests you'll need to make for ambitious (where bounding box for data is unknown) requests. It's focused around wind data, but could be used for other values if needed. (Maybe waves? Who knows. That'd be cool)

This is not flight path prediction software on its own - check out fnstraj2 for that.

How it works

  1. You initialize grads-queryable with your launch or starting coordinates
var gradsQ = new GradsQ( lat, lon, alt, options )
  1. grads-queryable makes a wide-area request around your launch location to get a rough idea of what wind (or whatever value you're looking up) is looking like.
  2. grads-queryable makes a quick estimate of flight distance based on the averages in that last request, then sets the bounding box
  3. grads-queryable grabs the wind values for a bounding box between your launch location and the estimated flight distance. All values are saved to a flat object and saved to redis.
  4. You can start your prediction code at this point, and you can query your instance of grads-queryable with the next moment of your prediction.
gradsQ.query( timeOffset, lat, lon, alt )
  1. grads-queryable searches the previously stored data for your location. If the location is unavailable, it makes a new grads request for data for your new location.
  2. Tada! You just made a flight path prediction or whatever you were trying to do.

Instructions

  1. npm i --save grads grads-queryable
  2. Initialize in your code:
var GradsQ = require('grads-queryable');

// Your launch or starting location
var gradsQ = new GradsQ( lat, lon, alt );

// Since the initializer needs to make some requests, you'll need to put a .ready()
gradsQ.ready(function() {

    var flightPath = [];

    // Linear vertical climb to 8000m
    // Lets say you're starting on the ground
    // Your max altitude is 8000m
    // In each `moment` of flight, you ascend 5m
    for ( var alt = 0; alt < 8000; alt + 60; ) {

        // Lets say each `moment` represents 1 minute
        // That means our climb rate is 1m/s.
        var timeOffset = 1;

        var myValues = gradsQ.query( timeOffset, lat, lon, alt );

        // Calculate new location etc etc            

        flightPath.push({
            alt: x,
            lat: y,
            lon: z
        });
    }

    // Make a cool map with flightPath

    // :D
});

Options / Defaults

  • This currently uses the GFS model.

Conventions

  • Times are stored as minutes
  • Distances are stored as meters