Skip to main content
added 181 characters in body
Source Link

Regarding your Post Scriptum: You already use the right projection. CRS:84 is synonymous to the EPSG-Code: 4326, which is the Coordinate-Reference-System known as: WSG84.

You can always use EPSG-Codes instead of CRS-Names. EPSG-Codes are not so ambiguous in my opinion.

In your Example, the transform-srs-parameter (-t_srs) would look like this: -t_srs EPSG:4326

Oh, and by the way: you dont need to retransform, when your dataset already has the right projection. So using the set-SRS parameter (-s_srs) would be appropriate in your example.

Regarding your Post Scriptum: You already use the right projection. CRS:84 is synonymous to the EPSG-Code: 4326, which is the Coordinate-Reference-System known as: WSG84.

You can always use EPSG-Codes instead of CRS-Names. EPSG-Codes are not so ambiguous in my opinion.

In your Example, the transform-srs-parameter (-t_srs) would look like this: -t_srs EPSG:4326

Regarding your Post Scriptum: You already use the right projection. CRS:84 is synonymous to the EPSG-Code: 4326, which is the Coordinate-Reference-System known as: WSG84.

You can always use EPSG-Codes instead of CRS-Names. EPSG-Codes are not so ambiguous in my opinion.

In your Example, the transform-srs-parameter (-t_srs) would look like this: -t_srs EPSG:4326

Oh, and by the way: you dont need to retransform, when your dataset already has the right projection. So using the set-SRS parameter (-s_srs) would be appropriate in your example.

Source Link

Regarding your Post Scriptum: You already use the right projection. CRS:84 is synonymous to the EPSG-Code: 4326, which is the Coordinate-Reference-System known as: WSG84.

You can always use EPSG-Codes instead of CRS-Names. EPSG-Codes are not so ambiguous in my opinion.

In your Example, the transform-srs-parameter (-t_srs) would look like this: -t_srs EPSG:4326