Norman Fomferra

This issue is similar to #832, as the cause is a misinterpretation of lat/lon coordinate variables. The variables of AOD ENVISAT MERIS orbit frequency products are all 1D, so are...

For time being a solution could be to display a better error message, e.g. "Unable to concatenate time steps, because their coordinate variables are not equal."

I used a dataset that was created for another project. It was written by NetCDF and is perfectly readable by xarray and is fully CF compliant.

It happened again, this time for a OC CCI 200-day spatial subset. ESA Climate Office (@esacci) can make the dataset available. Please ask Paul or Ed.

If no bbox given, the operation should use the spatial extent taken from lon/lat coordinate variables.

@HelenClifton as it is an ID, it is ok have a string like that. Maybe the issue should not target the ID but instead ask for providing an editable human-readable...

We came across this issue recently when trying to open CCI Land Cover with dim size (lon=120000, lat=60000) prepared for the Copernicus Climate Data Store. Their convention is 0

@JanisGailis happy to discuss a solution with you early next week.

Note, this is not a bug because KMZ/KML is currently not among the supported formats. Consider converting it to GeoJSON or ESRI Shapefile format, then try again. @papesci see [here](https://gis.stackexchange.com/questions/114066/handling-kml-csv-with-geopandas-drivererror-unsupported-driver-ucsv?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa),...

@esacci nice work! Not that this is the same static imagery (Natural Earth 2) we use when there is no internet connection. However, it has the disadvantage that it is...