Edit - Geographic Information Systems Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Thanks Mark, It still requires us to expose the offending mapinfo format attribute (there's only one - mapinfo_type). As a better solution we settled on removing that attribute just before the tab writer rather than after the reader as in our case we had lots of readers but only one writer. Ideally if there's a conflict between the ffs geometry (correct) and the attribute of mapinfo_type (incorrect) it would be better if FME ignored mapinfo_type rather than dropping the geometry. Is this something that could be achieved within the MapInfo writer? Even as a tick box the user could control?

Vicky Bonwick
– Vicky Bonwick

2013-08-21 23:34:28 +00:00
Commented Aug 21, 2013 at 23:34

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »