<br><font size=2><tt>IMO:</tt></font>
<br>
<br><font size=2><tt>Paul,<br>
<br>
> <br>
> On Feb 21, 2008, at 4:19 PM, Bruce.Bannerman@dpi.vic.gov.au wrote:<br>
> ><br>
> > What it comes down to is what is appropriate for your use case.<br>
> <br>
> Indeed! However, there seem to be vanishingly few use cases for which
<br>
> raster-in-database is actually the more appropriate solution.<br>
> </tt></font>
<br>
<br><font size=2><tt>;-) I beg to differ.</tt></font>
<br>
<br><font size=2><tt><br>
> (BTW, point-in-time recovery, a nice example of a place where database
<br>
> semantics have an upper hand. Although more modern file systems
and <br>
> enterprise backup systems are pretty competitive now... even a <br>
> relatively simple hack like the OS/X Time Machine feature solves that
<br>
> problem for-all-practical-purposes.)<br>
></tt></font>
<br>
<br>
<br><font size=2><tt>Trying to manage very large regional datasets via
a file based solution is problematic as described earlier with tile based
approach to vector data in particular. Again for my use case the DB is
better.</tt></font>
<br>
<br>
<br><font size=2><tt>Just to throw in another related issue:</tt></font>
<br>
<br><font size=2><tt>Lidar systems are throwing out an enormous amount
of data. I had one dataset of only around 17 million odd records several
years ago (of course stored in our corporate db ;-) ) that we could not
handle with ArcGIS Desktop (v9.1). From memory it was a 32bit issue.</tt></font>
<br>
<br><font size=2><tt>What approaches are people using with large Lidar
datasets?</tt></font>
<br>
<br>
<br><font size=2><tt>Bruce</tt></font>
<br>
<br><font size=2><tt><br>
</tt></font>
<P><FONT face=Arial size=2>Notice:</FONT><FONT
style="BACKGROUND-COLOR: #ff0000"><BR></FONT><FONT size=2><FONT face=Arial>This
email and any attachments may contain information that is personal,
confidential,<BR>legally privileged and/or copyright.</FONT> <FONT face=Arial>No
part of it should be reproduced, adapted or communicated </FONT><FONT
face=Arial>without the prior written consent of the copyright owner.
</FONT></FONT></P>
<P><FONT size=2><FONT face=Arial>It is the responsibility of the recipient to
check for and remove viruses.</FONT></FONT></P>
<P><FONT face=Arial size=2>If you have received this email in error, please
notify the sender by return email, delete it from your system and destroy any
copies. You are not authorised to use, communicate or rely on the information
contained in this email.</FONT></P>
<P><FONT face=Arial color=#008000 size=2>Please consider the environment before
printing this email.</FONT></P>
<P><FONT face=Arial size=2></FONT> </P>
<P> </P>
<P> </P>