[Qgis-user] Re: Annoying CRS-Problem with EPSG 31468 / 2167: Conclusions?

[Etienne Tourigny]

The following only applies to builds using master (and upcoming 1.8)
and gdal-1.9

Jeff pushed in master the fix which add missing TOWGS84 parameters (by
using GDAL_FIX_ESRI_WKT=TOWGS84).  It is possible that using
GDAL_FIX_ESRI_WKT=GEOGCS would resolve this issue.  Perhaps we couls
add an option for this, and set the default to GEOGCS?

see bug http://hub.qgis.org/issues/5142

Is there a proper fix for this in 1.7.4?

Etienne


On Thu, Mar 22, 2012 at 12:35 PM,  <bernhard.stroebl at jena.de> wrote:
>
> Am 22.03.2012 16:05, schrieb Bernd Vogelgesang:
>
>> So, the problem was now described thoroughly, but what are the
>> conclusions now?
>
>
> There is already a ticket open http://hub.qgis.org/issues/4977
> although I have no idea if the issue has been solved or not
>
>>
>> I'm going to spread QGIS in my region in the next months, and it's quite
>> hard to explain to the people, who to 99% work with EPSG 31468-data,
>> that they can't ever rely on any data they produce and that they have to
>> double-check each layer after creation for the right CRS, even if they
>> set it correctly in each setting available?!?
>>
>> I'm not too familiar with all those packages involved handling the CRSs,
>> so can someone please point me the way who to address with this problem?
>>
>> For novice QGIS-users, this "bug" is a real exclusion criterion for QGIS
>> for they will only create crap with it!
>>
>> Again my findings:
>> Options settings: new layers and projects are created with EPSG 31468,
>> promting for CRS ist set.
>>
>> - EPSG 31468-Layers with a prj-file from ArcGIS get loaded as 2167
>> without promting for the CRS
>> - EPSG 31468-Layers loaded into a EPSG 31468-Region in GRASS are handed
>> back to QGIS as ... 2167
>> - New Layers created in some plugins (like some ftools-plugins), added
>> to the TOC, are in ... 2167 .. or even 3397
>>
>>
>> What can i do? (And i really wonder what all those other german users do
>> and why the don't complain...)
>
>
> For me the base of the problem seems to be that the prj file is not matched
> to the right EPSG srs. As soon as you tell the layer it is EPSG:31468 it is
> positioned correctly. So the problem arises only with shapefiles; at my work
> we use PostGIS for most of our data (that is of course no help for you but
> explains why I am not "complaining")
>
> Bernhard
>>
>>
>> Thanx for advice
>> Bernd
>>
>>
>> (QGIS 1.7.4, osgeo4w advanced install, Win7 64bit)
>>
>>
>>
>> _______________________________________________
>> Qgis-user mailing list
>> Qgis-user at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-user
>>
>>
>> ________ Information from NOD32 ________
>> This message was checked by NOD32 Antivirus System for Linux Mail Server.
>> http://www.nod32.com
>
>
>
>
> ________ Information from NOD32 ________
> This message was checked by NOD32 Antivirus System for Linux Mail Server.
> http://www.nod32.com
> _______________________________________________
> Qgis-user mailing list
> Qgis-user at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-user