Delivery zones in one command
Weekend Projects, episode two: distance rings around a made-up depot, sixty made-up deliveries, and a map file that opens almost anywhere.

I gave a single command sixty deliveries and one depot, and it handed back a zone map, a slide-ready image and an interactive page, in 0.6 seconds. Drawing a delivery zone used to mean a GIS licence and an afternoon. Now it's a single line in a terminal.
Weekend Projects is my Monday series about small builds I do at home. This one's for anyone who plans deliveries, events or service areas, and who has ever stared at a map trying to decide where "close enough" ends. I wanted catchment zones around a single base, done in one go, without opening a heavy desktop program.
The base and the bit I added
The starting point is an open-source mapping app that runs right in the browser. It already has layers and a 3D tilt, which is lovely to play with on a Sunday and properly handy when you want to see the shape of a place rather than a flat grid. I didn't change its code. My add-on sits next to it, and I used coding tools to help build it, which mostly means I described what I wanted and kept poking until the output stopped surprising me.
So here's the add-on. You give it a base and a list of points. It draws distance rings around the base, say 5, 10 and 20 kilometres, and counts how many points land in each. Then it writes a GeoJSON file, a PNG you can drop into slides, and an interactive HTML map anyone can open in a browser.
Honestly, that last file matters more than the maths.
What the test showed
For the demo I invented a depot and sixty deliveries. Sample data only, nothing from a real business. Eight deliveries landed within 5 km. Twenty-one sat between 5 and 10 km, twenty-six between 10 and 20 km, and five fell outside every ring.
It can also skip the rings and use public boundaries instead. In that mode it ranks whole regions by distance from the depot and counts the points in each one. For some planning questions that's the more honest view, because people tend to think in regions, not neat circles.
And because the output is plain GeoJSON, the zones drop straight back into the browser mapping app for proper analysis. You can load the file, tilt the view and look at your zones from a different angle. Everything runs locally, on sample data, with no paid APIs.
Where it gets it wrong
Mr. Mummu, who drifts into these posts now and then, once offered to drop a cake round to a friend who lived "just over there". He measured the trip on his phone with a ruler held against the screen. Barely three kilometres, he announced, and set off on foot with the cake in a tin and his notebook marked "Urgent" under one arm. The ruler had not mentioned the water in between, or the hill that only appears when you're carrying a cake. Two hours later he rang his aunty, who has never trusted a map app in her life, and she told him to come home and catch the bus like a sensible man. Before he did, he wrote one line in the notebook: the crow does not deliver cake.
That's the main limit of this build, so I'll say it plainly. These rings are straight-line distance, not drive time. Rivers, harbours and roads are ignored. A delivery 6 km away across water could be a long trip in a van, and the ring has no idea. Drive-time zones need a routing engine and a road network. You can run those for free, but they're heavy, and I didn't bundle one into a weekend project.
Boundary data is coarse too, so coastlines and areas are approximate. And when the zones go back into the mapping app, it uses its own default styling instead of my colours. Still rough around the edges, in other words.
Why I bothered
Years ago I shot Street View tours for a living, and I spent far too long in clunky desktop tools for jobs this simple. Drawing a circle, counting some dots and exporting something a person can read shouldn't take an afternoon, and that stuck with me.
What this weekend taught me is that the mapping engine is the easy part. Plenty of open-source tools will happily draw a ring for you. The real work is getting a file that a developer, a designer and an ops manager can all use without asking you for a different format. The developer wants GeoJSON, the designer wants a PNG, and the ops manager wants something to click on and zoom into. One command that hands each of them their own file is the bit I'm actually proud of.
If you plan deliveries or events, a rough zone map like this is a decent first look, as long as you remember the crow is doing the measuring. The full demo is on my YouTube channel, Gautam Atmakuri, in the Weekend Experiments playlist. I'll pop the link in the comments, with credit to the open-source project this add-on sits beside.
About the Creator
Gautam Atmakuri
I once spent seven days blindfolded, silent and without food to see what my senses were hiding. I write about that, my baby boy, barefoot running, Tirupati to Auckland life, and the business, marketing and tech I build at AumnI digital.
Enjoyed the story? Support the Creator.
Subscribe for free to receive all their stories in your feed. You could also become a paid subscriber, letting them know you appreciate their work.
Comments
There are no comments for this story
Be the first to respond and start the conversation.