Please or Register to create posts and topics.

Grok is unable to generate a GPX file that imports into Scenic

PatB@patb
16 Posts
Member
#1 · 08.08.2025, 11:47

I've been trying to generate a route from Grok.  From its description of the route, it seems to grasp what I desire better than ChatGPT.  However, despite multiple attempts, I've been unable to get a route import into Scenic.  I've tried getting Grok to compare with files from Mappite and ChatGPT that successfully import into Scenic, but that isn't helping.  Scenic wants to import the route as locations of POIs, see the other file attached, the PNG.

Can anyone familiar with gpx who can see what is wrong with the attached GPX file pasted below?

Thank you in advance.

Pat

<?xml version="1.0" encoding="UTF-8"?>
<gpx version="1.2" creator="Grok 3">
<metadata>
<name>SAM Heritage Challenge - Norfolk</name>
<time>2025-08-08T17:22:00Z</time> <!-- 6:22 PM BST today -->
</metadata>
<wpt lat="52.0567" lon="1.2231" type="STOP">
<name>Start: Rushmere St Andrew</name>
<time>2025-08-08T17:22:00Z</time>
</wpt>
<wpt lat="52.0834" lon="1.1045" type="STOP">
<name>B1077 Ipswich</name>
<time>2025-08-08T17:22:00Z</time>
</wpt>
<wpt lat="52.1112" lon="1.0389" type="STOP">
<name>B1113 Saxmundham</name>
<time>2025-08-08T17:22:00Z</time>
</wpt>
<wpt lat="52.2389" lon="1.1123" type="STOP">
<name>B1354 Halesworth</name>
<time>2025-08-08T17:22:00Z</time>
</wpt>
<wpt lat="52.5000" lon="1.2000" type="STOP">
<name>B1136 Bungay</name>
<time>2025-08-08T17:22:00Z</time>
</wpt>
<wpt lat="52.7000" lon="0.9500" type="STOP">
<name>B1145 Fakenham</name>
<time>2025-08-08T17:22:00Z</time>
</wpt>
<wpt lat="52.8804" lon="0.8862" type="STOP">
<name>Binham Priory</name>
<time>2025-08-08T17:22:00Z</time>
</wpt>
<wpt lat="52.8500" lon="0.9000" type="STOP">
<name>B1388 Wells</name>
<time>2025-08-08T17:22:00Z</time>
</wpt>
<wpt lat="52.8197" lon="0.9487" type="STOP">
<name>North Elmham Chapel</name>
<time>2025-08-08T17:22:00Z</time>
</wpt>
<wpt lat="52.8300" lon="0.9300" type="STOP">
<name>B1110 Swaffham</name>
<time>2025-08-08T17:22:00Z</time>
</wpt>
<wpt lat="52.8394" lon="0.9281" type="STOP">
<name>Creake Abbey</name>
<time>2025-08-08T17:22:00Z</time>
</wpt>
<wpt lat="52.8200" lon="0.8800" type="STOP">
<name>B1355 Docking</name>
<time>2025-08-08T17:22:00Z</time>
</wpt>
<wpt lat="52.8198" lon="0.8702" type="STOP">
<name>Shell Fakenham</name>
<time>2025-08-08T17:22:00Z</time>
</wpt>
<wpt lat="52.7000" lon="0.9000" type="STOP">
<name>B1105 Swanton Morley</name>
<time>2025-08-08T17:22:00Z</time>
</wpt>
<wpt lat="52.5000" lon="1.1000" type="STOP">
<name>B1122 Beccles</name>
<time>2025-08-08T17:22:00Z</time>
</wpt>
<wpt lat="52.0567" lon="1.2231" type="STOP">
<name>End: Rushmere St Andrew</name>
<time>2025-08-08T17:22:00Z</time>
</wpt>
</gpx>

Click for thumbs down.0Click for thumbs up.0
Guido@guidomm
4,831 Posts
Admin
#2 · 08.08.2025, 18:05

I understand the question. I myself have tried to generate GPX files with LLM’s like ChatGPT. In my experience it’s not fail safe yet. It will be a little while longer before they can reliable generate GPX files consistently.

Click for thumbs down.0Click for thumbs up.1
PatB has reacted to this post.
PatB
If you're enjoying Scenic and are happy with the support, please leave a nice rating in the App Store. It would mean a lot to me ❤️
pe112@pe112
38 Posts
Member
#3 · 08.08.2025, 22:58

The Pat,
to answer your concrete question:
This GPX file indeed holds only a collection of waypoint (<wpt>) elements which Scenic correctly offers you to import as Locations or POIs.
A route however would require a <rte> element filled with <rtept> elements.
Under https://www.topografix.com/gpx.asp you can find a nice overview over GPX files.
The dirty little details are all here: https://www.topografix.com/gpx.asp
Best, Martin

Click for thumbs down.0Click for thumbs up.1
Last edited on 08.08.2025, 23:00 by pe112
PatB has reacted to this post.
PatB
PatB@patb
16 Posts
Topic AuthorMember
#4 · 10.08.2025, 03:09

Thank you for your replies.

Grok has tried using other XML elements, including track, but Scenic doesn't follow them for some reason, and hence is trying to simplify the code until Scenic can lock in on the routing data.  In previous attempts, the Scenic route didn't follow the tracking tag data.  However, comparing the files again, I notice that Grok has different coordinates from Scenic, so maybe this is the core issue...

The main reason I'm experimenting with AI routes is that Scenic tends to create routes heavily biased towards the smallest back roads possible.  I don't mind taking in some single-track roads, but not when they're full of potholes, the crown of the road has vegetation reducing the road to a tyre's width, or has high hedgerows combined with blind bends.  I do like the idea of trying greenlaning, but for now, I only ride a road bike and am looking for faster twisty roads, especially when wanting to cover longer distances.  The previous version worked quite well in "fast curvy" mode, but I struggle to find that sweet spot in the current version - hopefully that will improve in time 🙂

 

Click for thumbs down.0Click for thumbs up.0