FME Console for testing
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
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
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
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
asked 1 hour ago
user4906240user4906240
423212
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
fme fme-desktop fme-workbench
asked 1 hour ago
user4906240user4906240
423212
asked 1 hour ago
user4906240user4906240
423212
asked 1 hour ago
user4906240user4906240
423212
asked 1 hour ago
user4906240user4906240
423212
asked 1 hour ago
user4906240user4906240
423212
423212
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
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.
answered 35 mins ago
nielsgerritsnielsgerrits
2,1381623
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.
answered 14 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
});
}
});
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
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
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
answered 35 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.
answered 35 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.
answered 35 mins ago
nielsgerritsnielsgerrits
2,1381623
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.
answered 35 mins ago
nielsgerritsnielsgerrits
2,1381623
edited 22 mins ago
answered 35 mins ago
nielsgerritsnielsgerrits
2,1381623
answered 35 mins ago
nielsgerritsnielsgerrits
2,1381623
answered 35 mins ago
nielsgerritsnielsgerrits
2,1381623
2,1381623
add a comment |
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.
answered 14 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.
answered 14 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.
answered 14 mins ago
Mark IrelandMark Ireland
9,90732760
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.
answered 14 mins ago
Mark IrelandMark Ireland
9,90732760
answered 14 mins ago
Mark IrelandMark Ireland
9,90732760
answered 14 mins ago
Mark IrelandMark Ireland
9,90732760
answered 14 mins ago
Mark IrelandMark Ireland
9,90732760
9,90732760
add a comment |
add a comment |
Thanks for contributing an answer to Geographic Information Systems Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
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
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
