<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="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Comic Sans MS";
panose-1:3 15 7 2 3 3 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{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";
mso-believe-normal-left:yes;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<![if mso 9]>
<style>
p.MsoNormal
{margin-left:3.0pt;}
</style>
<![endif]><!--[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=blue style='margin-left:3.0pt;margin-top:3.0pt;
margin-right:3.0pt;margin-bottom:.75pt'><!--ppd1000033-->
<div class=Section1>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>Bobb
wrote: “Here's my reasoning, we're never (ever?) going to hit the top end
on how big files ever get, resolution just keeps going up and up, so there is
always going to be some upper limit that will need to be breached somehow.
Working out a proper method for segregating the data up front (dare I say
it), as some sort of standard (which can be adjusted as time passes) will make
everything work nicely, then all will work with available tools when they are
available, if tools to handle larger datasets become available, and the
community feels there is a reason/need that these new larger files need to be
handled, then they get to change the standard.”<o:p></o:p></span></font></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>I
agree with some of the points you are making in your argument Bobb. There is
certainly a practical limit to how much you data you should put in a single
file. That is why we have lumber cut to 8 foot lengths. You don’t need a
flatbed semi to carry it to your house. :]<o:p></o:p></span></font></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>When
you refer to a standard for splitting data up front, what do you mean?<o:p></o:p></span></font></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>It
would be interesting to come up with a standard structure on a computer file
system that could be used to accessed tiled raster data, if this hasn’t
been done already. One the file system structure was defined, it would be
fairly easy to write open source software that accessed this structure and
provided individual tiles as a service to desktop GIS applications.<o:p></o:p></span></font></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>Landon<o:p></o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='margin:0in;margin-bottom:.0001pt;
text-align:center'><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
discuss-bounces@lists.osgeo.org [mailto:discuss-bounces@lists.osgeo.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Bob Basques<br>
<b><span style='font-weight:bold'>Sent:</span></b> Monday, August 24, 2009 7:33
AM<br>
<b><span style='font-weight:bold'>To:</span></b> OSGeo Discussions<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [OSGeo-Discuss] Open
File Formats and ProprietaryAlgorithms</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p><font size=3 face="Comic Sans MS"><span style='font-size:12.0pt;font-family:
"Comic Sans MS"'>All,</span></font> <o:p></o:p></p>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p><font size=3 face="Comic Sans MS"><span style='font-size:12.0pt;font-family:
"Comic Sans MS"'>Ok, I'm probably going to get someone irritated, but here goes
. .</span></font> <o:p></o:p></p>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p><font size=3 face="Comic Sans MS"><span style='font-size:12.0pt;font-family:
"Comic Sans MS"'>Why not approach this from the other end of the spectrum and
work at making the original files smaller. Work with the providers to
make the images smaller in the first place, or at least come up with a maximum
practical size to work with, I mean if this is the only (or biggest reason) for
implementing JP2, then getting folks to make the smaller deliverables seems
like a better long term approach.</span></font> <o:p></o:p></p>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p><font size=3 face="Comic Sans MS"><span style='font-size:12.0pt;font-family:
"Comic Sans MS"'>Here's my reasoning, we're never (ever?) going to hit the top
end on how big files ever get, resolution just keeps going up and up, so there
is always going to be some upper limit that will need to be breached somehow.
Working out a proper method for segregating the data up front (dare I say
it), as some sort of standard (which can be adjusted as time passes) will make
everything work nicely, then all will work with available tools when they are
available, if tools to handle larger datasets become available, and the
community feels there is a reason/need that these new larger files need to be
handled, then they get to change the standard.</span></font> <o:p></o:p></p>
<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p><font size=3 face="Comic Sans MS"><span style='font-size:12.0pt;font-family:
"Comic Sans MS"'>bobb</span></font> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:0in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'><br>
<br>
<br>
<o:p></o:p></span></font></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'><br>
<br>
>>> "Fawcett, David" <David.Fawcett@state.mn.us>
wrote:<o:p></o:p></span></font></p>
<div style='border:none;border-left:solid #050505 1.0pt;padding:0in 0in 0in 5.0pt;
margin-left:11.25pt'>
<p style='background:#F3F3F3'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'><br>
I realize that there are likely not a large number of people who have<br>
the expertise and experience to write this kind of code. <br>
<br>
Is this a project that should be shopped around for funding? Google<br>
Summer of Code? A grant from our ~benevolent overlord
Google? Some<br>
other foundation or org interested in open data formats? <br>
<br>
David.<br>
-----Original Message-----<br>
From: discuss-bounces@lists.osgeo.org<br>
[mailto:discuss-bounces@lists.osgeo.org] On Behalf Of Michael P. Gerlek<br>
Sent: Thursday, August 20, 2009 4:36 PM<br>
To: OSGeo Discussions<br>
Subject: RE: [OSGeo-Discuss] Open File Formats and Proprietary<br>
Algorithms<br>
<snip><br>
<br>
<br>
> Do you know why there hasn't been a broader adoption of JP2?<br>
<br>
Not through lack of trying on my part :-)<br>
<br>
I think the two biggest reasons are:<br>
<br>
(1) The algorithms for handling large images in memory really are rocket<br>
science, and no one in the FOSS community has gotten the "itch"<br>
sufficiently bad enough to go and do the work needed inside the existing<br>
open source packages. Hopefully someday someone will.<br>
<br>
<br>
_______________________________________________<br>
Discuss mailing list<br>
Discuss@lists.osgeo.org <a
href="http://lists.osgeo.org/mailman/listinfo/discuss">http://lists.osgeo.org/mailman/listinfo/discuss</a><br>
_______________________________________________<br>
Discuss mailing list<br>
Discuss@lists.osgeo.org<br>
<a href="http://lists.osgeo.org/mailman/listinfo/discuss">http://lists.osgeo.org/mailman/listinfo/discuss</a><o:p></o:p></span></font></p>
</div>
</div>
<BR><BR><P><FONT face=Arial><FONT size=1><STRONG>Warning:<BR></STRONG>Information provided via electronic media is not guaranteed against defects including translation and transmission errors. </FONT></FONT><FONT face=Arial><FONT size=1>If the reader is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this information in error, please notify the sender immediately.</FONT></FONT></P></body>
</html>