Three build modes for a static map app, and why the ordinary build stays noindexA static map app can be built in more than one way, and the outputs do not carry the same rules. Pounce Atlas has three build modes. This post explains each one, and why the ordinary build stays out o2 min read·pounceza.hashnode.devNov 3
A clean-room release check for a static map app: what it proves and what it does notPounce Atlas is an open-source explorer for geographic datasets. Before a source archive is shared, its maintainers run a clean-room check: extract the archive into an empty folder, install, test, bui2 min read·pounceza.hashnode.devNov 3
A map explorer that still works when WebGL fails: fallback, keyboard and accessibility checksA map explorer depends on WebGL for its 3D view. Browsers, devices and graphics drivers do not always provide it. This post describes how Pounce Atlas keeps its records usable when that happens, and w2 min read·pounceza.hashnode.devNov 1
Imported files stay on your device: how Pounce Atlas handles CSV and JSONPounce Atlas is an open-source explorer for geographic datasets. It can load your own CSV or JSON file in the browser. This post explains what the app does with that file, what it does not do, and wha2 min read·pounceza.hashnode.devNov 1
An announcement isn’t an opening: separating event, observation and snapshot datesDisclosure: AI assisted the drafting of this article; Pounce reviewed it against the public Atlas source. Pounce builds Pounce Atlas, an open-source explorer for geographic datasets. Its examples are5 min read·pounceza.hashnode.devNov 1