[postgis-devel] Postgis Raster JPEG 2000 (openjpeg)
clay.nathaniel at gmail.com
Mon Apr 7 12:54:50 PDT 2014
There are two JPEG 2000 specifications that apply that are applicable to
our needs and fulfill some of the requirements that I came up with.
1. JPIP or JPEG 2000 Photo Interactive Protocol (
This would give us a well thought out index format that would allow us to
treat our raster blob as a embedded table. With the ability to insert,
update and union the rasters without decompressing the tiles in their
entirety and in most cases decompression would not be necessary at all. (
2. OSGEO JPEG 2000 GML (
GML would allow us to annotate raster with vectors and provide spatial and
temporal reference of the embedded code streams ( tiles).
PS. Have you collected your thoughts yet on the current short comings?
Nathaniel Hunter Clay
On Mon, Mar 24, 2014 at 3:08 PM, Nathaniel Clay <clay.nathaniel at gmail.com>wrote:
> What I really want is Nested Tables, as far as I can tell Postrgresql
> doesn't fully support it.....
> Nathaniel Hunter Clay
> On Mon, Mar 24, 2014 at 1:37 PM, Bborie Park <dustymugs at gmail.com> wrote:
>> So not self-contained? For one coverage table containing raster tiles,
>> you'd have a second hidden table of the packets? How would a function know
>> where the packet table is?
>> On Mon, Mar 24, 2014 at 9:41 AM, Nathaniel Clay <clay.nathaniel at gmail.com
>> > wrote:
>>> No, each of the packets would be stored in a row in the packet table,
>>> and the raster tile object would have the FK of each of the packets related
>>> to that tile and maintain a ordered lists of the packet tables FK's of each
>>> progression order.
>>> Nathaniel Hunter Clay
>>> postgis-devel mailing list
>>> postgis-devel at lists.osgeo.org
>> postgis-devel mailing list
>> postgis-devel at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the postgis-devel