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

tiledata

v1.0.6

Published

Provides an easy way of fetching map data as tiles from different sources. Relies on the browser environment and depends on proj4js for the moment. See the example index.html for more details.

Downloads

5

Readme

tiledata

Provides an easy way of fetching map data as tiles from different sources. Relies on the browser environment and depends on proj4js for the moment. See the example index.html for more details.

Usage

Import tiledata.js as a ES6 module. The core functions are setConfig and getTiledata. First you have to initialize the module by calling setConfig which takes the following kind of options object:

{
    sources: [{
        name: string,
        type: 'wmts' | 'wms',
        url: string, // With type 'wmts' the url shall contain substrings "{x}", "{y}", and "{z}" to be replaced with the corresponding coordinates.
        layers?: string, // Needed only when using wms.
        fetchOptions?: {}, // Passed onto the browser's fetch function.
        valueFunction: (r: number, g: number, b: number) => number
    }],
    tileSize?: number, // Defaults to 256
    saveDataByTile?: (name: string, data: any) => any,
    getDataByTile?: (name: string) => any
}

After which you're able to use the getTiledata function. Parameters are as follows: tileCoords: Object containing the x, y, and z coordinates for the desired tile. sourceNames: String array in which the strings point to previously defined sources by the name. For instance:

getTiledata({ x: 1888, y: 2000 , z: 10 }, ['elevations'])

returns a Promise which resolves to

{ elevations: Int16Array }

example

Requires a options.js file in the folder. Template:

export default {
  mapboxToken: 'VALID_TOKEN'
}

TODO

  • [ ] Add support for different typed array formats such as Float32.