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

@basemaps/server

v7.12.0

Published

WMTS/XYZ Tile server command line interface.

Downloads

150

Readme

@basemaps/server

WMTS/XYZ Tile server command line interface.

This wraps the @basemaps/lambda-tiler into a standalone http server using fastify.

Usage

Basemaps server expects a folder tree full of configuration, with multiple tilesets and styles configuration files.

basemaps-server --config path/to/config/

Usage docker

The server is also published as a docker container

docker run -it \
    --volume $PWD/config:/config \
    --volume $PWD/tiffs:$PWD/tiffs \
    -p 5000:5000 \
     ghcr.io/linz/basemaps-server:v6 --config /config

Where ${PWD}/config contains all the configuration and ${PWD}/tiffs is all the relevant tiff files

Bundled configuration

Basemaps server can also be configured with a single JSON configuration bundle file using @basemaps/cli

By bundling the configuration the startup time is greatly reduced as each individual tiff file does not have to be scanned for dimensions, it does mean that new tiffs will not be picked up until a new bundle is created.

bmc bundle --config config/ --output config.bundle.json
basemaps-server --config config.bundle.json

Usage with LINZ imagery

Usage with basemaps config, you will need access to basemaps' imagery cache

please contact [email protected] if you need access.

git clone github.com/linz/basemaps-config

bmc bundle --config basemaps-config/config --output config.bundle.json
basemaps-server --config config.bundle.json

Direct TIFF access

If you have a folder of tiffs the @basemaps/server can index the folder and create tiles from it

For example given a structure where there are two folders full of tiffs

/images/00_gebco_2021_305-75m/*.tiff
/images/10_geographx_nz_texture_shade_2012_8-0m/*.tiff

running basemaps-server /images/00_gebco_2021_305-75m/ /images/10_geographx_nz_texture_shade_2012_8-0m/ will create two tile sets one for each folder gebco_2021... and geographx_nz_t... and then also create a combined layer in the order the tiffs are found.

Developing

When running the @basemaps/server in development mode, ensure @basemaps/landing page has been built and bundled

npm install
npm run build

npx lerna run bundle --stream # Bundle everything

This will package all the static assets into landing/dist and will be served from http://localhost:5000