Solved

Python FME API Documentation: Code example for raster creation could be wrong

Forum|Forum|7 years ago
May 29, 2018
7 replies
20 views

takashi

I'm afraid that this code in the "Getting Started Working with rasters" section is wrong.

        # creating the new FMERaster
        rasterProperties = fmeobjects.FMERasterProperties(numRows, numCols,
                                                          xCellOrigin, yCellOrigin,
                                                          xSpacing, ySpacing,
                                                          xOrigin, yOrigin,
                                                          xRotation, yRotation)

According to the API reference, the order of parameters should be:

        # creating the new FMERaster
        rasterProperties = fmeobjects.FMERasterProperties(numRows, numCols,
                                                          xSpacing, ySpacing,
                                                          xCellOrigin, yCellOrigin,
                                                          xOrigin, yOrigin,
                                                          xRotation, yRotation)

Best answer by fmelizard

Hi @takashi. I've passed this onto Development, I'll update when I receive a response. Thank you.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

+21

fmelizard
Safer
Best Answer
Forum|Forum|7 years ago
May 29, 2018

Hi @takashi. I've passed this onto Development, I'll update when I receive a response. Thank you.

Upvote

+21

fmelizard
Safer
Forum|Forum|7 years ago
May 29, 2018

Hi @takashi. I've passed this onto Development, I'll update when I receive a response. Thank you.

Hi @takashi. Yes you are correct, that's a good find. Development will correct the section to match the proper usage according to the API documentation.