Configuring lidR catalog to save files with same filename?Clip multiple .las files data to polygon shapefile...

Why is it "take a leak?"

How can I handle a player who pre-plans arguments about my rulings on RAW?

Create chunks from an array

How to kill a localhost:8080

Giving a talk in my old university, how prominently should I tell students my salary?

Rationale to prefer local variables over instance variables?

Why do members of Congress in committee hearings ask witnesses the same question multiple times?

apt: What's the difference between "apt install php" and "apt install php-defaults"?

How to mitigate "bandwagon attacking" from players?

Are small insurances worth it

Levi-Civita symbol: 3D matrix

Where is the fallacy here?

Why can't we make a perpetual motion machine by using a magnet to pull up a piece of metal, then letting it fall back down?

Why do phishing e-mails use faked e-mail addresses instead of the real one?

Plagiarism of code by other PhD student

Which sins are beyond punishment?

What are SHA-rounds?

Is there a full canon version of Tyrion's jackass/honeycomb joke?

Misplaced tyre lever - alternatives?

What could trigger powerful quakes on icy world?

3.5% Interest Student Loan or use all of my savings on Tuition?

When to use mean vs median

Was it really inappropriate to write a pull request for the company I interviewed with?

Is it possible to counterspell the revised Artificer?



Configuring lidR catalog to save files with same filename?


Clip multiple .las files data to polygon shapefile using FUSIONHow to create a continuous scale with distinct/custom color and value breaks with ggplot2 mapClipping object of class LAS with polygon shapefile using lidR?Optimizing workflow for FUSION's PolyClipData?Combing multiple LAS files with different vertical and horizontal accuracy?Getting source bounds when filtering LAS using PDAL?Calculating standard metrics in multiple LiDAR files with lidR 2.0Watershed a catalog RasterStack in place of RasterLayer in lidR?Removing noise from point cloud with lidR packagelasclipCircle with catalog













4















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))









share|improve this question





























    4















    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))









    share|improve this question



























      4












      4








      4








      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))









      share|improve this question
















      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






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 3 hours ago









      Andre Silva

      7,700113685




      7,700113685










      asked 6 hours ago









      César ArqueroCésar Arquero

      849424




      849424






















          1 Answer
          1






          active

          oldest

          votes


















          4














          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}")





          share|improve this answer

























            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


















            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









            4














            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}")





            share|improve this answer






























              4














              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}")





              share|improve this answer




























                4












                4








                4







                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}")





                share|improve this answer















                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}")






                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited 3 hours ago









                Andre Silva

                7,700113685




                7,700113685










                answered 5 hours ago









                César ArqueroCésar Arquero

                849424




                849424






























                    draft saved

                    draft discarded




















































                    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.




                    draft saved


                    draft discarded














                    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





















































                    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







                    Popular posts from this blog

                    As a Security Precaution, the user account has been locked The Next CEO of Stack OverflowMS...

                    Список ссавців Італії Природоохоронні статуси | Список |...

                    Українські прізвища Зміст Історичні відомості |...