<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Webdings;
panose-1:5 3 1 2 1 5 9 6 7 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:.5in;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:2025545426;
mso-list-type:hybrid;
mso-list-template-ids:-1004270648 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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 class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Elevation FIT,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Hope everyone enjoyed the holidays and got off to a good start with the New Year. Some time has passed since our last meeting, and I need to provide a quick update. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> Since our last meeting the follow<span style='color:#003300'>ing</span> has occurred (in a nutshell):<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='font-family:Symbol;color:#1F497D'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><b><u>Governance</u></b><span style='color:#003300'> -</span> <span style='color:#003300'>W</span>e need to be making progress. Key objectives include producing 1) an Elevation Stewardship Plan and 2) an Elevation FIT Charter. Next steps include: 1) meeting with representatives from PAC, FIT and GPL to address development of these OGIC products, 2) distributing our draft stewardship plan for FIT review and comment<span style='color:#003300'>,</span> and then 3) moving forward with completion and adoption. First the Stewardship plan and then the Charter.<span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><b><u>Pursuing Data Development</u></b><span style='color:#003300'> -</span> <span style='color:#003300'>A</span>fter a fairly exhaustive evaluation of IFSAR and lack of consensus to pursue, work began evaluating alternate options for acquiring elevation data for the ‘hinterlands’ and developing a matrix for review by the group, i.e., a tool to asses options and reach consensus. Options currently include 1) IFSAR, 2) lower density Lidar, 3) deriving DEMs from existing NAIP, and 4) including DEMs in upcoming flights. Selective criteria under consideration for the matrix currently include 1) cost, 2) quality, 3) value supporting common needs, and 4) reusability, i.e., public elevation information with no restrictions on use or distribution preferred. <b><u><o:p></o:p></u></b></p><p class=MsoListParagraph>Regarding options 3 and 4: Emmor Nile (ODF) has been involved, and Doug Smith (DSA) has been researching options with Mike Tully from ASI (NAIP contractors).<span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><b><u>Including Bathymetry</u></b> <span style='color:#003300'>- </span>After the presentation, discussion and consensus to incorporate bathymetry at our last meeting, Emmor Nile (ODF), Jon Dasler (DEA), Jacob Macdonald (USACE) and I continued discussion regarding the accommodation of these data. The basic idea is to update the current elevation standard, 2005 Oregon Elevation Data Standard Version 1.1, to include and reference bathymetry:<o:p></o:p></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='font-family:"Courier New"'><span style='mso-list:Ignore'>o<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]>Building on domains and feature types to accommodate Bathymetry vector data, e.g., 1) spot depth/elevation points, 2) contour lines (depth contours or isobaths), cross<span style='color:#003300'>-</span>sections and breaklines such as thalweg, channel, shelf, top of bank; and 3) polygons to delineate water’s edge and mapping extents<span style='color:#003300'>.</span><o:p></o:p></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='font-family:"Courier New"'><span style='mso-list:Ignore'>o<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]>Addressing datum and accuracy standards such as 1) reference to the standards and methods used for data collection and an associated mapping accuracy indicator, e.g., NMAS for 10ft contours; and 2) anchor points with horizontal and vertical datum descriptions to provide a spatial reference and an indicator to determine if data have been projected.<o:p></o:p></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='font-family:"Courier New"'><span style='mso-list:Ignore'>o<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]>Updating the raster elevation standard at the same time to address bathymetry in that format as well.<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Next steps include: 1) refining the 2005 Oregon Elevation Data Standard Version 1.1, 2) circulating it for review and comment, 3) accommodating comments, 4) FIT adoption, and then 5) OGIC adoption.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><b><u>Pursuing Data Sharing</u></b> <span style='color:#003300'>- </span>Evaluating methods to provide on-line web services to best available elevation data <b><u><o:p></o:p></u></b></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='font-family:"Courier New"'><span style='mso-list:Ignore'>o<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]>Initiating a pilot to evaluate web based services with NASA, following up their offer to host Lidar data for the state and pursuing methods to provide OSS access via WorldWind (preliminary stages); investigating other solutions as well, such as LP360 Server, ArcGIS Server, and existing solutions available across the state.<b><u><o:p></o:p></u></b></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='font-family:"Courier New"'><span style='mso-list:Ignore'>o<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]>Identifying policy issues needing attention, e.g., clarifying national security interests, clarifying ‘public information’, etc. and in general refining policy to encourage the sharing of publicly<span style='color:#003300'>-</span>funded elevation data cross the state.<b><u><o:p></o:p></u></b></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Next steps for pilots include 1) clarifying state needs for web<span style='color:#003300'>-</span>based services, 2) clarifying specifics of pilot, 3) evaluating solutions, and 4) developing recommendations for funding. Next steps for the policy issues include 1) identifying issues that restrict access and prevent data sharing (core issues), 2) evaluating technical methods to address core issues and 3) proposing policy language to address core issues and promote data sharing.<o:p></o:p></span></p><p class=MsoNormal><b><u><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p><span style='text-decoration:none'> </span></o:p></span></u></b></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I’m currently operating under the following priorities, in this order, 1) governance as requested by OGIC, 2) data development plan for the hinterlands as needed by those without OLC products or resources to acquire OLC products, 3) follow<span style='color:#003300'>-</span>up from actions at FIT meetings (bathymetry), and 4) general needs expressed by FIT meeting attendees and others throughout the state to promote data sharing<span style='color:#003300'>;</span> i.e., many people are still struggling to find best available elevation data and get access. . . . . I know that other priorities exist. This is not intended to be full account of what needs to occur, just an update.<o:p></o:p></span></p><p class=MsoNormal><b><u><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p><span style='text-decoration:none'> </span></o:p></span></u></b></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Significant work lies ahead. Success requires a balance between finding creative solutions to support short<span style='color:#003300'>-</span>term needs and reserving time to craft a solid governance model to support long<span style='color:#003300'>-</span>term needs. Once through <span style='color:#003300'>our City </span>budget process (preparing FY10 estimated actual and FY11 budget, accommodating further budget reductions and dealing with some staff transfers)<span style='color:#003300'>,</span> I’ll follow up with a more in-depth update and schedule for the 2011. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>In the interim, please feel free to comment, question and clarify your needs regarding elevation data. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Thank you for your time,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><b><i><span style='font-family:"Arial","sans-serif"'>Brandt Melick</span></i></b><i><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1728D4'><br></span></i><span style='font-size:13.5pt;font-family:Webdings;color:#1728D4'>ü</span><span style='font-size:10.0pt;font-family:Webdings;color:#1728D4'> </span><i><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1728D4'>TSD Manager<o:p></o:p></span></i></p><p class=MsoNormal><i><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1728D4'><o:p> </o:p></span></i></p><p class=MsoNormal><i><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1728D4'>Technical Services Division<o:p></o:p></span></i></p><p class=MsoNormal><i><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1728D4'>Public Works Department<o:p></o:p></span></i></p><p class=MsoNormal><i><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1728D4'>City of Springfield<br>225 Fifth Street<br>Springfield, OR 97477</span></i><span style='font-family:"Calibri","sans-serif";color:#1728D4'><o:p></o:p></span></p><p class=MsoNormal><i><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1728D4'>Phone: 541.726.4645<br>Fax: 541.736.1021</span></i><span style='color:#1728D4'><o:p></o:p></span></p><p class=MsoNormal><i><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1728D4'>Email: </span></i><a href="mailto:bmelick@springfield-or.gov"><i><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>bmelick@springfield-or.gov</span></i></a><i><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></i></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Please note that my email has changed to <a href="mailto:bmelick@springfield-or.gov">bmelick@springfield-or.gov</a>. My old email address will continue to work for some time.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p></div></body></html>