Combined Spatial and Non-Spatial Readers and Writers

Tandra Geraedts
Tandra Geraedts
  • Updated

Introduction

FME 2025.0 introduced combined spatial and non-spatial readers and writers. Readers such as Oracle Spatial Object and Oracle Non-Spatial are one reader called Oracle. A similar naming scheme is for the writer.

Having nearly identical readers and writers for spatial and non-spatial data was deemed to be confusing, especially for new users and users who are not working with spatial data. Combining spatial and non-spatial together will reduce errors in users selecting an incorrect format. 

The functionality of the readers and writers remains the same, and spatial data can be processed with the renamed reader and writer. 

This list has been updated to FME 2025.2 and will be updated as more readers and writers are combined and renamed.

Renamed Readers and Writers

Below is the table of the formats whose reader and writer have been combined into one. 

Old Format Name

Combined Format Name

Amazon Aurora Non-Spatial (MySQL compatible) Amazon Aurora (MySQL compatible)
Amazon Aurora Spatial (MySQL compatible)
IBM DB2 Non-Spatial (JDBC) IBM DB2 (JDBC)
Google Cloud SQL Spatial Google Cloud SQL (MySQL compatible)
Google Cloud SQL Non-Spatial
IBM Informix Non-Spatial (JDBC) IBM Informix (JDBC)
MariaDB/SkySQL (MySQL compatible) Spatial MariaDB MySQL (MySQL compatible)
MariaDB/SkySQL (MySQL compatible) Non-Spatial
Oracle Autonomous Non-Spatial Oracle Autonomous
Oracle Autonomous Spatial Object
Oracle Non-Spatial Oracle
Oracle Spatial Object
SAP HANA Non-Spatial SAP HANA
SAP HANA Spatial
SAP Cloud Platform HANA Service Non-Spatial SAP HANA Cloud
SAP Cloud Platform HANA Service Spatial
Snowflake Non-Spatial Snowflake
Snowflake Spatial
Microsoft SQL Server Non-Spatial Microsoft SQL Server
Microsoft SQL Server Spatial
Microsoft Azure SQL Database Non-Spatial Microsoft Azure SQL Database
Microsoft Azure SQL Database Spatial
Microsoft SQL Server Non-Spatial (JDBC) Microsoft SQL Server (JDBC)
Microsoft SQL Server Spatial (JDBC)
Microsoft Azure SQL Database Non-Spatial (JDBC) Microsoft Azure SQL Database (JDBC)
Microsoft Azure SQL Database Spatial (JDBC)
Teradata Non-Spatial Teradata
Teradata Spatial

Was this article helpful?

We're sorry to hear that.

Please tell us why.

As of January 14th, 2026, comments on knowledge base articles have been closed. To make sure questions don’t get missed and to enable more community support, we’ve moved discussions to the FME Community. If you have a question or a comment about this article, please create a new post or create a support ticket.