<html o="urn:schemas-microsoft-com:office:office" v="urn:schemas-microsoft-com:vml" xmlns="http://www.w3.org/TR/REC-html40" w="urn:schemas-microsoft-com:office:word">
<head>
<style type="text/css">
<!--
body { margin-left: 4px; margin-right: 4px; font-variant: normal; margin-top: 4px; margin-bottom: 1px; line-height: normal }
li.msonormal { margin-left: 0in; margin-right: 0in; font-family: Times New Roman; font-size: 12.0pt }
span.emailstyle18 { color: navy; font-family: Arial }
a:visited { color: blue; text-decoration: underline }
p { margin-right: 0in; margin-left: 0in; font-family: Times New Roman; margin-top: 0in; margin-bottom: .0001pt; font-size: 12.0pt }
span.msohyperlink { color: blue; text-decoration: underline }
span.msohyperlinkfollowed { color: blue; text-decoration: underline }
a:link { color: blue; text-decoration: underline }
p.msonormal { margin-right: 0in; margin-left: 3.0pt; font-family: Times New Roman; font-size: 12.0pt }
div.msonormal { margin-left: 0in; margin-right: 0in; font-family: Times New Roman; font-size: 12.0pt }
-->
</style>
</head>
<body style="margin-right: 3.0pt; margin-left: 3.0pt; margin-top: 3.0pt; margin-bottom: .75pt" link="blue" lang="EN-US" vlink="blue">
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">Landon,</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">>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. </font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">Hmm, interesting angle, to expand on your idea a bit more, what about a processing suite (or set of suites) that process data for different types of uses, visual display, DEM analysis, etc. Each "processor" stack would/could have it's own rules associated with data resolution vs files sizes, etc. </font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">bobb</font> </p>
<br> <br><br>
<p style="margin-bottom: 0; margin-top: 0">
<br>
<br>
>>> "Landon Blake" <lblake@ksninc.com> wrote:<br> </p>
<div style="margin-right: 0; margin-left: 15px; margin-top: 0; border-left: solid 1px #050505; margin-bottom: 0; background-color: #f3f3f3; padding-left: 7px">
<p style="margin-bottom: 0; margin-top: 0">
<!--ppd1000033-->
</p>
<div class="section1">
<br>
<div style="font-family: Arial; font-size: 10.0pt">
<p style="margin-bottom: 0; margin-top: 0">
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="#DEFAULT"></o> </p>
</div>
<br>
<div style="font-family: Arial; font-size: 10.0pt">
<p style="margin-bottom: 0; margin-top: 0">
<o p="#DEFAULT">
</o> </p>
</div>
<br>
<div style="font-family: Arial; font-size: 10.0pt">
<p style="margin-bottom: 0; margin-top: 0">
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="#DEFAULT"></o> </p>
</div>
<br>
<div style="font-family: Arial; font-size: 10.0pt">
<p style="margin-bottom: 0; margin-top: 0">
<o p="#DEFAULT">
</o> </p>
</div>
<br>
<div style="font-family: Arial; font-size: 10.0pt">
<p style="margin-bottom: 0; margin-top: 0">
When you refer to a standard for splitting data up front, what do you mean?<o p="#DEFAULT"></o> </p>
</div>
<br>
<div style="font-family: Arial; font-size: 10.0pt">
<p style="margin-bottom: 0; margin-top: 0">
<o p="#DEFAULT">
</o> </p>
</div>
<br>
<div style="font-family: Arial; font-size: 10.0pt">
<p style="margin-bottom: 0; margin-top: 0">
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="#DEFAULT"></o> </p>
</div>
<br>
<div style="font-family: Arial; font-size: 10.0pt">
<p style="margin-bottom: 0; margin-top: 0">
<o p="#DEFAULT">
</o> </p>
</div>
<br>
<div style="font-family: Arial; font-size: 10.0pt">
<p style="margin-bottom: 0; margin-top: 0">
Landon<o p="#DEFAULT"></o> </p>
</div>
<div>
<div style="text-align: center; margin-right: 0in; margin-left: 0in; margin-top: 0in; margin-bottom: .0001pt" align="center" class="msonormal">
<div style="font-size: 12.0pt">
<p style="margin-bottom: 0; margin-top: 0">
<hr size="2" tabindex="-1" width="100%" align="center">
</p>
</div>
</div>
<br>
<div style="font-family: Tahoma; font-weight: bold; font-size: 10.0pt">
<p style="margin-bottom: 0; margin-top: 0">
From: </p>
</div>
<div style="font-family: Tahoma; font-size: 10.0pt">
<p style="margin-bottom: 0; margin-top: 0">
discuss-bounces@lists.osgeo.org [mailto:discuss-bounces@lists.osgeo.org] </p>
<div style="font-weight: bold">
<p style="margin-bottom: 0; margin-top: 0">
On Behalf Of </p>
</div>
<p style="margin-bottom: 0; margin-top: 0">
Bob Basques<br> </p>
<div style="font-weight: bold">
<p style="margin-bottom: 0; margin-top: 0">
Sent: </p>
</div>
<p style="margin-bottom: 0; margin-top: 0">
Monday, August 24, 2009 7:33 AM<br> </p>
<div style="font-weight: bold">
<p style="margin-bottom: 0; margin-top: 0">
To: </p>
</div>
<p style="margin-bottom: 0; margin-top: 0">
OSGeo Discussions<br> </p>
<div style="font-weight: bold">
<p style="margin-bottom: 0; margin-top: 0">
Subject: </p>
</div>
<p style="margin-bottom: 0; margin-top: 0">
RE: [OSGeo-Discuss] Open File Formats and ProprietaryAlgorithms </p>
</div>
<p style="margin-bottom: 0; margin-top: 0">
<o p="#DEFAULT">
</o>
</p>
</div>
<br>
<div style="font-size: 12.0pt">
<p style="margin-bottom: 0; margin-top: 0">
<o p="#DEFAULT">
</o> </p>
</div>
<br>
<div style="font-family: Comic Sans MS; font-size: 12.0pt">
<p style="margin-bottom: 0; margin-top: 0">
All, </p>
</div>
<p style="margin-bottom: 0; margin-top: 0">
<o p="#DEFAULT">
</o>
</p>
<br>
<div style="font-size: 12.0pt">
<p style="margin-bottom: 0; margin-top: 0">
<o p="#DEFAULT">
</o> </p>
</div>
<br>
<div style="font-family: Comic Sans MS; font-size: 12.0pt">
<p style="margin-bottom: 0; margin-top: 0">
Ok, I'm probably going to get someone irritated, but here goes . . </p>
</div>
<p style="margin-bottom: 0; margin-top: 0">
<o p="#DEFAULT">
</o>
</p>
<br>
<div style="font-size: 12.0pt">
<p style="margin-bottom: 0; margin-top: 0">
<o p="#DEFAULT">
</o> </p>
</div>
<br>
<div style="font-family: Comic Sans MS; font-size: 12.0pt">
<p style="margin-bottom: 0; margin-top: 0">
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. </p>
</div>
<p style="margin-bottom: 0; margin-top: 0">
<o p="#DEFAULT">
</o>
</p>
<br>
<div style="font-size: 12.0pt">
<p style="margin-bottom: 0; margin-top: 0">
<o p="#DEFAULT">
</o> </p>
</div>
<br>
<div style="font-family: Comic Sans MS; font-size: 12.0pt">
<p style="margin-bottom: 0; margin-top: 0">
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. </p>
</div>
<p style="margin-bottom: 0; margin-top: 0">
<o p="#DEFAULT">
</o>
</p>
<br>
<div style="font-size: 12.0pt">
<p style="margin-bottom: 0; margin-top: 0">
<o p="#DEFAULT">
</o> </p>
</div>
<br>
<div style="font-family: Comic Sans MS; font-size: 12.0pt">
<p style="margin-bottom: 0; margin-top: 0">
bobb </p>
</div>
<p style="margin-bottom: 0; margin-top: 0">
<o p="#DEFAULT">
</o>
</p>
<br>
<div style="font-size: 12.0pt">
<p style="margin-bottom: 0; margin-top: 0">
<br>
<br>
<br>
<o p="#DEFAULT">
</o>
</p>
</div>
<br>
<div style="font-size: 12.0pt">
<p style="margin-bottom: 0; margin-top: 0">
<br>
<br>
>>> "Fawcett, David" <David.Fawcett@state.mn.us> wrote:<o p="#DEFAULT"></o> </p>
</div>
<div style="padding-right: 0in; margin-left: 11.25pt; padding-top: 0in; border-left: solid #050505 1.0pt; padding-bottom: 0in; padding-left: 5.0pt; border: none">
<br>
<div style="font-size: 12.0pt">
<p style="margin-bottom: 0; margin-top: 0">
<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="#DEFAULT"></o> </p>
</div>
</div>
</div>
<p style="margin-bottom: 0; margin-top: 0">
<br>
<br>
</p>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Arial" size="1"><b>Warning:<br style="font-family: Arial; font-weight: bold; font-size: 1"></b>Information provided via electronic media is not guaranteed against defects including translation and transmission errors. 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>
</p>
</div>
</body>
</html>