While I understand your point about the ultimate product being proprietary to a specific vendor, I think you're being too pedantic about the definition of data. As an example --- When I was a F-35 flight test engineer, Lockheed Martin would send us 10 Hz data in csv files that we (as government engineers) would run through Matlab (and later Python) to get it in a suitable condition to then run through our own software designed to enable a human analyst to review and score certain aspects of the jet's performance. We'd then package that up into pretty charts and graphs to give back to LM and tell them to fix whatever we found wrong. We called that data. When presenting those charts and graphs to leadership, we referred to it as data.
So yeah, I don't want to see raw data that's being pumped off whatever supercomputer is running the weather model - it would look nonsensical. But if a vendor is going to analyze that raw data using its own algorithms in order to package it into a digestible format for human eyes to view and understand, I'm going to call it data.