GEOTRANSFORMER - Revision history

Ak3gseis: EPSG for UTM coordinates with 8 digits easting

2023-02-27T14:19:32Z

EPSG for UTM coordinates with 8 digits easting

← Older revision		Revision as of 14:19, 27 February 2023
Line 2:		Line 2:
	\|name_de=GEOTRANSFORMER		\|name_de=GEOTRANSFORMER
	\|name=GEOTRANSFORMER		\|name=GEOTRANSFORMER
	\|version=~~June 2022~~		\|version=February 2023
	\|version_descr=~~September 2022~~		\|version_descr=February 2023
	\|catchwords=coordinate transformation<br/>		\|catchwords=coordinate transformation<br/>
	coordinate system<br/>		coordinate system<br/>
Line 124:		Line 124:
	* Gauss-Krueger 3 degree / DHDN: EPSG 31492-31495 ( EPSG = 31490 + Streifennummer ), reused for datum BKG <50,3 degree N		* Gauss-Krueger 3 degree / DHDN: EPSG 31492-31495 ( EPSG = 31490 + Streifennummer ), reused for datum BKG <50,3 degree N
	* UTM / ETRS89 : EPSG 25828-25838 (EPSG = 25800 + zone number)		* UTM / ETRS89 : EPSG 25828-25838 (EPSG = 25800 + zone number)
			* UTM / ETRS89, 8 digits : 4647, 5649, 5650, 35832, 35833
	* UTM / ED50 : EPSG 23028-23038 (EPSG = 23000 + zone number)		* UTM / ED50 : EPSG 23028-23038 (EPSG = 23000 + zone number)
	* UTM / WGS84 (North) : EPSG 32601-32660 (EPSG = 32600 + zone number)		* UTM / WGS84 (North) : EPSG 32601-32660 (EPSG = 32600 + zone number)

Ak3gseis at 13:44, 10 October 2022

2022-10-10T13:44:48Z

