Card applications
Maps make spatial relationships visible that stay hidden in tables, built from open components instead of dependence on a single vendor.
Maps for websites and internal applications, built from open components: OpenStreetMap as the map base, PostGIS as the spatial database, Mapbox GL for display in the browser.
What comes out of it
A map showing your own geodata, with your layers, your points and a design that matches the rest of the site. It can stand in public or behind a login, and it can be built into an existing application.
What I take on
Advice on choosing the components, the installation, moving your geodata across and adapting the display. Plus introducing the people who will look after the map later, and technical support while it runs. Consulting, prototype, delivery and upkeep come from one hand.
Speed is a point of its own. A map with a few hundred points is quickly built; one with a hundred thousand calls for decisions about pre-computation, tiles and generalisation. Those decisions come before the first line of code.
Where the map runs
On your own infrastructure or with a provider of your choice. Because every component is open, you stay independent of any single provider and keep your geodata in your own hands.
What I advise against
A map of your own where a ready-made service will do. If all you want is to show one location, you do not need a map application, you need an address and a link.
Frequent questions
What about large volumes of data?
Rendering performance for large holdings is a work item of its own, vector tiles, generalisation and caching are part of it.
Own infrastructure or cloud?
Both are possible. The decision hangs on data protection, load and the operational know-how available.
Can our own geodata be integrated?
Yes, including versioning and history, so it stays traceable what changed when.