[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Unfortunately mass abuse of MOBAC and similar tools has been a major factor in creating the current situation. The damage is already done and cannot be readily undone. Many similar tools have been disbanded. Some creators of the tools regret ever having done so, or not restricting their usage effectively. Even when MOBAC took action some hardened, prolific and determined abusers deliberately reverted to usage of versions prior to this in order to continue this misguided behaviour, some even attempting to create hybrid versions using older components with newer ones, so as to have new features with old map sources.

Consequently, many previously freely accessible map sources are now API access only, but still free within reasonable limitation. GPS Cycle Computer could potentially implement these API's as previously detailed. Others have removed free access of any kind entirely.

Regarding rendering off line mapping, conceivably, if users were to actually download OpenStreetMap raw data in excess of their actual need similar to how Tile Servers have been abused, a similar issue would occur with the provision of raw data and the enormous amount of data downloaded.

However, rendering is currently neither particularly 'convenient' or 'user friendly' in comparison to bulk downloading improperly from Tile Servers whilst any remain to be abused.

Whilst there have been some third party attempts to build extensions / bridges / plugins for / between MOBAC and Mapertive, for GPS Cycle Computer usage, these are unnecessary and MOBAC is unnecessary as Maperitive directly as standard exports tiles in OSM format suitable for usage with GPS Cycle Computer.

Whilst Maperitive could be easier to use in conjunction with raw data, it is not excessively difficult or impossible. Perhaps there does need to remain some barrier to entry maybe in part due to the aforementioned issues of data consumption, and abuse, until these can be reliably and sustainably resolved.

Regarding Tile Servers, the current 'solution' is that ordinary users of Tile Servers download only what is needed, when it is needed. This is mostly what free Tile Server fair usage amounts to, and the right for their service they provide to be used on their terms, to be credited for their hard work, expenditure, and resources, and in some cases to generate revenue from related commercial enterprise that funds the provision of the free Tile Server in the first instance. The no 'pre-downloading' or 'pre-caching' and similar are again aimed at MOBAC and similar tools, but unfortunately make no distinction and are all encompassing. Regardless of contrary individual opinion, it is hardly unreasonable, and another example of willingness to work on and provide thankless tasks, but not in return for disrespect or abuse. Users that object are free to provide their own Tile Servers for similar individuals to themselves throughout the entire world to abuse relentlessly at their personal expense.

A better solution would be the API route whereby all map sources have an API and all applications implement the API of the map source. Then the user registers with the map source service provider for an account suitable for their needs, and adds to that account unique device keys generated by the API for each device, and receives an API key used on each device / application. The data is locally transferable between devices however the user cannot exceed the limits of their account accessed via their API key, in terms of number of devices or data downloaded. Data retention could be handled by the API by detecting tiles older than a certain limit, and automatically not displaying / deleting / downloading them again as required. Furthermore it would be recorded on account what tiles were provided when, preventing attempts to circumvent this. A common method of user authentication in other areas is requirement to provide means of payment by credit or debit card which is then verified. This tends to ensure registrations are genuine, and tends to ensure one account per individual, and if remaining within the free limits no charge would be made. This would be more satisfactory, and few if any genuine users would object. It is not entirely secure, however, it is more robust and advantageous than at present. The API could detect attempts to circumvent measures and block accounts and target the unique specifics of those accounts, users, devices, payment cards, addresses etc, somewhat preventing further usage / abuse and or registration of new accounts with those details, without affecting legitimate users.

As there are far more users than applications, this, or something similar, is probably how in the future such mapping access will be, as it would be more lucrative, and enable more application development. Currently API keys are increasingly implemented but are usually application specific, causing an issue to projects such as GPS Cycle Computer that have no revenue stream to fund enhanced API access.

Regarding how others have handled these issues, most, if not all, of the major manufacturers / brands of GPS equipment, and dedicated GPS Cycle Computer devices, and some applications have overcome the issues by making the required acknowledgements and providing their users with ready made pre preprepared packaged maps ready for download and usage, using their own resources, and / or access to dedicated tile servers, using their own resources.

As previously detailed, GPS Cycle Computer could potentially integrate support for legitimately obtained and usable and or freely available device specific mapping.

GPS Cycle Computer could provide similar pre packaged mapping of its own, and / or access to its own dedicated tile server. There are a number of issues however with doing so.

Unfortunately, GPS Cycle Computer is not currently even hosted properly as a project, as it used to be before the changes with Google Code, when there are free viable alternatives such as Microsoft CodePlex detailed in the mid part of post 2029. With recognised credible project hosting comes credibility for the project, essential when attracting new users. When linked from CodePlex or similar, Dropbox or similar may have a role hosting maps for download.

low.flying.pigs