Cities

One routing graph per city

Chale gives every launch city its own isolated routing data. It costs more to run and it is the reason a short trip can never quietly become an intercity journey.

· 3 min read

Most routing services will happily draw you a line between any two points on the map. If one of those points is 200 km away because a search matched a similarly named place in another district, the route is still perfectly valid — and the fare attached to it is a disaster.

What we do instead

Each Chale city runs its own routing service against its own extracted map data, pinned to a fixed version. Rewa routes against Rewa. Prayagraj routes against Prayagraj. Satna routes against Satna. There is no shared graph that spans them, so there is no route that spans them either.

The effect on a booking

If you set a pickup inside a service area and a destination outside it, Chale does not quote you a long-distance fare. It tells you the destination is outside the area it serves. That is a worse outcome for a demo and a much better one for a person standing on a street.

What it costs

Each city needs its own prepared dataset and its own running service, and adding a city is real work rather than a configuration line. We think a system that cannot produce an absurd route is worth the extra machinery.

Try it for yourself.

Set a pickup and a destination and see what the platform tells you.