V3

Well, g_GEOHASH_PRECISION might change with a revision, and we don't want the security rules to stop that. Our libraries assume a maximum geohash length of 22 (which corresponds to a resolution of 1e-9meters), so that's the maximum we want to allow, but there's nothing stopping us from using more or less precise geohashes in the future...

Regarding the extra check, good idea, I tested it and it works so I added modified the check to include that