This issue tracks the ouput file format, it is mainly meant for discussions and tracking. Currently, KML is the only format that allows extensibility for wind intensity and timestamps already in the specifications. For example, a GeoJSON accepts coordinates and altitude but there is no option to add a custom attribute for wind for timestamp. Therefore, any software reading this GeoJSON with the wind and time data can simply ignore it.
We can add time and wind to KML files because it is just XML (as GeoJSON is to JSON) but, because custom attributes are part of the KML specifications, software will read the wind and time at the very least.
SHP file is another consideration as is other data formats including CSV. These can be explored.
This issue tracks the ouput file format, it is mainly meant for discussions and tracking. Currently, KML is the only format that allows extensibility for wind intensity and timestamps already in the specifications. For example, a GeoJSON accepts coordinates and altitude but there is no option to add a custom attribute for wind for timestamp. Therefore, any software reading this GeoJSON with the wind and time data can simply ignore it.
We can add time and wind to KML files because it is just XML (as GeoJSON is to JSON) but, because custom attributes are part of the KML specifications, software will read the wind and time at the very least.
SHP file is another consideration as is other data formats including CSV. These can be explored.