Gsyfuy

How does signal strength relate to bandwidth?

How can I be pwned if I'm not registered on the compromised site?

Difference between 'stomach' and 'uterus'

Deal the cards to the players

Is there a math equivalent to the conditional ternary operator?

Reason why dimensional travelling would be restricted

Are there other characters in the Star Wars universe who had damaged bodies and needed to wear an outfit like Darth Vader?

Draw bounding region by list of points

How do I deal with being envious of my own players?

Called into a meeting and told we are being made redundant (laid off) and "not to share outside". Can I tell my partner?

If nine coins are tossed, what is the probability that the number of heads is even?

What could be a means to defeat a child’s nightmare?

If there are any 3nion, 5nion, 7nion, 9nion, 10nion, etc.

PTIJ: What’s wrong with eating meat and couscous?

Caulking a corner instead of taping with joint compound?

Practical reasons to have both a large police force and bounty hunting network?

Formatting a table to look nice

Split a number into equal parts given the number of parts

How to get the first element while continue streaming?

Why is my Contribution Detail Report (native CiviCRM Core report) not accurate?

Book about a time-travel war fought by computers

Correct physics behind the colors on CD (compact disc)?

3.5% Interest Student Loan or use all of my savings on Tuition?

Can we carry rice to Japan?

GDAL GetGeoTransform Documentation — Is there an oversight, or what am I misunderstanding?

What should I expect in this case?How can I fix badly specified geographic coordinate system with units in arc-seconds?GDAL/proj4 equirectangular projection coordinate system units assumed by OGRSpatialReference and GDALDataset::GetGeoTransform()?how to georeference my png using gdalSeeking Python GDAL documentation?Bad corner coordinates transforming SRTM *.hgt files to GRD format using gdal_translateASCII coordinates to geographic coordinates with GDAL?Georeferencing a PDF with pixels coordinates not in cornersProblem with transform in GRIB using GDALHow to calculate the image size knowing its coordinates and pixel size?

1

The documentation for GDALDataset::GetGeoTransform says some things that are rather confusing.

Fetches the coefficients for transforming between pixel/line (P,L) raster space, and projection coordinates (Xp,Yp) space.

Xp = padfTransform[0] + P*padfTransform[1] + L*padfTransform[2];

Yp = padfTransform[3] + P*padfTransform[4] + L*padfTransform[5];

In a north up image, padfTransform[1] is the pixel width, and padfTransform[5] is the pixel height.

The upper left corner of the upper left pixel is at position (padfTransform[0],padfTransform[3]).

The default transform is (0,1,0,0,0,1) and should be returned even when a CE_Failure error is returned, such as for formats that don't support transformation to projection coordinates.

If this is a matrix, it makes sense that Pixel_X is at 1,1 and Pixel_Y is at 2,2.

Here is my question:

So should the equation for Yp be:

Yp = padfTransform[3] + L*padfTransform[4] + P*padfTransform[5];

in which the positions of L and P are swapped?

Or if I am confused about something, can someone help me get unconfused?

gdal documentation

share|improve this question

edited 2 hours ago

user2856

30.1k258105

asked 3 hours ago

philologonphilologon

1205

add a comment | 

1

The documentation for GDALDataset::GetGeoTransform says some things that are rather confusing.

Fetches the coefficients for transforming between pixel/line (P,L) raster space, and projection coordinates (Xp,Yp) space.

Xp = padfTransform[0] + P*padfTransform[1] + L*padfTransform[2];

Yp = padfTransform[3] + P*padfTransform[4] + L*padfTransform[5];

In a north up image, padfTransform[1] is the pixel width, and padfTransform[5] is the pixel height.

The upper left corner of the upper left pixel is at position (padfTransform[0],padfTransform[3]).

The default transform is (0,1,0,0,0,1) and should be returned even when a CE_Failure error is returned, such as for formats that don't support transformation to projection coordinates.

If this is a matrix, it makes sense that Pixel_X is at 1,1 and Pixel_Y is at 2,2.

Here is my question:

So should the equation for Yp be:

Yp = padfTransform[3] + L*padfTransform[4] + P*padfTransform[5];

in which the positions of L and P are swapped?

Or if I am confused about something, can someone help me get unconfused?

gdal documentation

share|improve this question

edited 2 hours ago

user2856

30.1k258105

asked 3 hours ago

philologonphilologon

1205

add a comment | 

The documentation for GDALDataset::GetGeoTransform says some things that are rather confusing.

Fetches the coefficients for transforming between pixel/line (P,L) raster space, and projection coordinates (Xp,Yp) space.

Xp = padfTransform[0] + P*padfTransform[1] + L*padfTransform[2];

Yp = padfTransform[3] + P*padfTransform[4] + L*padfTransform[5];

In a north up image, padfTransform[1] is the pixel width, and padfTransform[5] is the pixel height.

The upper left corner of the upper left pixel is at position (padfTransform[0],padfTransform[3]).

The default transform is (0,1,0,0,0,1) and should be returned even when a CE_Failure error is returned, such as for formats that don't support transformation to projection coordinates.

If this is a matrix, it makes sense that Pixel_X is at 1,1 and Pixel_Y is at 2,2.

Here is my question:

So should the equation for Yp be:

Yp = padfTransform[3] + L*padfTransform[4] + P*padfTransform[5];

in which the positions of L and P are swapped?

Or if I am confused about something, can someone help me get unconfused?

gdal documentation

share|improve this question

edited 2 hours ago

user2856

30.1k258105

asked 3 hours ago

philologonphilologon

1205

Yp = padfTransform[3] + L*padfTransform[4] + P*padfTransform[5];

