[gdal-dev] What's so wrong with this nc file ...
That the geotransform is not detected gdalinfo xxx.grd Warning 1: dimension #1 (x) is not a Longitude___/X dimension. Warning 1: dimension #0 (y) is not a Latitude/Y dimension. Driver: netCDF/Network Common Data Format ... Corner Coordinates: Upper Left (0.0,0.0) Lower Left (0.0, 59.0) Upper Right ( 37.0,0.0) Lower Right ( 37.0, 59.0) Center ( 18.5, 29.5) I can't get why it's complaining on "dimension #1 (x) is not a Longitude/X dimension." Tried to check the full docs (netcdfdataset.cpp) but not even with a debugger I can understand the why. Due to it the x,y coordinates are not fished from file, either from Julia or from GMT NOTE: this works but does not use GDAL grdinfo xxx.grd xxx.grd: Title: z xxx.grd: Command: xxx.grd: Remark: xxx.grd: Gridline node registration used [Cartesian grid] xxx.grd: Grid file format: nf = GMT netCDF format (32-bit float), CF-1.7 xxx.grd: x_min: 580155 x_max: 581235 x_inc: 30 name: x n_columns: 37 xxx.grd: y_min: 4416795 y_max: 4418535 y_inc: 30 name: y n_rows: 59 xxx.grd: v_min: 0.205308780074 v_max: 0.56782335043 name: z ... This DOES NOT WORK (it uses GDAL) grdinfo xxx.grd=gd Warning 1: dimension #1 (x) is not a Longitude___/X dimension. Warning 1: dimension #0 (y) is not a Latitude/Y dimension. xxx.grd: Title: Grid imported via GDAL xxx.grd: Command: xxx.grd: Remark: xxx.grd: Gridline node registration used [Cartesian grid] xxx.grd: Grid file format: gd = Import/export through GDAL xxx.grd: x_min: 0.5 x_max: 36.5 x_inc: 1 name: x n_columns: 37 xxx.grd: y_min: 0.5 y_max: 58.5 y_inc: 1 name: y n_rows: 59 xxx.grd: v_min: 0.205308780074 v_max: 0.56782335043 name: z xxx.grd: scale_factor: 1 add_offset: 0 +proj=utm +zone=10 +ellps=WGS84 +units=m +no_defs What's so wrong with this nc file? I have others that look similar in terms of attributes and things work fine, but for some other cases I get the terrible Warning 1: dimension #1 (x) is not a Longitude/X dimension. Warning 1: dimension #0 (y) is not a Latitude/Y dimension. and I'm screwed. xxx.grd Description: xxx.grd ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] GDAL does not find geometries from KML
Hi, I found what is the problem. The service is sending old style KML, the current specification has this note: Note: The tag has been deprecated. Use instead. Search-replace made GDAL to find the missing geometries. -Jukka Rahkonen- Lähettäjä: Rahkonen Jukka (MML) Lähetetty: tiistai 19. lokakuuta 2021 15.53 Vastaanottaja: 'gdal-dev@lists.osgeo.org' Aihe: GDAL does not find geometries from KML Hi, I tried to convert geometries from a KML file captured with URL https://www.sedecatastro.gob.es/cartografia/fxcc/fxcc_kml.aspx?refcat=0717611VK4701F Ogrinfo finds layers INFO: Open of `0717611VK4701F.kml' using driver `LIBKML' successful. 1: 0717611VK4701F 2: PLANTA GENERAL 3: PLANTA BAJA 00 Ogrinfo finds also a POINT Z geometry from layer 0717611VK4701F. By looking at the KML file with a text editor layers PLANTA GENERAL and PLANTA BAJA 00 both contain one GeometryCollection which is made out of one or several POLYGON Z geometries. However, ogrinfo does not find those geometries. The KML file opens with Google Earth and shows a 3D model of a building. Is there perhaps something special in the structure of this KML? -Jukka Rahkonen- ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
[gdal-dev] GDAL does not find geometries from KML
Hi, I tried to convert geometries from a KML file captured with URL https://www.sedecatastro.gob.es/cartografia/fxcc/fxcc_kml.aspx?refcat=0717611VK4701F Ogrinfo finds layers INFO: Open of `0717611VK4701F.kml' using driver `LIBKML' successful. 1: 0717611VK4701F 2: PLANTA GENERAL 3: PLANTA BAJA 00 Ogrinfo finds also a POINT Z geometry from layer 0717611VK4701F. By looking at the KML file with a text editor layers PLANTA GENERAL and PLANTA BAJA 00 both contain one GeometryCollection which is made out of one or several POLYGON Z geometries. However, ogrinfo does not find those geometries. The KML file opens with Google Earth and shows a 3D model of a building. Is there perhaps something special in the structure of this KML? -Jukka Rahkonen- ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
