This is not useable by the general public. I will get it in a better state during the next year. Also see the corresponding issue ticket.

~David

To take somethling like

edit in this sofware like

which gets you a tactile map like

This allows for the efficient creation of tactile indoor maps in mass. It enabled the creation of 41 tactile maps for toilets of the Congress Center Hamburg (CCH). This was done for 39C3, an event with 16,000 visitors.

All public toilets were equipped with a tactile map for orientation.

npm install .
npm run start # or npm run build

The static web files for hosting are put in dist/.

No worries.

You need a working node/npm installation. This project uses the current Node LTS version 24 ‘krypton’.

A common way is to use ’Node Version Manager’ (NVM). It manages multiple (or just one) installed node versions on your system. It works as an indirection in your $PATH and executes the node version specified by something you selected for the currently active terminal session with nvm install. This reads the .nvmrc file in this directory, installs the specified version if not already, and switches to it.

nvm use does the same thing, without installing. You can follow instructions to automatically run nvm use when a .nvmrc file exists, if you wish.

You can also just set your global default nodes version via nvm alias default lts/krypton.

You can do that to some degree. You can certainly try. Basically insert dependency hell discussion here. The projects you want to build / execute with node themselves are not part of your systems package management, thus might conflict with their maintainers choices as they are independent of them (and to each other). Thus, we add an indirection for decoupling.

Other solutions (like containers) exist for this problem, and can be applied if you prefer them.