I created a work space with reader and writer and transformers but at the end when I get the result there are many fields which are "Null". I also used the template in the FME hub and got the same result. that would be great if any one helps me with this issue.
Question
Hello, I would like to know how can I convert GML data to geodatabse without missing my Information in attribute table
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.
+22- Influencer
- 344 replies
Would yo be able to post a sample of the data and your workspace?
Maybe there is something wrong with the attribute mapping, but I can't know for sure without taking a look at it.
+22- Influencer
- 344 replies
It seems my workspace didnot upload. I uploaded my Workspace here again
As far as I can tell you are getting all those nulls because the source info doesn't have those values.
If you want to build a Dynamic process, you need to delete all the writer feature types except one, otherwise you are going to end with a lot of duplicates.
In the one you leave, remove all the User Attributes; because I guess you want the same ones as in the input.
As far as I can tell you are getting all those nulls because the source info doesn't have those values.
If you want to build a Dynamic process, you need to delete all the writer feature types except one, otherwise you are going to end with a lot of duplicates.
In the one you leave, remove all the User Attributes; because I guess you want the same ones as in the input.
But when I open the gml file in QGIS, I can see some values. I activated dynamic process because I wanted to be sure I will have all source info
As far as I can tell you are getting all those nulls because the source info doesn't have those values.
If you want to build a Dynamic process, you need to delete all the writer feature types except one, otherwise you are going to end with a lot of duplicates.
In the one you leave, remove all the User Attributes; because I guess you want the same ones as in the input.
I can also see the info with FME inspector but after converting all are "Null"
+22- Influencer
- 344 replies
As far as I can tell you are getting all those nulls because the source info doesn't have those values.
If you want to build a Dynamic process, you need to delete all the writer feature types except one, otherwise you are going to end with a lot of duplicates.
In the one you leave, remove all the User Attributes; because I guess you want the same ones as in the input.
You are right! I'm not sure what is going on. Have you tried using the CityGML Reader instead of the GML one?
As far as I can tell you are getting all those nulls because the source info doesn't have those values.
If you want to build a Dynamic process, you need to delete all the writer feature types except one, otherwise you are going to end with a lot of duplicates.
In the one you leave, remove all the User Attributes; because I guess you want the same ones as in the input.
Should I remove USER Attributes in Output or Input? and actually it does not matter Dynamic or Manual one. I just want to have those info
As far as I can tell you are getting all those nulls because the source info doesn't have those values.
If you want to build a Dynamic process, you need to delete all the writer feature types except one, otherwise you are going to end with a lot of duplicates.
In the one you leave, remove all the User Attributes; because I guess you want the same ones as in the input.
Yes, I have tried both and I got the same result
+22- Influencer
- 344 replies
As far as I can tell you are getting all those nulls because the source info doesn't have those values.
If you want to build a Dynamic process, you need to delete all the writer feature types except one, otherwise you are going to end with a lot of duplicates.
In the one you leave, remove all the User Attributes; because I guess you want the same ones as in the input.
In a Dynamic workspace, if you want the same attributes as in the input, you should delete the attributes in the Writer.
I honestly don't know what is going on. It should be simple, but I can't make it work. Sorry.
Maybe someone else has a better day than I
As far as I can tell you are getting all those nulls because the source info doesn't have those values.
If you want to build a Dynamic process, you need to delete all the writer feature types except one, otherwise you are going to end with a lot of duplicates.
In the one you leave, remove all the User Attributes; because I guess you want the same ones as in the input.
Thanks for your reply