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

dirty-reprojectors

v0.0.2

Published

make different projections

Downloads

6,563

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

dsiodsio

Keywords

Readme

Dirty Reprojectors

Quick and dirty re-projections to trick your web maps out of web mercator.

Install

npm install -g dirty-reprojectors

Usage

CLI

cat input.geojson | dirty-reproject --forward PROJECTION [--reverse PROJECTION=mercator] > output.geojson

Example: to reproject some geojson so that web mapping libraries will render it looking like 'albersUsa':

cat input.geojson | dirty-reproject --forward albersUsa > output.geojson

For a list of supported projections, dirty-reproject --list

API

reproject

Reprojects the given geometry coordinate array in place, with unprojectable points or degenerate geometries removed. If both options.forward and options.reverse are supplied, then forward is performed first.

Parameters

  • options Object
    • options.forward (Function | string)? The forward projection to use.
    • options.reverse (Function | string)? The reverse projection to use.
    • options.projections Object? A map of named projections to use. If provided, then string values of options.forward or options.reverse will be used as keys to look up the projection function in options.projections. For an extensive list provided by d3-geo-projection, use require('dirty-reprojectors/projections').
  • coordinates Array

How it works

Take, for example:

cat input.geojson | dirty-reproject --forward albersUsa > output.geojson

What this actually does is:

  1. Project input.geojson from WGS 84 (longitude/latitude) into albersUsa, with the target coordinates scaled to match the dimensions of Web Mercator.
  2. Reverse-project the result back to WGS84 as if it had been projected with Web Mercator. So now, when your favorite web mapping library tries to project it into mercator, the geometries end up looking like they were projected using Albers.

The main catch is that if you actually look at the longitude/latitude coordinates in output.geojson, they are totally wrong. (There are other, subtler catches, too, having to do with Web Mercator's limited latitude range, varying loss of precision, and probably many other nuances I am not aware of.)

Credits