The Snowflake Spatial reader and writer modules provide FME with access to attribute data held in Snowflake database tables.
FME provides read and write access via Snowflake’s JDBC driver, which is bundled with FME.
Using Snowflake Spatial in FME
Spatial support for Snowflake is available in FME 2020.1 and up.
To learn more about Snowflake and FME, see:
- Using Geospatial Data in Snowflake
- FME Community: Using Snowflake Spatial in FME for Geospatial Data
Snowflake Spatial Product and System Requirements
|
Format |
Product |
Operating System |
||||
|---|---|---|---|---|---|---|
|
Reader/Writer |
FME Desktop License |
FME Server |
FME Cloud |
Windows |
Linux |
Mac |
|
Reader |
Available in FME Professional Edition and higher |
Yes |
Yes |
64-bit: Yes |
Yes |
Yes |
|
Writer |
Available in FME Database Edition and higher |
Yes |
Yes |
64-bit: Yes |
Yes |
Yes |
- More about FME Licenses and Subscriptions.
- More about FME Desktop Editions and Licenses.
Usage Notes
The performance of this format is dependent on the amount of memory allocated to the Java Virtual Machine (JVM). The following environment variable allows you to specify memory available to Java Plugins:
- FME_JVM_MIN_HEAP_SIZE: Initial heap size for initializing the JVM. If unset, the default value is 1024K.
This variable must be set in multiples of 1024 and greater than 1 MB. To indicate kilobytes, megabytes, or gigabytes, append k or K, m or M, or g or G, respectively. For example, any of these values is acceptable:
6291456
6144k
6m
- FME_JVM_MAX_HEAP_SIZE: Maximum heap size for initializing the JVM. If unset, the default value is 16384K.
This variable must be set in multiples of 1024 and greater than 2 MB. To indicate kilobytes, megabytes, or gigabytes, append k or K, m or M, or g or G, respectively. For example, any of these values is acceptable:
83886080
81920k
80m
Note: To pass additional parameters used by FME to the Java Virtual Machine, use the JAVA_TOOL_OPTIONS environment variable.