Quick and dirty re-projections to trick your web maps out of web mercator.
npm install -g dirty-reprojectors
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
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 Take, for example:
cat input.geojson | dirty-reproject --forward albersUsa > output.geojson
What this actually does is:
input.geojson
from WGS 84 (longitude/latitude) into albersUsa
, with the target coordinates scaled to match the dimensions of Web Mercator.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.)