Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi francois,
All the screenshots now :
regards,
All the screenshots now :
regards,
Hi Jérôme,
You can not handle Geometric objects with tPostgreSQL* components.
Indeed, you should use sPostgis* components to handle geometry columns in SDI 1.2.0.
In the new upcoming release, the 1.3.0, you will be able to use tPostgreSQL* components using the "Geometry" type for your geometry columns.
So for now, you will have to wait until 1.3.0 or to switch to sPostgis* components.
FYI, the 1.3.0 release is coming very soon!
Cheers,
Mathieu
You can not handle Geometric objects with tPostgreSQL* components.
Indeed, you should use sPostgis* components to handle geometry columns in SDI 1.2.0.
In the new upcoming release, the 1.3.0, you will be able to use tPostgreSQL* components using the "Geometry" type for your geometry columns.
So for now, you will have to wait until 1.3.0 or to switch to sPostgis* components.
FYI, the 1.3.0 release is coming very soon!
Cheers,
Mathieu
Hi Mathieu,
Thanks for your help,
indeed, if I use the sPostgisInput component in the place of tPostgresInput component,
the shapefile is created.
But for this, i must specify that my geometry field (wkb_geometry) is an object type in the place of an string type.
It is the Retrieve Shema command that initialize my geometry field like an string type, why not
like an object type ?
I am impatient to test the 1.3.0 release...
regards,
Thanks for your help,
indeed, if I use the sPostgisInput component in the place of tPostgresInput component,
the shapefile is created.
But for this, i must specify that my geometry field (wkb_geometry) is an object type in the place of an string type.
It is the Retrieve Shema command that initialize my geometry field like an string type, why not
like an object type ?
I am impatient to test the 1.3.0 release...
regards,
Hello,
Yep in SDI 1.2 **ALL** Geometry should be define as a "the_geom" column name of type "Object". Object is a generic Talend Type useful to do more or less everything :/. That's why in 1.3, we added a new Talend type called "Geometry" which has to be used for all your geometry columns.
Columns names are not important.
That point also changed in SDI 1.3 as we defined how to map a postgres geometry type to a Talend geometry type and should be supported in all metadata discovery wizard in Talend. Test and comments are welcomed. If you found any side effects on classical Talend component do not hesitate to post on the forum in order to check that this new Geometry type is not causing trouble in more generic talend process.
Go online http://spatialdataintegrator.org
Cheers.
Francois
But for this, i must specify that my geometry field (wkb_geometry) is an object type in the place of an string type.
Yep in SDI 1.2 **ALL** Geometry should be define as a "the_geom" column name of type "Object". Object is a generic Talend Type useful to do more or less everything :/. That's why in 1.3, we added a new Talend type called "Geometry" which has to be used for all your geometry columns.
Columns names are not important.
It is the Retrieve Shema command that initialize my geometry field like an string type, why not
like an object type ?
That point also changed in SDI 1.3 as we defined how to map a postgres geometry type to a Talend geometry type and should be supported in all metadata discovery wizard in Talend. Test and comments are welcomed. If you found any side effects on classical Talend component do not hesitate to post on the forum in order to check that this new Geometry type is not causing trouble in more generic talend process.
regards,
Go online http://spatialdataintegrator.org
Cheers.
Francois
Hi francois,
i had downloaded the new version,
and indeed version 1.3.0 brings the solution to the points evoked previously.
regards,
i had downloaded the new version,
and indeed version 1.3.0 brings the solution to the points evoked previously.
regards,