Re: [gdal-dev] [Question] PROJ4String to WKT2 Transformations

2022-01-10 Thread Even Rouault
Felipe, when using PROJ to transform a PROJ.4 string to WKT2, there's (as far as I can think of) no loss of information. Loss of information can occur in the other way round. The main source of loss is that proj4 strings have a limited set of known datums, so sometimes you'll just have a +el

Re: [gdal-dev] [Question] PROJ4String to WKT2 Transformations

2022-01-10 Thread Rahkonen Jukka (MML)
Hi, The more or less same question seems to be asked some time ago in gis.stackexchange https://gis.stackexchange.com/questions/420378/can-we-construct-wkt2-from-proj4string-correctly. -Jukka Rahkonen- Lähettäjä: gdal-dev Puolesta Felipe Matas via gdal-dev Lähetetty: maanantai 10. tammikuut

[gdal-dev] [Question] PROJ4String to WKT2 Transformations

2022-01-10 Thread Felipe Matas via gdal-dev
Hi hi, I was looking for someplace to ask about this, and I was in doubt is was here or in PROJ, but lets do a try. Actually, probably I'm not the only one, I have some questions about how WKT2 and PROJ4Strings are transformed. >From what I read, a PROJ4String don't have enough info to construct

Re: [gdal-dev] Mapsforge binary map format

