Skip to main content

Hello!

 

 

I like to read line geometry from a PostGIS DB and save it to an ESRI File GDB. When I check the translation via Inspector everything looks ok but when I save it to the file GDB the geometry suddenly looks very generalized. The same translation to shapefile works just fine. Any idea what I'm doing wrong? Thank you for your help.

Hi @kasparlov

Would you be able to confirm 'Simplify Geometry' is set to 'No' in the File Geodb writer parameters?

Kind regards,

Debbi


Hi Debbi,

I don't see this option when I open the parameter settings


Hi Debbi,

I don't see this option when I open the parameter settings

Debbi is using a different writer.

 

 

You are using the one that doesn't need ESRI products in the computer.

 

 


Debbi is using a different writer.

 

 

You are using the one that doesn't need ESRI products in the computer.

 

 

I do have ArcGIS 10.2 installed but still don't get the writer Debbi is using. Maybe because I'm using the 64-bit version of FME?

 

 


I do have ArcGIS 10.2 installed but still don't get the writer Debbi is using. Maybe because I'm using the 64-bit version of FME?

 

 

I'm afraid I have no idea. I only have FME 32-bits in the office.

 

 

The writer doesn't appear at all? Not even grey out? As far as I know, the writer Debbi is using is in every FME solution: https://www.safe.com/pricing/fme-desktop/

 

 


I'm afraid I have no idea. I only have FME 32-bits in the office.

 

 

The writer doesn't appear at all? Not even grey out? As far as I know, the writer Debbi is using is in every FME solution: https://www.safe.com/pricing/fme-desktop/

 

 

Seems it's a dependency issue. I'll try if it works if I install 32-bit FME.

 

 

 


Seems it's a dependency issue. I'll try if it works if I install 32-bit FME.

 

 

 

It should work if you install 32-bit FME.

 

If you want to continue using 64-bit FME, you will need to have 64-bit Background Geoprocessing 10.2 installed to use the File Geodatabase reader/writer as ArcGIS Desktop is a 32-bit product. Please see this article for more details: https://knowledge.safe.com/articles/315/geodatabase-formats-missing-greyed-out-or-have-unm.html

 

Please note the 64-bit Background Geoprocessing and ArcGIS Desktop versions must match (ie. both should be 10.2).

 


It should work if you install 32-bit FME.

 

If you want to continue using 64-bit FME, you will need to have 64-bit Background Geoprocessing 10.2 installed to use the File Geodatabase reader/writer as ArcGIS Desktop is a 32-bit product. Please see this article for more details: https://knowledge.safe.com/articles/315/geodatabase-formats-missing-greyed-out-or-have-unm.html

 

Please note the 64-bit Background Geoprocessing and ArcGIS Desktop versions must match (ie. both should be 10.2).

 

Thank you, I will check it out.

 

 


Thank you, I will check it out.

 

 

Sorry to dig this thread up. I installed 64-bit Background Geoprocessing with the correct version and I am now able to create a File GDB Writer but even with simplify geometry set to "no" I get the same generalized geometry. What's more now FME seems to crash during the translation (although the GDB is created and the programm is still working) and logs the attached exeption:

 

 

Any ideas?

 

error-log.txt

 


Sorry to dig this thread up. I installed 64-bit Background Geoprocessing with the correct version and I am now able to create a File GDB Writer but even with simplify geometry set to "no" I get the same generalized geometry. What's more now FME seems to crash during the translation (although the GDB is created and the programm is still working) and logs the attached exeption:

 

 

Any ideas?

 

error-log.txt

 

Hi @kasparlov

 

I think this new error requires closer investigation. Would you mind creating a case here https://www.safe.com/support/report-a-problem/" target="_blank"> https://www.safe.com/support/report-a-problem/? Please attach your workspace, data, and log file to your case.

 


Hi Debbi,

I don't see this option when I open the parameter settings

Unfortunately I'm handling confidential data but I could try to recreate the error with dummy data.

 

 


Reply