Tables created with KNIME in PostgreSQL are not displayed in ArcGIS

KNIME Analytics Platform
1

Hello,

I hope this is just a minor problem. Using KNIME, I created several ETL worksheets that transfer data from a REST API to a PostgreSQL database. These are the tables named sen_XXXX.

There are also the tables named “std_” for master data.

I created all the “sen_xxx” tables manually in the PostgreSQL database. I couldn’t find the old “DB Table Creator” node at the time.

The “std_xxx” tables were created using the KNIME “DB Table Creator” node. See Figure 1. Yes, with the old node. The new one is unusable. I can’t figure it out.

grafik
grafik945×480 37.8 KB

Fig 1

Now that the data is in the database, I wanted to view and test it in ArcGIS Pro. Here’s what I noticed:

All “sen_xx” tables created in the database are displayed on the left in the catalog.

All „std_xx“ tables (created with KNIME) are not. pgAdmin is highlighted in yellow on the right.

It was used with the same login credentials; currently, only the SuperAdmin postgreSQL account is set up.

grafik
grafik945×881 202 KB

Does anyone have any idea what could be causing this?

Because one of the std_ tables contains the geometry.

Regards,
Patrik

1 Like
2

Hallo,

I found the problem.

Table names in lowercase only.

3 Likes
3

Copilot:

When using data from a PostgreSQL database with ArcGIS Pro, do table and field names always have to be lowercase?

In short: Yes — for ArcGIS Pro, table and field names in PostgreSQL must always be lowercase if you want ArcGIS Pro to recognize, read, and process them. This is not an optional convention, but a technical limitation of the ArcGIS-PostgreSQL integration.

ArcGIS Pro does not support PostgreSQL objects (tables, fields, schemas) whose names contain uppercase or mixed case.

The reason: PostgreSQL only handles case correctly if names are enclosed in quotation marks—and ArcGIS Pro does not support this.

Evidence from the Esri documentation:

ArcGIS Pro does not display tables with uppercase or mixed case because PostgreSQL requires double quotation marks, which ArcGIS does not support. Esri’s solution: Change table names to lowercase.

Patrik

2 Likes