Configuring lidR catalog to save files with same filename?
I'm trying to learn how to use the options of catalog() within the lidR package in R. I'd like to save directly the processed files, for example, using grid_terrain() function over a catalog and save files keeping the filename of the original LAZ/LAS file.
As you can see in the guide of the package, catalog has the option of save the file using things like {XBOTTOM}_{ID}:
# Internal engine will not return results into R. Instead it will write results in files.
opt_output_files(ctg) <- "/path/to/folder/templated_filename_{XBOTTOM}_{ID}
I'd like to save the files using the same filename, but, I don't know how to configure that part with {} in the opt_output_files() option. I tried several things like, for instance: opt_output_files(cat) <- paste0(output,"/{data$filename}") but, it doesn't work.
lasdir <- "C:/lazfiles"
output <- "C:/output"
cat <- catalog(lasdir)
lasfiles <- cat@data$filename #with this you can see the filenames
opt_progress(cat) <- TRUE
opt_output_files(cat) <- paste0(output,"/{data$filename}")
opt_cores(cat) <- 3
opt_chunk_buffer(cat) <- 20
#function that I want to use over the catalog files
mdt <- grid_terrain(cat, res = 5, algorithm = knnidw(k = 5, p = 2))
r lidar save lidr catalog-service
edited Mar 6 at 14:09
Andre Silva
7,735113785
asked Mar 6 at 11:22
César ArqueroCésar Arquero
859524
add a comment |
I'm trying to learn how to use the options of catalog() within the lidR package in R. I'd like to save directly the processed files, for example, using grid_terrain() function over a catalog and save files keeping the filename of the original LAZ/LAS file.
As you can see in the guide of the package, catalog has the option of save the file using things like {XBOTTOM}_{ID}:
# Internal engine will not return results into R. Instead it will write results in files.
opt_output_files(ctg) <- "/path/to/folder/templated_filename_{XBOTTOM}_{ID}
I'd like to save the files using the same filename, but, I don't know how to configure that part with {} in the opt_output_files() option. I tried several things like, for instance: opt_output_files(cat) <- paste0(output,"/{data$filename}") but, it doesn't work.
lasdir <- "C:/lazfiles"
output <- "C:/output"
cat <- catalog(lasdir)
lasfiles <- cat@data$filename #with this you can see the filenames
opt_progress(cat) <- TRUE
opt_output_files(cat) <- paste0(output,"/{data$filename}")
opt_cores(cat) <- 3
opt_chunk_buffer(cat) <- 20
#function that I want to use over the catalog files
mdt <- grid_terrain(cat, res = 5, algorithm = knnidw(k = 5, p = 2))
r lidar save lidr catalog-service
edited Mar 6 at 14:09
Andre Silva
7,735113785
asked Mar 6 at 11:22
César ArqueroCésar Arquero
859524
add a comment |
I'm trying to learn how to use the options of catalog() within the lidR package in R. I'd like to save directly the processed files, for example, using grid_terrain() function over a catalog and save files keeping the filename of the original LAZ/LAS file.
As you can see in the guide of the package, catalog has the option of save the file using things like {XBOTTOM}_{ID}:
# Internal engine will not return results into R. Instead it will write results in files.
opt_output_files(ctg) <- "/path/to/folder/templated_filename_{XBOTTOM}_{ID}
I'd like to save the files using the same filename, but, I don't know how to configure that part with {} in the opt_output_files() option. I tried several things like, for instance: opt_output_files(cat) <- paste0(output,"/{data$filename}") but, it doesn't work.
lasdir <- "C:/lazfiles"
output <- "C:/output"
cat <- catalog(lasdir)
lasfiles <- cat@data$filename #with this you can see the filenames
opt_progress(cat) <- TRUE
opt_output_files(cat) <- paste0(output,"/{data$filename}")
opt_cores(cat) <- 3
opt_chunk_buffer(cat) <- 20
#function that I want to use over the catalog files
mdt <- grid_terrain(cat, res = 5, algorithm = knnidw(k = 5, p = 2))
r lidar save lidr catalog-service
edited Mar 6 at 14:09
Andre Silva
7,735113785
asked Mar 6 at 11:22
César ArqueroCésar Arquero
859524
I'm trying to learn how to use the options of catalog() within the lidR package in R. I'd like to save directly the processed files, for example, using grid_terrain() function over a catalog and save files keeping the filename of the original LAZ/LAS file.
As you can see in the guide of the package, catalog has the option of save the file using things like {XBOTTOM}_{ID}:
# Internal engine will not return results into R. Instead it will write results in files.
opt_output_files(ctg) <- "/path/to/folder/templated_filename_{XBOTTOM}_{ID}
I'd like to save the files using the same filename, but, I don't know how to configure that part with {} in the opt_output_files() option. I tried several things like, for instance: opt_output_files(cat) <- paste0(output,"/{data$filename}") but, it doesn't work.
lasdir <- "C:/lazfiles"
output <- "C:/output"
cat <- catalog(lasdir)
lasfiles <- cat@data$filename #with this you can see the filenames
opt_progress(cat) <- TRUE
opt_output_files(cat) <- paste0(output,"/{data$filename}")
opt_cores(cat) <- 3
opt_chunk_buffer(cat) <- 20
#function that I want to use over the catalog files
mdt <- grid_terrain(cat, res = 5, algorithm = knnidw(k = 5, p = 2))
r lidar save lidr catalog-service
r lidar save lidr catalog-service
edited Mar 6 at 14:09
Andre Silva
7,735113785
asked Mar 6 at 11:22
César ArqueroCésar Arquero
859524
edited Mar 6 at 14:09
Andre Silva
7,735113785
asked Mar 6 at 11:22
César ArqueroCésar Arquero
859524
edited Mar 6 at 14:09
Andre Silva
7,735113785
edited Mar 6 at 14:09
Andre Silva
7,735113785
edited Mar 6 at 14:09
Andre Silva
7,735113785
7,735113785
asked Mar 6 at 11:22
César ArqueroCésar Arquero
859524
asked Mar 6 at 11:22
César ArqueroCésar Arquero
859524
asked Mar 6 at 11:22
César ArqueroCésar Arquero
859524
859524
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Found the answer in the grid_terrain help section "supported processing options":
output_files: Return the output in R or write each cluster’s output in a file. Supported templates are ... , ORIGINALFILENAME.
This is the solution:
opt_output_files(cat) <- paste0(output,"/{ORIGINALFILENAME}")
edited Mar 6 at 14:13
Andre Silva
7,735113785
answered Mar 6 at 12:22
César ArqueroCésar Arquero
859524
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%2f314547%2fconfiguring-lidr-catalog-to-save-files-with-same-filename%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Found the answer in the grid_terrain help section "supported processing options":
output_files: Return the output in R or write each cluster’s output in a file. Supported templates are ... , ORIGINALFILENAME.
This is the solution:
opt_output_files(cat) <- paste0(output,"/{ORIGINALFILENAME}")
edited Mar 6 at 14:13
Andre Silva
7,735113785
answered Mar 6 at 12:22
César ArqueroCésar Arquero
859524
add a comment |
Found the answer in the grid_terrain help section "supported processing options":
output_files: Return the output in R or write each cluster’s output in a file. Supported templates are ... , ORIGINALFILENAME.
This is the solution:
opt_output_files(cat) <- paste0(output,"/{ORIGINALFILENAME}")
edited Mar 6 at 14:13
Andre Silva
7,735113785
answered Mar 6 at 12:22
César ArqueroCésar Arquero
859524
add a comment |
Found the answer in the grid_terrain help section "supported processing options":
output_files: Return the output in R or write each cluster’s output in a file. Supported templates are ... , ORIGINALFILENAME.
This is the solution:
opt_output_files(cat) <- paste0(output,"/{ORIGINALFILENAME}")
edited Mar 6 at 14:13
Andre Silva
7,735113785
answered Mar 6 at 12:22
César ArqueroCésar Arquero
859524
Found the answer in the grid_terrain help section "supported processing options":
output_files: Return the output in R or write each cluster’s output in a file. Supported templates are ... , ORIGINALFILENAME.
This is the solution:
opt_output_files(cat) <- paste0(output,"/{ORIGINALFILENAME}")
edited Mar 6 at 14:13
Andre Silva
7,735113785
answered Mar 6 at 12:22
César ArqueroCésar Arquero
859524
edited Mar 6 at 14:13
Andre Silva
7,735113785
edited Mar 6 at 14:13
Andre Silva
7,735113785
edited Mar 6 at 14:13
Andre Silva
7,735113785
7,735113785
answered Mar 6 at 12:22
César ArqueroCésar Arquero
859524
answered Mar 6 at 12:22
César ArqueroCésar Arquero
859524
answered Mar 6 at 12:22
César ArqueroCésar Arquero
859524
859524
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%2f314547%2fconfiguring-lidr-catalog-to-save-files-with-same-filename%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
