Can't correctly recognize the Geometry column

yeah, looks like wrong reader(?)

You could of course use geometryreplacer on the string.

@gio : No I didn't try the geometryreplacer Transformer.

@nielsgerrits : yes you're right. (I read a PosGIS column type from a PostgreSQL reader. My data are in Psotgresql database )

@jerome "PostGIS is an extension to the PostgreSQL object-relational database system which allows GIS (Geographic Information Systems) objects to be stored in the database. PostGIS includes support for GiST-based R-Tree spatial indexes, and functions for analysis and processing of GIS objects." - https://postgis.net/docs/manual-2.5/ 

PostgreSQL non spatial --> PostgreSQL reader

PostgreSQL spatial --> PostGIS reader

@gio What settings do you need to get the GeometryReplacer to work with the geometry column? When I read a 3D point (0.5,0.5,0.5) with the PostgreSQL reader the geometry value is:

0101000080000000000000E03F000000000000E03F000000000000E03F

Using the GeometryReplacer with WKB I get:

2019-09-04 06:50:08|   0.5|  0.0|WARN  |Invalid WKB encountered.

This is in 2019.1.1.0

0101000080000000000000E03F000000000000E03F000000000000E03F

2019-09-04 06:50:08|   0.5|  0.0|WARN  |Invalid WKB encountered.

@nielsgerrits I belive you need to set it to OGC Well Known Binary (not tested)

@itay Yeah thats what I thought but this gave me the "Invalid WKB encountered." warning.

oops...I see that now...

@nielsgerrits: I had installed the posgis extension with Postgresql and it worked well. But I didn't think it was necessary to change the type of Reader. I didn't know OGC WKB.

@jerome

Hi,

Geometryreplacer: Hex Encoded OGC Well Known Binary

(The letters in the string indicate it is hexadecimal.)

Greets

You're right . I used the wrong reader: my data was in a Posgresql database format but my column was in Postgis. So with the Postgis format I can now read my geometry data.

Thanks.

Learned something today, thanks!