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

lorawan-phy

v0.1.1

Published

Copy of the LoRaWAN PHY spec in machine-readable form

Downloads

5

Readme

LoRaWAN-PHY

Copy of the LoRaWAN PHY spec in machine-readable form

This repository contains JSON files that are copies of the PHY definitions of the LoRaWAN spec.

File structure

The files are structured like this:

<version>/<region>/<definition>/<lang>.json

and

<version>/<region>/<definition>.json, if it does not contain text that needs to be translated

where

  • version is the version of the definition, i.e. 1.1
  • region is the region ID of the definition
  • definition is a technical name of the definition
  • lang is an ISO 639-1 language code (every text field will be translated to that language)

there are additional files in the root directory:

  • regions.json contains a list of regions with their technical names along with humanized names. Since these names are not in a specific language, this file is not available in other languages

Supported regions

  • [x] EU 863-870
  • [ ] US 902-928
  • [x] China 779-787 (*)
  • [ ] EU 443
  • [x] Australia 915-928 (*)
  • [x] China 470-510 (*)
  • [x] Asia 923 (*)
  • [ ] South Korea 920-923
  • [ ] India 865-867
  • [x] Russia 864 (*)

*: Frequency Range and Datarate values only

Supported Languages

  • [x] English
  • [x] German
  • [ ] Your language here