Geocode: Difference between revisions

Revision as of 22:47, 13 June 2023

Revision as of 22:49, 13 June 2023

Line 122:

Any ''geocode system'' [[#Systems of regular grids|based on regular grid]], in general is also a shorter way to express a latitudinal/longitudinal coordinate. But a geocode with more than 6 characters is difficult for remember. On the other hand, a [[#Systems of standard names|geocode based on standard name]] (or abbreviation or the complete name) is easier to remember.

So, thisThis suggests that a "mixed code" can solve the problem, reducing the number of characters when a name can be used as the "context" offor the grid-based geocode. For example, in a book where the author says "all geocodes here are contextualized by the chapter's city". In the chapter about Paris, where all places have a Geohash with prefix <code>u09</code>, itthat code can be removed &mdash;. forFor instance Geohash <code>u09tut</code> can be reduced to <code>tut</code>, or, by an explicit code for context "FR-Paris <code>tut</code>". ItThis is only possible when the context resolution (e.g. translation from "FR-Paris" to the prefix <code>u09</code>) is well-known.

In fact a methodology exists for [[#Hierarchical grids|hierarchical grid-based geocodes]] with non-variable size, where the code prefix describes a broader area, which can be associated with a name. So, it is possible to shorten by replacing the prefix to the associated context. The most usual context is an official name. Examples: