No subject
Thu Jun 18 20:39:52 CEST 2009
=20
Regards,
=20
=20
Juan Lucas Dom=EDnguez Rubio
---
Prodevelop SL, Valencia (Espa=F1a)
Tlf.: 96.351.06.12 -- Fax: 96.351.09.68
http://www.prodevelop.es <http://www.prodevelop.es/>=20
---
________________________________
De: gvsig_internacional-bounces at listserv.gva.es en nombre de Simon =
Cropper (Botanicus Australia Pty Ltd)
Enviado el: lun 30/11/2009 1:36
Para: Users and Developers mailing list
Asunto: Re: [Gvsig_english] BIG problems with reprojecting AGD66 to =
GDA94
Juan Lucas,
Thanks for the feedback. So that others are able to follow the thread
and have the outcome at their disposal I will repeat what has been
stated so far both in this email and other that you have sent me.
*OBSERVATION A*
If you are using the reprojection tool and converting between systems in
the same datum then the tool will work.
This means if you are converting between AGD66 GEO <=3D> AGD66 AMG55 =
<=3D>
AGD66 VicGrid there are no problems.
This also applies for GDA94 GEO <=3D> GDA94 MGA55 <=3D> GDA94 VicGrid.
*OBSERVATION B*
It is necessary to 'transform' a dataset if you are changing between
datums. That is, moving between AGD66 to GDA94 or back the other way.
The regional transformation parameters for Victoria are published by the
Intergovernmental Committee of Surveying and Mapping in the GDA94
Technical manual Version 2.3, Amendment 1
(http://www.icsm.gov.au/icsm/gda/gdatm/gdav2.3.pdf).
The parameters *DO NOT WORK IF PLUGGED INTO THE REPROJECTION TOOL AS IS,
YOU NEED TO CHANGE THE SIGN (+/-) OF VARIOUS VALUES DEPENDING ON YOUR
DESIRED OUTCOME !* This is done by manually transforming the vector
files by typing in the following values under the various situation
specified.
The following values can be used to _correctly reproject one file to
another file_. Note you need to ensure the signs before the various
values are correct.
_*File2File: AGD66 =3D> GDA94*_
Dx =3D 119.353
Dy =3D 48.301
Dz =3D -139.484
Rx =3D -0.415
Ry =3D -0.26
Rx =3D -0.437
Sc =3D 0.613
_*File2File: GDA94 =3D> AGD66*_
Dx =3D -119.353
Dy =3D -48.301
Dz =3D 139.484
Rx =3D 0.415
Ry =3D 0.26
Rx =3D 0.437
Sc =3D -0.613
If you are _reprojecting of the fly_. The values are reversed.
*_View Projection=3DAGD66; File Projection=3DGDA94_*
Dx =3D 119.353
Dy =3D 48.301
Dz =3D -139.484
Rx =3D -0.415
Ry =3D -0.26
Rx =3D -0.437
Sc =3D 0.613
_*View Projection=3DGDA94; File Projection=3DAGD66*_
Dx =3D -119.353
Dy =3D -48.301
Dz =3D 139.484
Rx =3D 0.415
Ry =3D 0.26
Rx =3D 0.437
Sc =3D -0.613
What is frustrating is that these values need to be entered every time
you make a change. Very laborious and also prone to typographical =
errors.
The GDA Technical Manual indicates that this 'rough' transformation has
an accuracy of about 1 metre. The observations made by Juan Lucas
supports this claim. I also found that in points I checked the values
were <1m from the reference points created using the transformation grid
and that the transformation work for latitude-longitude as well as
northing-easting.
*OBSERVATION C*
Although a transformation grid is available, apparently in the correct
format, this grid does not work with gvSIG.
*OBSERVATION D*
Although I am not happy that the transformation grid does not work as my
reprojected points are not exactly the same as the reference points, the
question is whether I am in any better position if I use ArcView (the
pseudo-reference point at the moment). The answer is NO. I reprojected
the same source using ArcView and found that points in the two
reprojected files were <1cm apart. Not exactly the same but close enough
that the gvSIG measure tool did not register the difference (although it
did plot them in different locations if you zoomed in enough). I suspect
that the two points differ because the ArcView procedure uses an earlier
version of the Regional Transformation Parameters.
*MY SUGGESTIONS*
*Suggestion 1.* The reprojection tool should produce and error, or at
least a warning, if the source file and destination files are not in the
same datum letting the user know that it is necessary to select an
appropriate transformation. The impression you get when selecting a
source DATUM-COORDINATE combo and a destination DATUM-COORDINATE combo
that the system is automatically sorting this issue out.
*Suggestion 2.* Someone should look at the transformation grid produced
by the Intergovernmental Committee of Surveying and Mapping and figure
out why it does not work. gvSIG can't truly become an international
package if files apparently in the correct format don't work, and that
values (in this case rotation values published in the literature) have
to have their signs reversed in gvSIG to get the transformation to work
properly.
*Suggestion 3.* OK, a work around has been found but it is not simple or
quick. Manual values need to be entered, but these vary depending on the
situation (see above), and they need to be entered every time you
conduct a reprojection. It would be advantageous if manually entered
data could be saved and subsequently picked from a list. This would
speed up the process and avoid typographical errors resulting in the
incorrect reprojection of data.
Thanks Juan Lucas for your feedback on this issue.
Cheers Simon
Simon Cropper
Botanicus Australia Pty Ltd
PO Box 160, Sunshine, Victoria 3020.
P: 9311 5822. M: 041 830 3437.
mailto: scropper at botanicusaustralia.com.au
<mailto:scropper at botanicusaustralia.com.au>
web: www.botanicusaustralia.com.au <http://www.botanicusaustralia.com.au =
<http://www.botanicusaustralia.com.au/> >
Juan Lucas Dominguez Rubio wrote:
> Hello, Simon.
>=20
> I have done a test with a view in EPSG:4202 and two shapefiles (a
> target shapefile in EPSG:4202 and a source shapefile in EPSG:4283)
> extracted from your DBF. After adding the target shapefile (same
> projection as the view) I have added the source shp trying a variety
> of transformations. When you add it to the view, gvSIG lets you choose
> among eleven available "EPSG transformations" between those two EPSG
> codes. The one that gives me the best result is the first one:
>=20
> Transformation code: 1278
> Name: AGD66 to GDA94 (1)
> (we are actually doing the inverse transformation (GDA94 to AGD66) but
> the algorithm seems to be aware of this and does it well)
>=20
> I have measured the distance between the obtained coordinates
> (transformed source shp) and the expected coordinates (target
> shp) for 5 random points and I get these errors:
>=20
> 1.2 m
> 0.9 m
> 1.57 m
> 0.88 m
> 0.96 m
>=20
> I have also looked into some pdf files and I have found these
> parameters (AGD66 to GDA94) for Victoria and NSW:
>=20
> http://www.icsm.gov.au/icsm/gda/gdatm/gdav2.3.pdf
>=20
> Dx =3D -119.353
> Dy =3D -48.301
> Dz =3D 139.484
> Rx =3D -0.415
> Ry =3D -0.26
> Rx =3D -0.437
> Sc =3D -0.613
>=20
> Since we are doing the inverse transfomation, we should reverse the
> sign for each parameter, but I don't get good results.
>=20
> I have also read somewhere that in Australia and the US, the rotation
> parameters have the inverse meaning than in Europe (big ???), so I
> tried these parameters (reversing the ones above except for the
> rotation parameters):
>=20
> Dx =3D 119.353
> Dy =3D 48.301
> Dz =3D -139.484
> Rx =3D -0.415
> Ry =3D -0.26
> Rx =3D -0.437
> Sc =3D 0.613
>=20
> And indeed, I get significantly smaller errors for those 5 points:
>=20
> 0.7 m
> 0.15 m
> 0.75 m
> 0.8 m
> 0.25 m
>=20
> Those 7 parameters can be entered with the "manual transformation"
> option. I didn't get the grid to work either, sorry, although the
> format seems to be one supported by gvSIG. And I have not done any
> tests with non-geographical SRS.
>=20
> Regards,
>=20
> Juan Lucas Dom=EDnguez Rubio
> ---
> Prodevelop SL, Valencia (Espa=F1a)
> Tlf.: 96.351.06.12 -- Fax: 96.351.09.68
> http://www.prodevelop.es <http://www.prodevelop.es/> =
<http://www.prodevelop.es/>
> ---
>
> =
------------------------------------------------------------------------
> *De:* gvsig_internacional-bounces at listserv.gva.es en nombre de Simon
> Cropper (Botanicus Australia Pty Ltd)
> *Enviado el:* s=E1b 28/11/2009 7:36
> *Para:* Users and Developers mailing list
> *Asunto:* [Gvsig_english] BIG problems with reprojecting AGD66 to =
GDA94
>
> Hi Guys,
>
> I am having problems getting the reproject tool to work as expected =
with
> Australian Projections/Datums.
>
> If I create a shapefile in AGD66 then reproject the file to GDA94 =
using
> the reproject tool, the points are moved but only ~20m rather than 204
> metres northeast of the original position. If I use the resulting =
GDA94
> file in the AGD66 View and tell the program, it reprojects on the fly
> and the points overlap.
>
> This shows (a) that the reproject on the fly facility works, and (b) I
> appear to have chosen the wrong projection.
>
> The problem is I have tried reprojecting northing-eastings,
> latitude-longitude, in EPSG and ESRI format but can't get the correct
> reprojection. I have been using EPSG:4202 for AGD66 geographicals,
> EPSG:4283 for GDA94 geographicals, EPSG:20255 for AGD/ AMG zone 55 and
> EPSG:28355 for GDA94/MGA zone 55. I have also tried ESRI: 28355 and
> ESRI:20255 with no luck.
>
> I have even downloaded the transformation grid but not been able to =
get
> this to work either.
>
> Can anyone help?
>
> Attached is a list of points in a table that are released by the local
> government apparently created by FME. This has the comparable
> coordinates in 4 commonly used projections for 160 distinct points
> across Victoria.
>
> Can anyone get the correct setting and procedure to get these points =
to
> superimpose when reprojecting on the fly and for the reproject =
facility
> to work correctly?
>
> I have also included some useful links to help the more industrious =
and
> knowledgeable to figure out what is wrong.
>
> =
http://www.land.vic.gov.au/Land/lcnlc2.nsf/LinkView/9B33746B3D77040F4A256=
A250008E70A5B923E73477D6D65CA256E5F0013D73B
>
> http://www.icsm.gov.au/icsm/gda/gdatm/
>
> http://www.icsm.gov.au/icsm/gda/gdatm/gdav2.3.pdf
>
> Any help would be appreciated as I am trying to tick this off my list =
of
> things gvSIG can do, and was surprised to see when resulting =
reprojected
> files were compared to external reference documents they did not =
align.
>
> Any help would be greatly appreciated.
> --
>
> Cheers Simon
>
> Simon Cropper
> Botanicus Australia Pty Ltd
> PO Box 160, Sunshine, Victoria 3020.
> P: 9311 5822. M: 041 830 3437.
> mailto: scropper at botanicusaustralia.com.au
> <mailto:scropper at botanicusaustralia.com.au>
> web: www.botanicusaustralia.com.au
> <http://www.botanicusaustralia.com.au=20
> <http://www.botanicusaustralia.com.au/>>
>
> =
------------------------------------------------------------------------
>
> _______________________________________________
> Gvsig_internacional mailing list
> Gvsig_internacional at listserv.gva.es
> http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
> =20
_______________________________________________
Gvsig_internacional mailing list
Gvsig_internacional at listserv.gva.es
http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
------_=_NextPart_001_01CA7212.596F050A
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<HTML dir=3Dltr><HEAD><TITLE>Re: [Gvsig_english] BIG problems with =
reprojecting AGD66 to GDA94</TITLE>=0A=
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A=
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18372"></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText80579>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D3 face=3D"Times New =
Roman">Excuse me, Simon. The Australian GSB grid file does work in =
gvSIG:</FONT></DIV>=0A=
<DIV dir=3Dltr> </DIV>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D3 face=3D"Times New =
Roman"><A =
href=3D"http://www.youtube.com/watch?v=3DeDfgMFlUnWo">http://www.youtube.=
com/watch?v=3DeDfgMFlUnWo</A></FONT></DIV>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D3 face=3D"Times New =
Roman">(full screen recommended)</FONT></DIV>=0A=
<DIV dir=3Dltr> </DIV>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D3 face=3D"Times New =
Roman">From EPSG:4202 to EPSG:4283: choose the left radio button (Layer =
SRS - EPSG:4202) as seen in the video.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D3 face=3D"Times New =
Roman">From EPSG:4283 to EPSG:4202: choose the right radio button (View =
SRS - EPSG:4202).</FONT></DIV>=0A=
<DIV dir=3Dltr> </DIV>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D3 face=3D"Times New =
Roman">Regards,</FONT></DIV>=0A=
<DIV dir=3Dltr> </DIV>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D3 face=3D"Times New =
Roman"></FONT> </DIV></DIV>=0A=
<DIV dir=3Dltr id=3DidSignature25184>=0A=
<DIV><FONT size=3D2 face=3D"Courier New"><FONT size=3D3 face=3D"Times =
New Roman">Juan Lucas Dom=EDnguez Rubio<BR></FONT>---</FONT></DIV>=0A=
<DIV><FONT size=3D2 face=3D"Courier New"><FONT size=3D2 face=3D"Courier =
New"><FONT size=3D2 face=3D"Courier New">Prodevelop SL, Valencia =
(Espa=F1a)</FONT></DIV>=0A=
<DIV>=0A=
<DIV><FONT size=3D2 face=3D"Courier New">Tlf.: 96.351.06.12 -- Fax: =
96.351.09.68<BR></FONT><A href=3D"http://www.prodevelop.es/"><FONT =
size=3D2 face=3D"Courier =
New">http://www.prodevelop.es</FONT></A><BR><FONT size=3D2 =
face=3D"Courier New">---</FONT></DIV></FONT></DIV></FONT></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT size=3D2 face=3DTahoma><B>De:</B> =
gvsig_internacional-bounces at listserv.gva.es en nombre de Simon Cropper =
(Botanicus Australia Pty Ltd)<BR><B>Enviado el:</B> lun 30/11/2009 =
1:36<BR><B>Para:</B> Users and Developers mailing list<BR><B>Asunto:</B> =
Re: [Gvsig_english] BIG problems with reprojecting AGD66 to =
GDA94<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Juan Lucas,<BR><BR>Thanks for the feedback. So that =
others are able to follow the thread<BR>and have the outcome at their =
disposal I will repeat what has been<BR>stated so far both in this email =
and other that you have sent me.<BR><BR>*OBSERVATION A*<BR><BR>If you =
are using the reprojection tool and converting between systems in<BR>the =
same datum then the tool will work.<BR><BR>This means if you are =
converting between AGD66 GEO <=3D> AGD66 AMG55 =
<=3D><BR>AGD66 VicGrid there are no problems.<BR><BR>This also =
applies for GDA94 GEO <=3D> GDA94 MGA55 <=3D> GDA94 =
VicGrid.<BR><BR>*OBSERVATION B*<BR><BR>It is necessary to 'transform' a =
dataset if you are changing between<BR>datums. That is, moving between =
AGD66 to GDA94 or back the other way.<BR><BR>The regional transformation =
parameters for Victoria are published by the<BR>Intergovernmental =
Committee of Surveying and Mapping in the GDA94<BR>Technical manual =
Version 2.3, Amendment 1<BR>(<A =
href=3D"http://www.icsm.gov.au/icsm/gda/gdatm/gdav2.3.pdf">http://www.ics=
m.gov.au/icsm/gda/gdatm/gdav2.3.pdf</A>).<BR><BR>The parameters *DO NOT =
WORK IF PLUGGED INTO THE REPROJECTION TOOL AS IS,<BR>YOU NEED TO CHANGE =
THE SIGN (+/-) OF VARIOUS VALUES DEPENDING ON YOUR<BR>DESIRED OUTCOME !* =
This is done by manually transforming the vector<BR>files by typing in =
the following values under the various =
situation<BR>specified.<BR><BR>The following values can be used to =
_correctly reproject one file to<BR>another file_. Note you need to =
ensure the signs before the various<BR>values are =
correct.<BR><BR> _*File2File: AGD66 =3D> =
GDA94*_<BR> Dx =3D 119.353<BR> Dy =
=3D 48.301<BR> Dz =3D -139.484<BR> =
Rx =3D -0.415<BR> Ry =3D -0.26<BR> =
Rx =3D -0.437<BR> Sc =3D =
0.613<BR><BR> _*File2File: GDA94 =3D> =
AGD66*_<BR> Dx =3D -119.353<BR> Dy =
=3D -48.301<BR> Dz =3D 139.484<BR> =
Rx =3D 0.415<BR> Ry =3D 0.26<BR> Rx =
=3D 0.437<BR> Sc =3D -0.613<BR><BR><BR>If you are =
_reprojecting of the fly_. The values are =
reversed.<BR><BR> *_View Projection=3DAGD66; File =
Projection=3DGDA94_*<BR> Dx =3D =
119.353<BR> Dy =3D 48.301<BR> Dz =3D =
-139.484<BR> Rx =3D -0.415<BR> Ry =
=3D -0.26<BR> Rx =3D -0.437<BR> Sc =
=3D 0.613<BR><BR> _*View Projection=3DGDA94; File =
Projection=3DAGD66*_<BR> Dx =3D =
-119.353<BR> Dy =3D -48.301<BR> Dz =
=3D 139.484<BR> Rx =3D 0.415<BR> Ry =
=3D 0.26<BR> Rx =3D 0.437<BR> Sc =3D =
-0.613<BR><BR><BR>What is frustrating is that these values need to be =
entered every time<BR>you make a change. Very laborious and also prone =
to typographical errors.<BR><BR>The GDA Technical Manual indicates that =
this 'rough' transformation has<BR>an accuracy of about 1 metre. The =
observations made by Juan Lucas<BR>supports this claim. I also found =
that in points I checked the values<BR>were <1m from the reference =
points created using the transformation grid<BR>and that the =
transformation work for latitude-longitude as well =
as<BR>northing-easting.<BR><BR>*OBSERVATION C*<BR><BR>Although a =
transformation grid is available, apparently in the correct<BR>format, =
this grid does not work with gvSIG.<BR><BR>*OBSERVATION =
D*<BR><BR>Although I am not happy that the transformation grid does not =
work as my<BR>reprojected points are not exactly the same as the =
reference points, the<BR>question is whether I am in any better position =
if I use ArcView (the<BR>pseudo-reference point at the moment). The =
answer is NO. I reprojected<BR>the same source using ArcView and found =
that points in the two<BR>reprojected files were <1cm apart. Not =
exactly the same but close enough<BR>that the gvSIG measure tool did not =
register the difference (although it<BR>did plot them in different =
locations if you zoomed in enough). I suspect<BR>that the two points =
differ because the ArcView procedure uses an earlier<BR>version of the =
Regional Transformation Parameters.<BR><BR>*MY =
SUGGESTIONS*<BR><BR>*Suggestion 1.* The reprojection tool should produce =
and error, or at<BR>least a warning, if the source file and destination =
files are not in the<BR>same datum letting the user know that it is =
necessary to select an<BR>appropriate transformation. The impression you =
get when selecting a<BR>source DATUM-COORDINATE combo and a destination =
DATUM-COORDINATE combo<BR>that the system is automatically sorting this =
issue out.<BR><BR>*Suggestion 2.* Someone should look at the =
transformation grid produced<BR>by the Intergovernmental Committee of =
Surveying and Mapping and figure<BR>out why it does not work. gvSIG =
can't truly become an international<BR>package if files apparently in =
the correct format don't work, and that<BR>values (in this case rotation =
values published in the literature) have<BR>to have their signs reversed =
in gvSIG to get the transformation to =
work<BR>properly.<BR><BR>*Suggestion 3.* OK, a work around has been =
found but it is not simple or<BR>quick. Manual values need to be =
entered, but these vary depending on the<BR>situation (see above), and =
they need to be entered every time you<BR>conduct a reprojection. It =
would be advantageous if manually entered<BR>data could be saved and =
subsequently picked from a list. This would<BR>speed up the process and =
avoid typographical errors resulting in the<BR>incorrect reprojection of =
data.<BR><BR>Thanks Juan Lucas for your feedback on this =
issue.<BR><BR>Cheers Simon<BR><BR>Simon Cropper<BR>Botanicus Australia =
Pty Ltd<BR>PO Box 160, Sunshine, Victoria 3020.<BR>P: 9311 5822. M: 041 =
830 3437.<BR>mailto: scropper at botanicusaustralia.com.au<BR><<A =
href=3D"mailto:scropper at botanicusaustralia.com.au">mailto:scropper at botani=
cusaustralia.com.au</A>><BR>web: www.botanicusaustralia.com.au <<A =
href=3D"http://www.botanicusaustralia.com.au/">http://www.botanicusaustra=
lia.com.au</A>><BR><BR><BR><BR>Juan Lucas Dominguez Rubio =
wrote:<BR>> Hello, Simon.<BR>> <BR>> I have done a test =
with a view in EPSG:4202 and two shapefiles (a<BR>> target shapefile =
in EPSG:4202 and a source shapefile in EPSG:4283)<BR>> extracted from =
your DBF. After adding the target shapefile (same<BR>> projection as =
the view) I have added the source shp trying a variety<BR>> of =
transformations. When you add it to the view, gvSIG lets you =
choose<BR>> among eleven available "EPSG transformations" between =
those two EPSG<BR>> codes. The one that gives me the best result is =
the first one:<BR>> <BR>> Transformation code: 1278<BR>> =
Name: AGD66 to GDA94 (1)<BR>> (we are actually doing the inverse =
transformation (GDA94 to AGD66) but<BR>> the algorithm seems to be =
aware of this and does it well)<BR>> <BR>> I have measured =
the distance between the obtained coordinates<BR>> (transformed =
source shp) and the expected coordinates (target<BR>> shp) for =
5 random points and I get these errors:<BR>> <BR>> 1.2 =
m<BR>> 0.9 m<BR>> 1.57 m<BR>> 0.88 m<BR>> 0.96 =
m<BR>> <BR>> I have also looked into some pdf files and I =
have found these<BR>> parameters (AGD66 to GDA94) for Victoria and =
NSW:<BR>> <BR>> <A =
href=3D"http://www.icsm.gov.au/icsm/gda/gdatm/gdav2.3.pdf">http://www.ics=
m.gov.au/icsm/gda/gdatm/gdav2.3.pdf</A><BR>> <BR>> Dx =3D =
-119.353<BR>> Dy =3D -48.301<BR>> Dz =3D 139.484<BR>> Rx =3D =
-0.415<BR>> Ry =3D -0.26<BR>> Rx =3D -0.437<BR>> Sc =3D =
-0.613<BR>> <BR>> Since we are doing the inverse =
transfomation, we should reverse the<BR>> sign for each parameter, =
but I don't get good results.<BR>> <BR>> I have also read =
somewhere that in Australia and the US, the rotation<BR>> parameters =
have the inverse meaning than in Europe (big ???), so I<BR>> tried =
these parameters (reversing the ones above except for the<BR>> =
rotation parameters):<BR>> <BR>> Dx =3D 119.353<BR>> Dy =
=3D 48.301<BR>> Dz =3D -139.484<BR>> Rx =3D -0.415<BR>> Ry =3D =
-0.26<BR>> Rx =3D -0.437<BR>> Sc =3D 0.613<BR>> <BR>> =
And indeed, I get significantly smaller errors for those 5 =
points:<BR>> <BR>> 0.7 m<BR>> 0.15 m<BR>> 0.75 =
m<BR>> 0.8 m<BR>> 0.25 m<BR>> <BR>> Those 7 parameters =
can be entered with the "manual transformation"<BR>> option. I didn't =
get the grid to work either, sorry, although the<BR>> format seems to =
be one supported by gvSIG. And I have not done any<BR>> tests with =
non-geographical SRS.<BR>> <BR>> =
Regards,<BR>> <BR>> Juan Lucas Dom=EDnguez Rubio<BR>> =
---<BR>> Prodevelop SL, Valencia (Espa=F1a)<BR>> Tlf.: =
96.351.06.12 -- Fax: 96.351.09.68<BR>> <A =
href=3D"http://www.prodevelop.es/">http://www.prodevelop.es</A> <<A =
href=3D"http://www.prodevelop.es/">http://www.prodevelop.es/</A>><BR>&=
gt; ---<BR>><BR>> =
------------------------------------------------------------------------<=
BR>> *De:* gvsig_internacional-bounces at listserv.gva.es en nombre de =
Simon<BR>> Cropper (Botanicus Australia Pty Ltd)<BR>> *Enviado =
el:* s=E1b 28/11/2009 7:36<BR>> *Para:* Users and Developers mailing =
list<BR>> *Asunto:* [Gvsig_english] BIG problems with reprojecting =
AGD66 to GDA94<BR>><BR>> Hi Guys,<BR>><BR>> I am having =
problems getting the reproject tool to work as expected with<BR>> =
Australian Projections/Datums.<BR>><BR>> If I create a shapefile =
in AGD66 then reproject the file to GDA94 using<BR>> the reproject =
tool, the points are moved but only ~20m rather than 204<BR>> metres =
northeast of the original position. If I use the resulting GDA94<BR>> =
file in the AGD66 View and tell the program, it reprojects on the =
fly<BR>> and the points overlap.<BR>><BR>> This shows (a) that =
the reproject on the fly facility works, and (b) I<BR>> appear to =
have chosen the wrong projection.<BR>><BR>> The problem is I have =
tried reprojecting northing-eastings,<BR>> latitude-longitude, in =
EPSG and ESRI format but can't get the correct<BR>> reprojection. I =
have been using EPSG:4202 for AGD66 geographicals,<BR>> EPSG:4283 for =
GDA94 geographicals, EPSG:20255 for AGD/ AMG zone 55 and<BR>> =
EPSG:28355 for GDA94/MGA zone 55. I have also tried ESRI: 28355 =
and<BR>> ESRI:20255 with no luck.<BR>><BR>> I have even =
downloaded the transformation grid but not been able to get<BR>> this =
to work either.<BR>><BR>> Can anyone help?<BR>><BR>> =
Attached is a list of points in a table that are released by the =
local<BR>> government apparently created by FME. This has the =
comparable<BR>> coordinates in 4 commonly used projections for 160 =
distinct points<BR>> across Victoria.<BR>><BR>> Can anyone get =
the correct setting and procedure to get these points to<BR>> =
superimpose when reprojecting on the fly and for the reproject =
facility<BR>> to work correctly?<BR>><BR>> I have also included =
some useful links to help the more industrious and<BR>> knowledgeable =
to figure out what is wrong.<BR>><BR>> <A =
href=3D"http://www.land.vic.gov.au/Land/lcnlc2.nsf/LinkView/9B33746B3D770=
40F4A256A250008E70A5B923E73477D6D65CA256E5F0013D73B">http://www.land.vic.=
gov.au/Land/lcnlc2.nsf/LinkView/9B33746B3D77040F4A256A250008E70A5B923E734=
77D6D65CA256E5F0013D73B</A><BR>><BR>> <A =
href=3D"http://www.icsm.gov.au/icsm/gda/gdatm/">http://www.icsm.gov.au/ic=
sm/gda/gdatm/</A><BR>><BR>> <A =
href=3D"http://www.icsm.gov.au/icsm/gda/gdatm/gdav2.3.pdf">http://www.ics=
m.gov.au/icsm/gda/gdatm/gdav2.3.pdf</A><BR>><BR>> Any help would =
be appreciated as I am trying to tick this off my list of<BR>> things =
gvSIG can do, and was surprised to see when resulting =
reprojected<BR>> files were compared to external reference documents =
they did not align.<BR>><BR>> Any help would be greatly =
appreciated.<BR>> --<BR>><BR>> Cheers Simon<BR>><BR>> =
Simon Cropper<BR>> Botanicus Australia Pty Ltd<BR>> PO Box 160, =
Sunshine, Victoria 3020.<BR>> P: 9311 5822. M: 041 830 3437.<BR>> =
mailto: scropper at botanicusaustralia.com.au<BR>> <<A =
href=3D"mailto:scropper at botanicusaustralia.com.au">mailto:scropper at botani=
cusaustralia.com.au</A>><BR>> web: =
www.botanicusaustralia.com.au<BR>> =
<http://www.botanicusaustralia.com.au <BR>> <<A =
href=3D"http://www.botanicusaustralia.com.au/">http://www.botanicusaustra=
lia.com.au/</A>>><BR>><BR>> =
------------------------------------------------------------------------<=
BR>><BR>> _______________________________________________<BR>> =
Gvsig_internacional mailing list<BR>> =
Gvsig_internacional at listserv.gva.es<BR>> <A =
href=3D"http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacion=
al">http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional</=
A><BR>> <BR>_______________________________________________=
<BR>Gvsig_internacional mailing =
list<BR>Gvsig_internacional at listserv.gva.es<BR><A =
href=3D"http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacion=
al">http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional</=
A><BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01CA7212.596F050A--
More information about the Gvsig_internacional
mailing list