Quote from PatB on 04.08.2025, 09:27

I looked through previous posts relating to vias, stops, and importing, and don't think this has been covered before.  Whenever I've imported motorcycle club rides into Scenic, all the waypoints are Stops.  Using the feature to convert all stops to vias works great to fix this, and I just assumed these files were created this way.

However, I decided to try ChatGPT to create a route for me yesterday that started from a club ride destination to find two locations from the club's annual riding challenge before directing me home.  I asked for all the waypoints to be vias, except for the two locations that I wanted to find, which should be stops.  ChatGPT created a very nice route, but all the waypoints were converted to stops.

I gave this as feedback to ChatGPT.  It said the waypoints were created as requested and suggested the following possible reasons for vias being converted to stops:

❌ 4. STOPs vs VIAs – everything imported as STOPs

Yes, this sounds like either:

• Scenic defaulting all GPX waypoints to STOPs, even when <type>stop</type> was only applied to some; or

• Scenic ignoring <type> tags from basic GPX 1.1 files.

Suggestions:

• Raise a note with Scenic support — they may advise a different GPX tag to control Via vs Stop (e.g. extensions or sym=Via), or confirm it’s a current limitation.

• I could also create a Scenic JSON or .itn-style GPX, if they offer an extended schema or support a more structured import format.

I thought you would be interested in seeing this in case improvements could be made, or to let us know how to avoid this future, such as using a different format.

I look forward to hearing your thoughts 🙂