Skip to main content
Solved

Bad SRID convert while converting postGIS to oracle spatial

  • November 14, 2017
  • 3 replies
  • 35 views
M
Forum|alt.badge.img

I have a GIS application using postGIS database . For some reasons i have to migrate from postGIS to oracle . And i got familiar with your awesome software

 

Migrating from a shape file to oracle is all right but when i am trying to convert data from postGIs to oracle, i have issues in converting geometry data , actually the source SRID is 4326 but when the convert is done , the geometry column is not in the right SRID and GeoServer is unable to load geometry data .

 

I tried different methods in converting data such as

 

1- select SRID from source and

 

2- using EPSG 4326 on Oracle writer SRID but i still have the same problem

Best answer by mandinariman

the problem solved

i find out that my postgis source data was in 900913 format that is not an official format of SRID and this is why FME Software couldn't convert properly

i converted my geometry data to 4326 format using script below

update planet_osm_roads set way = ST_Transform(way, 4326)

and now when i convert my postgis to oracle by FME everything is all right.

View original
Did this help you find an answer to your question?

3 replies

erik_jan
Contributor
Forum|alt.badge.img+17
  • erik_janContributor
  • Contributor
  • November 14, 2017

The best way of doing this is inserting a record for the table in the MDSYS.USER_SDO_GEOM_METADATA table in Oracle, containing the right SRID.

If you create the table using FME, you can do that using the parameters section on the table.

M
Forum|alt.badge.img
erik_jan wrote:

The best way of doing this is inserting a record for the table in the MDSYS.USER_SDO_GEOM_METADATA table in Oracle, containing the right SRID.

If you create the table using FME, you can do that using the parameters section on the table.

thanks dear @erik_jan

 

yes i can set SRID to 4326 and the SRID section of geometry data will change from null to 4326 like data below

 

before:

 

{2002,4326,null,{1,2,1},699956.85,3853005.3,5700031.07,3852978.66,5700057.01,3852973.81,5700069.08,3852975.18,5700082.09,3852980.66,5700092.13,3852987.72,5700099.65,3852995.49,5700105.59,3853004.61,5700110.37,3853017.6,5700110.83,3853031.29,5700106.04,3853042.69,5700096.69,3853055.02,5700078.43,3853068.69,5700010.33,3853109.78}}

 

after

 

{2002,4326,null,{1,2,1},699956.85,3853005.3,5700031.07,3852978.66,5700057.01,3852973.81,5700069.08,3852975.18,5700082.09,3852980.66,5700092.13,3852987.72,5700099.65,3852995.49,5700105.59,3853004.61,5700110.37,3853017.6,5700110.83,3853031.29,5700106.04,3853042.69,5700096.69,3853055.02,5700078.43,3853068.69,5700010.33,3853109.78}}

 

but the problem is in vector data that doesnt't seem to be converted correctly cause i know the correct format of 4326 is like sample below

 

xx.xxxxxxx
M
Forum|alt.badge.img
  • mandinariman
  • Author
  • Best Answer
  • December 26, 2017

the problem solved

i find out that my postgis source data was in 900913 format that is not an official format of SRID and this is why FME Software couldn't convert properly

i converted my geometry data to 4326 format using script below

update planet_osm_roads set way = ST_Transform(way, 4326)

and now when i convert my postgis to oracle by FME everything is all right.

Reply


Helpful Members This Week

Community Stats

30,971
Posts
117,398
Replies
38,758
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.