Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • 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 44
    • Issues 44
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • OpenWalnut
  • OpenWalnut CoreOpenWalnut Core
  • Issues
  • #39

Closed
Open
Opened May 08, 2017 by Sebastian Eichelbaum@ebaum
  • Report abuse
  • New issue
Report abuse New issue

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

To upload designs, you'll need to enable LFS. More information
Assignee
Assign to
Long Term Goals
Milestone
Long Term Goals
Assign milestone
Time tracking
None
Due date
None
1
Labels
Task
Assign labels
  • View project labels
Reference: openwalnut/openwalnut#39