The suffixes listed are prefixed by the current <ReaderKeyword> in a mapping file. By default, the <ReaderKeyword> for the Google Maps Engine Raster reader is GOOGLEMAPSENGINERASTER_IN.
REFRESH_TOKEN
This directive specifies a refresh token for OAuth 2.0 authentication to Google Maps Engine. See the Reader Parameters.
Required/Optional
Required
Mapping File Syntax
<ReaderKeyword>_REFRESH_TOKEN <token>
Workbench Parameter
Refresh Token
PROJECT
This directive specifies the Google Maps Engine project that contains the raster asset of interest.
Required/Optional
Required
Mapping File Syntax
<ReaderKeyword>_PROJECT <ProjectNameOrID>
Workbench Parameter
Project
DEF
Each Google Maps Engine raster asset may be defined before it is read. The syntax of the definition is:
GOOGLEMAPSENGINERASTER_DEF <rasterNameOrId>
| Parameter | Contents |
|---|---|
| rasterNameOrId |
The recognized forms are:
If the raster asset does not exist, the writer will attempt to create it, provided that the user’s account is enabled for the Trusted Testers table creation API. |
SEARCH_ENVELOPE
Using the minimum and maximum x and y parameters, define a bounding box that will be used to filter the input features. Only features that interact with the bounding box are returned.
If all four coordinates of the search envelope are specified as 0, the search envelope will be disabled.
Mapping File Syntax
<ReaderKeyword>_SEARCH_ENVELOPE <minX> <minY> <maxX> <maxY>
Note: If all four coordinates of the search envelope are specified as zero, the search envelope will be disabled.
Required/Optional
Optional
Workbench Parameter
Minimum X, Minimum Y, Maximum X, Maximum Y
CLIP_TO_ENVELOPE
This directive specifies whether or not FME should clip features to the envelope specified in the SEARCH_ENVELOPE directive.
Values
YES | NO (default)
Mapping File Syntax
<ReaderKeyword>_CLIP_TO_ENVELOPE [yes | no]
Workbench Parameter
Clip To Envelope
EXPOSED_ATTRS
This directive allows the selection of format attributes to be explicitly added to the reader feature type.
This is similar to exposing format attributes on a reader feature type once it has been generated; however, it is even more powerful because it enables schema-driven applications other than Workbench to access and leverage these attributes as if they were explicitly on the schema as user attributes.
The result of picking a list of attributes is a comma-separated list of attribute names and types that will be added to the schema features. Currently all reader feature types will receive the same set of additional schema attributes for a given instance of the reader.
Required/Optional
Optional
Mapping File Syntax
Not applicable.
While it is possible for FME Objects applications to invoke this directive, the required format is not documented.
This directive is intended for use in our GUI applications (for example, Workbench) only.
Workbench Parameter
Additional Attributes to Expose