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

qa-extractor

v1.1.0

Published

Extract given values from QA Tiles

Downloads

7

Readme

qa-extractor

Coverage Status Circle CI David DM

Extract given features from a OSM-QA-Tiles (https://osmlab.github.io/osm-qa-tiles/)

Usage Data

./index.js --input=<FILE.mbtiles> --output=<File.mbtiles> --selector=""

Selector Options

and

and is the default relation between terms. It is accomplished simply by specifying the next term required.

Example: building highway (building AND highway)

and not

As with and it is accomplished by specifying the next term. not is accomplished by preceding the term with a -. There should be no space between the not operation (-) and the next term.

Example: building highway (building AND NOT highway)

or

OR is represented with the | character.

Example: highway | building Example: highway=residential | @type:Point

Metadata Terms

@id

Search for the exact id of a feature. Values must be an integer.

Example: @id:414317386

@type

Search for the type of a feature. Values can be one of node, way, area for searching OSM types or of Point, 'LineString', 'Polygon' for geojson types.

Example: @type:way

@version

Search for the edit version of a feature. Values must be an integer.

Example: @version:1

@changeset

Search for features in a given changeset. Values must be an integer.

Example: @changeset:1234

@uid

Search for features last edited by user id. Values must be an integer.

Example: @uid:1234

@user

Search for features last edited by username. Values must be a string.

Example: @user:ingalls

@timestamp

Search by last edit date of feature. Values must be integer.

Example: @timestamp:12344