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

extended-nmea

v2.1.3

Published

A TypeScript library for parsing NMEA0183-like sentences with support for custom and proprietary sentences.

Downloads

198

Readme

extended-nmea

An extensible TypeScript library for parsing NMEA0183-like sentences.

This library implements the NMEA0183 standard as described in the document under docs/NMEA0183.pdf and provides type-safe classes and interfaces for parsing raw text into useful objects.

Extensibility means you can add your own custom/proprietary sentences using this library in your project.


Usage

Simply import the decoder and use it to decode incoming data.

import {Decoder} from "extended-nmea";

const sentence = Decoder.decode("$--ROT,0.02,A*14\r\n");

console.log(sentence.valid);    // output: true
console.log(sentence.type);     // output: "talker"

Every codec can have different getters:

import {ROT} from "extended-nmea";

const rotSentence = Decoder.decode("$--ROT,0.02,A*14\r\n") as ROT;

console.log(rotSentence.sentenceId);    // output: "ROT"
console.log(rotSentence.rateOfTurn);    // output: 0.02
console.log(rotSentence.statusValid);   // output: true

As per NMEA0183 standard, query sentences and proprietary sentence decoding is also supported:

// you can use `decode`, `decodeTalker`, `decodeQuery´ or `decodeProprietary` to get different interfaces.
const querySentence = Decoder.decodeQuery("$GPECQ,RMC\r\n");

console.log(querySentence.talkerId);    // output: "GP"
console.log(querySentence.listenerId);  // output: "EC"
console.log(querySentence.mnemonic);    // output: "RMC"

import {ROT} from "extended-nmea";

// you can also use a generic parameter, if you know whether you are dealing with a talker or a proprietary sentence
const genericSentence = Decoder.decodeTalker<ROT>("$--ROT,0.03,A*15\r\n");

console.log(genericSentence.rateOfTurn);    // output: 0.03
console.log(genericSentence.statusValid);   // output: true

To support proprietary sentences and have the ability to add custom ones, you can register them before decoding:

import {ProprietarySentence, RawNmeaSentence} from "extended-nmea";

// you can also extend TalkerSentence to add a custom sentence in the form of "$AABBB,xxx*CC", where BBB is your custom id.
class MyCustomSentence extends ProprietarySentence {
	public static readonly ManufacturerId = "ABC";

	constructor(data: RawNmeaSentence) {
		super(data, MyCustomSentence.ManufacturerId);
	}
	
	public get firstField(): string {
		return this.fields[1];
	}
}

// use `Decoder.register` for talker sentences
Decoder.registerProprietary(MyCustomSentence.ManufacturerId, MyCustomSentence);

const myCustomSentence = Decoder.decode("$PABC,123\r\n");

console.log(myCustomSentence.manufacturerId); // output: "ABC"
console.log(myCustomSentence.type); // output: "proprietary"
console.log(myCustomSentence.firstField); // output: "123"

You can also remove previously registered (or even stock) sentences using the unregister methods:

Decoder.unregisterProprietary("ABC");
Decoder.unregister("RMC");

Development

Any contribution, be it an issue to request features or report bugs, or a pull request, is greatly appreciated.

Setup

Local development can be set up by first cloning this repository:

$ git clone https://github.com/ricardoboss/extended-nmea

Then installing the dependencies using yarn:

$ yarn install

Testing

For testing, this library uses mocha. If you want to run tests, use yarn run test. In case you want to watch for file changes and re-run all tests, execute yarn run test:watch and leave it running. It will then show any failed tests while you are working the code.

Every pull request will automatically be tested using GitHub actions. They will also only be accepted, if all existing tests succeed (or have been adjusted depending on what the PR changes). Please also add new tests in case you add functionality.


Motivation

The motivation behind this project arose when I wanted to create a web application, which parsed and then visualized data provided in the NMEA0183 standard. After looking into some existing libraries, I forked jamesp/node-nmea and started tinkering with the code and even opened a pull request.

When I began my original project, I wanted to harness the power of type safety from TypeScript. Since node-nmea was not type safe, it didn't play well with the rest of the code. That's why I created this version of my fork, which is a completely new implementation with the same idea, just with TypeScript support.

In the end, I created ricardoboss/vessel-state, which uses this library to update a Vuex store's state, representing a vessel with the latest information available.


License

This project is licensed under the MIT license. Please review the LICENSE file for more information.