MapLogics articles https://maplogics.com Writing about territories, routing, addresses and the operations around them, from the people building a geographic decision engine. en-us Thu, 03 Sep 2026 00:00:00 GMT ZIP codes are not shapes, and territory maps built on them leak https://maplogics.com/articles/zip-codes-are-not-boundaries/ A ZIP code is a set of delivery routes, not an area. Territory maps built on ZIP lists have gaps and overlaps nobody drew, and here is where they show up. Thu, 03 Sep 2026 00:00:00 GMT Clarence Williams III https://maplogics.com/articles/zip-codes-are-not-boundaries/ Routing a lead inside a franchise network is a contract problem https://maplogics.com/articles/franchise-territory-routing/ In a franchise network the routing rule is a promise somebody bought. Here is what changes about the software when the map is part of an agreement. Thu, 03 Sep 2026 00:00:00 GMT Clarence Williams III https://maplogics.com/articles/franchise-territory-routing/ A geofencing API is not a territory system, and the gap is the rules https://maplogics.com/articles/geofencing-apis/ Geofencing answers whether a point is inside a shape. Territory software answers who should do the work and why, which is a different amount of problem. Thu, 03 Sep 2026 00:00:00 GMT Clarence Williams III https://maplogics.com/articles/geofencing-apis/ Geocoding precision belongs in the answer, not in a footnote https://maplogics.com/articles/geocoding-precision/ Every geocoder returns a point. What separates a usable decision from a confident wrong one is knowing whether that point is a building or an average. Thu, 03 Sep 2026 00:00:00 GMT Clarence Williams III https://maplogics.com/articles/geocoding-precision/ Lead routing accuracy is four different numbers, not one https://maplogics.com/articles/lead-routing-accuracy/ A routing accuracy figure usually hides four separate failures with four separate fixes. Here is how to take them apart and which one to work on first. Thu, 03 Sep 2026 00:00:00 GMT Clarence Williams III https://maplogics.com/articles/lead-routing-accuracy/ What to look for in service area software, and what to ignore https://maplogics.com/articles/service-area-software/ Most service area tools answer whether you cover an address. The questions that separate them are about capability, precision, history and refusals. Thu, 03 Sep 2026 00:00:00 GMT Clarence Williams III https://maplogics.com/articles/service-area-software/ How a territory dispute is settled, and what it needs from you https://maplogics.com/articles/territory-disputes/ Territory disputes turn on a date, a boundary and a rule. Most software can answer one of the three, which is why the argument goes to a spreadsheet. Thu, 03 Sep 2026 00:00:00 GMT Clarence Williams III https://maplogics.com/articles/territory-disputes/ What a serviceability API should return, and what it should refuse to https://maplogics.com/articles/serviceability-api/ Whether you serve an address is a yes, a no, or an admission of uncertainty. An API that only has the first two is one that guesses. Thu, 03 Sep 2026 00:00:00 GMT Clarence Williams III https://maplogics.com/articles/serviceability-api/ What a territory version has to record to be worth having https://maplogics.com/articles/territory-versioning/ Versioning a territory map is not saving a copy. Here is what has to be in a version for it to answer a question about last March. Thu, 03 Sep 2026 00:00:00 GMT Clarence Williams III https://maplogics.com/articles/territory-versioning/