<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns="http://www.w3.org/TR/REC-html40" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="GENERATOR" content="MSHTML 8.00.6001.19258">
<style>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
LI.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
DIV.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoAcetate {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
LI.MsoAcetate {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
DIV.MsoAcetate {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
SPAN.BalloonTextChar {
FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text"; mso-style-name: "Balloon Text Char"
}
SPAN.EmailStyle19 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: personal
}
SPAN.EmailStyle20 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal
}
SPAN.EmailStyle21 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.WordSection1 {
page: WordSection1
}
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div dir="ltr" align="left">
<div dir="ltr" align="left"><font color="#000080" face="Arial">All,</font></div>
<div dir="ltr" align="left"><font color="#000080" face="Arial"><span class="174475121-12072012"></span></font> </div>
<div dir="ltr" align="left"><font color="#000080" face="Arial"><span class="174475121-12072012">I have been asked to respond to the "observations" below.</span></font></div>
<div dir="ltr" align="left"><font color="#000080" face="Arial"><span class="174475121-12072012"></span></font> </div>
<div dir="ltr" align="left"><font color="#000080" face="Arial"><span class="174475121-12072012">First of all, OR-Trans (OT) is not, in the form it was given to DAS, a cartographic product. It is a GIS dataset for analysis. The USGS transportation layer is
a cartographic product. Comparing them is like comparing apples and oranges.</span></font></div>
<div dir="ltr" align="left"><font color="#000080" face="Arial"><span class="174475121-12072012"></span></font> </div>
<div dir="ltr" align="left"><span class="174475121-12072012"><font color="#000080" face="Arial">The OT data given to DAS GEO was made into a layer file based on whether or not a road was a highway or not and what type of road a record is (Road, Street, Avenue
etc). This is not the best way to mimic the a road networks true functional use. There are some avenues that carry more traffic than others and a street may carry more traffic than a road in one case and visa versa in another. The best way to symbolize
a road network is through the use of a combination of factors. You can see ODOT's product that incorporates that appropriate cartography while using OT here:
</font>
<div><font size="2"><a title="blocked::blocked::https://gis.odot.state.or.us/transgis/
blocked::https://gis.odot.state.or.us/transgis/" href="blocked::blocked::https://gis.odot.state.or.us/transgis/"><font title="blocked::blocked::https://gis.odot.state.or.us/transgis/" color="#000080" face="Arial">https://gis.odot.state.or.us/transgis/</font></a></font><font face="Arial"><font color="#000080"> <span class="174475121-12072012">
This is available as a service and was used in the Raptor application for the Olympic trials in Eugene.</span></font></font></div>
<div><font face="Arial"><font color="#000080"><span class="174475121-12072012"></span></font></font> </div>
<div><font face="Arial"><font color="#000080"><span class="174475121-12072012">In the version of OT that was given to DAS GEO, there are only 25 of the 36 counties data that is in that service, plus state data and federal data. So there will be roads and in
fact entire counties worth of data missing. We are limited in distributing data at this point by not having data sharing agreements with all of our data sources. ODOT worked with a contractor that had significant dealings with the local data development
for county and 911 purposes and were able to leverage that for getting DSA's signed to share data.</span></font></font></div>
<div><font face="Arial"><font color="#000080"><span class="174475121-12072012"></span></font></font> </div>
<div><font face="Arial"><font color="#000080"><span class="174475121-12072012">The good thing for state agencies is that we have "gentlemen's" agreements with the other 11 counties to be able to distribute data to state agencies for official state business
and only that. Since this is published as a service it was decided to show the lesser dataset (That is what we decided wasn't it Erik?).</span></font></font></div>
<div><font face="Arial"><font color="#000080"><span class="174475121-12072012"></span></font></font> </div>
<div><font face="Arial"><font color="#000080"><span class="174475121-12072012">Railroads in ODOT data are a GIS analytical. dataset and not a cartographic dataset again. We have done some work to make the GIS data look a little more cartographically pleasing
in the TransGIS link above.</span></font></font></div>
<span class="174475121-12072012">
<div><br>
<font color="#000080" face="Arial">Since these are services, I will have to defer creating "light" and "dark" version to Erik. But I am sure that is feasible.</font></div>
<div><font color="#000080" face="Arial"></font> </div>
<div></span><span class="174475121-12072012"><font color="#000080" face="Arial">Since cartography wasn't the mark we were trying to hit, it stands to reason that we can't compete in that venue. But as one can see, TransGIS does a much better job getting to
a cartographic product even though we are using a dataset meant for analysis. But that service is not ODOT's cartography and for that matter the data isn't ODOT's data we are merely the folks that were tasked to compile a whole bunch of data that gave folks
a complete census of the roads (to the extent possible) in Oregon using data developed locally that is usually the most timely and most accurate (spatially and attributes).</font></span></div>
<div><span class="174475121-12072012"><font color="#000080" face="Arial"></font></span> </div>
<div><span class="174475121-12072012"><font color="#000080" face="Arial">I hope that clarifies what the appropriate uses for OR-Trans should be. And explains some of the observations seen. Please if you have specific questions/concerns like these talk to
me. Chances are I will probably have an answer for you.</font></span></div>
<span class="174475121-12072012">
<div><br>
<font color="#000080" face="Arial">Thank you</font></div>
<div><br>
<span class="174475121-12072012"><font color="#000080" face="Arial">Chad</font></span></span></div>
</span></div>
<br>
</div>
<br>
<div dir="ltr" lang="en-us" class="OutlookMessageHeader" align="left">
<hr tabindex="-1">
<font size="2" face="Tahoma"><b>From:</b> gpl_list-bounces@listsmart.osl.state.or.us [mailto:gpl_list-bounces@listsmart.osl.state.or.us]
<b>On Behalf Of </b>HILL Milton E * EISPD GEO<br>
<b>Sent:</b> Thursday, July 12, 2012 9:15 AM<br>
<b>To:</b> 'gpl_list@listsmart.osl.state.or.us'<br>
<b>Subject:</b> [gpl_list] Comments regarding the recent DOT Transportation Layer<br>
</font><br>
</div>
<div></div>
<div class="WordSection1">
<p class="MsoNormal"><span style="COLOR: #1f497d">From Dorothy:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><i><span style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: #1f497d"><o:p> </o:p></span></i></p>
<p class="MsoNormal"><i><span style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: #1f497d">--- Milt<o:p></o:p></span></i></p>
</div>
<p class="MsoNormal"><span style="COLOR: #1f497d"><o:p> </o:p></span></p>
<div>
<div style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<p class="MsoNormal"><b><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</span></b><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> Dorothy Mortenson [mailto:dorothy.c.mortenson@state.or.us]
<br>
<b>Sent:</b> Thursday, July 12, 2012 9:13 AM<br>
<b>To:</b> HILL Milton E * EISPD GEO<br>
<b>Subject:</b> FW: Comments regarding the recent DOT Transportation Layer<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: #1f497d; FONT-SIZE: 10pt">Milt,</span></b><b><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="COLOR: #1f497d">Can you send this to the GPL? I do not have permission to send and Bob is out for a couple of weeks. Thank you.<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="COLOR: #1f497d">Dorothy<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="COLOR: #1f497d">-----------------------------------------------<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"><o:p> </o:p></span></p>
<p class="MsoNormal">I have taken a closer look at the transportation rest service:<o:p></o:p></p>
<p class="MsoNormal"><a href="http://navigator.state.or.us/ArcGIS/rest/services/Framework/Trans_GeneralMap/MapServer">http://navigator.state.or.us/ArcGIS/rest/services/Framework/Trans_GeneralMap/MapServer</a>
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have compared it to the USGS transportation layer that was used for the recently published topographic maps:<o:p></o:p></p>
<p class="MsoNormal"><a href="http://services.nationalmap.gov/ArcGIS/rest/services/transportation/MapServer">http://services.nationalmap.gov/ArcGIS/rest/services/transportation/MapServer</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Comments:<o:p></o:p></p>
<p class="MsoNormal">1) In comparing the two in ArcMap, USGS wins in that:<o:p></o:p></p>
<p class="MsoNormal">* The grouping of layers is done very well in the USGS version, with the ability to turn different layers on and off (interstate, county roads, etc. and their respective labels).<o:p></o:p></p>
<p class="MsoNormal">* It appears to be more complete. I found that when I zoomed in, there were connecting roads missing, whereas they are filled in and seamless in USGS. An example is attached.<o:p></o:p></p>
<p class="MsoNormal">* The documentation is pretty good, tho could stand for a little improvement.<o:p></o:p></p>
<p class="MsoNormal">* The railroads are much cleaner, tho maybe not as technically correct. USGS wins cartographically; ODOT might be a good choice for query analysis.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">2) Both could use a "light" and "dark" version, depending on what the background will be.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">3) I believe the ODOT version is missing the mark cartographically at the statewide level, but could be greatly improved if it used a similar strategy as the USGS as far as how the layers are broken out. The symbology for the Highway Network
theme and the Signed Routes are a little too bold to be used with anything else. As a guide, look at any of the Street Map services. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have not looked at the downloadable data yet.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dorothy<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ><(((('>
</span><span style="FONT-FAMILY: 'Tahoma','sans-serif'"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">Dorothy Mortenson</span><span style="FONT-FAMILY: 'Tahoma','sans-serif'"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">Oregon Water Resources Department</span><span style="FONT-FAMILY: 'Tahoma','sans-serif'"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">(503)986-0857</span><span style="FONT-FAMILY: 'Tahoma','sans-serif'"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>