Skip to main content
Solved

Getting an error that the Geometry Type: Unknown (0) and no geometry mapping entry found for 'esriFieldTypeString(200)' in metafile 'C:\\Program Files\\FME\\metafile\\ARCGISONLINEFEATURES.fmf? Has anyone run into this problem?


Forum|alt.badge.img

I am trying to write out some “UK Flood Security” polygons obtained from an API to my ArcGIS Online account as a new Feature Service. I keep getting an error that the “Geometry Type: Unknown (0) and

“No geometry mapping entry found for 'esriFieldTypeString(200)' in metafile 'C:\\Program Files\\FME\\metafile\\ARCGISONLINEFEATURES.fmf'.

A fatal error has occurred. Check the logfile above for details.”

The FME ArcGIS Online Writer has geometry set to Polygons. That is the data type I see coming from the API.

Best answer by nathanatsafe

This error is usually thrown when invalid characters inside attribute names are sent into the ArcGISOnline writer. Typically this would be characters such 

@ . {}
. We're looking into a little better error handling here, as the message is not explicit.

 

 

Hope this helps!

 

Nathan

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

4 replies

erik_jan
Contributor
Forum|alt.badge.img+17
  • Contributor
  • April 18, 2018

Seems like a case for Safe Support as the fmf file is an FME installed file.


Forum|alt.badge.img
  • Author
  • April 18, 2018

Thanks I already logged the incident with Safe Support. I was hoping for a quick fix. Maybe not.


nathanatsafe
Safer
Forum|alt.badge.img+7
  • Safer
  • Best Answer
  • April 20, 2018

This error is usually thrown when invalid characters inside attribute names are sent into the ArcGISOnline writer. Typically this would be characters such 

@ . {}
. We're looking into a little better error handling here, as the message is not explicit.

 

 

Hope this helps!

 

Nathan


Forum|alt.badge.img
  • Author
  • April 20, 2018
nathanatsafe wrote:

This error is usually thrown when invalid characters inside attribute names are sent into the ArcGISOnline writer. Typically this would be characters such 

@ . {}
. We're looking into a little better error handling here, as the message is not explicit.

 

 

Hope this helps!

 

Nathan

Thanks for your help Nathan. Thanks for the better error handling in the code. I'll be careful having odd characters (@,{}, 2) in the field names and not having duplicate field names such as "floodAreaid" and "floodAreaID".

 

 


Reply


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