Kdtyjb

Can a Wizard take the Magic Initiate feat and select spells from the Wizard list?

Converting a text document with special format to Pandas DataFrame

When does Bran Stark remember Jamie pushing him?

Why did Bronn offer to be Tyrion Lannister's champion in trial by combat?

Why is one lightbulb in a string illuminated?

Why these surprising proportionalities of integrals involving odd zeta values?

Marquee sign letters

Coin Game with infinite paradox

What is the ongoing value of the Kanban board to the developers as opposed to management

How can I wire a 9-position switch so that each position turns on one more LED than the one before?

Should man-made satellites feature an intelligent inverted "cow catcher"?

Knights and Knaves question

Putting Ant-Man on house arrest

Proving inequality for positive definite matrix

Is Vivien of the Wilds + Wilderness Reclamation a competitive combo?

How to ask rejected full-time candidates to apply to teach individual courses?

Pointing to problems without suggesting solutions

Raising a bilingual kid. When should we introduce the majority language?

Etymology of 見舞い

Why does BitLocker not use RSA?

FME Console for testing

Why aren't road bike wheels tiny?

What is the definining line between a helicopter and a drone a person can ride in?

What's the difference between using dependency injection with a container and using a service locator?

FME Console for testing

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

1

I am using FME workbench 2018.1. I am working on a model where i have to apply lots of string operations on different feature classes and then merge them into one. I want to know if there is any console area where i can quickly test the function and see the output rather then running the whole FME again and again. I have been using inspector and logger but i am wondering if there is a console in FME.

fme fme-desktop fme-workbench

share|improve this question

asked 1 hour ago

user4906240user4906240

423212

add a comment | 

1

I am using FME workbench 2018.1. I am working on a model where i have to apply lots of string operations on different feature classes and then merge them into one. I want to know if there is any console area where i can quickly test the function and see the output rather then running the whole FME again and again. I have been using inspector and logger but i am wondering if there is a console in FME.

fme fme-desktop fme-workbench

share|improve this question

asked 1 hour ago

user4906240user4906240

423212

add a comment | 

I am using FME workbench 2018.1. I am working on a model where i have to apply lots of string operations on different feature classes and then merge them into one. I want to know if there is any console area where i can quickly test the function and see the output rather then running the whole FME again and again. I have been using inspector and logger but i am wondering if there is a console in FME.

fme fme-desktop fme-workbench

share|improve this question

asked 1 hour ago

user4906240user4906240

423212

share|improve this question

asked 1 hour ago

user4906240user4906240

423212

share|improve this question

asked 1 hour ago

user4906240user4906240

423212

asked 1 hour ago

user4906240user4906240

423212

asked 1 hour ago

user4906240user4906240

423212

2 Answers
2

active

oldest

votes

1

You probably want to use Feature Caching, introduced in FME 2018. This function caches all features at every transformer. This way you can run the proces from a specific transformer.

To enable Feature Caching click "Run", "Run With Feature Caching".

After a full run you can click a transformer and hit "Run From This".

A few additions:

• This can use a lot of temp disk space as there will be a lot of caching.


• Because all the read / write actions the performance might be slower.


• To overcome previous issues, transformers in closed bookmarks will not be cached separately, only at the bookmark output.


• In FME 2019 the "Run Workspace" (F5) button is defaulted to run with cached features, to re-run completely fresh use CTRL-F5. This works far more intuitive.

Also see this blog post and this article.

share|improve this answer

edited 41 mins ago

answered 55 mins ago

nielsgerritsnielsgerrits

2,1381623

add a comment | 

1

Feature Caching (as noted in another answer) is a good way to go here. Also use a Sampler or limit the number of features being read, as often you'll only want to test one or two features to ensure something is working, not the whole source dataset.

Also, if your transformations use regex then FME has a regex editor with built in tests. Access it through Open Regex Editor, wherever that is available:

Then you have a dialog in which to test expressions:

DateTime transformers have a similar dialog for testing expressions.

share|improve this answer

answered 34 mins ago

Mark IrelandMark Ireland

9,90732760

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "79"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f319553%2ffme-console-for-testing%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

1

You probably want to use Feature Caching, introduced in FME 2018. This function caches all features at every transformer. This way you can run the proces from a specific transformer.

