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

nearby-points

v1.0.10

Published

A package for finding data points within a region.

Downloads

17

Readme

nearby-points

A package for finding data points within a region.

Full API reference

sample usage

import { PositionalDB, PointData } from "nearby-points";

// create subclass PointData 
class Restaurant extends PointData {
    
    foodCategory: string;
    rating: number;

    constructor(x: number, y: number, foodCategory: string, rating: number) {
        super(x, y);
        
        this.foodCategory = foodCategory;
        this.rating = rating;
    }
}

// initialize db
const foodDB = new PositionalDB("filename.db", 
                                "foodCategory TEXT, rating REAL");

// insert data
foodDB.add(new Restaurant(10, 10, "fried chicken", 3.6));
foodDB.add(new Restaurant(13, 76, "sandwiches", 4.1));
foodDB.add(new Restaurant(90, 45, "smoothies", 4.7));

// find restaurants within 100 units of (50, 50)
const foodNearby = foodDB.getWithinRadius(50, 50, 100);

performance

nearby-points is much faster then dumping all points into one SQL table. However, .db files will take more disk space.

Tests for finding points within 20 units of (50, 50):

n - number of points, randomly generated between (0,0) and (100, 100)

plain db - SQLite3 database where all data points are put into 1 table

positional db - SQLite3 database created using PositionalDB class

speed (ms)

| n | 100 | 1,000 | 10,000 | 100,000 | | ------------ | ------ | ------ | ------ | -------- | |plain db | 0.1759 | 1.6521 | 12.062 | 147.9294 | |positional db | 0.2663 | 0.3484 | 2.625 | 17.2353 |

disk space (bytes)

| n | 100 | 1,000 | 10,000 | 100,000 | | ------------ | ---- | ------ | ------- | -------- | |plain db | 4096 | 122880 | 1257472 | 12984320 | |positional db | 4096 | 208896 | 1515520 | 13004800 |

The code that ran these tests can be found here

diagram of grid created by PositionalDB