Timeline for Using FME to convert a MapInfo TAB to GML with style attributes
Current License: CC BY-SA 3.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 3, 2014 at 3:20 | comment | added | MickyT | Let us continue this discussion in chat. | |
Sep 3, 2014 at 3:15 | comment | added | MickyT | No obviously you can't, but your transformer will have the attributes available. Hook up a logger and check. Whoever uses your transformer will need to create attributes in the output feature to take what your transformer is outputting. Transformers do not write features. | |
Sep 3, 2014 at 3:01 | comment | added | Coxy | The screenshot is a blank workspace proof of concept before I try to edit our actual transformer. Obviously I can't define attributes in the output in the latter. | |
Sep 3, 2014 at 2:57 | comment | added | MickyT | You need to define attributes in the writer's featuretype for the exposed/created attributes to go to otherwise they will not be written to the GML. Looking at your screenshot I would say none of your attributes are going through | |
Sep 3, 2014 at 2:52 | comment | added | Coxy | Thanks for the screenshot, but I need to do this in a transformer. Is there no way to accomplish this using the AttributeExposer/Creator building blocks? | |
Sep 3, 2014 at 2:48 | history | edited | MickyT | CC BY-SA 3.0 |
added 166 characters in body
|
Sep 3, 2014 at 2:40 | comment | added | MickyT | Once they are exposed you can treat them the same as any attribute in FME. I'll see try an add a screenshot to the answer | |
Sep 3, 2014 at 2:33 | comment | added | Coxy | Thanks for that. So to start with I should have an AttributeExposer to expose the pen color etc., then link that into an AttributeCreator? | |
Sep 3, 2014 at 2:23 | history | answered | MickyT | CC BY-SA 3.0 |