Map applications
Maps make visible the spatial relationships that stay hidden in tables. I build them from open components, so you stay independent of any single vendor.
Maps for websites and internal applications, built from open components: OpenStreetMap as the map base, PostGIS as the spatial database, MapLibre GL for display in the browser.
Result
You get a map that shows your own geodata, with your layers, your points and a design that matches the rest of the site. It can be public or sit behind a login, and it can be built into an existing application.
My part
I advise you on choosing the components, install them, move your geodata across and adapt the display. I also introduce the people who will look after the map later, and I provide technical support while it runs. That way you get consulting, prototype, delivery and upkeep from a single source.
One point deserves attention of its own: speed. 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.
Location
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.
Reservations
Where a ready-made service will do, I advise against a map of your own. 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?
Displaying large datasets quickly is a work step of its own. It includes vector tiles, generalisation and caching.
Own infrastructure or cloud?
Both are possible. The decision depends on data protection, load and the operational know-how available.
Can our own geodata be integrated?
Yes, including versioning and history, so you can always trace what changed when.