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

ocr-parser

v0.2.5

Published

Fast and efficient DOM-less OCR parser for use in browsers (including Workers) and Node

Downloads

20

Readme

ocr-parser

This library provides a simple interface to parse OCR data from a stream, buffer or string. It does not rely on any DOM APIs and can therefore be used in contexts where there is no built-in support for XML parsing, most notabily in Web Workers and Service Workers.

Currently the library supports hOCR and ALTO OCR markup.

Usage

Before OCR markup can be parsed, the XML parser has to be initialized. The library uses sax-wasm under the hood, which needs to be initialized with its WASM code before it can be used. By default, the WASM will be loaded from unpkg.com, but you can also provide a custom callback to the initialize function to load the WASM from a different source. Make sure that the WASM matches the versio of sax-wasm used by this library (currently 2.2.4).

import { initialize as initializeXmlParser } from 'ocr-parser';

// Load from unpkg.com
await initializeXmlParser();

// Load from custom source (e.g. from base64-encoded constant)
await initializeXmlParser(() => Promise.resolve(WASM_BLOB));

Once the parser has been initialized, call parseOcrPages or any of the format-specific functons (parseAltoPages, parseHocrPages) with your markup to retrieve an asynchronous generator over all the pages in the markup.

import { parseOcrPages } from 'ocr-parser';

for await (const page of parseOcrPages(markup, 'hocr')) {
  // Do something with the page
  console.log(page);
}

Data Structures

The markup is parsed into a simple hierarchical data structure:

OcrPage
└── OcrBlock
    └── OcrParagraph
        └── OcrLine
            ├── OcrWord
            └── string

The OcrBlock and OcrParagraph levels are only present if they are encoded in the markup. Every element has getters for any of the lower levels, so yo can simply access OcrPage#words to get a flat list of all words on the page. string children of OcrLine elements are 'stray' text nodes (including whitespace) that are not explicitely encoded as words (and thus have no associated bounding box).