Geohashing - System Design

If you don't know this, you suck at system design. Take the whole Earth and divide it into four quadrants. Mark the bottom and left as zeros and the top and right as ones. We first ask if it's left or right. Since it's left, we mark it as a zero. Then we ask if it's down or up, and since it's up, we mark it as a one. You would then take the quadrant that you've got and divide it up again. You could do this infinitely. Typically, when you hash, you have a binary sequence under the hood, and then you're going to read that in terms of hex. And that's pretty much done here. Hex is base 16 with the numbers 0 through 9 and then A through F. For whatever reason, geohashing uses base 32. So, what's cool about geohashing is that your precision is going to determine your specificity. Meaning, if you go to an extreme precision, you're actually going to get a very precise location on the Earth. For example, a one-character geohash is about 5,000 square kilometers, a very general place. If you get seven characters, you're at about the block level. By 12 characters, you're at almost their exact location. This is very useful for system design because nearby geohashes means that things are close. If you were in this geohash, anyone around you would make a good friend. Then, you would just need to determine your precision. Do you want general areas or do you want more specific? I teach this stuff every day and growing really fast, so follow along to learn more.