To enable Feature Caching click "Run", "Run With Feature Caching".

After a full run you can click a transformer and hit "Run From This".

A few additions:

• This can use a lot of temp disk space as there will be a lot of caching.


• Because all the read / write actions the performance might be slower.


• To overcome previous issues, transformers in closed bookmarks will not be cached separately, only at the bookmark output.


• In FME 2019 the "Run Workspace" (F5) button is defaulted to run with cached features, to re-run completely fresh use CTRL-F5. This works far more intuitive.

Also see this blog post and this article.

share|improve this answer

edited 41 mins ago

answered 55 mins ago

nielsgerritsnielsgerrits

2,1381623

add a comment | 

1

You probably want to use Feature Caching, introduced in FME 2018. This function caches all features at every transformer. This way you can run the proces from a specific transformer.

To enable Feature Caching click "Run", "Run With Feature Caching".

After a full run you can click a transformer and hit "Run From This".

A few additions:

• This can use a lot of temp disk space as there will be a lot of caching.


• Because all the read / write actions the performance might be slower.


• To overcome previous issues, transformers in closed bookmarks will not be cached separately, only at the bookmark output.


• In FME 2019 the "Run Workspace" (F5) button is defaulted to run with cached features, to re-run completely fresh use CTRL-F5. This works far more intuitive.

Also see this blog post and this article.

share|improve this answer

edited 41 mins ago

answered 55 mins ago

nielsgerritsnielsgerrits

2,1381623

add a comment | 

You probably want to use Feature Caching, introduced in FME 2018. This function caches all features at every transformer. This way you can run the proces from a specific transformer.

To enable Feature Caching click "Run", "Run With Feature Caching".

After a full run you can click a transformer and hit "Run From This".

A few additions:

• This can use a lot of temp disk space as there will be a lot of caching.


• Because all the read / write actions the performance might be slower.


• To overcome previous issues, transformers in closed bookmarks will not be cached separately, only at the bookmark output.


• In FME 2019 the "Run Workspace" (F5) button is defaulted to run with cached features, to re-run completely fresh use CTRL-F5. This works far more intuitive.

Also see this blog post and this article.

share|improve this answer

edited 41 mins ago

answered 55 mins ago

nielsgerritsnielsgerrits

2,1381623

share|improve this answer

edited 41 mins ago

answered 55 mins ago

nielsgerritsnielsgerrits

2,1381623

answered 55 mins ago

nielsgerritsnielsgerrits

2,1381623

answered 55 mins ago

nielsgerritsnielsgerrits

2,1381623

1

Feature Caching (as noted in another answer) is a good way to go here. Also use a Sampler or limit the number of features being read, as often you'll only want to test one or two features to ensure something is working, not the whole source dataset.

Also, if your transformations use regex then FME has a regex editor with built in tests. Access it through Open Regex Editor, wherever that is available:

Then you have a dialog in which to test expressions:

DateTime transformers have a similar dialog for testing expressions.

share|improve this answer

answered 34 mins ago

Mark IrelandMark Ireland

9,90732760

add a comment | 

1

Feature Caching (as noted in another answer) is a good way to go here. Also use a Sampler or limit the number of features being read, as often you'll only want to test one or two features to ensure something is working, not the whole source dataset.

Also, if your transformations use regex then FME has a regex editor with built in tests. Access it through Open Regex Editor, wherever that is available:

Then you have a dialog in which to test expressions:

DateTime transformers have a similar dialog for testing expressions.

share|improve this answer

answered 34 mins ago

Mark IrelandMark Ireland

9,90732760

add a comment | 

Feature Caching (as noted in another answer) is a good way to go here. Also use a Sampler or limit the number of features being read, as often you'll only want to test one or two features to ensure something is working, not the whole source dataset.

Also, if your transformations use regex then FME has a regex editor with built in tests. Access it through Open Regex Editor, wherever that is available:

Then you have a dialog in which to test expressions:

DateTime transformers have a similar dialog for testing expressions.

share|improve this answer

answered 34 mins ago

Mark IrelandMark Ireland

9,90732760

share|improve this answer

answered 34 mins ago

Mark IrelandMark Ireland

9,90732760

answered 34 mins ago

Mark IrelandMark Ireland

9,90732760

answered 34 mins ago

Mark IrelandMark Ireland

9,90732760