Am 30.03.2012 19:44, schrieb Etienne Tourigny:
On Fri, Mar 30, 2012 at 6:23 AM, wrote:
Etienne,
I see this stuff from a user's point of view. I am currently not working
with different projections but my projects are EPSG:31468 and my data, too.
So this is my perspective. I am neither a geode
Berhard,
I thinks I have found a solution to your problem (in master only
though). I suspect the same can be applied to 1.7.4 , if gdal-1.9 is
used.
First, make sure that 'crssync' is executed after installing master,
this adds the necessary definitions that are missing. This is probably
why EPSG
On Fri, Mar 30, 2012 at 6:23 AM, wrote:
> Etienne,
>
> I see this stuff from a user's point of view. I am currently not working
> with different projections but my projects are EPSG:31468 and my data, too.
> So this is my perspective. I am neither a geodesist nor did I dig into how
> different so
Etienne,
I see this stuff from a user's point of view. I am currently not working
with different projections but my projects are EPSG:31468 and my data,
too. So this is my perspective. I am neither a geodesist nor did I dig
into how different software handles srs or prj files. All that I know
On Mon, Mar 26, 2012 at 3:42 AM, wrote:
> Am 23.03.2012 13:32, schrieb Etienne Tourigny:
>
>> On Fri, Mar 23, 2012 at 5:26 AM, wrote:
>>>
>>> I just tested with current trunk (compiled on OpenSUSE 64bit):
>>> When I load
>>>
>>> PROJCS["Transverse_Mercator",GEOGCS["GCS_bessel",DATUM["D_Deutsches
Am 26.03.2012 08:57, schrieb Jürgen E. Fischer:
Moin Bernhard,
On Mon, 26. Mar 2012 at 08:42:02 +0200, bernhard.stro...@jena.de wrote:
thank you for your instructions
I replaced WGS84 in qgsogrprovider.cpp with GEOGCS (QGIS master)
result stays the same: User-defined srs with towgs84 params is
Moin Bernhard,
On Mon, 26. Mar 2012 at 08:42:02 +0200, bernhard.stro...@jena.de wrote:
> thank you for your instructions
> I replaced WGS84 in qgsogrprovider.cpp with GEOGCS (QGIS master)
> result stays the same: User-defined srs with towgs84 params is applied
Just to be sure: You are using GDAL
Am 23.03.2012 13:32, schrieb Etienne Tourigny:
On Fri, Mar 23, 2012 at 5:26 AM, wrote:
I just tested with current trunk (compiled on OpenSUSE 64bit):
When I load
PROJCS["Transverse_Mercator",GEOGCS["GCS_bessel",DATUM["D_Deutsches_Hauptdreiecksnetz",SPHEROID["Bessel_1841",6377397.155,299.1528128
On Fri, Mar 23, 2012 at 5:26 AM, wrote:
> I just tested with current trunk (compiled on OpenSUSE 64bit):
> When I load
> PROJCS["Transverse_Mercator",GEOGCS["GCS_bessel",DATUM["D_Deutsches_Hauptdreiecksnetz",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIMEM["Greenwich",0],UNIT["Degree",0.01
Bernd Vogelgesang wrote:
So, the problem was now described thoroughly, but what are the
conclusions now?
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 pro
I just tested with current trunk (compiled on OpenSUSE 64bit):
When I load
PROJCS["Transverse_Mercator",GEOGCS["GCS_bessel",DATUM["D_Deutsches_Hauptdreiecksnetz",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIMEM["Greenwich",0],UNIT["Degree",0.017453292519943295]],PROJECTION["Transverse_Merca
Am Donnerstag 22 März 2012, 16:35:18 schrieb bernhard.stro...@jena.de:
>
> 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 n
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 f
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
So, the problem was now described thoroughly, but what are the conclusions now?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 doubl
15 matches
Mail list logo
