Hi, all,
The Definition of Google Plus Codes, a.k.a. Opern Location Codes, can be
found at https://en.wikipedia.org/wiki/Open_Location_Code
The complete code also specifies, by its length, the size of the area
being described. When using them in splitter, I have never seen a tile
whose code was longer than 8 characters, an area 250m east to west and
125m north to south. I use the largest OLC centered on the tile in
question that fits within the tile.
Randolph J. Herber
On 4/8/2020 4:59 AM, Ticker Berkin wrote:
Hi Gerd
I'd say that if the splitter is going to generate descriptions per tile
(geonames) it should generate one for each tile and, if there isn't a
centre of a city within the tile and no default description, it should
use a modified form of the nearest city to make it unique from a
possible adjacent tile that might use the same city.
Maybe something like "GB-~Basingstoke", but no solution is ideal and
there could still be duplicates.
The splitter could keep track of which names were have been used and,
for the ones outside the tile, added an increasing suffix number, so
would have "GB-Basingstoke-2" etc
Ticker
On Wed, 2020-04-08 at 08:38 +0000, Gerd Petermann wrote:
Hi all,
this is a follow up of http://gis.19327.n8.nabble.com/documentation-i
mprovement-tp5962609p5962747.html
Since I don't use these options for my maps I am unsure what is best.
The --geonames-file option tries to find a city within the calculated
tile. If none is found it either writes the value
given with --description or just a comment.
I think it would be best to always write the nearest city.
Gerd
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
