Why doesn't TW recognize all towns?

Forums › General Discussion › Why doesn't TW recognize all towns?

CountyJailer Feb 27, 2015

I just placed a turf in a town called Quinlan, OK. But it says it's in Mooreland, OK. Is it because of size? I'm capo in a town of 28 people called Avard, OK.
⌖Շ☠ངんꀨ😲🔫😏⌖🖕 Feb 27, 2015

Try using the Google geocoder
CountyJailer Feb 27, 2015

ℤȺℂℍꀨ😲🔫😏 wrote:
Try using the Google geocoder

Didn't help :-/
LaTortuga Feb 27, 2015

In general Google is better at differentiating locations but it is based on their database. Try tapping around the area sometimes you just have to find the right spot. Example... I am Capo of Miami New Mexico. Who knew! Where's the beach? 😳😳😳 👍🐢 LT
λⱢᘮÇλГD Feb 28, 2015

If the city is small and close to a larger city, the map likes to group the smaller city with the larger city
Boner Jams '03 Feb 28, 2015

≛Cactus🌵King≛ wrote:
If the city is small and close to a larger city, the map likes to group the smaller city with the larger city

Yes, the map is sentient like that.
☠ðůﾅ⌖ʟḁẘ☠ Feb 28, 2015

The real reason is the "beauty update". Basically anywhere Nick has an ex girlfriend it's been considered a dead zone by this update. No geocoder can help your from Beauties wrath. Sorry 😁
Boner Jams '03 Feb 28, 2015

Depending on what city layer you use when mapping, you will get different results. My guess is that Quinlan is so tiny, geographically, it wasn't worth drawing borders around. Just two cents from a semi-pro GIS person.