qgis trunk does not associate the right crs to shapes

[lutra]

Tested on trunk in both windows (seven) and linux (ubuntu 9.10) and it seems that is only a windows issue.

Add a vector that has a coordinate system that is not in the qgis default list.

As usual the unknown crs is added to the custom crs list, but in the vector properties the vector is assigned the wgs84 crs.

If you try to manually define the crs ("specify crs") in the vector properties ("general" tab), then no string at all show in the appropriate space in the "general" tab.

[lutra]

It is still true on the latest trunk revision.

[msieczka]

What EPSG code, for example?

Do you maybe know what GDAL and PROJ versions are the Windows and Ubuntu QGIS instalation build against, respectively?

[lutra]

You can test one of the shapes you can download here (should be code ESRI 102164), but is easily replicable with other non EPSG crs.

​http://www.iambiente.pt/atlas/dl/download.jsp?zona=continente&grupo=&tema=c_ph

The problem is ONLY under windows, regardless the version, using qgis trunk installed with the osgeo4w installer.

I cannot see this under Ubuntu using qgis trunk self compiled, but all the other packages from the ububtugis repository.

[lutra]

This is no more a "only windows" issue. It is easy to replicate also under linux with the latest code revision.

Moreover there there are shapes that have a crs that is in the qgis internal db but it fails to read it completely like

​http://www.igeo.pt/produtos/cadastro/caop/download/CAOP20090_Shapes/Cont_AAd_CAOP20090.zip ​http://www2.apambiente.pt/atlas/dl/regista_dl.jsp?zona=continente&grupo=&tema=c_redehidro

[jef]

probably fixed in r13586. It was impossible to save any custom crs to a fresh user db. But these might well be two different issues as the bug description states that the crs was saved. So feel free to reopen.

[lutra]

Hi Jurgen,

just tested r13586 and seems ok. Will do further tests and leave feedback. .qpj files are still saved in the wrong location. I remember there was a ticket about this issue, I'll se if it was already closed.