2022-01-10 Thread Even Rouault
Hi Matthias, Le 10/01/2022 à 19:33, Matthias Kuhn a écrit : Hi, I just came across the .map format, a tiled vector format (see https://www.openandromaps.org/en/ ) I tried opening the files and failed, is there support for this in gdal/ogr? I don't think

[gdal-dev] Mapsforge binary map format

2022-01-10 Thread Matthias Kuhn
Hi, I just came across the .map format, a tiled vector format (see https://www.openandromaps.org/en/) I tried opening the files and failed, is there support for this in gdal/ogr? Thanks Matthias Previous question on the topic: https://www.openandromaps.org/en/oam-forums/topic/openandromaps-in-q

Re: [gdal-dev] RPCs in GeoTIFF

2022-01-10 Thread Matt.Wilkie
Thanks for the nudge. I implemented that code as a simple command line script a couple of months ago but neglected to put it anywhere someone else could use it. Fixed that today ;-) https://gist.github.com/maphew/29a73ee7a4517663cef5081c15799fc3 ``` '''Copy RPC metdata from IN raster to OUT ras

Re: [gdal-dev] Bug in OGR library

2022-01-10 Thread Kopszak Marta - Partner Hurt
Thanks Even for very quick bug fix in QGIS! Kind regards, Marta From: Even Rouault Sent: Monday, January 10, 2022 3:22 PM To: Kopszak Marta - Partner Hurt ; gdal-dev@lists.osgeo.org Subject: Re: [gdal-dev] Bug in OGR library Marta, I was lucky enough to figure out from the error messages tha

Re: [gdal-dev] Discrepancy in proj values between ubuntu-small and ubuntu-full images

2022-01-10 Thread Rajsekar Manokaran
Hi Even, Thanks for explaining the difference between the images. You're absolutely right: I indeed assumed the two were using the same ellipsoids. If I use epsg:4269 (nad83 ell.) as the src, all the numbers are consistent. - Regards Rajsekar On Mon, Jan 10, 2022 at 8:05 PM Even Rouault wro

Re: [gdal-dev] Discrepancy in proj values between ubuntu-small and ubuntu-full images

2022-01-10 Thread Even Rouault
Rajsekar, One of the reason that the -full image is larger than the -small one is that the former includes > 500 MB of geodetic grids, whereas the later only includes very basic ones. (I've just amended https://github.com/OSGeo/gdal/blob/master/docker/README.md to make it clearer) As you do

Re: [gdal-dev] Bug in OGR library

2022-01-10 Thread Even Rouault
Marta, I was lucky enough to figure out from the error messages that your issue came when using QGIS, but it would have been appropriate to mention it from the start so we get the global picture. This is in fact a QGIS bug, which is only seen with the ODS & XLSX driver since they use the OGR

[gdal-dev] Discrepancy in proj values between ubuntu-small and ubuntu-full images

2022-01-10 Thread Rajsekar Manokaran
Hi gdal devs and users, I came across a discrepancy in proj. values between ubuntu-small and ubuntu-full docker images even for the same gdal version tag. I tried to convert a few coords from epsg:4326 to epsg:2271. The coords are: Input: -77.75 40.16 # this is the center meridian,

Re: [gdal-dev] Bug in OGR library

2022-01-10 Thread Rahkonen Jukka (MML)
Hi, I asked you to create a GML with SQL query from one feature in a hope that the huuuge value from your database would be generated as a FID and appear in GML. Did you try what happens? So if missing primary key is the main problem why not to add a primary key into your table? Or did you alr

Re: [gdal-dev] Bug in OGR library

2022-01-10 Thread Kopszak Marta - Partner Hurt
I think a single record wouldn't help you. If I would copy only one record to another empty database it could be exported to .xlsx. We have a postgres database and a table without any primary key, so QGIS uses a tid. The overall size of the database is huuuge (billions of records), so the tid re

Re: [gdal-dev] Bug in OGR library

2022-01-10 Thread Rahkonen Jukka (MML)
Hi, Now it starts to make sense. Could you paste the contents of a single row that you can’t write into xlsx format? You can capture it with ogrinfo “ogrinto [database connection] -sql "select * from my_table limit 1". Or maybe better to convert that row into GML format and attach that to your

Re: [gdal-dev] Bug in OGR library

2022-01-10 Thread Kopszak Marta - Partner Hurt
I have 2 bilions of rows in the whole database and I try to export only one table which has 56 columns and 423 thousands of rows so it’s not the issue with Microsoft Excel limitation. I can’t write even a single row (error Feature creation error (OGR error: negative FID are not supported) occur

Re: [gdal-dev] Bug in OGR library

2022-01-10 Thread Rahkonen Jukka (MML)
Hi, Could you clarify a bit? You have billion rows in the database table but xlsx and ods can support at maximum a bit more than one million rows (1,048,576). You can’t imagine to have success with converting the whole table. Or is your problem that you can’t write even a single row from the so

Re: [gdal-dev] Bug in OGR library

2022-01-10 Thread Kopszak Marta - Partner Hurt
Hi Even, Thanks for your replay. More info about the problem: Error: Save error: Export to vector file failed. Error: Feature write errors: Feature creation error (OGR error: negative FID are not supported) The database has more than 2 bilons of records (record – I mean record in the database ta

Re: [gdal-dev] Bug in OGR library

2022-01-10 Thread Andreas Oxenstierna
Excel limitations, see https://support.microsoft.com/en-us/office/excel-specifications-and-limits-1672b34d-7043-467e-8e27-269d656771c3 ODS: https://wiki.openoffice.org/wiki/Documentation/FAQ/Calc/Miscellaneous/What%27s_the_maximum_number_of_rows_and_cells_for_a_spreadsheet_file%3F Hälsningar A

Re: [gdal-dev] Bug in OGR library

2022-01-10 Thread Rahkonen Jukka (MML)
Hi, Excel xlsx format supports at maximum 1,048,576 rows by 16,384 columns https://support.microsoft.com/en-us/office/excel-specifications-and-limits-1672b34d-7043-467e-8e27-269d656771c3. Do your data fit within these limits? -Jukka Rahkonen- Lähettäjä: gdal-dev Puolesta Kopszak Marta - Part

Re: [gdal-dev] Bug in OGR library

2022-01-10 Thread Even Rouault
Marta, What is the bug exactly ? "2 billion records" : by record, you mean cells, like a sheet with 2048 columns and 1048576 rows ? By quickly looking at the code I can't see an obvious limitation, but that doesn't mean anything. Closer investigation would be needed. Please file an issue at

[gdal-dev] Bug in OGR library

2022-01-10 Thread Kopszak Marta - Partner Hurt
Dear Sirs, I ran into an error when exporting data through the OGR library to the .xlsx and .ods format. The bug occurs when there are more than 2 billion records in the database. I know the problem was solved for other formats, e.g. csv. Will the problem be solved also for other formats (e.g. x