Par trailapi | Mise à jour il y a 4 mois | Travel

9 / 10



Niveau de service


Retour à toutes les discussions

Bad list of maps returned

il y a un an

I’m getting the same 3 (wrong) maps returned by the ‘Trail Map List’ endpoint no matter what id I put in. The steps I’m taking are:

  1. Enter a lat/lon in ‘Find Bike Trails’ endpoint. This seems to work well and I choose a trail ID.
  2. Use trail id from step 1 in the ‘Trail Map List’ endpoint. Always get 3 maps returned, ids: 3857, 3910, 24127. At least one of those is a trail in Hawaii (I chose lat/lon coords and trail ids from both Casper, WY and Colorado Springs, CO just to see if I would get different results).

Should I be doing something differently?


Wanted to give a specific example. I’m using the example given by trailapi to the previous comment.

Search for bike trails within 5 miles of a point in southwestern Colorado Springs, CO:’
I get something like 36 responses. Among them is “Captain Jack’s”, which was mentioned in the previous comment. In the previous comment trailapi claims the trail id is ‘7’. However, this is the response I see for Captain Jack’s.

{15 items
"name":“Captain Jack’s”
“city”:“Colorado Springs”
“country”:“United States”
“features”:“Night riding allowed”
Clearly the id is supposed to be ‘288892’. So…
The response I get is:

[3 items
0:{7 items
"name":": Official Map"
1:{7 items
"name”:”: Official Map”
“description”:“Mostly fire road (feels like singletrack) with steep drop into and out of the canyon midway. Watch for hikers, dogs and horses.”
2:{7 items
"name”:”: SWMBA Trails”
(Note, none of those maps is for Captain Jack’s)

Indeed, if I use ‘7’ as the id in the ‘…/trails/<id>/maps/’ endpoint I get back maps for Captain Jack’s. Where is ‘7’ coming from? What am I doing wrong here?

trailapi commented il y a un an

Thanks for the message and the detailed info! We looked into this and have corrected the error.

Trail IDs were re-indexed in 2020, and 7 was the old ID for Captain Jack’s. The API translated old to new IDs, but wasn’t properly recognizing the new ones being returned by the explore endpoint.

Please let us know if you’re still having issues.

Participez à la discussion - ajoutez un commentaire ci-dessous:

Connectez-vous / Inscrivez-vous pour publier de nouveaux commentaires
Note : 4 - Votes : 5