<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Jason Amadori.com</title>
	<atom:link href="http://jasonamadori.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://jasonamadori.com</link>
	<description>Jason Amadori&#039;s LIDAR GIS Blog</description>
	<lastBuildDate>Thu, 16 Feb 2012 16:28:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='jasonamadori.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://s2.wp.com/i/buttonw-com.png</url>
		<title>Jason Amadori.com</title>
		<link>http://jasonamadori.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://jasonamadori.com/osd.xml" title="Jason Amadori.com" />
	<atom:link rel='hub' href='http://jasonamadori.com/?pushpress=hub'/>
		<item>
		<title>Another Cool Airport Mapping Project</title>
		<link>http://jasonamadori.com/2011/11/30/another-cool-airport-mapping-project/</link>
		<comments>http://jasonamadori.com/2011/11/30/another-cool-airport-mapping-project/#comments</comments>
		<pubDate>Wed, 30 Nov 2011 15:12:06 +0000</pubDate>
		<dc:creator>Jason</dc:creator>
				<category><![CDATA[Asset Management]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Pavement Management]]></category>
		<category><![CDATA[airport pavement management]]></category>
		<category><![CDATA[automated crack detection]]></category>
		<category><![CDATA[concrete]]></category>
		<category><![CDATA[concrete distress mapping]]></category>
		<category><![CDATA[distresses]]></category>
		<category><![CDATA[pavement design]]></category>
		<category><![CDATA[pavement management]]></category>
		<category><![CDATA[pop-outs]]></category>

		<guid isPermaLink="false">https://eartheyelidar.wordpress.com/?p=296</guid>
		<description><![CDATA[We just recently completed a cool project for an airport client who was having issues with their concrete surface and “pop-outs” caused by extended freeze/thaw weather events.  Pop-outs are caused when the surface of the concrete sheds pieces that are about an inch wide and can be anywhere from &#60;1cm to 3cm deep.  The following [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=296&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p align="justify">We just recently completed a cool project for an airport client who was having issues with their concrete surface and “pop-outs” caused by extended freeze/thaw weather events.  Pop-outs are caused when the surface of the concrete sheds pieces that are about an inch wide and can be anywhere from &lt;1cm to 3cm deep.  The following graphic shows what the pop-outs look like in the field.</p>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/11/img_2626r.jpg"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="IMG_2626r" src="http://eartheyelidar.files.wordpress.com/2011/11/img_2626r_thumb.jpg?w=595&#038;h=399" alt="IMG_2626r" width="595" height="399" border="0" /></a></p>
<p align="justify">The client was looking for a way to quantify the number of pop-outs per slab using an automated process to avoid having to survey every pop-out which would prove to be cost-prohibitive based on the overall size of the project.</p>
<p align="justify">Earth Eye deployed 2 teams of data collection vehicles to compare the imagery that could be obtained from our right-of-way cameras as well as from our pavement camera.</p>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/11/macvans_fog.jpg"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="MACVans_Fog" src="http://eartheyelidar.files.wordpress.com/2011/11/macvans_fog_thumb.jpg?w=595&#038;h=446" alt="MACVans_Fog" width="595" height="446" border="0" /></a></p>
<p align="justify">The pavement camera has a resolution of 1mm and gives us the ability to resolve the pop-outs from a nadir view, making it easier to automate the extraction of these features from the imagery.  Also, the nadir view gives us more spatial accuracy, so the locations of the pop-outs can be accurately mapped and then compared with future imagery to help quantify the amount of new pop-outs that have arisen since the last inventory.  Furthermore, the gray-scale image provided by the pavement camera provided more contrast between the concrete surface and the pop-out which is much lighter in color.  It was determined that the nadir-view pavement camera provided the best starting point, from which to test the automated pop-out extraction process.  The following image illustrates a sample pavement image – note the pop-outs are very visible without having to zoom into the image.</p>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/11/image.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/11/image_thumb.png?w=596&#038;h=646" alt="image" width="596" height="646" border="0" /></a></p>
<p align="justify">The next image shows the results of our automated classification routine without any manual augmentation of missed pop-outs.  We are realizing a consistent yield of greater than 95% of pop-outs identified as compared to control slabs that were collected manually in the field.  Being able to efficiently map the pop-outs with a very high-yielding and automated algorithm allows us to efficiently map the pop-outs to support maintenance operations for this airport facility.</p>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/11/image1.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/11/image_thumb1.png?w=593&#038;h=635" alt="image" width="593" height="635" border="0" /></a></p>
<p align="justify">All of the pop-outs are geospatially referenced, so we can export all of the pop-outs as polygons with an area measurement associated with them.  This area can then be converted to a severity and used to prescribe a specific maintenance activity based on the size and depth of the pop-out.  The goal of the project was to create a quantified measurement (count) of the pop-outs for this entire project and we successfully completed this task with high-yielding, geospatial results.</p>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/11/image2.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/11/image_thumb2.png?w=593&#038;h=371" alt="image" width="593" height="371" border="0" /></a></p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/eartheyelidar.wordpress.com/296/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/eartheyelidar.wordpress.com/296/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/eartheyelidar.wordpress.com/296/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/eartheyelidar.wordpress.com/296/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/eartheyelidar.wordpress.com/296/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/eartheyelidar.wordpress.com/296/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/eartheyelidar.wordpress.com/296/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/eartheyelidar.wordpress.com/296/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/eartheyelidar.wordpress.com/296/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/eartheyelidar.wordpress.com/296/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/eartheyelidar.wordpress.com/296/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/eartheyelidar.wordpress.com/296/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/eartheyelidar.wordpress.com/296/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/eartheyelidar.wordpress.com/296/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=296&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://jasonamadori.com/2011/11/30/another-cool-airport-mapping-project/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<georss:point>28.509939 -81.154447</georss:point>
		<geo:lat>28.509939</geo:lat>
		<geo:long>-81.154447</geo:long>
		<media:content url="http://1.gravatar.com/avatar/3d3d8416c175862522eff2ab19c1f953?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">Jason</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/11/img_2626r_thumb.jpg" medium="image">
			<media:title type="html">IMG_2626r</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/11/macvans_fog_thumb.jpg" medium="image">
			<media:title type="html">MACVans_Fog</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/11/image_thumb.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/11/image_thumb1.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/11/image_thumb2.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>
	</item>
		<item>
		<title>Automated Pavement Distress Analysis &#8211; The Final Frontier?</title>
		<link>http://jasonamadori.com/2011/05/25/automated-pavement-distress-analysis-the-final-frontier/</link>
		<comments>http://jasonamadori.com/2011/05/25/automated-pavement-distress-analysis-the-final-frontier/#comments</comments>
		<pubDate>Wed, 25 May 2011 01:06:15 +0000</pubDate>
		<dc:creator>Jason</dc:creator>
				<category><![CDATA[Pavement Management]]></category>
		<category><![CDATA[AMS]]></category>
		<category><![CDATA[Asset Management]]></category>
		<category><![CDATA[budget forecasting]]></category>
		<category><![CDATA[capital improvement planning]]></category>
		<category><![CDATA[GIS]]></category>
		<category><![CDATA[GPS]]></category>
		<category><![CDATA[infrastructure]]></category>
		<category><![CDATA[MAC]]></category>
		<category><![CDATA[Mobile Data Collection]]></category>
		<category><![CDATA[pavement]]></category>
		<category><![CDATA[pavement design]]></category>
		<category><![CDATA[pavement imagery]]></category>
		<category><![CDATA[pavement management]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[PCR]]></category>
		<category><![CDATA[resurfacing]]></category>
		<category><![CDATA[road resurfacing]]></category>

		<guid isPermaLink="false">https://eartheyelidar.wordpress.com/?p=278</guid>
		<description><![CDATA[ We have been working with some automated methods for quantifying crack measurements and have had some interesting results.  How great would it be to collect pavement images, batch them on a server and have it spit out accurate crack maps that you can overlay in a GIS?  The technology is here!  Or, is it? Most [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=278&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p align="justify"> We have been working with some automated methods for quantifying crack measurements and have had some interesting results.  How great would it be to collect pavement images, batch them on a server and have it spit out accurate crack maps that you can overlay in a GIS?  The technology is here!  Or, is it?</p>
<p align="justify">Most pavement inspections involve intricate processes where pavement experts rate segments visually, either from field visits or rating pavement images in the office.  This introduces a lot of subjectivity in the rating results and typically culminates in a spreadsheet showing pavement ratings by segment.  The data is then modeled using ASTM performance curves that have been built from industry proven pavement experiments.</p>
<p align="justify">There is no doubt that these curves are tried and true representations of how pavement performs in varying physical and environmental conditions and each project should take these factors into consideration when developing the preservation plans for an agency.</p>
<p align="justify">We have been working to develop a rating workflow that focuses on a combination of automated and manual processes to bridge the current gap of Quantitative and Qualitative pavement inspections.  The way we are doing this is through the application of GIS to the automated rating process.  Here’s how it works…</p>
<p align="justify">First, we begin with a pavement image from our <a title="Pavemetrix Website" href="http://www.pavemetrics.com/laser_road.html">LRIS pavement imaging system</a>.  Images are captured at a 1mm-pixel resolution and then analyzed through an automated image processing workflow.</p>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/05/image.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/05/image_thumb.png?w=617&#038;h=464" alt="image" width="617" height="464" border="0" /></a></p>
<p align="justify">The resulting image creates a “crack map” that identifies the type, severity and extent of the distresses on that section of pavement.  The process is fully automated and handled by the computer.</p>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/05/image1.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/05/image_thumb1.png?w=618&#038;h=600" alt="image" width="618" height="600" border="0" /></a></p>
<p align="justify">Once we have the crack maps in place, we then apply a manual editing process that is GIS-centric by nature and the resulting crack map is a more accurate representation of the real-world conditions.</p>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/05/image2.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/05/image_thumb2.png?w=621&#038;h=603" alt="image" width="621" height="603" border="0" /></a></p>
<p align="justify">Once the edited crack maps are compiled, the data is exported to a GIS where the extents are calculated geospatially and then integrated with a pavement management system.  This is where all of the Pavement Condition Indices (PCI) are calculated and applied to each agency’s specific pavement rating methodologies.  Since the process is geospatial in nature, it is easily imported to ANY pavement management software and gives our clients the flexibility to apply any rating methodology they desire.</p>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/05/image3.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/05/image_thumb3.png?w=603&#038;h=774" alt="image" width="603" height="774" border="0" /></a></p>
<p align="justify">Of course, all agencies have a certain spending threshold and there are cases where automation is the only way to cost-effectively manage large volumes of data.  We recognize this fact and are working hard to bridge the gap of available funding and high quality data.</p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/eartheyelidar.wordpress.com/278/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/eartheyelidar.wordpress.com/278/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/eartheyelidar.wordpress.com/278/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/eartheyelidar.wordpress.com/278/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/eartheyelidar.wordpress.com/278/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/eartheyelidar.wordpress.com/278/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/eartheyelidar.wordpress.com/278/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/eartheyelidar.wordpress.com/278/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/eartheyelidar.wordpress.com/278/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/eartheyelidar.wordpress.com/278/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/eartheyelidar.wordpress.com/278/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/eartheyelidar.wordpress.com/278/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/eartheyelidar.wordpress.com/278/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/eartheyelidar.wordpress.com/278/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=278&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://jasonamadori.com/2011/05/25/automated-pavement-distress-analysis-the-final-frontier/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<georss:point>28.509939 -81.154447</georss:point>
		<geo:lat>28.509939</geo:lat>
		<geo:long>-81.154447</geo:long>
		<media:content url="http://1.gravatar.com/avatar/3d3d8416c175862522eff2ab19c1f953?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">Jason</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/05/image_thumb.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/05/image_thumb1.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/05/image_thumb2.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/05/image_thumb3.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>
	</item>
		<item>
		<title>What are you going to do with your NERC data?</title>
		<link>http://jasonamadori.com/2011/04/28/what-are-you-going-to-do-with-your-nerc-data/</link>
		<comments>http://jasonamadori.com/2011/04/28/what-are-you-going-to-do-with-your-nerc-data/#comments</comments>
		<pubDate>Thu, 28 Apr 2011 23:45:59 +0000</pubDate>
		<dc:creator>Jason</dc:creator>
				<category><![CDATA[Airborne LiDAR]]></category>
		<category><![CDATA[Asset Management]]></category>
		<category><![CDATA[accuracy assessment for lidar]]></category>
		<category><![CDATA[aerial photography]]></category>
		<category><![CDATA[AMS]]></category>
		<category><![CDATA[budget forecasting]]></category>
		<category><![CDATA[capital improvement planning]]></category>
		<category><![CDATA[Consequences]]></category>
		<category><![CDATA[elevations]]></category>
		<category><![CDATA[Encroachments]]></category>
		<category><![CDATA[GIS]]></category>
		<category><![CDATA[GPS]]></category>
		<category><![CDATA[ground surface model]]></category>
		<category><![CDATA[infrastructure]]></category>
		<category><![CDATA[lidar]]></category>
		<category><![CDATA[NERC]]></category>
		<category><![CDATA[NERC Compliance]]></category>
		<category><![CDATA[risk]]></category>
		<category><![CDATA[Risk Assessment]]></category>
		<category><![CDATA[TIN]]></category>

		<guid isPermaLink="false">https://eartheyelidar.wordpress.com/?p=265</guid>
		<description><![CDATA[So, you’ve collected your entire Transmission network using LiDAR, built your PLS-CADD models and identified your encroachments – what’s next?  How about leveraging that data to manage the Work Activities required to upgrade/maintain your Transmission network? We have all heard about Asset Management and how it can help an agency extend the useful life of [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=265&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>So, you’ve collected your entire Transmission network using LiDAR, built your PLS-CADD models and identified your encroachments – what’s next?  How about leveraging that data to manage the Work Activities required to upgrade/maintain your Transmission network?</p>
<p align="justify">We have all heard about Asset Management and how it can help an agency extend the useful life of its infrastructure.  We all know that in principal it makes all the sense in the world, but the actual application of these concepts require investment in software, hardware and personnel.  What we will never know is – How much should we invest in the management of our assets?  Using the NERC regulation and the frenzied data collection going on in our industry as an example, consider the following.</p>
<p align="justify">Most Airborne LiDAR companies are collecting and delivering data in the $500 – $1,500 per linear mile range, depending on the downstream processing requirements.  Most of this data is delivered to the end user as .LAS point clouds, PLS-CADD .BAK, files and some other CAD or GIS formats.  Once it is delivered, the agency has a unique opportunity to leverage the delivered products for future value.</p>
<p align="justify">If we use Vegetation Encroachment data as an example, we can illustrate how the encroachment information can be used to create a vegetation Asset Class and managed throughout its life-cycle.  Most likely, the data delivered to an agency will include .LAS point clouds with classified data reflecting terrain, conductors, towers, buildings, etc.  In addition to this, vector data is also delivered and can be used to support maintenance management activities.  The graphic below illustrates a common Transmission LiDAR deliverable.</p>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/04/image13.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb13.png?w=610&#038;h=332" alt="image" width="610" height="332" border="0" /></a></p>
<p align="justify">Note the Red vegetation in the graphic above.  It shows the vegetation points that have been flagged as encroachment violations based on its proximity to the conductors.  These points can then be mapped in a GIS or Asset Management program for further analysis.  In doing so, an agency can gather more value from this information.  For example, the graphic below illustrates the “grow-in” (light blue) and “fall-in” (red) violations for a section of Transmission line.</p>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/04/image14.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border-width:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb14.png?w=611&#038;h=332" alt="image" width="611" height="332" border="0" /></a></p>
<p align="justify">GIS mapping provides the user the spatial context necessary to make informed vegetation management decisions.  First, the location of vegetation encroachments are known and with a little manipulation, the volume and area of the vegetation can be determined very easily.  This gives an agency the ability to control the costs associated with their vegetation management program.  Asset management software that leverages GIS can provide the tools necessary to develop an immediate return-on-investment of the software purchase and associated data collection expenditures.</p>
<p align="justify">First, the user creates the geospatial layers from the classified point cloud.  Vegetation violations can be exported as points and then aggregated into vegetation encroachment units.  These units are then integrated with the Work and Asset management system through the use of GIS.  Since the geometry of the encroachment units are known based on its GIS attributes, an agency can then determine the following characteristics about their encroachments:</p>
<ol>
<li>
<div align="justify">Maximum Height of Encroachment Unit</div>
</li>
<li>
<div align="justify">Average Height of Encroachment Unit</div>
</li>
<li>
<div align="justify">Total Area (acres) of Encroachment Unit</div>
</li>
<li>
<div align="justify">Total Area (acres) of Encroachment Units along a particular circuit</div>
</li>
</ol>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/04/image15.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb15.png?w=609&#038;h=366" alt="image" width="609" height="366" border="0" /></a></p>
<p align="justify">Since the agency knows so much about their encroachments, they can very accurately determine the volume of vegetation that needs to be removed.  The agency also knows other geospatial characteristics of the vegetation units and can then apply specific cost factors to the removal process.  In addition, GIS also provides a great way to provide contractors with maps and exhibits that will help them generate more accurate bids based on relevant information.  The graphic below shows a KMZ export of Vegetation Encroachments that can be provided to field units in charge of vegetation removal.</p>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/04/image16.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb16.png?w=605&#038;h=425" alt="image" width="605" height="425" border="0" /></a></p>
<p align="justify">A typical vegetation removal contract is assigned to a forestry company who heads to the field and clears vegetation based on their perception of what needs to be removed.  Now, agencies can tell the forestry companies exactly how much (estimated) vegetation needs to be removed and WHERE it is.  Pretty amazing concept to embrace because now an agency can accurately predict the costs of their vegetation management program.</p>
<p align="justify">Another factor that can be applied to this information is the concept of Risk.  Risk takes into consideration the consequences of failure of a particular asset and then provides a Criticality Index for specific Asset Classes and Asset Types.  The more critical the Asset – the higher the priority it gets when determining an agency’s primary work focus.  In other words, this concept helps to identify the most critical components of your infrastructure and helps you to prioritize its maintenance over less critical assets.  By prioritizing using Risk, an agency can take measures to minimize the Risk that exists in its Asset portfolio by fixing these pieces and parts first.</p>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/04/image17.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb17.png?w=605&#038;h=391" alt="image" width="605" height="391" border="0" /></a></p>
<p>None of this stops once you get to the Work Management piece of the puzzle.  I’ll be providing more information related to tracking the work activities as they are completed in the field and using this information to develop more accurate budget forecasts for the future.</p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/eartheyelidar.wordpress.com/265/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/eartheyelidar.wordpress.com/265/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/eartheyelidar.wordpress.com/265/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/eartheyelidar.wordpress.com/265/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/eartheyelidar.wordpress.com/265/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/eartheyelidar.wordpress.com/265/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/eartheyelidar.wordpress.com/265/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/eartheyelidar.wordpress.com/265/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/eartheyelidar.wordpress.com/265/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/eartheyelidar.wordpress.com/265/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/eartheyelidar.wordpress.com/265/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/eartheyelidar.wordpress.com/265/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/eartheyelidar.wordpress.com/265/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/eartheyelidar.wordpress.com/265/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=265&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://jasonamadori.com/2011/04/28/what-are-you-going-to-do-with-your-nerc-data/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<georss:point>28.509939 -81.154447</georss:point>
		<geo:lat>28.509939</geo:lat>
		<geo:long>-81.154447</geo:long>
		<media:content url="http://1.gravatar.com/avatar/3d3d8416c175862522eff2ab19c1f953?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">Jason</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb13.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb14.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb15.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb16.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb17.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>
	</item>
		<item>
		<title>Mobile LiDAR to Support Positive Train Control</title>
		<link>http://jasonamadori.com/2011/04/28/mobile-lidar-to-support-positive-train-control/</link>
		<comments>http://jasonamadori.com/2011/04/28/mobile-lidar-to-support-positive-train-control/#comments</comments>
		<pubDate>Thu, 28 Apr 2011 15:59:06 +0000</pubDate>
		<dc:creator>Jason</dc:creator>
				<category><![CDATA[Airborne LiDAR]]></category>
		<category><![CDATA[Asset Management]]></category>
		<category><![CDATA[mobile lidar]]></category>
		<category><![CDATA[AMS]]></category>
		<category><![CDATA[elevations]]></category>
		<category><![CDATA[GPS]]></category>
		<category><![CDATA[ground surface model]]></category>
		<category><![CDATA[infrastructure]]></category>
		<category><![CDATA[lidar]]></category>
		<category><![CDATA[LiDAR for PTC]]></category>
		<category><![CDATA[Mobile Data Collection]]></category>
		<category><![CDATA[survey]]></category>
		<category><![CDATA[TIN]]></category>

		<guid isPermaLink="false">https://eartheyelidar.wordpress.com/?p=250</guid>
		<description><![CDATA[DTS/Earth Eye just completed a positive train control (PTC) project for a national train company who was evaluating the differences between Airborne LiDAR and Mobile LiDAR to support the collection of PTC data.  They are currently collecting airborne data for approximately 15,000 linear miles of rail.  In certain areas, the airborne data does not provide [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=250&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.dtsgis.com">DTS</a>/<a href="http://eartheye.com">Earth Eye</a> just completed a <a href="http://en.wikipedia.org/wiki/Positive_train_control">positive train control (PTC)</a> project for a national train company who was evaluating the differences between Airborne LiDAR and Mobile LiDAR to support the collection of PTC data.  They are currently collecting airborne data for approximately 15,000 linear miles of rail.  In certain areas, the airborne data does not provide enough fidelity to accurately map the rails or the asset infrastructure that support the railroad operations.</p>
<p align="justify">From <a href="http://en.wikipedia.org/wiki/Positive_train_control">Wikipedia</a> – “The main concept in PTC (as defined for <a href="http://en.wikipedia.org/wiki/North_American">North American</a> Class I <a href="http://en.wikipedia.org/wiki/Freight_train">freight railroads</a>) is that the train receives information about its location and where it is allowed to safely travel, also known as movement authorities. Equipment on board the train then enforces this, preventing unsafe movement. PTC systems will work in either <a href="http://en.wikipedia.org/wiki/Dark_territory">dark territory</a> or signaled territory and often use <a href="http://en.wikipedia.org/wiki/GPS">GPS</a> navigation to track train movements. The <a href="http://en.wikipedia.org/wiki/Federal_Railroad_Administration">Federal Railroad Administration</a> has listed among its goals, &#8220;To deploy the Nationwide Differential Global Positioning System (NDGPS) as a nationwide, uniform, and continuous positioning system, suitable for train control.”</p>
<p align="justify">The project involved the collection of Mobile LiDAR using the Riegl VMX-250 as well as forward-facing video to support PTC Asset Extraction.  The system was mounted on a Hi-Rail vehicle and track access was coordinated through the master scheduler with the Railroad company.  Once we had access to the tracks, we had one shot to make sure the data was collected accurately and we had complete coverage.  All data was processed on-site to verify coverage and we had a preliminary solution by the end of the day that was checked against control to verify absolute accuracies.  We collected the 10-mile section of rail in about 2 hours and this timing included a couple of track dismounts required to let some freight trains move on through.</p>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/04/imag0166.jpg"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="IMAG0166" src="http://eartheyelidar.files.wordpress.com/2011/04/imag0166_thumb.jpg?w=302&#038;h=184" alt="IMAG0166" width="302" height="184" border="0" /></a><a href="http://eartheyelidar.files.wordpress.com/2011/04/imag0168.jpg"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="IMAG0168" src="http://eartheyelidar.files.wordpress.com/2011/04/imag0168_thumb.jpg?w=302&#038;h=183" alt="IMAG0168" width="302" height="183" border="0" /></a></p>
<p align="justify">The following graphics illustrate the point cloud coverage colored by elevation (left) and Intensity (right).</p>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/04/image4.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb4.png?w=303&#038;h=190" alt="image" width="303" height="190" border="0" /></a><a href="http://eartheyelidar.files.wordpress.com/2011/04/image5.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb5.png?w=300&#038;h=189" alt="image" width="300" height="189" border="0" /></a></p>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/04/image6.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb6.png?w=301&#038;h=171" alt="image" width="301" height="171" border="0" /></a><a href="http://eartheyelidar.files.wordpress.com/2011/04/image7.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb7.png?w=298&#038;h=170" alt="image" width="298" height="170" border="0" /></a></p>
<p align="justify">Mapping the rails in 3D was accomplished by developing a software routine designed to track the top of the rail and minimize any “jumping” that can occur in the noise of the LiDAR data.  Basically, a linear smoothing algorithm is applied to the rail breakline and once it is digitized the algorithm fits it to the top of the rail.  The following graphic illustrates how this is accomplished – the white cross-hairs on the top of the rail correspond to the breakline location in 3D.</p>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/04/image8.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb8.png?w=611&#038;h=332" alt="image" width="611" height="332" border="0" /></a></p>
<p>So, back to the discussion about Airborne PTC vs Mobile PTC data.  Here is a signal tower collected by Airborne LiDAR.  The level of detail needed to map and code the Asset feature is lacking, making it difficult to collect PTC information efficiently without supplemental information.</p>
<p><a href="http://eartheyelidar.files.wordpress.com/2011/04/image9.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb9.png?w=608&#038;h=480" alt="image" width="608" height="480" border="0" /></a></p>
<p align="justify">The next graphic shows the detail of the same Asset feature from the mobile LiDAR data.  It is much easier to identify the Asset feature and Type from the point cloud.  In addition to placing locations for the Asset feature, we also provided some attribute information that was augmented by the Right-of-Way camera imagery.  By utilizing this data fusion technique, we can provide the rail company with an accurate and comprehensive PTC database.</p>
<p><a href="http://eartheyelidar.files.wordpress.com/2011/04/image10.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb10.png?w=608&#038;h=480" alt="image" width="608" height="480" border="0" /></a></p>
<p>This graphic shows how the assets are placed in 3D, preserving the geospatial nature of the data in 3D which is helpful when determining the hierarchy of Assets that share the same structure.</p>
<p><a href="http://eartheyelidar.files.wordpress.com/2011/04/image11.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb11.png?w=609&#038;h=494" alt="image" width="609" height="494" border="0" /></a></p>
<p>One last cool shot of a station with all of the furniture, structures, etc that make it up – pretty cool!</p>
<p><a href="http://eartheyelidar.files.wordpress.com/2011/04/image12.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb12.png?w=612&#038;h=383" alt="image" width="612" height="383" border="0" /></a></p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/eartheyelidar.wordpress.com/250/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/eartheyelidar.wordpress.com/250/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/eartheyelidar.wordpress.com/250/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/eartheyelidar.wordpress.com/250/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/eartheyelidar.wordpress.com/250/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/eartheyelidar.wordpress.com/250/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/eartheyelidar.wordpress.com/250/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/eartheyelidar.wordpress.com/250/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/eartheyelidar.wordpress.com/250/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/eartheyelidar.wordpress.com/250/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/eartheyelidar.wordpress.com/250/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/eartheyelidar.wordpress.com/250/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/eartheyelidar.wordpress.com/250/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/eartheyelidar.wordpress.com/250/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=250&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://jasonamadori.com/2011/04/28/mobile-lidar-to-support-positive-train-control/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		<georss:point>28.509939 -81.154447</georss:point>
		<geo:lat>28.509939</geo:lat>
		<geo:long>-81.154447</geo:long>
		<media:content url="http://1.gravatar.com/avatar/3d3d8416c175862522eff2ab19c1f953?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">Jason</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/imag0166_thumb.jpg" medium="image">
			<media:title type="html">IMAG0166</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/imag0168_thumb.jpg" medium="image">
			<media:title type="html">IMAG0168</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb4.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb5.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb6.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb7.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb8.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb9.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb10.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb11.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb12.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>
	</item>
		<item>
		<title>Mobile LiDAR and Cross-Slope Analysis</title>
		<link>http://jasonamadori.com/2011/04/27/mobile-lidar-and-cross-slope-analysis/</link>
		<comments>http://jasonamadori.com/2011/04/27/mobile-lidar-and-cross-slope-analysis/#comments</comments>
		<pubDate>Wed, 27 Apr 2011 19:24:47 +0000</pubDate>
		<dc:creator>Jason</dc:creator>
				<category><![CDATA[Asset Management]]></category>
		<category><![CDATA[mobile lidar]]></category>
		<category><![CDATA[capital improvement planning]]></category>
		<category><![CDATA[elevations]]></category>
		<category><![CDATA[GIS]]></category>
		<category><![CDATA[GPS]]></category>
		<category><![CDATA[ground control]]></category>
		<category><![CDATA[ground surface model]]></category>
		<category><![CDATA[infrastructure]]></category>
		<category><![CDATA[lidar]]></category>
		<category><![CDATA[MAC]]></category>
		<category><![CDATA[Mobile Data Collection]]></category>
		<category><![CDATA[pavement]]></category>
		<category><![CDATA[pavement design]]></category>
		<category><![CDATA[pavement imagery]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[PCR]]></category>
		<category><![CDATA[resurfacing]]></category>
		<category><![CDATA[road resurfacing]]></category>
		<category><![CDATA[survey]]></category>
		<category><![CDATA[TIN]]></category>

		<guid isPermaLink="false">https://eartheyelidar.wordpress.com/?p=224</guid>
		<description><![CDATA[DTS/EarthEye just completed a 9-mile mobile LiDAR scan of I-95 here in Florida and provided one of our partners with cross-slope information in a period of days.   The data was collected with our buddies at Riegl USA using their VMX-250 mobile LiDAR.  This information will be used to generate pavement resurfacing plans for the Florida [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=224&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.dtsgis.com">DTS</a>/<a href="http://www.eartheye.com">EarthEye</a> just completed a 9-mile mobile LiDAR scan of I-95 here in Florida and provided one of our partners with cross-slope information in a period of days.   The data was collected with our buddies at <a href="http://www.rieglusa.com/">Riegl USA</a> using their <a href="http://www.rieglusa.com/products/mobile/vmx-250/index.shtml">VMX-250 mobile LiDAR</a>.  This information will be used to generate pavement resurfacing plans for the Florida Department of Transportation (FDOT).</p>
<p align="justify">This project shows the value that this type of project can provide to the end user on both sides of the fence.</p>
<p align="justify">First, the paving contractor can use this data to develop their 30% plans for submittal to FDOT when bidding on a resurfacing or re-design contract.  Having accurate and relevant data related to the roadway’s characteristics gives the paving contractor an edge over the competition because they know what the field conditions are before preparing an over-engineered design specification.  This happens all of the time because the detailed field conditions are unknown while they are preparing their plans and they only have historical information to work from.</p>
<p align="justify">On the other side of the fence resides the FDOT.  They can benefit from this information because if they can provide this detailed information as part of a bid package, they can reap the benefits that are gained from better information.  If all contractors have the detailed as-built information (or in this case, accurate cross-slopes), they can all prepare their submittals using the same base information.  This will provide the FDOT project manager with more accurate responses based on true field conditions, resulting in more aggressive pricing and decreased project costs.</p>
<p align="justify">Here are some screenshots of the information.</p>
<p align="justify"><a href="http://eartheyelidar.files.wordpress.com/2011/04/image.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb.png?w=612&#038;h=383" alt="image" width="612" height="383" border="0" /></a></p>
<p align="center">LiDAR Data Viewed by Intensity and Corresponding Cross-Slope Profile</p>
<p align="left">Once the data has been collected and calibrated, we generate cross-slopes at a defined interval and export those out as 3D vectors.</p>
<p align="left"><a href="http://eartheyelidar.files.wordpress.com/2011/04/image1.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb1.png?w=612&#038;h=383" alt="image" width="612" height="383" border="0" /></a></p>
<p>These vectors are then symbolized based on their cross-slope percentages and exported as a KML file for ease of use.</p>
<p><a href="http://eartheyelidar.files.wordpress.com/2011/04/image2.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb2.png?w=607&#038;h=354" alt="image" width="607" height="354" border="0" /></a></p>
<p>Although this is a pretty simple step, the presentation of the data in <a href="http://www.google.com/earth/index.html">Google Earth</a> makes it easy for the end-user to visually identify problem areas and design the corrective actions according to field measurements.</p>
<p><a href="http://eartheyelidar.files.wordpress.com/2011/04/image3.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb3.png?w=603&#038;h=366" alt="image" width="603" height="366" border="0" /></a></p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/eartheyelidar.wordpress.com/224/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/eartheyelidar.wordpress.com/224/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/eartheyelidar.wordpress.com/224/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/eartheyelidar.wordpress.com/224/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/eartheyelidar.wordpress.com/224/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/eartheyelidar.wordpress.com/224/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/eartheyelidar.wordpress.com/224/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/eartheyelidar.wordpress.com/224/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/eartheyelidar.wordpress.com/224/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/eartheyelidar.wordpress.com/224/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/eartheyelidar.wordpress.com/224/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/eartheyelidar.wordpress.com/224/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/eartheyelidar.wordpress.com/224/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/eartheyelidar.wordpress.com/224/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=224&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://jasonamadori.com/2011/04/27/mobile-lidar-and-cross-slope-analysis/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<georss:point>28.509939 -81.154447</georss:point>
		<geo:lat>28.509939</geo:lat>
		<geo:long>-81.154447</geo:long>
		<media:content url="http://1.gravatar.com/avatar/3d3d8416c175862522eff2ab19c1f953?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">Jason</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb1.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb2.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/04/image_thumb3.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>
	</item>
		<item>
		<title>Chasing Cracks&#8230;</title>
		<link>http://jasonamadori.com/2011/03/23/chasing-cracks/</link>
		<comments>http://jasonamadori.com/2011/03/23/chasing-cracks/#comments</comments>
		<pubDate>Wed, 23 Mar 2011 03:22:21 +0000</pubDate>
		<dc:creator>Jason</dc:creator>
				<category><![CDATA[Pavement Management]]></category>
		<category><![CDATA[AMS]]></category>
		<category><![CDATA[Asset Management]]></category>
		<category><![CDATA[Consequences]]></category>
		<category><![CDATA[MAC]]></category>
		<category><![CDATA[Mobile Data Collection]]></category>
		<category><![CDATA[MUTCD]]></category>
		<category><![CDATA[Retroreflectivity]]></category>
		<category><![CDATA[risk]]></category>
		<category><![CDATA[Risk Assessment]]></category>
		<category><![CDATA[Sign Data Collection]]></category>
		<category><![CDATA[Sign Retroreflectivity]]></category>
		<category><![CDATA[valuation]]></category>

		<guid isPermaLink="false">https://eartheyelidar.wordpress.com/?p=207</guid>
		<description><![CDATA[Not the same crack that is in the news, but it is pretty addicting… We’ve built a bunch of new tools centered on pavement crack assessment and we’re excited about how it will increase the transparency related to pavement assessments.  In the past, pavement assessments have been more about delivering segments with PCI values attached [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=207&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>Not the same crack that is in the news, but it is pretty addicting…</p>
<p>We’ve built a bunch of new tools centered on pavement crack assessment and we’re excited about how it will increase the transparency related to pavement assessments.  In the past, pavement assessments have been more about delivering segments with PCI values attached to them and less about the actual measurements that were used during the creation of this data.</p>
<p><a href="http://eartheyelidar.files.wordpress.com/2011/03/image.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border-width:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/03/image_thumb.png?w=606&#038;h=459" border="0" alt="image" width="606" height="459" /></a></p>
<p>Our clients are always quick to say “We went out and checked a few segments and our assessments were different than what was reported”.  This lead to an educational discussion about how the ratings were created and how we applied the ASTM methodology to arrive at these results.  Most of the time we all agreed that there was always some subjectivity in the ratings, but that the standard rating methodology had been applied the same way throughout the network.</p>
<p>Our goal has always been to increase the transparency related to pavement inspections and this new approach has helped us to take a step in that direction.  The process is GIS-centric, as it is with all of our processes and involved a ton of tool development that will continue to evolve over time.  So, here’s what we’re doing…</p>
<p>First, we are collecting crack images using a downward-facing 4k linescan camera system with laser illumination.  This ensures that all of the pavement images are uniform and are not subject to low-lighting or shadows from natural and man-made features.  These images are 1mm resolution, allowing us to see the detailed cracking – especially at the lowest severity levels.</p>
<p><a href="http://eartheyelidar.files.wordpress.com/2011/03/image1.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border-width:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/03/image_thumb1.png?w=610&#038;h=448" border="0" alt="image" width="610" height="448" /></a></p>
<p>The following graphic illustrates the output from the crack mapping software we are using.  Cracks are identified in the imagery automatically from the software and are exported as geospatial points, lines and polygons.</p>
<p><a href="http://eartheyelidar.files.wordpress.com/2011/03/screenshot2.jpg"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border-width:0;" title="ScreenShot2" src="http://eartheyelidar.files.wordpress.com/2011/03/screenshot2_thumb.jpg?w=380&#038;h=486" border="0" alt="ScreenShot2" width="380" height="486" /></a></p>
<p>The software does a great job of identifying longitudinal, transverse, and alligator cracking.  Once we have the initial crack map, our team of compilers goes in and edits the crack maps as needed.  Typically, we are editing out false-positives and adding in other distresses as dictated by the scope of work.  This editing is done within our EarthView software and is completely geospatial in nature.  In other words, we can export these cracks, so they can be viewed in a GIS.  This is pretty exciting because all of these cracks can be mapped and themed in a GIS based on their severity levels.</p>
<p><a href="http://eartheyelidar.files.wordpress.com/2011/03/image2.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border-width:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/03/image_thumb2.png?w=614&#038;h=346" border="0" alt="image" width="614" height="346" /></a></p>
<p>This process gives the end user of the data a simple QA/QC process that can be used to understand the specific issues related to each segment.  Furthermore, this data is then combined with other GIS data sets (Functional Classification, Traffic Counts, etc.) so that a more holistic approach can be taken towards the determination of which segments need in terms of repair methods.  This data can also be exported to Google Earth for easy viewing and display in a non-GIS software.</p>
<p><a href="http://eartheyelidar.files.wordpress.com/2011/03/image3.png"><img style="background-image:none;padding-left:0;padding-right:0;display:inline;padding-top:0;border:0;" title="image" src="http://eartheyelidar.files.wordpress.com/2011/03/image_thumb3.png?w=615&#038;h=376" border="0" alt="image" width="615" height="376" /></a></p>
<p>We hope that this provides the end user with more tools in their GIS arsenal to better plan, bid, and execute their Capital Improvement Planning for the year.  In other words, our clients will be able to do more with their limited funding than ever before!</p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/eartheyelidar.wordpress.com/207/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/eartheyelidar.wordpress.com/207/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/eartheyelidar.wordpress.com/207/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/eartheyelidar.wordpress.com/207/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/eartheyelidar.wordpress.com/207/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/eartheyelidar.wordpress.com/207/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/eartheyelidar.wordpress.com/207/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/eartheyelidar.wordpress.com/207/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/eartheyelidar.wordpress.com/207/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/eartheyelidar.wordpress.com/207/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/eartheyelidar.wordpress.com/207/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/eartheyelidar.wordpress.com/207/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/eartheyelidar.wordpress.com/207/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/eartheyelidar.wordpress.com/207/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=207&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://jasonamadori.com/2011/03/23/chasing-cracks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<georss:point>28.509939 -81.154447</georss:point>
		<geo:lat>28.509939</geo:lat>
		<geo:long>-81.154447</geo:long>
		<media:content url="http://1.gravatar.com/avatar/3d3d8416c175862522eff2ab19c1f953?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">Jason</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/03/image_thumb.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/03/image_thumb1.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/03/screenshot2_thumb.jpg" medium="image">
			<media:title type="html">ScreenShot2</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/03/image_thumb2.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/03/image_thumb3.png" medium="image">
			<media:title type="html">image</media:title>
		</media:content>
	</item>
		<item>
		<title>Sign Retroreflectivity Compliance &#8211; A Geospatial Approach</title>
		<link>http://jasonamadori.com/2011/01/14/sign-retroreflectivity-compliance-a-geospatial-approach/</link>
		<comments>http://jasonamadori.com/2011/01/14/sign-retroreflectivity-compliance-a-geospatial-approach/#comments</comments>
		<pubDate>Fri, 14 Jan 2011 19:39:34 +0000</pubDate>
		<dc:creator>Jason</dc:creator>
				<category><![CDATA[Asset Management]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[AMS]]></category>
		<category><![CDATA[Consequences]]></category>
		<category><![CDATA[MAC]]></category>
		<category><![CDATA[Mobile Data Collection]]></category>
		<category><![CDATA[MUTCD]]></category>
		<category><![CDATA[Retroreflectivity]]></category>
		<category><![CDATA[risk]]></category>
		<category><![CDATA[Risk Assessment]]></category>
		<category><![CDATA[Sign Data Collection]]></category>
		<category><![CDATA[Sign Retroreflectivity]]></category>
		<category><![CDATA[valuation]]></category>

		<guid isPermaLink="false">http://jasonamadori.com/?p=170</guid>
		<description><![CDATA[We just completed a sign retroreflectivity shortlist presentation for the a client and discussed the options available for gaining compliance based on FHWA regulations as described in the MUTCD.  The client was sold on the &#8220;Blanket Replacement&#8221; method by a vendor who specializes in sign replacement. I was thinking &#8220;what a great selling strategy&#8221;, but [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=170&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>We just completed a sign retroreflectivity shortlist presentation for the a client and discussed the options available for gaining compliance based on FHWA regulations as described in the MUTCD.  The client was sold on the &#8220;Blanket Replacement&#8221; method by a vendor who specializes in sign replacement.</p>
<div id="attachment_176" class="wp-caption aligncenter" style="width: 585px"><a href="http://eartheyelidar.files.wordpress.com/2011/01/retro_guidelines.jpg"><img class="size-full wp-image-176 " style="border:3px solid black;" title="MUTCD Retroreflectivity Guidelines" src="http://eartheyelidar.files.wordpress.com/2011/01/retro_guidelines.jpg?w=575&#038;h=325" alt="" width="575" height="325" /></a><p class="wp-caption-text">MUTCD Retroreflectivity Guidelines</p></div>
<p>I was thinking &#8220;what a great selling strategy&#8221;, but then I thought twice about it.  This vendor had the ability to write their own ticket for selling their sign materials!  A great strategy for the vendor, but not a good option for the client.</p>
<p>We approached the presentation using a different approach &#8211; it combined the concept of risk with the general principles of Asset Management.  First, we would inventory their existing sign network to determine what they had and where it was.  Then, we would prioritize which areas were the most likely to fail based on the average age of the signs as well as the risk associated with the actual failure (e.g. pedestrian injury or vehicle damage due to an accident).</p>
<p style="text-align:center;">&nbsp;</p>
<div id="attachment_183" class="wp-caption aligncenter" style="width: 386px"><a href="http://eartheyelidar.files.wordpress.com/2011/01/risk_vw1.jpg"><img class="size-full wp-image-183 " style="border:3px solid black;" title="Risk_VW" src="http://eartheyelidar.files.wordpress.com/2011/01/risk_vw1.jpg?w=575" alt=""   /></a><p class="wp-caption-text">Risk Assessment for Signs</p></div>
<p style="text-align:center;">&nbsp;</p>
<div id="attachment_173" class="wp-caption aligncenter" style="width: 585px"><a href="http://eartheyelidar.files.wordpress.com/2011/01/baseline_calcs.jpg"><img class="size-full wp-image-173 " style="border:3px solid black;" title="Sample Replacement Cost Calculation" src="http://eartheyelidar.files.wordpress.com/2011/01/baseline_calcs.jpg?w=575&#038;h=301" alt="" width="575" height="301" /></a><p class="wp-caption-text">Sample Replacement Cost Calculation</p></div>
<p>This approach takes into consideration the entire segment of a road instead of considering an individual asset.  The client believes that it is more cost effective to replace the worst signs along a segment using a single mobilization of field crews, rather than jumping around and fixing signs based solely on their condition.  Therefore, we are combining the geospatial location, condition, age, value and MUTCD to develop a risk score for each individual sign.</p>
<div id="attachment_178" class="wp-caption aligncenter" style="width: 585px"><a href="http://eartheyelidar.files.wordpress.com/2011/01/sign_replacement_cycle.jpg"><img class="size-full wp-image-178" title="Sign_Replacement_Cycle" src="http://eartheyelidar.files.wordpress.com/2011/01/sign_replacement_cycle.jpg?w=575&#038;h=318" alt="" width="575" height="318" /></a><p class="wp-caption-text">Project Life Cycle</p></div>
<p>This analysis is used to create the biggest bang for the buck for our client by reducing risk related to accidents caused by failing signs.  Since all agencies have to be compliant with Regulatory, Guide and Warning signs by 2015, this approach will support a phased approach while taking care of the highest risk signs and working through the lower risk signs until all non-compliant signs have been replaced or are scheduled for replacement.</p>
<div id="attachment_175" class="wp-caption aligncenter" style="width: 585px"><a href="http://eartheyelidar.files.wordpress.com/2011/01/retro_dates.jpg"><img class="size-full wp-image-175 " style="border:3px solid black;" title="Retro_Dates" src="http://eartheyelidar.files.wordpress.com/2011/01/retro_dates.jpg?w=575&#038;h=300" alt="" width="575" height="300" /></a><p class="wp-caption-text">Compliance Dates for Sign Retroreflectivity</p></div>
<p style="text-align:center;">&nbsp;</p>
<div id="attachment_184" class="wp-caption aligncenter" style="width: 457px"><a href="http://eartheyelidar.files.wordpress.com/2011/01/valuation_vw1.jpg"><img class="size-full wp-image-184 " style="border:3px solid black;" title="Valuation_VW" src="http://eartheyelidar.files.wordpress.com/2011/01/valuation_vw1.jpg?w=575" alt=""   /></a><p class="wp-caption-text">Valuation of Sign Asset</p></div>
<p>In conclusion, the use of Risk to support the prioritization of asset maintenance serves an appropriate role in saving clients time and money.  By replacing the highest risk assets first, an agency can reduce their exposure to lawsuits related to failing infrastructure.</p>
<div id="attachment_182" class="wp-caption aligncenter" style="width: 585px"><a href="http://eartheyelidar.files.wordpress.com/2011/01/dashboard1.jpg"><img class="size-full wp-image-182 " style="border:3px solid black;" title="Dashboard" src="http://eartheyelidar.files.wordpress.com/2011/01/dashboard1.jpg?w=575&#038;h=177" alt="" width="575" height="177" /></a><p class="wp-caption-text">Executive Dashboard</p></div>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/eartheyelidar.wordpress.com/170/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/eartheyelidar.wordpress.com/170/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/eartheyelidar.wordpress.com/170/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/eartheyelidar.wordpress.com/170/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/eartheyelidar.wordpress.com/170/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/eartheyelidar.wordpress.com/170/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/eartheyelidar.wordpress.com/170/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/eartheyelidar.wordpress.com/170/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/eartheyelidar.wordpress.com/170/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/eartheyelidar.wordpress.com/170/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/eartheyelidar.wordpress.com/170/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/eartheyelidar.wordpress.com/170/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/eartheyelidar.wordpress.com/170/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/eartheyelidar.wordpress.com/170/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=170&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://jasonamadori.com/2011/01/14/sign-retroreflectivity-compliance-a-geospatial-approach/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<georss:point>28.509939 -81.154447</georss:point>
		<geo:lat>28.509939</geo:lat>
		<geo:long>-81.154447</geo:long>
		<media:content url="http://1.gravatar.com/avatar/3d3d8416c175862522eff2ab19c1f953?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">Jason</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/01/retro_guidelines.jpg" medium="image">
			<media:title type="html">MUTCD Retroreflectivity Guidelines</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/01/risk_vw1.jpg" medium="image">
			<media:title type="html">Risk_VW</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/01/baseline_calcs.jpg" medium="image">
			<media:title type="html">Sample Replacement Cost Calculation</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/01/sign_replacement_cycle.jpg" medium="image">
			<media:title type="html">Sign_Replacement_Cycle</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/01/retro_dates.jpg" medium="image">
			<media:title type="html">Retro_Dates</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/01/valuation_vw1.jpg" medium="image">
			<media:title type="html">Valuation_VW</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2011/01/dashboard1.jpg" medium="image">
			<media:title type="html">Dashboard</media:title>
		</media:content>
	</item>
		<item>
		<title>URISA Caribbean Conference in Trinidad</title>
		<link>http://jasonamadori.com/2010/12/08/urisa-caribbean-conference-in-trinidad/</link>
		<comments>http://jasonamadori.com/2010/12/08/urisa-caribbean-conference-in-trinidad/#comments</comments>
		<pubDate>Wed, 08 Dec 2010 12:00:19 +0000</pubDate>
		<dc:creator>Jason</dc:creator>
				<category><![CDATA[Asset Management]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Utilities]]></category>

		<guid isPermaLink="false">http://jasonamadori.com/?p=167</guid>
		<description><![CDATA[I am here for 3 days supporting the URISA Caribbean conference and presented to a group of Utilities who were interested in Asset Management of their electrical infrastructure.  It was interesting to hear that they have the same issues that we encounter in the US related to infrastructure preservation funding &#8211; Limited budgets, underfunded programs [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=167&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>I am here for 3 days supporting the URISA Caribbean conference and presented to a group of Utilities who were interested in Asset Management of their electrical infrastructure.  It was interesting to hear that they have the same issues that we encounter in the US related to infrastructure preservation funding &#8211; Limited budgets, underfunded programs and failing infrastructure.</p>
<p>We always do our best to stay &#8220;realistic&#8221; when it comes to Asset Management.  It has not been a priority in the past and will not be one in the future &#8211; until things start failing.  The funding will never be there in the amount that it is needed, so what do you do then?</p>
<p><strong>Start Small&#8230;</strong></p>
<p>We had a long discussion in this workshop about starting small and working your way into a larger AMS implementation.  By starting small, you can increase the probability of success of your project and &#8220;correct the path of the ship&#8221; if something was missed or overlooked.  Select one Asset Type and focus on building it into a comprehensive database of information.  By selecting one Asset Type, you can limit the amount of effort and risk it will take to build it into your AMS.</p>
<p><strong>Show it Off&#8230;</strong></p>
<p>Once you have some good asset data, show it off to everyone and make sure the decision-makers understand that it is available for use.  Build charts, graphs and reports about the Asset and build a plan around getting that Asset into the work cycle for maintenance and operations.  One of the most important things I recommend is to identify the &#8220;Worst&#8221; Assets and get them fixed immediately.  These typically create liability for your agency and if left unattended, could cost more than the AMS itself.</p>
<p><strong>Make it Indispensable</strong></p>
<p>Once the AMS is used to make decisions and answer questions related to infrastructure, it will become the &#8220;Go To&#8221; system that your agency will use moving forward.  At that time, you will be able to show the value of the system and gain leverage in terms of future funding, new assets, etc.  At this point, no one would make the call to shut this system down because of the value it adds to everyday decision-making.</p>
<p>Those are some recommendations that we discussed this week &#8211; looking forward to 2 more days of collaboration and learning about Trinidad&#8217;s Utility industry!</p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/eartheyelidar.wordpress.com/167/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/eartheyelidar.wordpress.com/167/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/eartheyelidar.wordpress.com/167/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/eartheyelidar.wordpress.com/167/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/eartheyelidar.wordpress.com/167/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/eartheyelidar.wordpress.com/167/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/eartheyelidar.wordpress.com/167/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/eartheyelidar.wordpress.com/167/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/eartheyelidar.wordpress.com/167/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/eartheyelidar.wordpress.com/167/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/eartheyelidar.wordpress.com/167/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/eartheyelidar.wordpress.com/167/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/eartheyelidar.wordpress.com/167/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/eartheyelidar.wordpress.com/167/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=167&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://jasonamadori.com/2010/12/08/urisa-caribbean-conference-in-trinidad/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<georss:point>28.509939 -81.154447</georss:point>
		<geo:lat>28.509939</geo:lat>
		<geo:long>-81.154447</geo:long>
		<media:content url="http://1.gravatar.com/avatar/3d3d8416c175862522eff2ab19c1f953?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">Jason</media:title>
		</media:content>
	</item>
		<item>
		<title>Some Cool Powerline Data to Support NERC&#8217;s Rule 810 Recommendation</title>
		<link>http://jasonamadori.com/2010/11/09/some-cool-powerline-data-to-support-nercs-rule-810-recommendation/</link>
		<comments>http://jasonamadori.com/2010/11/09/some-cool-powerline-data-to-support-nercs-rule-810-recommendation/#comments</comments>
		<pubDate>Tue, 09 Nov 2010 22:18:10 +0000</pubDate>
		<dc:creator>Jason</dc:creator>
				<category><![CDATA[Airborne LiDAR]]></category>
		<category><![CDATA[3D as-built]]></category>
		<category><![CDATA[Airborne LiDAR for Utilities]]></category>
		<category><![CDATA[FERC Regulations]]></category>
		<category><![CDATA[lidar]]></category>
		<category><![CDATA[NERC Regulations]]></category>
		<category><![CDATA[Transmission Compliance]]></category>
		<category><![CDATA[Transmission Encroachments]]></category>
		<category><![CDATA[Utility LiDAR]]></category>

		<guid isPermaLink="false">http://jasonamadori.com/?p=140</guid>
		<description><![CDATA[With the recent release of NERC&#8217;s &#8220;Recommendation to Industry&#8221; on October 7th, 2010, we have been contacted by many transmission companies to LiDAR their transmission lines.  The recommendation asks all Transmission Planning Engineers, Transmission Maintenance Engineers and Transmission Planners to measure and report any &#8220;Facility Ratings&#8221; that do not meet their intended design criteria based [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=140&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>With the recent release of NERC&#8217;s &#8220;Recommendation to Industry&#8221; on October 7th, 2010, we have been contacted by many transmission companies to LiDAR their transmission lines.  The recommendation asks all Transmission Planning Engineers, Transmission Maintenance Engineers and Transmission Planners to measure and report any &#8220;Facility Ratings&#8221; that do not meet their intended design criteria based on actual field conditions.  The plan to achieve this must be submitted to NERC by December 15th, 2010.</p>
<p>This post discusses how we are supporting the industry with this compliance effort utilizing LiDAR, imagery and spatial analysis.</p>
<p>The first step in the process is the data collection effort focused on collecting precise powerline data and calibrating it to local control to achieve engineering-grade accuracies.</p>
<div id="attachment_154" class="wp-caption alignnone" style="width: 338px"><img class="size-full wp-image-154" title="Classified LiDAR Point Cloud (Brown = Ground, Green = Vegetation)" src="http://eartheyelidar.files.wordpress.com/2010/11/transmission_pc_3.jpg?w=575" alt="Classified LiDAR Point Cloud (Brown = Ground, Green = Vegetation)"   />Cl<span style="line-height:17px;font-size:11px;">assified LiDAR Point Cloud (Brown = Ground, Green = Vegetation)</span></dt>
</dl>
</div>
<p>The next process involves the creation of 3D vectors from the point cloud.  First, the raw point cloud is loaded into our Viewer.</p>
<div class="mceTemp">
<dl class="wp-caption  alignleft">
<dt class="wp-caption-dt"><img class="size-medium wp-image-143" title="Powerline Data Displayed by Elevation" src="http://eartheyelidar.files.wordpress.com/2010/11/powerline.jpg?w=300&#038;h=182" alt="Powerline Data Displayed by Elevation" width="300" height="182" /><p class="wp-caption-text">Powerline Data Displayed by Elevation</p></div>
<p style="text-align:left;">&nbsp;</p>
<p style="text-align:left;">&nbsp;</p>
<p style="text-align:left;">&nbsp;</p>
<p style="text-align:left;">&nbsp;</p>
<p style="text-align:left;">&nbsp;</p>
<p style="text-align:left;">&nbsp;</p>
<p style="text-align:left;">&nbsp;</p>
<p style="text-align:left;">&nbsp;</p>
<div id="attachment_147" class="wp-caption alignleft" style="width: 310px"><a href="http://eartheyelidar.files.wordpress.com/2010/11/powerline_slide_1.jpg"><img class="size-medium wp-image-147" title="Raw Point Cloud" src="http://eartheyelidar.files.wordpress.com/2010/11/powerline_slide_1.jpg?w=300&#038;h=147" alt="Raw Point Cloud" width="300" height="147" /></a><p class="wp-caption-text">Raw Point Cloud</p></div>
<p style="text-align:left;">&nbsp;</p>
<p style="text-align:left;">&nbsp;</p>
<p style="text-align:left;">&nbsp;</p>
<p style="text-align:left;">&nbsp;</p>
<p style="text-align:left;">&nbsp;</p>
<p style="text-align:left;">&nbsp;</p>
<p style="text-align:left;">&nbsp;</p>
<p style="text-align:left;"><a href="http://eartheyelidar.files.wordpress.com/2010/11/powerline_slide_2.jpg"><img class="size-medium wp-image-148" title="Create Attachment Points at Conductor Location" src="http://eartheyelidar.files.wordpress.com/2010/11/powerline_slide_2.jpg?w=300&#038;h=147" alt="Create Attachment Points at Conductor Location" width="300" height="147" /></a></p>
<div class="mceTemp">
<dl class="wp-caption alignleft">
<dd class="wp-caption-dd">Create Attachment Points at Conductor Location</dd>
</dl>
</div>
<p style="text-align:left;">&nbsp;</p>
<p style="text-align:left;">&nbsp;</p>
<div id="attachment_161" class="wp-caption alignnone" style="width: 310px"><a href="http://eartheyelidar.files.wordpress.com/2010/11/powerline_slide_31.jpg"><img class="size-medium wp-image-161" title="Select 3 Locations along Line" src="http://eartheyelidar.files.wordpress.com/2010/11/powerline_slide_31.jpg?w=300&#038;h=147" alt="Select 3 Locations along Line" width="300" height="147" /></a><p class="wp-caption-text">Select 3 Locations along Line</p></div>
<div id="attachment_151" class="wp-caption alignleft" style="width: 310px"><a href="http://eartheyelidar.files.wordpress.com/2010/11/powerline_slide_5.jpg"><img class="size-medium wp-image-151" title="Software Models Line Geometry in 3D from Point Cloud" src="http://eartheyelidar.files.wordpress.com/2010/11/powerline_slide_5.jpg?w=300&#038;h=146" alt="Software Models Line Geometry in 3D from Point Cloud" width="300" height="146" /></a><p class="wp-caption-text">Software Models Line Geometry in 3D from Point Cloud</p></div>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Resulting Data set in EarthView Software:</p>
<div id="attachment_153" class="wp-caption alignleft" style="width: 310px"><a href="http://eartheyelidar.files.wordpress.com/2010/11/transmission_pc_2.jpg"><img class="size-medium wp-image-153" title="Transmission Lines Modeled in 3D" src="http://eartheyelidar.files.wordpress.com/2010/11/transmission_pc_2.jpg?w=300&#038;h=189" alt="Transmission Lines Modeled in 3D" width="300" height="189" /></a><p class="wp-caption-text">Transmission Lines Modeled in 3D</p></div>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Once the lines are modeled, we work with the agency to define the search criteria for performing the spatial analysis and encroachment analysis in the software.  We load these parameters and automatically identify the encroachments related to vegetation features and conductors.</p>
<div id="attachment_156" class="wp-caption alignleft" style="width: 310px"><a href="http://eartheyelidar.files.wordpress.com/2010/11/veg_encroach_1.jpg"><img class="size-medium wp-image-156" title="Vegetation Encroachments Modeled in 3D and Highlighted in Blue (Grow-in) and Orange (Fall-in)" src="http://eartheyelidar.files.wordpress.com/2010/11/veg_encroach_1.jpg?w=300&#038;h=183" alt="Vegetation Encroachments Modeled in 3D and Highlighted in Blue (Grow-in) and Orange (Fall-in)" width="300" height="183" /></a><p class="wp-caption-text">Vegetation Encroachments Modeled in 3D and Highlighted in Blue (Grow-in) and Orange (Fall-in)</p></div>
<div id="attachment_157" class="wp-caption alignleft" style="width: 310px"><a href="http://eartheyelidar.files.wordpress.com/2010/11/veg_encroach_2.jpg"><img class="size-medium wp-image-157" title="Orthographic View of Potential Violations" src="http://eartheyelidar.files.wordpress.com/2010/11/veg_encroach_2.jpg?w=300&#038;h=183" alt="Orthographic View of Potential Violations" width="300" height="183" /></a><p class="wp-caption-text">Orthographic View of Potential Violations</p></div>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Parcel data is then used to deploy field crews and empowers them with local information in the case they need to determine who is responsible for vegetation encroachment and property access.</p>
<div id="attachment_158" class="wp-caption alignleft" style="width: 310px"><a href="http://eartheyelidar.files.wordpress.com/2010/11/veg_encroach_3_parcels.jpg"><img class="size-medium wp-image-158" title="Owner Information Incorporated into Vegetation Analysis" src="http://eartheyelidar.files.wordpress.com/2010/11/veg_encroach_3_parcels.jpg?w=300&#038;h=184" alt="Owner Information Incorporated into Vegetation Analysis" width="300" height="184" /></a><p class="wp-caption-text">Owner Information Incorporated into Vegetation Analysis</p></div>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Planimetric data is also created so that the information can be used to update line drawings and as-built information.</p>
<div id="attachment_145" class="wp-caption alignleft" style="width: 310px"><a href="http://eartheyelidar.files.wordpress.com/2010/11/powerline3.jpg"><img class="size-medium wp-image-145" title="Planimetric Data Incorporated into Point Cloud" src="http://eartheyelidar.files.wordpress.com/2010/11/powerline3.jpg?w=300&#038;h=197" alt="Planimetric Data Incorporated into Point Cloud" width="300" height="197" /></a><p class="wp-caption-text">Planimetric Data Incorporated into Point Cloud</p></div>
<div id="attachment_146" class="wp-caption alignleft" style="width: 310px"><a href="http://eartheyelidar.files.wordpress.com/2010/11/powerline4.jpg"><img class="size-medium wp-image-146" title="Planimetric Data Incorporated into Point Cloud" src="http://eartheyelidar.files.wordpress.com/2010/11/powerline4.jpg?w=300&#038;h=175" alt="Planimetric Data Incorporated into Point Cloud" width="300" height="175" /></a><p class="wp-caption-text">Planimetric Data Incorporated into Point Cloud</p></div>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>At the end of the day, we are able to generate many different types of deliverables for our clients.  The keys to this process include accurate calibration of data, 3D vector generation, encroachment automation, and industry-specific delivery formats.</p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/eartheyelidar.wordpress.com/140/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/eartheyelidar.wordpress.com/140/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/eartheyelidar.wordpress.com/140/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/eartheyelidar.wordpress.com/140/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/eartheyelidar.wordpress.com/140/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/eartheyelidar.wordpress.com/140/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/eartheyelidar.wordpress.com/140/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/eartheyelidar.wordpress.com/140/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/eartheyelidar.wordpress.com/140/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/eartheyelidar.wordpress.com/140/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/eartheyelidar.wordpress.com/140/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/eartheyelidar.wordpress.com/140/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/eartheyelidar.wordpress.com/140/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/eartheyelidar.wordpress.com/140/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=140&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://jasonamadori.com/2010/11/09/some-cool-powerline-data-to-support-nercs-rule-810-recommendation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<georss:point>28.509939 -81.154447</georss:point>
		<geo:lat>28.509939</geo:lat>
		<geo:long>-81.154447</geo:long>
		<media:content url="http://1.gravatar.com/avatar/3d3d8416c175862522eff2ab19c1f953?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">Jason</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2010/11/transmission_pc_3.jpg" medium="image">
			<media:title type="html">Classified LiDAR Point Cloud (Brown = Ground, Green = Vegetation)</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2010/11/powerline.jpg?w=300" medium="image">
			<media:title type="html">Powerline Data Displayed by Elevation</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2010/11/powerline_slide_1.jpg?w=300" medium="image">
			<media:title type="html">Raw Point Cloud</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2010/11/powerline_slide_2.jpg?w=300" medium="image">
			<media:title type="html">Create Attachment Points at Conductor Location</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2010/11/powerline_slide_31.jpg?w=300" medium="image">
			<media:title type="html">Select 3 Locations along Line</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2010/11/powerline_slide_5.jpg?w=300" medium="image">
			<media:title type="html">Software Models Line Geometry in 3D from Point Cloud</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2010/11/transmission_pc_2.jpg?w=300" medium="image">
			<media:title type="html">Transmission Lines Modeled in 3D</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2010/11/veg_encroach_1.jpg?w=300" medium="image">
			<media:title type="html">Vegetation Encroachments Modeled in 3D and Highlighted in Blue (Grow-in) and Orange (Fall-in)</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2010/11/veg_encroach_2.jpg?w=300" medium="image">
			<media:title type="html">Orthographic View of Potential Violations</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2010/11/veg_encroach_3_parcels.jpg?w=300" medium="image">
			<media:title type="html">Owner Information Incorporated into Vegetation Analysis</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2010/11/powerline3.jpg?w=300" medium="image">
			<media:title type="html">Planimetric Data Incorporated into Point Cloud</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2010/11/powerline4.jpg?w=300" medium="image">
			<media:title type="html">Planimetric Data Incorporated into Point Cloud</media:title>
		</media:content>
	</item>
		<item>
		<title>Getting Ready for Some Rail Data</title>
		<link>http://jasonamadori.com/2010/09/24/getting-ready-for-some-rail-data/</link>
		<comments>http://jasonamadori.com/2010/09/24/getting-ready-for-some-rail-data/#comments</comments>
		<pubDate>Fri, 24 Sep 2010 12:35:46 +0000</pubDate>
		<dc:creator>Jason</dc:creator>
				<category><![CDATA[mobile lidar]]></category>
		<category><![CDATA[lidar]]></category>
		<category><![CDATA[LiDAR for PTC]]></category>
		<category><![CDATA[Positive Train Control]]></category>
		<category><![CDATA[Rail Collection]]></category>
		<category><![CDATA[Rail lData Collection]]></category>

		<guid isPermaLink="false">http://jasonamadori.com/?p=130</guid>
		<description><![CDATA[We are going to have some rail data collected here soon and I&#8217;ll post the results as soon as I get them.  We&#8217;ll be collecting a 17-mile section of track in the DC area, so it will be full of urban canyons, tunnels and highway overpasses.  At least we&#8217;ll know how well the equipment will [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=130&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>We are going to have some rail data collected here soon and I&#8217;ll post the results as soon as I get them.  We&#8217;ll be collecting a 17-mile section of track in the DC area, so it will be full of urban canyons, tunnels and highway overpasses.  At least we&#8217;ll know how well the equipment will be performing in the field because this will be a true field test of the equipment.</p>
<p>We just finished getting e-Rail certified to work with the railroad, so now it is time to provide some value to this market.  They are looking to collect features that will support <a title="PTC" href="http://en.wikipedia.org/wiki/Positive_train_control" target="_blank">Positive Train Control</a> as well as giving them engineering-grade information that can be used for maintenance &amp; rehabilitation efforts.</p>
<div id="attachment_133" class="wp-caption aligncenter" style="width: 585px"><a href="http://eartheyelidar.files.wordpress.com/2010/09/rail_3.jpg"><img class="size-full wp-image-133" title="Rail_3" src="http://eartheyelidar.files.wordpress.com/2010/09/rail_3.jpg?w=575&#038;h=366" alt="" width="575" height="366" /></a><p class="wp-caption-text">Rail Intensity</p></div>
<p>Our goal will be to collect all of this information in one pass and give them tools to automate the extraction of other features such as the rail, ballast, gauge, etc.  Data collection will happen next week and we&#8217;ll have some results to share at that point.</p>
<div id="attachment_134" class="wp-caption aligncenter" style="width: 585px"><a href="http://eartheyelidar.files.wordpress.com/2010/09/rail_4.jpg"><img class="size-full wp-image-134" title="Rail_4" src="http://eartheyelidar.files.wordpress.com/2010/09/rail_4.jpg?w=575&#038;h=365" alt="" width="575" height="365" /></a><p class="wp-caption-text">Rail LiDAR with Elevation</p></div>
<div id="attachment_131" class="wp-caption aligncenter" style="width: 585px"><a href="http://eartheyelidar.files.wordpress.com/2010/09/rail_1.jpg"><img class="size-full wp-image-131" title="Rail_1" src="http://eartheyelidar.files.wordpress.com/2010/09/rail_1.jpg?w=575&#038;h=362" alt="" width="575" height="362" /></a><p class="wp-caption-text">Rail Data Themed by Elevation</p></div>
<div id="attachment_132" class="wp-caption aligncenter" style="width: 585px"><a href="http://eartheyelidar.files.wordpress.com/2010/09/rail_2.jpg"><img class="size-full wp-image-132" title="Rail_2" src="http://eartheyelidar.files.wordpress.com/2010/09/rail_2.jpg?w=575&#038;h=362" alt="" width="575" height="362" /></a><p class="wp-caption-text">Rail Data with Intensity</p></div>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/eartheyelidar.wordpress.com/130/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/eartheyelidar.wordpress.com/130/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/eartheyelidar.wordpress.com/130/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/eartheyelidar.wordpress.com/130/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/eartheyelidar.wordpress.com/130/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/eartheyelidar.wordpress.com/130/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/eartheyelidar.wordpress.com/130/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/eartheyelidar.wordpress.com/130/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/eartheyelidar.wordpress.com/130/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/eartheyelidar.wordpress.com/130/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/eartheyelidar.wordpress.com/130/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/eartheyelidar.wordpress.com/130/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/eartheyelidar.wordpress.com/130/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/eartheyelidar.wordpress.com/130/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=jasonamadori.com&amp;blog=10808310&amp;post=130&amp;subd=eartheyelidar&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://jasonamadori.com/2010/09/24/getting-ready-for-some-rail-data/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<georss:point>28.509939 -81.154447</georss:point>
		<geo:lat>28.509939</geo:lat>
		<geo:long>-81.154447</geo:long>
		<media:content url="http://1.gravatar.com/avatar/3d3d8416c175862522eff2ab19c1f953?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">Jason</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2010/09/rail_3.jpg" medium="image">
			<media:title type="html">Rail_3</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2010/09/rail_4.jpg" medium="image">
			<media:title type="html">Rail_4</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2010/09/rail_1.jpg" medium="image">
			<media:title type="html">Rail_1</media:title>
		</media:content>

		<media:content url="http://eartheyelidar.files.wordpress.com/2010/09/rail_2.jpg" medium="image">
			<media:title type="html">Rail_2</media:title>
		</media:content>
	</item>
	</channel>
</rss>
