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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@opengeoweb/soundings

v14.3.0

Published

GeoWeb soundings library for the opengeoweb project

Readme

Soundings

This library was generated with Nx.

Configuration for soundings EDR services

The sources that are available in the soundings sources menu are specified in the initialPresets.json file.

There, you can specify the required details for each source under the soundingsCollections property:

"soundingsCollections": [
      {
        "name": "Harmonie scandinavia hybrid",
        "id": "harmonie_scandinavia_hybrid",
        "url": "https://opendata.fmi.fi/edr",
        "description": "MEPS/vertical coordinate model level",
        "parameterMappings": {
          "temperature": "temperature",
          "windDirection": "winddirection",
          "windSpeed": "windspeedms",
          "pressure": "pressure",
          "dewpoint": "dewpoint"
        }
      },
      {
        "name": "Harmonie scandinavia pressure",
        "id": "harmonie_scandinavia_pressure",
        "url": "https://opendata.fmi.fi/edr",
        "description": "MEPS/vertical coordinate pressure",
        "parameterMappings": {
          "temperature": "temperature",
          "windDirection": "winddirection",
          "windSpeed": "windspeedms",
          "pressure": "pressure",
          "dewpoint": "dewpoint"
        }
      }
]

Each source should have a name, id, source url and description and include parameter mappings telling the soundings API which EDR parameters to assign to which physical property.

The following mappings are needed:

  • pressure
  • temperature
  • dewpoint (OR specificHumidity OR relativeHumidity, from which we can derive dewpoint in case it is not available)
  • (windSpeed AND windDirection) OR (windU AND windV), either one of the two can be used

If your EDR parameter is called windSpeedInMS the mapping would be as follows: windSpeed: windSpeedInMS

Running unit tests

Run nx test soundings to execute the unit tests via Jest.