Originally Posted by
pandaperth
Lingo Lesson: not -sXXX rather ,XXX for a surface segment

Originally Posted by
ernestnywang
For GCMap that's how the system works, but in general ticketing lingo surface segment (or open-jaw) is usually denoted as either // or /-, so your first open-jaw would be BKK//HAN or BKK/-HAN.
But ... when someone posts a tentative itinerary here and asks for help, what is the first thing most of us do? Paste it into the GCM! Now, it seems to me that people asking for help should make it as easy as possible for the helpers. That's why I would advise against both sHAN and xSYD. Instead, simply use UPPERCASE for stops and lowercase for transits, and if there happen to be any surface segments just mention them. Thus, the OP here could say:
"Hi guys! I'm thinking about OSL-hel-BKK-HAN-NRT-HAN-KUL-MNL-SYD-BNE-syd-AKL-LAX-LAS-MIA-lhr-OSL, with BKK-HAN, HAN-KUL, SYD-BNE and LAX-LAS as surface segments."
Then ... click click ... the GCM tells us with no fiddling about that he's using all 16 segments, totalling 33 728 miles (although the mileage bit isn't as important here as it would be for an xGLOBxx ticket). It also shows us a map to help us visualise where the routing could be tweaked.
Of course, we know -- and a beginner will soon recognise -- that having any surface segments at all (not to mention
four !) is foolishly wasteful. Luckily, most people asking for help here -- just as, I presume, most people taking xONEx trips -- don't have any. (Still, it's too bad that something such as ...-AAA//BBB-... doesn't work in the GCM.)