I'm reading an HTML table from a website and its bringing in both Real64 and Real32 numbers which I'm writing to a Geodatabase table. No matter if I specify column types of Float, Double, or Integer I get unwanted results where the number has a comma separator in the thousandth position (From table) - the resulting number adds a period in the output. Some of the numbers are dropping a zero when the number ends with zero: 8450 becomes 845. Has anyone experienced this before?
Question
Issue with Real64 or Real32 reformatting when writing to file a geodatabase.
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.

