I don't think that's how it works. From experience from working on an experimental online learning system... it can't remember verbatim unless it is _really_ in there many many times. It can reconstruct it pretty close though.
source: online learning of codebases in the hundreds of thousands to millions of lines of code
As someone who grew up in the US and then moved to the EU; I came here to say exactly this. You leave your private house, get in your private car, then go somewhere. You could live 10 years beside someone and never know their name.
Here in the EU, I know most of the people on my street because I walk by them every day on my way to the store. In the US, even though I lived less than 1 mile/500ish meters from the store, I couldn't walk there if I wanted to.
Urban design makes a huge difference. The post war culdesac boom was a terrible idea. It does tend to keep unwanted strangers and poor people out of your neighborhood though, which was probably the point.
So, just add a 0 z-coordinate. And fwiw, points are usually represented on a computer with a 4D position, not a 3D one. So; if they specify "3D" then point clouds likely aren't covered.
Standard point clouds files are magic, standard bitmap files aren't! I don't make the rules, France does.
Of course it doesn't make any sense. We're engineering for (particularly inane) legal requirements, not information theoretic ones.
However, if The Rules are somehow that industry standard point cloud files are un-FOI-able, then any file can be made un-FOI-able, because any file can be translated to/from a standard point cloud file.
Reminds me of a new PM believing that "arabic numerals" mean arabic script instead of real every day numbers because AI told them so. Despite the entire team trying to explain it to them.
Some people would just rather believe a computer than the evidence right in front of them.
source: online learning of codebases in the hundreds of thousands to millions of lines of code
reply