Hi, I’m Andrew, and I’m the guy behind OpenTileServer.
If you’ve ever tried setting up a tile server and felt overwhelmed by endless commands and cryptic documentation, you’re not alone. I’ve been there too – sitting in front of a terminal, wondering why something wasn’t working. That’s why I created OpenTileServer: to take the headache out of map hosting and make it accessible for everyone.
Why I Built This
I’ve always loved maps. There’s something fascinating about turning raw data into something visual and useful. But the more I worked with mapping tools, the more I realized how complicated things could get – especially when it came to hosting your own map server.
Most tutorials out there assume you already know what you’re doing, or they’re so outdated that they cause more problems than they solve. I wanted to change that by creating a resource that’s clear, practical, and up-to-date.
What I Believe
Here’s my approach in a nutshell:
- Maps should be open. I’m a huge fan of open-source tools and open data. I think it’s important to keep this stuff available to everyone.
- Setting up a tile server shouldn’t require a PhD. I break things down step by step, so you’re never left scratching your head.
- Helping others is part of the fun. I’ve learned a lot from the open-source community, and I’m happy to give back by sharing what I know.
Why Bother with Your Own Tile Server?
Good question! There are plenty of paid map services out there, so why bother hosting your own?
It comes down to control. When you run your own tile server, you decide how your maps look, how they’re used, and who can access them. Plus, it’s way more fun to tinker with your own setup than to rely on someone else’s system.
I built OpenTileServer to make that process as simple as possible. Whether you’re just starting out or you’ve been in the map game for years, I hope you find something useful here.
Thanks for stopping by, and happy mapping!
— Andrew