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

klv-parser-misb

v2.0.5

Published

This package can be used to parse binary data following the MISB0601.17 standard.

Downloads

62

Readme

Buymeacoffee

This package can be used to parse binary data following the MISB0601.17 standard. Usage:

const KLV = require('klv-parser-misb');
const fs = require('fs');

// Configs useful for debugging
const options = {
  removeUndefinedKeys: true,
  logKeyValues: false,
  logErrors: false,
}

// Parse a whole file
fs.readFile('klv-file.klv', (err, file) => {
    let KLVdata = KLV.parseKLVfile(file, options);
    let packets = KLVdata.packets;
    let nDropped = KLVdata.nDropped;
    
    // Do something with the data...
}

// Or use streams
let filestream = fs.createReadStream('klv-file.klv');
let parseStream = KLV.createParseStream(options);
filestream.pipe(parseStream);
parseStream.pipe(/* Somewhere else */);

You can either use KLV.parseKLVfile to parse a binary file or KLV.createParseStream to setup a streaming chain. The binary KLV file's packets are parsed into easily manageable JS objects.

This package focuses mostly on the geographic values. As a consequence, some fields are not supported, mostly consisting of sets and weird data structures. The unsupported fields are:

  • Tag 48: Security Local Metadata Set
  • Tag 60: Weapon Load
  • Tag 61: Weapon Fired
  • Tag 66: Target Location Covariance Matrix (Deprecated in standard)
  • Tag 73: RVT Local Data Set
  • Tag 74: VMTI Local Data Set
  • Tag 81: Image Horizon Pixel Pack
  • Tag 94: MIIS Core Identifier
  • Tag 95: SAR Motion Imagery Local Set
  • Tag 97: Range Image Local Set
  • Tag 98: Geo-Registration Local Set
  • Tag 99: Composite Imaging Local Set
  • Tag 100: Segment Local Set
  • Tag 101: Amend Local Set
  • Tag 102: SDCC-FLP
  • Tag 115: Control Command
  • Tag 116: Control Command Verification List
  • Tag 121: Active Wavelength List
  • Tag 122: Country Codes
  • Tag 127: Sensor Frame Rate Pack
  • Tag 128: Wavelengths List
  • Tag 130: Airbase Locations
  • Tag 138: Payload List
  • Tag 139: Active Payloads
  • Tag 140: Weapons Stores
  • Tag 141: Waypoint List
  • Tag 142: View Domain

If you're in the business of using these fields your programming is probably advanced enough to implement them yourself. The cases are already defined in the source code, albeit without functionality. If you do implement these I would appreciate a pull request on github :)

Some fields are untested for real life situations as I don't have any data to test them on. If you come across any wrongly parsed values, please raise an issue or create a pull request on github.