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

geo-point-in-polygon

v1.0.0

Published

determine if a lon,lat point is inside a polygon using great circle calculations

Downloads

2,404

Readme

geo-point-in-polygon

determine if a lon,lat point is inside a polygon using great circle calculations

example

The benefits of great circle calculations are very apparent at high latitudes.

The triangle described here covers the pole even though the latitudes of each point in the triangle is further south.

var geoPointInPolygon = require('geo-point-in-polygon')
console.log(geoPointInPolygon(
  [0,90], // north pole
  [
    [-156.78872,+71.29058], // utqiagvik
    [- 51.72157,+64.18347], // nuuk
    [+ 88.20270,+69.35350], // norilsk
  ]
)) // true

also gracefully handles the anti-meridian without special cases:

var geoPointInPolygon = require('geo-point-in-polygon')
console.log(geoPointInPolygon(
  [+178.44149,-18.14161], // suva
  [
    [+139.69171,+35.68950], // tokyo
    [+174.76667,-36.86667], // auckland
    [-155.09000,+19.72972], // hilo
  ]
)) // true

api

var geoPointInPolygon = require('geo-point-in-polygon')
var geoPointInPolygonNested = require('geo-point-in-polygon/nested')
var geoPointInPolygonFlat = require('geo-point-in-polygon/flat')

geoPointInPolygon(point, polygon, start=0, end=polygon.length, outside=ANTIPODE)

Return whether point is inside polygon.

  • polygon is an array of [lon,lat] points or a flat array of [lon0,lat0,lon1,lat1,...]
  • point is a 2-item array [lon,lat] of decimal degrees
  • start is an inclusive offset into polygon. default 0
  • end is an exclusive offset into polygon. default polygon.length
  • outside is a [lon,lat] coordinate that is known to be outside the polygon

By default, outside is set to the antipode of the first point in polygon which should work for all polygons that span less than 180 degrees of longitude. If your polygon spans >=180 degrees, you will need to use other domain information to find a point known to be outside the polygon.

install

npm install geo-point-in-polygon

license

bsd