I noticed that SD generated FPL's through Slovenian airspace will never be accepted because SD uses 'coordinates' rather than official entry/exit points. (I had one unaltered SD generated plan rejected recently for this reason). Slovenian AIP:

REF AIP SLOVENIA ENR 1.10 PARA 1.3. B. SPECIALARANGEMENTS FOR IFR AND VFR FLIGHTS (ICAO NOTIFICATION OF DIFFERENCE) FLIGHTPLANS WITH FLIGHT ROUTES CROSSING FIR LJLA BOUNDARY OR VOLUMES OF CONTROLAIRSPACE SHALL INCLUDE OFFICIALLY PUBLISHED ENTRY/EXIT REPORTING POINTS.COORDINATES OR ANY OTHER NAMES ARE NOT ALLOWED THEREFORE SUCH FPL WILL BEREJECTED.

.. not sure what we can do about that in SD. I guess we have to remember to make manual changes to the plans.

There exists a strict definition of what goes where and in which format when you submit a FPL. This is true for VFR and IFR plans. However, VFR FPLs get interpreted by the local authority and are not validated by IFPS at Eurocontrol. Local authorities do exercise quite a bit of liberty and deviate from the internationally defined FPL format. For this reason it is hard to come up with a FPL format which works in all countries.

Most countries want their border crossing and reporting points as they are defined on the respective ICAO map. No ICAO map I know has lat/lon identifiers for VRPs. Every country I fly to accepts the alphanumeric designators as printed on the ICAO map. Therefore it would be nice if SD preferentially used these identifiers and not the (albeit standard and ought-to-be-accepted) lat/lon format.

Greetings, -- Chris.