Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
OpenWalnut Core OpenWalnut Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 64
    • Issues 64
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenWalnut
  • OpenWalnut CoreOpenWalnut Core
  • Issues
  • #39

Closed
Open
Created May 08, 2017 by Sebastian Eichelbaum@ebaumMaintainer

-RM-384-MR-LAS Reader unification

We have 2 LAS readers. The one from Andreas' LiDAR toolbox and a simple one in the release branch.

We should consider unifying them. The one from Andreas contains nice additional functionality but does not use the rather new WDataModule mechanism and provides some functions where I am not sure whether they belong in a reader, like WLasReader::setContrast.

(from redmine: created on 2014-10-22, closed on 2015-03-14)

Assignee
Assign to
Long Term Goals
Milestone
Long Term Goals
Assign milestone
Time tracking