> For that particular file, I see that the "feature_id" variable > (corresponding to the "feature_id" dimension) has a cf_role = > "timeseries_id" attribute, and that the global metadata has a > featureType = "timeSeries" attribute. So given > > https://cfconventions.org/Data/cf-conventions/cf-conventions-1.11/cf-conventions.html#coordinates-metadata > , this seems to be relatively standardized, and in that case the > heuristics could be improve to recognize that the main dimension is > feature_id (probably with a test that the size of the time dimension is > 1). As far as I can see/remember, the vector layer support in netCDF > was originally developed for the featureType=point and profile use cases > , so some tuning for timeseries isn't unexpected > > Thanks! I've made *some* progress, the deepest I've been down in that file ... I hope to be able to craft these suggestions at some point.
Cheers, Mike > Even > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > -- Michael Sumner Software and Database Engineer Australian Antarctic Division Hobart, Australia e-mail: mdsum...@gmail.com
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev