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

geojpairdown

v1.0.1

Published

Takes a geojson file and creates two files, one with the geojson and an id, the other a json object with the keys as values.

Downloads

4

Readme

This is to split up a geojson file which may have a lot of attributes, and just give it one id attribute and another file which all or the specified fields which can then be joined to the other layer when/if required.

For an example of how to use it check see if it works with your geojson see the test directory and specifically the test.js file for a implementation.

Basically you require it and give it the first argument as a string path to your file and the second argument as the beginning of the file output.

So like in the sample if you do

var pairDown = require('../index.js');

var pair = pairDown('./test/testfile.geojson', './test/tester');

This will output in the test directory a file tester.geojson and testerfeats.json with the Basically geojson in one and the feature data in the json.

caveats: right now designed just to handle OSM files coming out of qgis in geojson format. only designed/tested with polygon features. a bunch of sloppy console.log ing

What's going on

In index js

Initialize all the filestreams

On each data event the first chunk gets called with startit() and the following ones with nextFeatStart()

startit starts making a file then starts to split it up