[Touch Diamond, MDA Compact IV General] low.flying.pigs:
In brief response:

It has been previously detailed individual usage varies and is to be respected, hence support and testing of features of no current personal usage for the benefit of the GCC project and users in general. Extremes of map zoom is one such area.

It has been previously detailed that upper and lower zoom level limits should be restricted within the realms of sensible, proportionate and usable practicality because if anything is seen at all, image resolution does not allow anything to be usefully discerned beyond the point of usable practicality serving no useful purpose whatsoever.

Upper and lower user selectable zoom limits are a standard feature in many mapping / mapping capable applications that have any degree of sophistication. There are abundant reasons for this commonplace and sensible approach.

Without however any cogent reasoning given, limits were nonetheless opposed at the time, allowing zoom in above level 23 and out below level 0 indefinitely until device malfunction.

Limits were subsequently fixed to level 0 and level 23. At that point there was no continuation of the apparently baseless objection to zoom limits. Implementation was carried out as the solution to an issue that was resultant solely from zooming upward beyond the capability of a device. That was one of the abundant reasons for limitation in the first instance. Inherently therefore that issue need not have arisen in the first instance.

As there are currently no user selectable zoom limits, consequently many inherent issues therein remain, attention to them having been drawn again. Given this attention, and that the features and functionality in GCC is inherently present for beta testers testing beta software to test, it was therefore tested accordingly, and results shared for the benefit of the GCC project and users in general.

Fundamentally the same three apparent options as before remain as available courses of action:

1: Retain lower zoom levels, leave issues with map tiles and displacement unfixed. Unsatisfactory for all purposes.

2: Retain lower zoom levels, fix issues. Implement user selectable zoom limits for an array of reasons, not least standard functionality that inherently satisfies the requirements of all users for all purposes. As maps are selectable, zoom limits could be implemented as selectable on a per map basis, not least because not all maps have all levels available, and not all users want all levels. Default range will be 0 - 23, unless otherwise known, such as for downloadable maps, osm_servers.txt can in addition to storing the tile server URL, be adapted to include the upper and lower limits available for download, usually 0 to 17, 18 or 19, which are then set as default. Levels 20 - 23 are seldom used, and since the OSM format is based on folder structure and file name, which determine the positioning of the tile, folders and tiles copies to any level other than that at which they originate, will not ordinarily work. The user can adjust limits as required but not outside the default ranges.

3: Remove lower zoom levels, effectively a fixed lower zoom limit. Unsatisfactory for users that required all zoom levels.

Further information to be added.

low.flying.pigs