IMO:
Thanks for the comments Michael,
I was wondering if you'd contribute;-)
(Also, note that wavelet does
not necessarily imply lossy anymore, as many assume. Story of my
life.)
Can you point me to any studies to support the claim that JPEG2000 can
indeed be indeed non-lossy?
IMO:
Hi Tyler,
Thanks for the reply.
Am I correct in believing that the two things people desire with
images in an RDB, is having an abstract 1) storage framework
(tables) and
2) a common access language (SQL) for managing the
framework. You could have the most complex storage
Hi,
Should we start spreading the GSoC 2008 program for OSGeo
around the Internet (Usenet, blogs, forums) or it's yet too early?
Greetings
--
Mateusz Loskot
http://mateusz.loskot.net
___
Discuss mailing list
Discuss@lists.osgeo.org
On 21.02.2008 12:45, Mateusz Loskot wrote:
Hi,
Should we start spreading the GSoC 2008 program for OSGeo
around the Internet (Usenet, blogs, forums) or it's yet too early?
I think we should first wait for Google to announce it (any day now). In
the mean time we can get organized (list
[EMAIL PROTECTED] wrote:
IMO:
Hi Tyler,
Thanks for the reply.
Am I correct in believing that the two things people desire with
images in an RDB, is having an abstract 1) storage framework
(tables) and
2) a common access language (SQL) for managing the
framework. You could have the
- Some of the biggest advantages though, come from the corporate IT
support that you come to rely on, e.g. regular backups, large disk
capacity on fast SAN devices, secure access to data by authorised
custodians, redundant databases for disaster recovery, point in time
restoration of
All too often, the benefits touted for raster-in-database have
nothing to do with the database, and everything to do with the data
preparation tools that the vendor is including with their raster-in-
database solution.
To store rasters in a database, you need a set of tools that will (a)
IMO:
Hi Paulo,
I have been wondering, and haven't found much literature on the
subject of applying GIS to the EP chain. I can see it would be
useful, but can't exactly see where and how.
Also note, that I am coming from a geology background, now working
with reservoir geophysics, and
On Thu, 2008-02-21 at 16:24 -0800, Paul Ramsey wrote:
On Feb 21, 2008, at 4:19 PM, [EMAIL PROTECTED] wrote:
What it comes down to is what is appropriate for your use case.
Indeed! However, there seem to be vanishingly few use cases for which
raster-in-database is actually the more
IMO:
Paul,
On Feb 21, 2008, at 4:19 PM, [EMAIL PROTECTED] wrote:
What it comes down to is what is appropriate for your use case.
Indeed! However, there seem to be vanishingly few use cases for which
raster-in-database is actually the more appropriate solution.
;-) I beg to
IMO:
Tim,
Would you like to expand on this?
Bruce
Completely off the wall thought, but what about using git?
Tim
Notice:
This email and any attachments may contain information that is personal,
confidential, legally privileged and/or copyright.No part of it should be
Hi Bruce,
What approaches are people using with large Lidar datasets?
You might take a look at the WeoGeo group. They are a commercial operation,
not FOSS, but they are throwing dedicated AWS instances at the issue of
lidar file serving. The dedicated instance, I gather, is for the sole
IMO
12 million records is teensy. Stuff it into PostGIS. It's the billion-
point LIDAR sets that leave me queasy, but I can't begin to think of a
reasonable architecture for that without learning more about how the
points are actually USED, which I really am not clear on at the moment.
13 matches
Mail list logo
