[gdal-dev] solved/ problem with wrong corner coordinates in a projected raster

Hello Jukka Thank you for that explanation and solution. It makes perfect sense, was easy to correct in my code, and fixed the problem. Greatly appreciated, Sam email signature Sam McClatchie (fisheries oceanographer) & Elena Turin (accounting & auditing) FishOcean Enterprises Ltd

Re: [gdal-dev] problem with wrong corner coordinates in a projected raster

Hi, The coordinate system and coordinate values must match. Now they don't. gdal_translate -of GTiff -outsize 1400 0 -a_srs EPSG:3857 -a_ullr 172.5 -35.0 175.0 -36.0 If the source image is in EPSG:4326 this should work: gdal_translate -of GTiff -outsize 1400 0 -a_srs EPSG:4326 -a_ullr 172.5 -35.

[gdal-dev] problem with wrong corner coordinates in a projected raster

Colleagues I want to georeference and project a raster image. I have an incorrect result where the image is improperly projected, and I am unsure why. The original image is "SST_plot_New_Zealand_Whangarei_clahe.tif" . (Note: I used links to my cloud server directory to av

Re: [gdal-dev] ogr gml Box handling

Thanks Even, I’ll try that out Andy Andrew, the GMLAS driver will fetch it as a string: $ ogrinfo GMLAS:input.gml -oo remove_unused_layers=yes -al -q Warning 1: Unhandled type: gMonthDay Warning 1: Unhandled type: gMonthDay Layer name: departedfeature OGRFeature(departedfeature):1 ogr_pki

Re: [gdal-dev] ogr gml Box handling

Andrew, the GMLAS driver will fetch it as a string: $ ogrinfo GMLAS:input.gml -oo remove_unused_layers=yes -al -q Warning 1: Unhandled type: gMonthDay Warning 1: Unhandled type: gMonthDay Layer name: departedfeature OGRFeature(departedfeature):1   ogr_pkid (String) = FDD58DEB0E04A917AB5BAEA4DFA

Re: [gdal-dev] ogr gml Box handling

Hi Jukka, Thanks for responding and apologies for not including enough context. I'm converting GML into a SQL file form during testing using a command like: ogr2ogr --config GML_GFS_TEMPLATE test.gfs --config PG_USE_COPY YES -skipfailures -lco spatial_index=NONE -lco create_table=off -lco schem

Re: [gdal-dev] ogr gml Box handling

Hi, Sorry but I do not understand at all what you want to do. Would you, if you read your question? Do you have some GML data that has a bounding box for each feature and you would like to convert the bbox into something? Would that be a second geometry for the attribute if the target format su

[gdal-dev] ogr gml Box handling

Hi, Trying to pull in the bounding box / envelope "Box" when loading gml with ogr2ogr 257023.700,620210.000 257023.700,620210.000 I've tried boundedBy in my gfs file. I've also tried seeing if I can pull through as a string using: bbox boundedBy|Box|coordinates Stri