← Older revision		Revision as of 13:44, 10 October 2022
Line 148:		Line 148:
	\|language=Fortran2003, C		\|language=Fortran2003, C
	\|add_software=NTv2 grids dhdn_to_etrs89_wsv_v1.gsb, stn_to_etrs89_wsv_v1.gsb and BETA2007.gsb		\|add_software=NTv2 grids dhdn_to_etrs89_wsv_v1.gsb, stn_to_etrs89_wsv_v1.gsb and BETA2007.gsb
	\|contact_original=~~[mailto:guntram.seiss@baw.de~~ G. Seiß] (main program, file I/O, libgeodesy)		\|contact_original=G. Seiß (main program, file I/O, libgeodesy)
	\|contact_maintenance=[mailto:pre.proghome@baw.de ~~Group~~ PRE]		\|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
	\|documentation=interactive dialog, self explaining<br/> $PROGHOME/examples/geotransformer<br/> $PROGHOME/examples/geotransformer/Anleitung_GEOTRANSFORMER.pdf <br/> Junkins, D.R. and Farley, S.A. (1995) '''N'''ational '''T'''ransformation '''v'''ersion '''2''' Users Guide, Geodetic Survey Division Geomatics Canada <br/>		\|documentation=interactive dialog, self explaining<br/> $PROGHOME/examples/geotransformer<br/> $PROGHOME/examples/geotransformer/Anleitung_GEOTRANSFORMER.pdf <br/> Junkins, D.R. and Farley, S.A. (1995) '''N'''ational '''T'''ransformation '''v'''ersion '''2''' Users Guide, Geodetic Survey Division Geomatics Canada <br/>
	Lott, Roger und OGP Geodesy Working Group (2015) Coordinate Conversions and Transformations including Formulas. [http://www.iogp.org/pubs/373-07-2.pdf Geomatics Guidance Note (IOGP Publication 373), 7. Part 2].<br/>		Lott, Roger und OGP Geodesy Working Group (2015) Coordinate Conversions and Transformations including Formulas. [http://www.iogp.org/pubs/373-07-2.pdf Geomatics Guidance Note (IOGP Publication 373), 7. Part 2].<br/>

Ak3gseis: Change contact_maintenance, language, version

2022-09-06T09:07:23Z

Change contact_maintenance, language, version

← Older revision		Revision as of 09:07, 6 September 2022
Line 2:		Line 2:
	\|name_de=GEOTRANSFORMER		\|name_de=GEOTRANSFORMER
	\|name=GEOTRANSFORMER		\|name=GEOTRANSFORMER
	\|version=~~October 2021~~		\|version=June 2022
	\|version_descr=~~June~~ 2022		\|version_descr=September 2022
	\|catchwords=coordinate transformation<br/>		\|catchwords=coordinate transformation<br/>
	coordinate system<br/>		coordinate system<br/>
Line 146:		Line 146:
	\|preprocessor=all programs wich use above listed file formats		\|preprocessor=all programs wich use above listed file formats
	\|postprocessor=all programs wich use above listed file formats		\|postprocessor=all programs wich use above listed file formats
	\|language=~~Fortran95~~, C		\|language=Fortran2003, C
	\|add_software=NTv2 grids dhdn_to_etrs89_wsv_v1.gsb, stn_to_etrs89_wsv_v1.gsb and BETA2007.gsb		\|add_software=NTv2 grids dhdn_to_etrs89_wsv_v1.gsb, stn_to_etrs89_wsv_v1.gsb and BETA2007.gsb
	\|contact_original=[mailto:guntram.seiss@baw.de G. Seiß] (main program, file I/O, libgeodesy)		\|contact_original=[mailto:guntram.seiss@baw.de G. Seiß] (main program, file I/O, libgeodesy)
	\|contact_maintenance=[mailto:~~guntram~~.~~seiss~~@baw.de ~~G. Seiß~~]		\|contact_maintenance=[mailto:pre.proghome@baw.de Group PRE]
	\|documentation=interactive dialog, self explaining<br/> $PROGHOME/examples/geotransformer<br/> $PROGHOME/examples/geotransformer/Anleitung_GEOTRANSFORMER.pdf <br/> Junkins, D.R. and Farley, S.A. (1995) '''N'''ational '''T'''ransformation '''v'''ersion '''2''' Users Guide, Geodetic Survey Division Geomatics Canada <br/>		\|documentation=interactive dialog, self explaining<br/> $PROGHOME/examples/geotransformer<br/> $PROGHOME/examples/geotransformer/Anleitung_GEOTRANSFORMER.pdf <br/> Junkins, D.R. and Farley, S.A. (1995) '''N'''ational '''T'''ransformation '''v'''ersion '''2''' Users Guide, Geodetic Survey Division Geomatics Canada <br/>
	Lott, Roger und OGP Geodesy Working Group (2015) Coordinate Conversions and Transformations including Formulas. [http://www.iogp.org/pubs/373-07-2.pdf Geomatics Guidance Note (IOGP Publication 373), 7. Part 2].<br/>		Lott, Roger und OGP Geodesy Working Group (2015) Coordinate Conversions and Transformations including Formulas. [http://www.iogp.org/pubs/373-07-2.pdf Geomatics Guidance Note (IOGP Publication 373), 7. Part 2].<br/>

Ak3gseis: Some new EPSG codes

2022-06-09T15:08:47Z

Some new EPSG codes

← Older revision		Revision as of 15:08, 9 June 2022
Line 2:		Line 2:
	\|name_de=GEOTRANSFORMER		\|name_de=GEOTRANSFORMER
	\|name=GEOTRANSFORMER		\|name=GEOTRANSFORMER
	\|version=~~February 2020~~		\|version=October 2021
	\|version_descr=~~March 2021~~		\|version_descr=June 2022
	\|catchwords=coordinate transformation<br/>		\|catchwords=coordinate transformation<br/>
	coordinate system<br/>		coordinate system<br/>
Line 9:		Line 9:
	Universal Transverse Mercator (UTM)<br/>		Universal Transverse Mercator (UTM)<br/>
	Universal Polar Stereographic <br/>		Universal Polar Stereographic <br/>
			Country Hamburg "Lagestatus 320" <br/>
	European Terrestrial Reference System 1989 (ETRS89)<br/>		European Terrestrial Reference System 1989 (ETRS89)<br/>
	world geodetic system 1984 (WGS84)<br/>		world geodetic system 1984 (WGS84)<br/>
Line 21:		Line 22:
	European petrol service group (EPSG)		European petrol service group (EPSG)
	\|shortdescription=This program transforms coordinates between different coordinate systems.		\|shortdescription=This program transforms coordinates between different coordinate systems.
	Currently implemented ~~coordinate systems~~ are:		Currently implemented map projections are:

	* Gauß-Krüger (stripe 2 to 5)		* Gauß-Krüger (stripe 2 to 5)
Line 28:		Line 29:
	* Rijksdatum (Netherlands)		* Rijksdatum (Netherlands)
	* local metric central projection		* local metric central projection
			* British National Grid

	Currently implemented geodetic 7-parameter transformations:		Currently implemented geodetic 7-parameter transformations:
Line 42:		Line 44:
	* Federal Intstitute for cartography und geodesy, latitudes <50,3 Grad N		* Federal Intstitute for cartography und geodesy, latitudes <50,3 Grad N
	* Amsterdam Datum		* Amsterdam Datum
			* OSGB36 (based on Airy 1830)
	* NTv2 grid shift methods GNTRANS-WSV (DHDN/STN -> ETRS89) and BETA2007 (DHDN -> ETRS89)		* NTv2 grid shift methods GNTRANS-WSV (DHDN/STN -> ETRS89) and BETA2007 (DHDN -> ETRS89)

Line 115:		Line 118:

	EPSG codes which are supported by libgeodesy are:		EPSG codes which are supported by libgeodesy are:
	* Gauss-Krueger 3 degree / DHDN: EPSG 31466-31469 (EPSG = 31464 + stripe number)		* Gauss-Krueger 3 degree / DHDN: EPSG 31466-31469 (EPSG = 31464 + stripe number), used with datum BKG >52,3 degree N
			* Gauss-Krueger / ETRS89, stripe 3 ("Lagestatus 320", Hamburg): EPSG 8395
	* Gauss-Krueger 3 degree / STN : EPSG 02397-02399, 05674-05675, 03838, 03829		* Gauss-Krueger 3 degree / STN : EPSG 02397-02399, 05674-05675, 03838, 03829
			* Gauss-Krueger 3 degree / DHDN: EPSG 31462-31465 ( EPSG = 31460 + Streifennummer ), reused for datum BKG between 50,3 degree N and 52,3 degree N
			* Gauss-Krueger 3 degree / DHDN: EPSG 31492-31495 ( EPSG = 31490 + Streifennummer ), reused for datum BKG <50,3 degree N
	* UTM / ETRS89 : EPSG 25828-25838 (EPSG = 25800 + zone number)		* UTM / ETRS89 : EPSG 25828-25838 (EPSG = 25800 + zone number)
	* UTM / ED50 : EPSG 23028-23038 (EPSG = 23000 + zone number)		* UTM / ED50 : EPSG 23028-23038 (EPSG = 23000 + zone number)
Line 123:		Line 129:
	* UPS / WGS84 : EPSG 32661 and 32761		* UPS / WGS84 : EPSG 32661 and 32761
	* RD Amersfoort New : EPSG 28992 and 7415		* RD Amersfoort New : EPSG 28992 and 7415
			* OSGB 1936/British National Grid: EPSG 27700
	* Geographic ETRS89 : EPSG 4258		* Geographic ETRS89 : EPSG 4258
	* Geographic WGS84 : EPSG 4326		* Geographic WGS84 : EPSG 4326
Line 129:		Line 136:
	* Geographic Amersfoort : EPSG 4289		* Geographic Amersfoort : EPSG 4289

	Some CRS, which are not supported ~~(like Gauß-Krüger combined with ETRS89),~~ can be realized ~~throug~~ the expert mode (basic knowledge of CRS's necessary).		Some CRS, which are not supported by an EPSG can be realized by using the expert mode (basic knowledge of CRS's necessary).

	It is recommended, to store the coordinate reference system as an EPSG code inside the basic datasets (raw data), if it is known. This can be done by the "magic comment" inside the most ASCII file types. Within file types, where storage is foreseen for an EPSG code, it should be placed there.		It is recommended, to store the coordinate reference system as an EPSG code inside the basic datasets (raw data), if it is known. This can be done by the magic comment"C CRS=#####" inside the most ASCII file types. Within file types, where storage is foreseen for an EPSG code, it should be placed there.

	Actual datasets should be stored with UTM/ETRS89 coordinates of the valid zone or in geographic coordinates (ETRS89 or WGS84) . Transforming older datasets with Gauß-Krüger coordinates into UTM/ETRS89 should be done preferably with the NTv2 method after GNTRANS-WSV. The transformation grid is valid only for German area including coastal waters. Coordinates outside this area must not be transformed by NTv2 but should be transformed using a valid Helmert transformation parameter set. In case of doubt the provider of the coordinate data shall provide the coordinate reference information.		Actual datasets should be stored with UTM/ETRS89 coordinates of the valid zone or in geographic coordinates (ETRS89 or WGS84) . Transforming older datasets with Gauß-Krüger coordinates into UTM/ETRS89 should be done preferably with the NTv2 method after GNTRANS-WSV. The transformation grid is valid only for German area including coastal waters. Coordinates outside this area must not be transformed by NTv2 but should be transformed using a valid Helmert transformation parameter set. In case of doubt the provider of the coordinate data shall provide the coordinate reference information.

Ak3gseis: Accuracy of coordinates in binary files

2021-03-16T12:36:40Z

Accuracy of coordinates in binary files

← Older revision		Revision as of 12:36, 16 March 2021
Line 2:		Line 2:
	\|name_de=GEOTRANSFORMER		\|name_de=GEOTRANSFORMER
	\|name=GEOTRANSFORMER		\|name=GEOTRANSFORMER
	\|version=~~July 2018~~		\|version=February 2020
	\|version_descr=~~July 2018~~		\|version_descr=March 2021
	\|catchwords=coordinate transformation<br/>		\|catchwords=coordinate transformation<br/>
	coordinate system<br/>		coordinate system<br/>
Line 106:		Line 106:
	* for some of the file types an optional export of all original coordinates as file type [[GEOPOS.DAT\|geopos.dat]] is possible. Those files can be used for control purpose and also in further pre processing programs e.g. [[TICLQ2]]. Please do not use this output option when transforming input files with a huge number of coordinates!!!		* for some of the file types an optional export of all original coordinates as file type [[GEOPOS.DAT\|geopos.dat]] is possible. Those files can be used for control purpose and also in further pre processing programs e.g. [[TICLQ2]]. Please do not use this output option when transforming input files with a huge number of coordinates!!!
	* file type 18 allows the user to define freely the columns, which have to be processed. A third column with altitude values can optionally be transformed during change of geodetic datum. Several coordinate pairs /tripel of a row may be transformed in a single step.		* file type 18 allows the user to define freely the columns, which have to be processed. A third column with altitude values can optionally be transformed during change of geodetic datum. Several coordinate pairs /tripel of a row may be transformed in a single step.

			All transformation algorithms use double precision floating point values for representation inside memory. Inside the two supported binaryfile formats single precision REAL values of the coordinates are stored. Theese formats should be used carefully, because spherical coordinates are written with unacceptable accuracy:

			* [[GITTER05.DAT and GITTER05.BIN\|gitter05.dat/bin]]: Creation of the ASCII formatted variant is recommended on output, and usage in future projects!
			* [[PROFIL05.BIN\|profil05.bin]]: Write this format only with projected coordinates (UTM, Gauß-Krüger). The accuracy of coordinate representation with projected coordinates is limited to 0,5-1m.

			Inside the supported ASCII file formats the accuracy of coordinate representation is choosen with respect to the reference system. This behavior ensures that accuracy is guaranteed to a certain limit, if spherical coordinates are written.

	EPSG codes which are supported by libgeodesy are:		EPSG codes which are supported by libgeodesy are:
Line 128:		Line 135:
	Actual datasets should be stored with UTM/ETRS89 coordinates of the valid zone or in geographic coordinates (ETRS89 or WGS84) . Transforming older datasets with Gauß-Krüger coordinates into UTM/ETRS89 should be done preferably with the NTv2 method after GNTRANS-WSV. The transformation grid is valid only for German area including coastal waters. Coordinates outside this area must not be transformed by NTv2 but should be transformed using a valid Helmert transformation parameter set. In case of doubt the provider of the coordinate data shall provide the coordinate reference information.		Actual datasets should be stored with UTM/ETRS89 coordinates of the valid zone or in geographic coordinates (ETRS89 or WGS84) . Transforming older datasets with Gauß-Krüger coordinates into UTM/ETRS89 should be done preferably with the NTv2 method after GNTRANS-WSV. The transformation grid is valid only for German area including coastal waters. Coordinates outside this area must not be transformed by NTv2 but should be transformed using a valid Helmert transformation parameter set. In case of doubt the provider of the coordinate data shall provide the coordinate reference information.

	Transforming coordinates is not a trivial task. Therefor the transformation result should be tested for plausibility and usability. Multible transformations forward and back can destroy accuracy of coordinates due to accumulation of numeric errors inside the basic algorithms.		Transforming coordinates is '''not a trivial task'''. Therefor the transformation result should be tested for plausibility and usability. Multible transformations forward and back can destroy accuracy of coordinates due to accumulation of numeric errors inside the basic algorithms.

	\|preprocessor=all programs wich use above listed file formats		\|preprocessor=all programs wich use above listed file formats

imported>Seiss Guntram: Inclusion of commanline input arguments

2018-11-08T14:13:03Z

Inclusion of commanline input arguments

← Older revision		Revision as of 14:13, 8 November 2018
Line 45:		Line 45:

	You can run the software in batch mode. There is no memory limit in amount of data to work with, because files are processed sequentially. To process 25 Mio. pairs of coordinates (Gauß-Krüger/DHDN <-> UTM/ETRS89) the software uses 280.68 minutes on a common INTEL CPU including Input/Output.		You can run the software in batch mode. There is no memory limit in amount of data to work with, because files are processed sequentially. To process 25 Mio. pairs of coordinates (Gauß-Krüger/DHDN <-> UTM/ETRS89) the software uses 280.68 minutes on a common INTEL CPU including Input/Output.

			Since November 2018 the application is able to get the user input via command line arguments. This mode of input is documented by the online help, which is called by typing '''''geotransformer -h'''''.


	Since May 2016 the software GEOTRANSFORMER is available without limits to its functionality on '''LINUX''' and '''WINDOWS''' driven INTEL based computers. It was validated on official test coordinates of the addressed systems. There exists a short "User Manual" for first time users.		Since May 2016 the software GEOTRANSFORMER is available without limits to its functionality on '''LINUX''' and '''WINDOWS''' driven INTEL based computers. It was validated on official test coordinates of the addressed systems. There exists a short "User Manual" for first time users.

imported>Seiss Guntram: remarks pointiing to the user manual

2018-07-06T09:50:26Z

remarks pointiing to the user manual

← Older revision		Revision as of 09:50, 6 July 2018
Line 46:		Line 46:
	You can run the software in batch mode. There is no memory limit in amount of data to work with, because files are processed sequentially. To process 25 Mio. pairs of coordinates (Gauß-Krüger/DHDN <-> UTM/ETRS89) the software uses 280.68 minutes on a common INTEL CPU including Input/Output.		You can run the software in batch mode. There is no memory limit in amount of data to work with, because files are processed sequentially. To process 25 Mio. pairs of coordinates (Gauß-Krüger/DHDN <-> UTM/ETRS89) the software uses 280.68 minutes on a common INTEL CPU including Input/Output.

	Since May 2016 the software GEOTRANSFORMER is available without limits to its functionality on '''LINUX''' and '''WINDOWS''' driven INTEL based computers. It was validated on official test coordinates of the addressed systems.		Since May 2016 the software GEOTRANSFORMER is available without limits to its functionality on '''LINUX''' and '''WINDOWS''' driven INTEL based computers. It was validated on official test coordinates of the addressed systems. There exists a short "User Manual" for first time users.

	The library '''libgeodesy''', which is used by this application, is used also in other applications to transform coordinates "on the fly". An "Application Programmer Interface" (API) called '''libgeodesyCAPI''' was supplied, to realize a port of the transformation functionality for MATLAB.		The library '''libgeodesy''', which is used by this application, is used also in other applications to transform coordinates "on the fly". An "Application Programmer Interface" (API) called '''libgeodesyCAPI''' was supplied, to realize a port of the transformation functionality for MATLAB.
Line 133:		Line 133:
	\|contact_original=[mailto:guntram.seiss@baw.de G. Seiß] (main program, file I/O, libgeodesy)		\|contact_original=[mailto:guntram.seiss@baw.de G. Seiß] (main program, file I/O, libgeodesy)
	\|contact_maintenance=[mailto:guntram.seiss@baw.de G. Seiß]		\|contact_maintenance=[mailto:guntram.seiss@baw.de G. Seiß]
	\|documentation=interactive dialog, self explaining<br/> $PROGHOME/examples/geotransformer <br/> Junkins, D.R. and Farley, S.A. (1995) '''N'''ational '''T'''ransformation '''v'''ersion '''2''' Users Guide, Geodetic Survey Division Geomatics Canada <br/>		\|documentation=interactive dialog, self explaining<br/> $PROGHOME/examples/geotransformer<br/> $PROGHOME/examples/geotransformer/Anleitung_GEOTRANSFORMER.pdf <br/> Junkins, D.R. and Farley, S.A. (1995) '''N'''ational '''T'''ransformation '''v'''ersion '''2''' Users Guide, Geodetic Survey Division Geomatics Canada <br/>
	Lott, Roger und OGP Geodesy Working Group (2015) Coordinate Conversions and Transformations including Formulas. [http://www.iogp.org/pubs/373-07-2.pdf Geomatics Guidance Note (IOGP Publication 373), 7. Part 2].<br/>		Lott, Roger und OGP Geodesy Working Group (2015) Coordinate Conversions and Transformations including Formulas. [http://www.iogp.org/pubs/373-07-2.pdf Geomatics Guidance Note (IOGP Publication 373), 7. Part 2].<br/>
	Bruijne, Arnoud de; van Buren, Joop; Kösters, Anton; van der Marel, Hans (2005): De geodetische referentiestelsels van Nederland. Geodetic reference frames in the Netherlands. Hg. v. Nederlandse Commissie voor Geodesie Netherlands Geodetic Commission. Delft. [http://www.ncgeo.nl/index.php?option=com_k2&view=item&id=2361:gs-43-a-de-bruijne-de-geodetische-referentiestelsels-van-nederland&Itemid=178&lang=nl Download here]. <br/>		Bruijne, Arnoud de; van Buren, Joop; Kösters, Anton; van der Marel, Hans (2005): De geodetische referentiestelsels van Nederland. Geodetic reference frames in the Netherlands. Hg. v. Nederlandse Commissie voor Geodesie Netherlands Geodetic Commission. Delft. [http://www.ncgeo.nl/index.php?option=com_k2&view=item&id=2361:gs-43-a-de-bruijne-de-geodetische-referentiestelsels-van-nederland&Itemid=178&lang=nl Download here]. <br/>

imported>Seiss Guntram: New format igeom.dat

2018-07-06T09:38:52Z

New format igeom.dat

← Older revision		Revision as of 09:38, 6 July 2018
Line 2:		Line 2:
	\|name_de=GEOTRANSFORMER		\|name_de=GEOTRANSFORMER
	\|name=GEOTRANSFORMER		\|name=GEOTRANSFORMER
	\|version=~~June 2017~~		\|version=July 2018
	\|version_descr=~~June 2017~~		\|version_descr=July 2018
	\|catchwords=coordinate transformation<br/>		\|catchwords=coordinate transformation<br/>
	coordinate system<br/>		coordinate system<br/>
Line 68:		Line 68:
	# world files which describe the georeference of an Image (typical file extensions are ''.pngw, .jpgw, .gifw'') or		# world files which describe the georeference of an Image (typical file extensions are ''.pngw, .jpgw, .gifw'') or
	# mesh of profiles (file type [[PROFIL05.BIN\|profil05.bin]]) or		# mesh of profiles (file type [[PROFIL05.BIN\|profil05.bin]]) or
	# CSV table ("comma seperated values") where columns are seperated by semicolon ( ; ).		# CSV table ("comma seperated values") where columns are seperated by semicolon ( ; )
			# indexed point data (index, x/longitude, y/latitude, z).

	\|outputfiles=		\|outputfiles=
Line 88:		Line 89:
	# world files which describe the georeference of an Image (typical file extensions are ''.pngw, .jpgw, .gifw'') or		# world files which describe the georeference of an Image (typical file extensions are ''.pngw, .jpgw, .gifw'') or
	# mesh of profiles (file type [[PROFIL05.BIN\|profil05.bin]]) and (optionally) files of type [[GEOPOS.DAT\|geopos.dat]] or		# mesh of profiles (file type [[PROFIL05.BIN\|profil05.bin]]) and (optionally) files of type [[GEOPOS.DAT\|geopos.dat]] or
	# CSV table ("comma seperated values") where columns are seperated by semicolon ( ; ).		# CSV table ("comma seperated values") where columns are seperated by semicolon ( ; )
			# indexed point data (index, x/longitude, y/latitude, z).

	\|methodology=		\|methodology=
Line 123:		Line 125:
	Actual datasets should be stored with UTM/ETRS89 coordinates of the valid zone or in geographic coordinates (ETRS89 or WGS84) . Transforming older datasets with Gauß-Krüger coordinates into UTM/ETRS89 should be done preferably with the NTv2 method after GNTRANS-WSV. The transformation grid is valid only for German area including coastal waters. Coordinates outside this area must not be transformed by NTv2 but should be transformed using a valid Helmert transformation parameter set. In case of doubt the provider of the coordinate data shall provide the coordinate reference information.		Actual datasets should be stored with UTM/ETRS89 coordinates of the valid zone or in geographic coordinates (ETRS89 or WGS84) . Transforming older datasets with Gauß-Krüger coordinates into UTM/ETRS89 should be done preferably with the NTv2 method after GNTRANS-WSV. The transformation grid is valid only for German area including coastal waters. Coordinates outside this area must not be transformed by NTv2 but should be transformed using a valid Helmert transformation parameter set. In case of doubt the provider of the coordinate data shall provide the coordinate reference information.

	Transforming coordinates is not a trivial task. Therefor the transformation result should be tested for plausibility and usability.		Transforming coordinates is not a trivial task. Therefor the transformation result should be tested for plausibility and usability. Multible transformations forward and back can destroy accuracy of coordinates due to accumulation of numeric errors inside the basic algorithms.

	\|preprocessor=all programs wich use above listed file formats		\|preprocessor=all programs wich use above listed file formats

imported>Seiss Guntram: added supported datum Amsterdam

2017-07-17T07:01:05Z

added supported datum Amsterdam

← Older revision		Revision as of 07:01, 17 July 2017
Line 41:		Line 41:
	* Federal Intstitute for cartography und geodesy, latitudes between 50,3 degrees N and 52,3 degrees N		* Federal Intstitute for cartography und geodesy, latitudes between 50,3 degrees N and 52,3 degrees N
	* Federal Intstitute for cartography und geodesy, latitudes <50,3 Grad N		* Federal Intstitute for cartography und geodesy, latitudes <50,3 Grad N
			* Amsterdam Datum
	* NTv2 grid shift methods GNTRANS-WSV (DHDN/STN -> ETRS89) and BETA2007 (DHDN -> ETRS89)		* NTv2 grid shift methods GNTRANS-WSV (DHDN/STN -> ETRS89) and BETA2007 (DHDN -> ETRS89)

imported>Seiss Guntram: remark to address libgeodesy and its MATLAB port

2017-07-14T07:53:33Z

remark to address libgeodesy and its MATLAB port

← Older revision		Revision as of 07:53, 14 July 2017
Line 46:		Line 46:

	Since May 2016 the software GEOTRANSFORMER is available without limits to its functionality on '''LINUX''' and '''WINDOWS''' driven INTEL based computers. It was validated on official test coordinates of the addressed systems.		Since May 2016 the software GEOTRANSFORMER is available without limits to its functionality on '''LINUX''' and '''WINDOWS''' driven INTEL based computers. It was validated on official test coordinates of the addressed systems.

			The library '''libgeodesy''', which is used by this application, is used also in other applications to transform coordinates "on the fly". An "Application Programmer Interface" (API) called '''libgeodesyCAPI''' was supplied, to realize a port of the transformation functionality for MATLAB.

	\|inputfiles=		\|inputfiles=