<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
One comment - have the LIDAR set to hillshade in grayscale (set symbology to hillshade) with the imagery overlayed & symbology partially transparent (or partially opaque). </div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
You can adjust the opacity to what looks good & you don't need to switch between them - you can see them both at once.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
You can play with the Z multiplier to tweak the hillshade to get the degree of contrast you want, also change the direction of the light source as desired.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
And a different (manual) workflow you might try (if I correctly understood what you are trying to do)...</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Create a new vector linestring layer (shapefile is probably simplest), make this editable.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
you should be able to see the railroad tracks of interest from the LIDAR & satellite layers on the screen, </div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
create a new linestring for each one (called digitising) by using the mouse to click on map where you want the line to go</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
When you have got all the lines you want to export to kml saved in the shapefile, you can export the layer as kml. It will not be a large file...</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature" style="color: inherit;">
<div style="margin-right: 0px; margin-left: 0px; font-family: Calibri, Arial, Helvetica, sans-serif;">
Brent Wood<br>
<br>
Principal Technician, Fisheries<br>
NIWA<br>
DDI: +64 (4) 3860529</div>
</div>
<div id="appendonsend" style="color: inherit;"></div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<hr style="display: inline-block; width: 98%;">
<div id="divRplyFwdMsg" dir="ltr" style="color: inherit;"><span style="font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"><b>From:</b> QGIS-User <qgis-user-bounces@lists.osgeo.org> on behalf of John W. Blue via QGIS-User <qgis-user@lists.osgeo.org><br>
<b>Sent:</b> Friday, November 15, 2024 07:01<br>
<b>To:</b> qgis-user@lists.osgeo.org <qgis-user@lists.osgeo.org><br>
<b>Subject:</b> Re: [Qgis-user] USGS 3DEM question: export to kml/kmz</span>
<div> </div>
</div>
<div style="font-size: 11pt;">Bernie,<br>
<br>
Thank you for the suggestion.<br>
<br>
As I was checking out the plugins I did see "Quick Maps" and thought of the same workflow but have not tried it yet. My only hesitation at the time was wanting to be able to mark the old roadbed as trail. With some more google searching today I found:<br>
<br>
<a href="https://ultrajourneys.org/digitizing-trails-in-qgis/" id="OWA1679e424-ddc4-31b2-6fc8-ff7aeef1818b" class="OWAAutoLink" data-auth="NotApplicable">https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fultrajourneys.org%2Fdigitizing-trails-in-qgis%2F&data=05%7C02%7Cbrent.wood%40niwa.co.nz%7C7f7582ab7e63476deb9008dd04d6662b%7C41caed736a0c468aba499ff6aafd1c77%7C0%7C0%7C638672041098875125%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=JRe4sm%2BFOCJdjCMu%2Fa6j80HqUINOrl%2FdrTYILguDzqM%3D&reserved=0</a><br>
<br>
Have not attempted to follow the tutorial so if you know of a better one all ears. Marking an old roadbed as a trail and getting that trail into a GPX format is the ultimate goal here.<br>
<br>
Thanks!<br>
<br>
John<br>
<br>
<br>
From: Bernie Connors [<a href="mailto:bernie.connors@unb.ca" id="OWAd12181bd-27d6-2c36-d0be-86686731a4d6" class="OWAAutoLink">mailto:bernie.connors@unb.ca</a>]<br>
Sent: Wednesday, November 13, 2024 9:03 PM<br>
To: John W. Blue<br>
Cc: qgis-user@lists.osgeo.org<br>
Subject: Re: [Qgis-user] USGS 3DEM question: export to kml/kmz<br>
<br>
Here is a suggestion. Keep the USGS DEM tif in QGIS and symbolize it as a hillshade. It will be very easy to spot abandoned railways in the hillshade. Then use the Quick Maps plugin to add the Google Satellite map to QGIS. You can easily switch back and
forth between Google Satellite layer and the USGS DEM hillshade.<br>
<br>
Cheers,<br>
Bernie.<br>
On Wed, Nov 13, 2024, 10:11 p.m. John W. Blue via QGIS-User <qgis-user@lists.osgeo.org> wrote:<br>
Thanks for the file composition info.<br>
<br>
Using that I was able to convert the downloaded 3DEM .tif from a raster to vector using Raster > Conversion > Polygonize (Raster to Vector) option. The resultant exported .kml file size was almost 1 Gb and while Google earth was to load it, it was nothing
but a white square.<br>
<br>
I did find that Raster > Analysis > Hillshade was able to produce some remarkable and useable results. What is strange is that the conversion of the hillshade raster to vector .kml never completes. It quickly gets to 7% and then seemly stalls out.<br>
<br>
Am I not waiting long enough?<br>
<br>
John<br>
<br>
<br>
<br>
From: oisin.kelly.wild@gmail.com [<a href="mailto:oisin.kelly.wild@gmail.com" id="OWA684a56a2-d36d-3970-23a7-044b98f62bcb" class="OWAAutoLink">mailto:oisin.kelly.wild@gmail.com</a>]<br>
Sent: Tuesday, November 12, 2024 3:01 PM<br>
To: John W. Blue<br>
Cc: qgis-user@lists.osgeo.org<br>
Subject: Re: [Qgis-user] USGS 3DEM question: export to kml/kmz<br>
<br>
The tif file is a raster.<br>
Kml is a vector format.<br>
You need to use one of the processing tools to extract contours or spot heights and then export the results to kml.<br>
Get BlueMail for Android<br>
On 12 Nov 2024, at 20:06, "John W. Blue via QGIS-User" <qgis-user@lists.osgeo.org> wrote:<br>
Hello,<br>
<br>
QGIS newbie here. I want to use USGS LiDAR to search for abandoned railroad grades as a layer in Google Earth.<br>
<br>
I am able to download the 1 meter tif from USGS and I am able to add it as a layer in QGIS. I cannot, however, figure out how export the layer as a kml/kmz file.<br>
<br>
I right-click on the layer and choose “Export” and then “Save As” followed by dropping the “Format” menu down. Heaps and heaps of options to choose from but none for kml/kmz.<br>
<br>
Any help in what I am missing or doing wrong would be appreciated.<br>
<br>
John<br>
________________________________________<br>
<br>
<br>
</div>
<table style="width: 600px; font-size: 8pt; font-family: Arial" cellspacing="20">
<tbody>
<tr>
<td><a href="https://www.niwa.co.nz/"><img src="https://www.niwa.co.nz/static/niwa-2018-horizontal-180.png">
</a></td>
<td>
<table style="width: 500px">
<tbody>
<span>Brent Wood <br>
<font color="#1793d2">Principal Technician - GIS and Spatial Data Management</font><br>
<font color="#1793d2">Programme Leader - Environmental Information Delivery</font><br>
+64-4-386-0529<br>
<br>
National Institute of Water & Atmospheric Research Ltd (NIWA)<br>
301 Evans Bay Parade Hataitai Wellington New Zealand<br>
<b>Connect with NIWA:</b> <a href="https://www.niwa.co.nz/">niwa.co.nz</a> <a href="https://www.facebook.com/nzniwa">
Facebook</a> <a href="https://www.linkedin.com/company/niwa">LinkedIn</a> <a href="https://twitter.com/niwa_nz">
Twitter</a> <a href="https://www.instagram.com/niwa_science">Instagram</a> <a href="https://www.youtube.com/channel/UCJ-j3MLMg1H59Ak2UaNLL3A">
YouTube</a> </span>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<font face="Arial" size="1">To ensure compliance with legal requirements and to maintain cyber security standards, NIWA's IT systems are subject to ongoing monitoring, activity logging and auditing. This monitoring and auditing service may be provided by third
parties. Such third parties can access information transmitted to, processed by and stored on NIWA's IT systems.
<br>
Note: This email is intended solely for the use of the addressee and may contain information that is confidential or subject to legal professional privilege. If you receive this email in error please immediately notify the sender and delete the email.
</font>
</body>
</html>