Text files typically only have hex values up 7F as the 8th bit is never set. This is the case with the "json" file. Each waypoint file is a true binary file having hex values from 00 to FF. The screen capture below is a hex view of one of the waypoint files. As you can see without knowing the internal structure of a waypoint file, you are going to have a very difficult time to create or modify this type of file.
View attachment 111209
Hey Pappy... I know this post is a little old, but the information is still good. I'm looking to find and work with the saved hyper lapse waypoint files, hence my interest in this post.
First a little clarification - Text files display 'text' in ASCII and the English language uses, for the most part, the first half of the table that ends with hex 7F, as you note, which is the "Del" key signal, and has a binary value of 0111 1111. All the hex values up to 7F have the eighth bit as zero (decimal values 0-127 lower ASCII). It isn't that the 8th bit isn't set or present, it is simply zero. The moment you use any character above 7F, that eighth bit becomes a one. A text file can and often does contain a character from the upper half or extended ASCII value set. If I used the word touché and spelled it correctly and saved it in a text file, the e with the accent is found in the upper half and is hex E9, which has a decimal value of 233 (falls in range of 128 - 255, which is extended ASCII). Hex E9 has a binary value of 1110 1001. So the 8th bit is one, not a zero and can clearly be used in a valid text file.
To further confuse things, DJI stores some configuration files with a "txt" file extension, but in reality they are binary plist files on the iOS side, and most likely XML files in Android. Security through obfuscation, perhaps? No real need for it, but that's DJI.
First, I don't mind working in hex and was hoping to get some information here that would help me understand the storage format. I was expecting a hex view of a waypoint file, but the screenshot above is the hex view of not a waypoint file, but rather of a PNG file. For sure, hex 89 50 4E 47 is the file signature of a PNG image file and you can see PNG is ASCII as the 2nd, 3rd, and 4th values in the signature. Do you still have the waypoint file, by chance, that you could share. I'm looking for JSON or waypoint files relating to my saved hyper lapse waypoint files in my DJI Fly files and I don't see them at all. I'm using iOS v1.6.4. Any information you can share I would much appreciate.
Best...
Steve