MeteoLatvia The Tactical Mesoanalyst user will visualize it, not import it. We import the data into our 24/7 real-time server infrastructure running ultra-fast bare-metal Pascal code, run our "special sauce" optimized geospatial data compression/streaming logic, and rapidly push to client over WebSocket/HTTP at extremely high levels of speed and bandwidth effiency compared to the absolute wasteful crap that is NetCDF, GRIB2, the NEXRAD L2 Archive format, etc.
For users to flexibly and configurably ingest direct, arbitrary, raw government data would fall under Industrial, not Tactical. Supporting this uncommon use-case significantly bloats the complexity and binary footprint, as well as exceeds most the needs and technical expertise of most users. This use case is actually the opposite of what we mean by "Tactical" Mesoanalyst; there will be "Industrial Mesoanalyst" likely for this purpose, if companies/governments want to do this. All of the datasets you mentioned I want to make available in WSV3 Tactical Mesoanalyst, possibly even with region-specific licenses, with the key distinction being we (TempoQuest) ingest the data and post-process into the super bandwidth optimized, fast-loading, efficient, proprietary raster data streaming engine being built for the product.
There is one exception: vector data ingest. This is static data from which users derive significant tactical value and should not be limited to industrial (broadcast is also under industrial). So, I intend WSV3 Tactical Mesoanalyst to have shapefile import like WSV3 Professional, and far better, supporting point objects, and competently displaying huge polygon and polyline datasets draped over 3D terrain and with better customization.
Everything else is real-time streaming bandwidth-optimized data requiring an internet connection, based on special proprietary technology being developed with modern GPU hardware, both client side and server side, to stream multiresolution hi-res 3D datasets to clients running the product on a power-constrained laptop over a bandwidth-constrained phone LTE WiFi connection within a mission-critical storm chasing context. That is the primary and ultimate usage context focus of WSV3 Tactical Mesoanalyst (see October 2023 post).
Industrial/Broadcast is a different context: plugged into the wall, less bandwidth/power resource constraint, possibly used by big companies who need to ingest their own proprietary raster data streams and/or broadcast on TV/media.
I will fight to make the Industrial side still way less expensive than WSI/Baron, but it needs to be around 5x more than Tactical, which I really want to impress people by not doubling the price, despite offering a 100x product. I would love for WSV3 Industrial Broadcast Mesoanalyst to be $100/month and available to consumers (the bosses will fight me on this) and only charge extra for TV broadcasting/certain watermark rights. Very few users have asked for custom private raster data ingest as opposed to simply me adding more data to the product.
But I will worry about Industrial/Broadcast in 2026. In the meantime WSV3 Tactical Mesoanalyst must maximize the value offered to the user at the same price-point as the current product and not more. I want to focus the functionality around the tactical in-field context and maximize content able to be delivered without raising the price.
It's possible to do this while also allowing free user import of vector data, just not local client-side raster data ingest which bloats the EXE and ruins the piracy protection model, which would require way higher prices.
Plus, you will really want to access all those datasets through native integration through our servers anyways, because they will download/display so much faster. This model also promotes global economic efficiency, decreasing the bandwidth bills of the user, us as the business, and the government, which promotes further innovation and lower prices. There's even an environmental impact optimization argument to be made.
We are getting as far away as possible from the antiquated, horrible, inefficient, security-disaster, bandwidth-wasting, slow, and frankly amateur "the Windows client EXE on the customer's computer downloads all the original heavy data straight from the government and does all the processing itself constantly on the client PC" model as possible, and that's a great thing.
In short, yes, I want to add all that data, just not to create the kind of heavy bloated product that allows the user to directly import/configure it themselves. I'm building a whole server-side engine that makes it easy for me to do just that, and we pay big bucks to process all that data so it downloads nice and fast for you with extremely low latency. Then for serious major industrial company clients, if they want to pay TempoQuest big bucks to run the same flexible ingest engine themselves on their servers, they can do that. We will be happy to pass that along in the form of low prices to consumers for the Windows PC WSV3 Tactical Mesoanalyst client application + data. You're not interested in having that as long as we make the same data available to you downstream in the app, correct? This is an example of how the price of the product to consumers can be lower and make everyone happier by choosing the right set of functionality that people actually derive value from as opposed to trying to do both client and server functionality wastefully within the same bloated EXE all on the client's computer, like WSV3 Professional. It's an amateur model that has held the product way back and I'm very excited to be going in the total opposite direction.
