Well, that's a clear message at least. Tim, can you point me to the source from where you determine what is or isn't ICAO compatible, please? I (and others) seem to have differeing information on this.
The reason I ask is because I just checked ICAO document PANS-ATM, 4444 which defines the standard format of an ICAO flight plan. (If you want to check, a simple Google search will get you there.) The assertion of yours, that route points have to be specified as coordinates, is simply not supported by ICAO standard. It clearly says (and I quoted from it before) that for flights not following prescribed ATS routes, significant points along the route should be added as
The coded designator (2 to 5 characters) assigned to the point (e.g. LN, MAY, HADDY), or, if no coded designator has been assigned, one of the following ways:
-- Degrees only (7 characters)
-- Degrees and minutes (11 characters)
-- Bearing and distance from a significant point
Specifically, regarding the specification of border crossing points, so called "boundary points" the ICAO standard document says:
The BOUNDARY POINT expressed either by a designator consisting of 2 to 5 characters, in Geographical Coordinates, in Appreviated Geographical Coordinates, or by bearing and distance from a significant point.
This point may be an agreed point located close to, rather than on, the FIR boundary.
So, clearly, if I choose a point for my route for which a coded designator has been assigned then I am REQUIRED to use that designator in the route definition. Strictly speaking, the flight plan SD generates by substituting coordinates in cases where a coded designator exists are not ICAO compliant.
Also, the use of GOLVA as border crossing point in the example I gave near the beginning of the thread is fully compliant with the ICAO standard.
Airfield ICAO codes, towns and VRPs are things which absolutely are not allowed in the route section of a flightplan.
I hope I was able to convince you that airfield codes and VRPs are REQUIRED to be used as such in an ICAO flight plan. About towns I fully agree with you. The rule is that you have to use the CODED DESIGNATOR if one exists. If there's none then you use one of the other methods (geographical coordinates, abbreviated geographical coordinates or distance/bearing from a significant point).
Regarding the use of "DCT" in the route description the standard document has this to say:
Insert DCT between successive points unless both points are defined by geographical coordinates or by bearing and distance.
In this respect we were both wrong. Since SD gives all points as geographical coordinates there shouldn't be a DCT interspersed between them. And as I, in my own flight plans, give those points as coded designators I should have DCT between successive points.
I realize, of course, that you are the "Game Master" in as far as you can evolve SD in any direction you like. No qualms about that. And, by the way, I do love SD and think it is currently the best flight planning software out there for European VFR pilots.
But if you point to ICAO requirements as justification for only allowing route points as coordinates then that is something that is not supported by ICAO standard.