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

@piuccio/flat-earth

v1.1.3

Published

Modern set of functions for handling coordinates in Node.js or the browser

Downloads

5

Readme

Modern set of functions for handling coordinates in Node.js or the browser

Installation

npm install --save @piuccio/flat-earth

That'll work for node.js and most likely for the browser as well if you're using Webpack, rollup or similar bundlers.

Disclaimer

This project only exposes simple utility functions that would be useful in map projects, it doesn't try to be extremely accurate. If you need high precision you're better off using other modules like geodesy, haversine or if available on your environment Google Maps API or similar.

Functions

geohash

Compute the Geohash of a point.

import { geohash } from '@piuccio/flat-earth';

console.log(geohash(35.6896491, 139.7001494)); // xn774cne32v3
console.log(geohash(35.6896491, 139.7001494, 7)); // xn774cn

The function is a simple wrapper around latlon-geohash geohash.encode()

equirectangularDistance

Compute the distance in meters between two coordinates using the fast Equirectangular approximation

import { equirectangularDistance } from '@piuccio/flat-earth';

console.log(equirectangularDistance(
  { lat: 35.6896491, lon: 139.7001494 },
  { lat: 35.6579909, lon: 139.7014112 },
)); // 3522

The Equirectangular approximation is much faster and a good enough approximation on small distances. For instance in the bounding box containing greater Tokyo the error compared to the Harvesine formual is < 10m. In the box containing the whole Japan the error is 16km (0.6%). Accuracy varies depending on the latitude.

boundingArea

Given a list of coordinates, compute the area containing all points. The area is described by the center point (lat, lon), the North-East and South-West edges.

import { boundingArea } from '@piuccio/flat-earth';

const area = boundingArea([
  { lat: 35.6896491, lon: 139.7001494 },
  { lat: 35.6579909, lon: 139.7014112 },
  { lat: 35.6812916, lon: 139.7666099 },
]);

/*
area = {
  center: {
    lat: 35.6762685,
    lon: 139.7230322,
  },
  ne: { lat: SHINJUKU.lat, lon: TOKYO.lon },
  sw: { lat: SHIBUYA.lat, lon: SHINJUKU.lon },
};
*/

The center or midpoint is computed as an average of the latitude and longitude mostly because it's expected to be used to center a Mercator map. When using only two points, you'd be better off computing the midpoint along a great circle path rather than the average.

getZoom

Given a bounding area, return the zoom level that would allow to fully display the bounding area on a map given a map size in pixels.

Openstreetmap seems to only have an integer zoom, while google maps on large screens also accepts decimal units. Use the precision to control the value. If no precision is specified it returns an integer.

import { boundingArea, getZoom } from '@piuccio/flat-earth';

const area = boundingArea([
  { lat: 35.6896491, lon: 139.7001494 },
  { lat: 35.6579909, lon: 139.7014112 },
  { lat: 35.6812916, lon: 139.7666099 },
]);
const zoom = getZoom(area, { width: 700, height: 700 });  // screen size in pixel
// 13

containingGeohashes

Given a location, computes the minimal list of Geohashes that need to be checked to find all points within a certain distance

import { containingGeohashes } from '@piuccio/flat-earth';

const containing = containingGeohashes({ lat: 35.6896491, lon: 139.7001494 }, 100);
/*
containing = {
  precision: 7,
  hashes: [
    'xn774cq',
    'xn774cr',
    'xn774cp',
    'xn774bz',
    'xn774by',
    'xn774bv',
    'xn774cj',
    'xn774cm',
    'xn774cn'
  ]
}
 */

The distance is measured in meters

distanceOnFoot

Computes the distance in meters that an average person covers in a given time (minutes)

import { distanceOnFoot } from '@piuccio/flat-earth';
console.log(distanceOnFoot(10)); // 834

Very simple computation from the assumption of 5 km/h

minutesOnFoot

Computes the time it takes an average person to cover the given distance (meters)

import { minutesOnFoot } from '@piuccio/flat-earth';
console.log(minutesOnFoot(100)); // 2

Very simple computation from the assumption of 5 km/h

Usage in node.js

All the example above use the ES modules syntax

import { distanceOnFoot } from '@piuccio/flat-earth';

On Node.js, if you're not using babel you can use instead

const { distanceOnFoot } = require('@piuccio/flat-earth');