share|improve this question

edited 2 hours ago

user2856

30.1k258105

asked 3 hours ago

philologonphilologon

1205

share|improve this question

edited 2 hours ago

user2856

30.1k258105

asked 3 hours ago

philologonphilologon

1205

edited 2 hours ago

user2856

30.1k258105

edited 2 hours ago

user2856

30.1k258105

asked 3 hours ago

philologonphilologon

1205

asked 3 hours ago

philologonphilologon

1205

1 Answer
1

active

oldest

votes

3

No.

For a north up image with no rotation (i.e. padfTransform[4] == padfTransform[2] == 0), the formula simply becomes:

Xp = padfTransform[0] + P*padfTransform[1];

Yp = padfTransform[3] + L*padfTransform[5];



# Where P = column number and L = row number

i.e add the starting X (or Y) to the column (or row) number multiplied by the pixel width (or height).

The rotation terms may be what's tripping you up...? When a pixel is rotated, the Y skew needs to be considered when calculating the X map coordinate and the X skew needs to be considered when calculating the Y map coordinate. There's a quite detailed explanation in the wikipedia article on world files.

share|improve this answer

edited 1 hour ago

answered 2 hours ago

user2856user2856

30.1k258105

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  That there is rotation is what was tripping me up. So can you tell me what P and L stand for? I naively supposed that P was Pixel dimension and L was Line dimension (the lines between pixels). Yes, that is as foolish as a sophomore reasoning with senior. In that vein, what do those letters stand for?
  
  – philologon
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @philologon P is column number, and L is row number. These are "coordinates" on the raster image.
  
  – Mike T
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks. I now see it is right there in the documentation. I always find a way to embarrass myself in these kinds of things, usually by skimming too fast.
  
  – philologon
  2 hours ago
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "79"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f314654%2fgdal-getgeotransform-documentation-is-there-an-oversight-or-what-am-i-misund%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

3

No.

For a north up image with no rotation (i.e. padfTransform[4] == padfTransform[2] == 0), the formula simply becomes:

Xp = padfTransform[0] + P*padfTransform[1];

Yp = padfTransform[3] + L*padfTransform[5];



# Where P = column number and L = row number

i.e add the starting X (or Y) to the column (or row) number multiplied by the pixel width (or height).

The rotation terms may be what's tripping you up...? When a pixel is rotated, the Y skew needs to be considered when calculating the X map coordinate and the X skew needs to be considered when calculating the Y map coordinate. There's a quite detailed explanation in the wikipedia article on world files.

share|improve this answer

edited 1 hour ago

answered 2 hours ago

user2856user2856

30.1k258105

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  That there is rotation is what was tripping me up. So can you tell me what P and L stand for? I naively supposed that P was Pixel dimension and L was Line dimension (the lines between pixels). Yes, that is as foolish as a sophomore reasoning with senior. In that vein, what do those letters stand for?
  
  – philologon
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @philologon P is column number, and L is row number. These are "coordinates" on the raster image.
  
  – Mike T
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks. I now see it is right there in the documentation. I always find a way to embarrass myself in these kinds of things, usually by skimming too fast.
  
  – philologon
  2 hours ago
  

  
  
  
  

add a comment | 

3

No.

For a north up image with no rotation (i.e. padfTransform[4] == padfTransform[2] == 0), the formula simply becomes:

Xp = padfTransform[0] + P*padfTransform[1];

Yp = padfTransform[3] + L*padfTransform[5];



# Where P = column number and L = row number

i.e add the starting X (or Y) to the column (or row) number multiplied by the pixel width (or height).

The rotation terms may be what's tripping you up...? When a pixel is rotated, the Y skew needs to be considered when calculating the X map coordinate and the X skew needs to be considered when calculating the Y map coordinate. There's a quite detailed explanation in the wikipedia article on world files.

share|improve this answer

edited 1 hour ago

answered 2 hours ago

user2856user2856

30.1k258105

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  That there is rotation is what was tripping me up. So can you tell me what P and L stand for? I naively supposed that P was Pixel dimension and L was Line dimension (the lines between pixels). Yes, that is as foolish as a sophomore reasoning with senior. In that vein, what do those letters stand for?
  
  – philologon
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @philologon P is column number, and L is row number. These are "coordinates" on the raster image.
  
  – Mike T
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks. I now see it is right there in the documentation. I always find a way to embarrass myself in these kinds of things, usually by skimming too fast.
  
  – philologon
  2 hours ago
  

  
  
  
  

add a comment | 

No.

For a north up image with no rotation (i.e. padfTransform[4] == padfTransform[2] == 0), the formula simply becomes:

Xp = padfTransform[0] + P*padfTransform[1];

Yp = padfTransform[3] + L*padfTransform[5];



# Where P = column number and L = row number

i.e add the starting X (or Y) to the column (or row) number multiplied by the pixel width (or height).

The rotation terms may be what's tripping you up...? When a pixel is rotated, the Y skew needs to be considered when calculating the X map coordinate and the X skew needs to be considered when calculating the Y map coordinate. There's a quite detailed explanation in the wikipedia article on world files.

share|improve this answer

edited 1 hour ago

answered 2 hours ago

user2856user2856

30.1k258105

Xp = padfTransform[0] + P*padfTransform[1];

Yp = padfTransform[3] + L*padfTransform[5];



# Where P = column number and L = row number

share|improve this answer

edited 1 hour ago

answered 2 hours ago

user2856user2856

30.1k258105

answered 2 hours ago

user2856user2856

30.1k258105

answered 2 hours ago

user2856user2856

30.1k258105