Skip to main content
Solved

Invalid Schema Directive Value - CSV Reader

  • July 24, 2014
  • 1 reply
  • 5 views

Forum|alt.badge.img
I'm getting the following message:

 

 

CSV Reader: Invalid schema directive value 'number<comma>15<comma>0<comma>number<comma>4<comma>...The expected syntax is SCHEMA <typename1>,<width1>,<precision1>,...<typenameN>,<widthN>,<precisionN>.  Using schema scanner instead

 

 

As you can see, no typenames are being furnished.  This happens reading a pipe- or tab-delimited CSV file.  User Attributes are parsed and assigned correctly when opening the reader properties, so I don't understand the error.

 

 

Also why all the <comma> indicators instead of a literal ','?

 

 

Later on, I'm getting many attribute could not be written errors associated with certain attributes. The containing feature has been dropped...outputs, writing to a file geodatabase as a dynamic writer.

 

 

Where can I go from here and/or what am I doing wrong with my simple csv -> file geodatabase translation?

Best answer by gio

Did you change delimiter to TAB when u added the csv reader? (comma is standard setting) I can't imagine you did'nt, but have to ask.

 

 

comma is just the reporting (try reading a fme report on a tcl script...lol)

 

 

If i choose tab as separator and the csv is acutally tab separated, everything works fine.

 

View original
Did this help you find an answer to your question?
<strong>This post is closed to further activity.</strong><br /> It may be a question with a best answer, an implemented idea, or just a post needing no comment.<br /> If you have a follow-up or related question, please <a href="https://community.safe.com/topic/new">post a new question or idea</a>.<br /> If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

gio
Contributor
Forum|alt.badge.img+15
  • Contributor
  • Best Answer
  • July 25, 2014
Did you change delimiter to TAB when u added the csv reader? (comma is standard setting) I can't imagine you did'nt, but have to ask.

 

 

comma is just the reporting (try reading a fme report on a tcl script...lol)

 

 

If i choose tab as separator and the csv is acutally tab separated, everything works fine.

 


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