I've had this problem several times in OOM where I can't properly import both OSM data and Lidar data where they are both in the correct spot with correct rotation and scale. Has anyone had success with this? I'm almost ready to call it quits and grab OCAD because everything I've seen makes it seem so much easier.
Whenever I put in the Lidar data first it didn't work, but georeferencing on a blank file, then adding the OSM data, and then the Lidar Data worked. I don't know if that will help your issue but perhaps it's worth a try?
AJ - I generally pull the OSM file into OOM as the first step to set the georeferencing the map. Then the lidar generated files get pulled in. However the files need to be in the same projection. Contact me via email and I can help you sort it out.
Unless they've fixed it, OOMapper requires that you must have world files for TIFF files (which normally don't need world files because the georeference information is inside the TIFF).
In QGIS, under Project Settings, set the CRS (projections) to UTM for your zone. For me in Cincinnati, it's 32616 (UTM Zone 16, Northern Hemisphere). As you go east it goes to 17, 18, 19. I use the website Acme Mapper with options set to Coordinates in UTM to get UTM zone and coordinates (and to view USGS maps).
Now you can use the "Raster" menu tools to reproject if necessary, but if they were already in the right coordinates just without the world file, you do "Raster" "???" "Extract Projection". Ideally point it to a single file or a directory of only image files (TIFF, JPG, PNG, with no world files. If you have world files, copy those and the images with them off into another directory. I usually save files without world files into a "temp" directory, and then I copy them into the "basemap" directory after I make the world files.
AJ was using the older Lidar file that was in PA State projection. He found the newer file, which is in UTM and meter
@cedatcreek TIFFs no longer require world files. I think support for GeoTIFFs was added about a year ago
Thanks, Tobby! I guess this means OOMapper users should make sure they have the latest stable release. To me, this is a really big deal because it was a reason people were having trouble. Really glad to hear it's fixed.