Unable to delete added map source (TileJSON)

frank

22 January 2018 00:31

I added the TileJSON file below, using filename bulgaria.tilejson, and it successfully showed up in the list of map sources under that name. Then I decided to change the filename to bgmountains.json and added it again, and the list of map sources added that new name. Then I tried to delete bulgaria.tilejson as an additional map source, but nothing happened. I was able to delete bulgaria.tilejson from the list of saved folders, but it still shows up as a map source.

Also, it would be nice if GaiaGPS would use the name in the TileJSON file as the map source name (e.g. "Bulgaria Topo Map") rather than the filename that was imported.

{
  "tilejson": "2.1.0",
  "name": "Bulgaria Topo Map",
  "description": "Bulgaria Topo Map",
  "version": "1.0.0",
  "attribution": "https://map.bgmountains.org",
  "scheme": "xyz",
  "tiles": [
    "https://bgmtile.kade.si/{z}/{x}/{y}.png"
  ],
  "minzoom": 1,
  "maxzoom": 19,
  "bounds": [
    -180,
    -85.05112877980659,
    180,
    85.0511287798066
  ]
}

0

• 

  Ashli Baldwin

  22 January 2018 18:09

  Hi Frank,

   

  If you login to your account on gaiagps.com and go to https://www.gaiagps.com/datasummary/mapsources/, I think you should be able to delete the extra map source from there.

  0
• 

  frank

  22 January 2018 23:38

  There are several help topics related to adding custom map sources. One method (apparently newer and preferred method) is to upload a TileJSON file to GaiaGPS.com to create a private map source (which can then optionally be made public), which will automatically appear on the GaiaGPS app, since GaiaGPS now requires an account at GaiaGPS.com.

  Older method was to download TileJSON file to smartphone, then import into GaiaGPS app, bypassing GaiaGPS.com. Problem I described occurred because I used this older method. I fixed the problem by uninstalling GaiaGPS app, then reinstalled, then reimported all my GPX tracks. Probably a cleanup like this was a good idea anyway, given all the changes made for version 7 on Android. (I upgraded from an older version, and did not uninstall reinstall at the time of the V7 release.)

  I suggest you go back and review the help files for adding custom map sources and either delete those that refer to the older import method, or annotate those help files to say the older method is deprecated in favor of the new method. Or else fix GaiaGPS app to allow deletion of map sources installed by direct import (the bug I was complaining about, which the uninstall-reinstall worked around).

  0
• 

  Ashli Baldwin

  07 February 2018 16:49

  Frank,

  Sorry for the delay. After doing some testing, I think there is a bug in newer Android versions affecting the removal of custom TileJSON map layers. I have created a bug report for this and submitted it to the Development Team.

  0

Please sign in to leave a comment.