[Touch Diamond, MDA Compact IV General] low.flying.pigs:
It could also be said, just looks like there are no users of GCC who miss

Alternatively, perhaps there does exist user demand. However in common with the majority of projects, there does not exist similar user willingness and or interest regarding actively positively contributing, or supporting development. Therefore the fact something has not previously arisen is in itself indicative of nothing necessarily other than the aforementioned willingness and or interest in actively positively contributing. Such issues have been previously addressed at considerable length.

As GPX 1.1 standards compliance is both a functionality improvement and essentially a bug fix, there appears no reason not to implement GPX 1.1 standards compliance from which all users of .gpx files would inherently have the benefit.

Similarly, the ability to further sort files would be of obvious benefit. Facility for doing so could be added to the existing context menus. File name and date would be easier to implement than track length which would the require the files to be read to determine this which could perhaps then be stored in an index so individual reading of each file each time would not be necessary.

GCC Boot development was suspended September 2014, in brief, due to awaiting resolution of serious Map Copyright Attribution issues, as as detailed fully here.

An initial simplistic and compliant solution for the Map Copyright Attribution issue appropriate for most if not all remaining legitimate users is straightforward and trivially simplistic to implement within the source code of GPS Cycle Computer to the extent a legitimate defence for not doing so, that would ultimately prevail in the event of legal challenge, appears not to exist. It requires no development of additional functionality, simply making compliant what already exists and disabling some non compliant aspects.

Such a solution was developed based on 4.12beta24 source code as mentioned in the detailed response however 4.12 final was released non compliant without prior announcement before it could be submitted.

In summary compliance entailed:

1. Disable Download and associated Selection List in Options > Map screen and osmservers.txt as the initial simplistic and compliant solution does not support online mapping and is not compliant unless these are disabled.

2. Disable copyright.txt as the function of which is replaced and more importantly enforced so as to actually achieve compliance as detailed in stage 3.

3. By default on the map screen utilising the existing attribution space and attribution prominence, at all times display the attribution 'Map data © OpenStreetMap'

The 'Map data © OpenStreetMap' attribution is 24 characters, 4 less than the 28 character '© OpenStreetMap contributors' thereby maximising screen space available for the underlying map. Used with appropriate mapping as detailed in stage 4, this is compliant as per the 'How to credit OpenStreetMap' section of the 'Copyright and Licence' detailed here and section 3a of the 'OpenStreetMap Legal FAQ' detailed here, the specific extract of the former and latter being:

4. Users straightforwardly and easily render their own OpenStreetMap based mapping as required from Mapsforge vector data, and in bulk if desired, using the latest MOBAC 2.x version, currently 2.0.0 alpha 4. See here.

5. Update documentation accordingly to state GPS Cycle Computer is intended for usage with mapping created as above, detailing the process of map creation as above, making clear that OpenStreetMap map data is available under the Open Database Licence, making clear other necessary information of whatever kind as required, and removing obsolete information.

The above initial simplistic and compliant solution is considered suitable for most if not all remaining legitimate users on the following basis. The simplistic solution can be expanded upon in a compliant manner as and if required.

Such users probably do not use online downloadable mapping within GCC and many devices offer no such support at a hardware level. The advantages of such online mapping over stored offline mapping are unclear. In any event, in most if not all instances, the requirements of remaining free to use without payment Tile Servers regarding Terms of Usage, Copyright Attribution and Tile Retention are such that this initial simplistic solution cannot support them. Any existing ability to use them as at 4.12 final was non compliant. Furthermore, Tile Servers are increasingly rare, many are either no longer available at all or have switched to API access control or a commercial payment only basis. However, compliant support could potentially be developed as required.

Such users probably do not legitimately use any non OpenStreetMap based mapping as it is unclear what if any such mapping actually legitimately exists that could be in legitimate usage now. However, users of any such mapping can provide details of it so that compliant support could potentially be developed as required.

Such users probably would welcome the ability to create their own free up to date mapping to their own requirements, on a sustainable and legitimate basis with the option of contributing to the development of the content and quality of that mapping. Furthermore, subject to appropriate compliance with distribution requirements, such rendered mapping could be distributed in a ready to download, extract, and use format to users.

low.flying.pigs