Skip to main content

Lots of great stuff at the World Tour events and people using FME to resolve interesting data challenges. What did you learn about FME, this week, that you didn't know before?

FME 2016.1 Data Inspector Point and Icon styles = Winner!


@mark_1spatial beat me to it, I was showing off the 2016.1 RC during a training course and noticed the new styling options.


of course the viewer had (albeit limited) point icons for ages.


of course the viewer had (albeit limited) point icons for ages.

Change colour of the point but since 2016.1 you can now choose a symbol icon, plus colour, plus size (slightly limited).


You don't know the Universalviewer ??

It's been around for quite a while..

...

:)


i learned

- not to send empty or missing attribute to a Autocad fanned out writer.

- that (multiple)conditional featuremerging does not behave well or predictable..

- conditonal filtering in rasterexpressions does not work. Though one is allowed to "acces" it..


You don't know the Universalviewer ??

It's been around for quite a while..

...

:)

I haven't used it it ages I will never use it now! :)


i learned

- not to send empty or missing attribute to a Autocad fanned out writer.

- that (multiple)conditional featuremerging does not behave well or predictable..

- conditonal filtering in rasterexpressions does not work. Though one is allowed to "acces" it..

Sounds like a bad week. @gio are you able to send in a support ticket on these with more details. The first one I'd expect you'd just get datasets with no name (reflecting the attribute having no value). The second one I presume is just chained FeatureMergers, which should work well -- if not that is a problem and we'd like to know. The last sounds like a GUI issue and I'll ask around about that. Sorry its been a string of downers.


FeatureWriter transformer is the best invention after the wheel


You don't know the Universalviewer ??

It's been around for quite a while..

...

:)

I miss the Universal Viewer. Hope the inspector's name will be changed back one day to Universal Viewer.


FeatureWriter transformer is the best invention after the wheel

Indeeeed. FME workspces are not finishing anymore... now, the chain is limitless ;)


So handy filling a testing extension into the "Search Envelope" as Published Parameter and link to them with the rest of Readers. So, you'll have framed your data, in my case, for testing a huge FME workspace.

;)

My new workspace. Something is missing


You don't know the Universalviewer ??

It's been around for quite a while..

...

:)

somehow the DataInspector and Universal viewer have co-existed for a long time...fme2015 still have them both.

no more in FME 2016 i suppose?


somehow the DataInspector and Universal viewer have co-existed for a long time...fme2015 still have them both.

no more in FME 2016 i suppose?

Couldn't find it in 2016.1 at least, so looks to be gone...


I found:

  • XQuery is much more powerful to manipulate XML than I thought before.

  • FME 2016.1 is more friendly to non-ascii characters than FME 2016.0.

  • There are cases that palette operations are helpful to manipulate color of a raster efficiently.
  • Bookmark Navigation is useful to move quickly to a specific part of large workspace.

  • Hidden Connections within a Bookmark might be one of good uses of them.


My new workspace. Something is missing

The cables ! It has become wireless.


somehow the DataInspector and Universal viewer have co-existed for a long time...fme2015 still have them both.

no more in FME 2016 i suppose?

Just a matter of renaming it I guess.


FeatureWriter transformer is the best invention after the wheel

Completely agree! Database read-write model now possible in 1 workbench instead of 3.


Couldn't find it in 2016.1 at least, so looks to be gone...

Well... fmeview.exe is still in the installation folder, if you really can't do without it. But it too is likely to disappear soon, and you really should be using the Inspector now instead.


That you can have to much data on FME server for a backup to run....

@FMELizard


that a failed called workspace (called by a workspacerunner) does not yield a log...


Reply