This looks a lot like floating point errors. There's probably some math involved in exporting that causes these slight inaccuracies.
It probably isn't too hard to write a short python script to go over the exported file, and round those values.
A community for users of the awesome, open source, free, animation, modeling, procedural generating, sculpting, texturing, compositing, and rendering software; Blender.
Rules:
This looks a lot like floating point errors. There's probably some math involved in exporting that causes these slight inaccuracies.
It probably isn't too hard to write a short python script to go over the exported file, and round those values.
The precision is default afaik, and necessary for accuracy when dealing with objects far from origin. The noise you see though is due to floating point precision which is a thing with numbers on computers. This is common to all 3d software. https://docs.oracle.com/cd/E19957-01/806-3568/ncg_goldberg.html
If you know your tolerances are much less and disk space is a concern you could post process this data in the file as text, but I wouldn’t bother.
For 32-bit float 6 decimal digital are precise in representation, beyond that expect to have rounding errors.
I don’t see if blender ever has 64-bit support but there were rejected requests.