No idea what that is, will have a look at it.
EDIT:I looked at it and, the only feature I think might be useful and would require changes to GSX is:
Having GSX to automatically recognize a SODE VGDS, if present in a scenery, and activate it automatically when selecting that gate in GSX, so you won't have to select the same gate in SODE, just to activate the VGDS.
This will require both a GSX update and a SODE update to support that, since the two will have to exchange that data, same as when using 3rd party sceneries with SODE jetways created by SODE.
mainly allowing us to set stop positions based on nose wheel position for different aircraft types rather than exit location
I don't think this is necessary. Sceneries using the SODE VGDS will use the SODE placer to create SODE VGDS so, we should assume a scenery developer using SODE VGDS would have tuned the stopping distance to be in agreement with that scenery ground markings.
So, you'll just follow the SODE VGDS indications, it won't matter to GSX, which will work with all its services just fine.
The only thing you might have to do, would be configuring all the parking stands in GSX with a SODE VGDS to have "NO Parking System" as their parking system, so GSX won't call a Marshaller there and this wouldn't be required anymore, if we would update GSX (and SODE would be updated too), to recognize SODE VGDS automatically.
