Hi,
Here, is our XP12 data (what we offer) part for the GAXUN1B departure at SPZO:
SID:010,5,GAXU1B,RW10,RW10,SP,P,G,G , ,302,IF, , , , , , , , , , , , , ,18000, , , , ,SPZO,SP,P,A, , , , ;
SID:020,5,GAXU1B,RW10,ZO536,SP,P,C,E , ,302,TF, , , , , , , , , , ,+,12000, , , , , , , , , , , , , , ;
SID:030,5,GAXU1B,RW10,ZO540,SP,P,C,E ,R,302,RF, , , , , ,004000, , , ,0014,+,13000, , , , , , ,RZO18,SP,P,C, , , , ;
SID:040,5,GAXU1B,RW10,ZO544,SP,P,C,E , ,302,TF, , , , , , , , , , ,+,13500, , , , , , , , , , , , , , ;
SID:050,5,GAXU1B,RW10,ZO548,SP,P,C,E ,L,302,RF, , , , , ,006000, , , ,0007,+,14000, , , , , , ,RZO62,SP,P,C, , , , ;
SID:060,5,GAXU1B,RW10,ZO552,SP,P,C,E , ,302,TF, , , , , , , , , , ,+,14700, , , , , , , , , , , , , , ;
SID:070,5,GAXU1B,RW10,ZO802,SP,P,C,E , ,302,TF, , , , , , , , , , ,+,15000, , , , , , , , , , , , , , ;
SID:080,5,GAXU1B,RW10,ZO804,SP,P,C,E ,L,302,RF, , , , , ,002600, , , ,0084,+,17500, , , , , , ,RZO81,SP,P,C, , , , ;
SID:090,5,GAXU1B,RW10,ZO806,SP,P,C,E , ,302,TF, , , , , , , , , , ,+,18000, , , , , , , , , , , , , , ;
SID:100,5,GAXU1B,RW10,ZO808,SP,P,C,E , ,302,TF, , , , , , , , , , ,+,FL220, , , , , , , , , , , , , , ;
SID:110,5,GAXU1B,RW10,GAXUN,SP,E,A,EE , ,302,TF, , , , , , , , , , ,+,FL250, , , , , , , , , , , , , , ;
In segment 080, you see the RF leg to ZO804, which means from the previous waypoint ZO802 → ZO804. When you compare it with the charts, it´s coded correctly. So, it must be another issue, is not a navdata issue, as I have written before.
Cheers,
Richard