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

@pirxpilot/google-polyline

v3.0.2

Published

Encode / decode Google's polyline format

Downloads

461

Readme

NPM version Build Status

google-polyline

Encodes and decodes Google's polyline format It's a forked version of google-polyline module with minor performance improvements and reversed order of coordinates: longitude, latitude (think x, y or easting, northing), which corresponds to position definition in GeoJSON spec.

Install

$ npm install --save @pirxpilot/google-polyline

# or

$ yarn add @pirxpilot/google-polyline

Usage

const { encode, decode } = require('@pirxpilot/google-polyline')

encode([
  [ -120.2, 38.5 ],
  [ -120.95, 40.7 ],
  [ -126.453, 43.252 ]
])

> '_p~iF~ps|U_ulLnnqC_mqNvxq`@'

decode( '_p~iF~ps|U_ulLnnqC_mqNvxq`@' )

> [
  [ -120.2, 38.5 ],
  [ -120.95, 40.7 ],
  [ -126.453, 43.252 ]
]

API

polyline.encode(points[, options])

returns a string representing encoded polyline

  • points is an array of points, each point is a 2 element array [longitude, latitude]
  • options.factor - optional (defaults to 1e5), factor by which coordinates are multiplied during encoding
  • options.mapFn - can be optionally passed to convert array of elements to [lon. lat] pairs mapFunction is called for each item in points array and has the same signature as Array.map callback
  • options.prefix - optional prefix for encoded String

polyline.decode(string[, options ])

returns an array of points representing decoded polyline

  • string is an encoded polyline representation
  • options.factor - optional (defaults to 1e5), factor by which coordinates are divided after decoding; use factor 1e6 when decoding polylines from OSM data (OSRM, mapzen etc.)
  • options.mapFn - optional - if provided it'll be called for each [lon. lat] pair to convert the point before it is added to resulting points array
  • start, end - (defaults to 0, points.length) - allows to decode a substring