Re: [OSGeo-Discuss] 'lossless' JPEG2000

2008-02-27 Thread François-Olivier Devaux

Hi Michael,

We made some tests with tiles of 1000*1000 pixels, with 1 tiles, and 
the memory used is about 112 MB for the encoding and 114 MB for the 
decoding.
If you don't want to use tiles, I don't think OpenJPEG can beat the 
commercial applications like Kakadu.


What standard do you follow for metadata ? OGC GMLJP2, or do you include 
GeoTIFF information in a JP2 file like Luratech suggested to the JPEG 
committee ?


Cheers,

François

Michael P. Gerlek a écrit :

François:

When you say Mega-Images (- geo-sized images), just how big are you talking 
about?

If you are in the 10-100GB range, I/LizardTech would be very interested in 
talking with you about the project, and also about supporting some of the geo 
metadata conventions.  (Especially if you can do GB-sized data sets in less 
than 1GB of RAM without requiring the image be tiled!)  ((Do you have any 
benchmark data you can share?)

-mpg

 

  

-Original Message-
From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of 
François-Olivier Devaux

Sent: Tuesday, February 26, 2008 12:47 AM
To: discuss@lists.osgeo.org
Subject: [OSGeo-Discuss] 'lossless' JPEG2000

Hi,

Norman Vine has pointed to me this discussion about JPEG 2000, and I 
thought it might be interesting to give you a small overview on JPEG 
2000 and present the OpenJPEG library on which we are working.



FIELDS WHERE JPEG 2000 IS USED

JPEG 2000 is becoming the reference in image compression for 
professional applications, where precision and flexibility is really 
necessary.


The most know field using JPEG 2000 is Digital Cinema, where 
JPEG 2000 
has been favored against MPEG2 and H.264. Linked to that field, High 
Quality Broadcast applications are also turning to JPEG 2000 
because of 
its quality and scalability (low resolution versions can be extracted 
directly from a high resolution sequence without any re-encoding, and 
JPEG 2000 sequences are encoded in intra which eases video editing).


More close to your field is Archiving, where we are feeling a 
trend to 
select JPEG 2000 as compression algorithm

http://www.egov.vic.gov.au/index.php?env=-inlink/detail:m1780-


1-1-8-s-0:l-9669-1-1--
  
Medical imaging applications, where lossless compression is a 
important 
requirement, are also taking full advantage of JPEG 2000 
remote browsing 
possibilities (with the JPIP protocol)

http://www.earthtimes.org/articles/show/aware-inc-to-demonstra


te-groundbreaking-medical-imaging-streaming-solution-at- himss08,290686.shtml
  

-
JPEG 2000 FEATURES

The JPEG 2000 features that are interesting for GeoSpatial 
Imagery is of 
course the ability to achieve lossless compression, the scalability 
(lower quality and resolutions as well as spatial areas can 
be extracted 
from a compressed file, without the need of decompression the entire 
file), the high precision (most codecs can at least handle 16 
bits per 
component, and up to 256 components) and the fact that the 
core coding 
system can be obtained free of charge.
JPEG 2000 also has an inherent robustness higher than most 
compression 
schemes (JPEG, ...) and a great protocol to interactively remotely 
browse images called JPIP.


-
OPENJPEG

OpenJPEG, is an open-source JPEG 2000 library. It has been 
very recently 
remodeled by the CNES and the french company CS to meet the 
requirements 
of applications using Mega-Images (- geo-sized images). Independent 
access to tiles has been improved, in order to increase the library 
encoding and decoding performances. This new version should be made 
accessible to users at the beginning of March. We are very 
happy of the 
performances of this new version, and are open to new contributions.
Regarding other JPEG 2000 open source solutions in your 
field, the GDAL 
library has a JPEG 2000 module that is based on Jasper, which 
is a great 
library, but has unfortunately not evolved for the last years.


-

Cheers,

François
___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss



___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss
  


___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] Google Summer of Code 2008

2008-02-27 Thread Wolf Bergenheim
Google announced Summer of Code 2008 on Monday, mentor applications can 
be sent in on the 3rd. So we should get to work on creating the ideas 
lists and signing up as volunteer mentors! ;)


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?



Please start spreading the word. I hope we will have many cool projects 
done this summer!


--Wolf

--

:3 ) Wolf Bergenheim ( 8:

___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


[OSGeo-Discuss] RE: OGC WPS and Amazon SQS

2008-02-27 Thread Randy George
I noticed OGC finalized the WPS spec:
http://www.opengeospatial.org/pressroom/pressreleases/843

 

Does anyone know of projects working on WPS implementations?

 

The goal of WPS is apparently to provide a consistent framework for
interchangeable service process algorithms that can potentially be chained
together into answers to higher level questions than the typical 'what',
'when', and 'where.' Dealing with 'why', 'how much', and 'what if' modeling
usually requires a process pipeline for convolutions, boolean band
operations, and summary pixel calculations, all of which are cpu cycle
intense, especially for large imagery sets. In fact cpu usage issues would
make the usual service approach prohibitive.  Even the little I have worked
on JAI pipelines shows me the futility of a one cpu to many service requests
approach for WPS.

 

However, looking at the AWS Simple Queue Service, SQS
http://www.amazon.com/Simple-Queue-Service-home-page/b/ref=sc_fe_l_2?ie=UTF8
http://www.amazon.com/Simple-Queue-Service-home-page/b/ref=sc_fe_l_2?ie=UTF
8node=13584001no=3435361me=A36L942TSJ2AJA
node=13584001no=3435361me=A36L942TSJ2AJA, some interesting possibilities
come to mind.

Locking message queues with AMI instance pools is essentially a poor man's
supercomputer. It would be interesting to look at harnessing the utility
computing concept with instance pools available for each stage in a process
pipeline connected using the asynchronous SQS service. This is a more or
less controlled 'distributed computing model' applied to WPS. 

Ref here for some examples of existing distributed computing projects:
http://distributedcomputing.info/projects.html 

 

Here are a couple possible approaches to a WPS service model that might
overcome the cpu bottle neck:

1)  Sequential SQS pipeline with dedicated instance for each process
node - this would work best for operations amenable to a streaming pipeline
- Boolean band operations or pixel summary operations for instance 

 

2)  Distributed computing model with a chunk server feeding a pipeline
and an array pool of instances processing the chunks coming down the SQS
queue - this would be better suited to tiled operations 

 

WPS is great when someone else provides the service. I imagine it would be
very interesting to the academic scientific world and government groups
tasked with providing access to all the myriad imagery coming off space
sensor platforms. 

 

Just thinking out loud.   More thoughts here:
http://www.cadmaps.com/gisblog/?p=28

 

randy

 

___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


RE: [OSGeo-Discuss] 'lossless' JPEG2000

2008-02-27 Thread Michael P. Gerlek
So that's 10GB of data, using tiles, at 100MB memory?  That's good, and maybe 
requiring tiles for larger images is something I could get used to.  What's the 
speed like?
 
We use both the GMLJP2 standard and the GeoTIFF-tag approach.
 
Gosh but I'd to get behind an open source geo-aware JP2 solution.
 
-mpg
 





From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of 
François-Olivier Devaux
Sent: Wednesday, February 27, 2008 1:50 AM
To: OSGeo Discussions
Subject: Re: [OSGeo-Discuss] 'lossless' JPEG2000


Hi Michael,

We made some tests with tiles of 1000*1000 pixels, with 1 tiles, 
and the memory used is about 112 MB for the encoding and 114 MB for the 
decoding.
If you don't want to use tiles, I don't think OpenJPEG can beat the 
commercial applications like Kakadu.

What standard do you follow for metadata ? OGC GMLJP2, or do you 
include GeoTIFF information in a JP2 file like Luratech suggested to the JPEG 
committee ?

Cheers,

François

Michael P. Gerlek a écrit : 

François:

When you say Mega-Images (- geo-sized images), just how big 
are you talking about?

If you are in the 10-100GB range, I/LizardTech would be very 
interested in talking with you about the project, and also about supporting 
some of the geo metadata conventions.  (Especially if you can do GB-sized data 
sets in less than 1GB of RAM without requiring the image be tiled!)  ((Do you 
have any benchmark data you can share?)

-mpg

 

  

-Original Message-
From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of 
François-Olivier Devaux
Sent: Tuesday, February 26, 2008 12:47 AM
To: discuss@lists.osgeo.org
Subject: [OSGeo-Discuss] 'lossless' JPEG2000

Hi,

Norman Vine has pointed to me this discussion about 
JPEG 2000, and I 
thought it might be interesting to give you a small 
overview on JPEG 
2000 and present the OpenJPEG library on which we are 
working.


FIELDS WHERE JPEG 2000 IS USED

JPEG 2000 is becoming the reference in image 
compression for 
professional applications, where precision and 
flexibility is really 
necessary.

The most know field using JPEG 2000 is Digital Cinema, 
where 
JPEG 2000 
has been favored against MPEG2 and H.264. Linked to 
that field, High 
Quality Broadcast applications are also turning to JPEG 
2000 
because of 
its quality and scalability (low resolution versions 
can be extracted 
directly from a high resolution sequence without any 
re-encoding, and 
JPEG 2000 sequences are encoded in intra which eases 
video editing).

More close to your field is Archiving, where we are 
feeling a 
trend to 
select JPEG 2000 as compression algorithm

http://www.egov.vic.gov.au/index.php?env=-inlink/detail:m1780-


1-1-8-s-0:l-9669-1-1--
  

Medical imaging applications, where lossless 
compression is a 
important 
requirement, are also taking full advantage of JPEG 
2000 
remote browsing 
possibilities (with the JPIP protocol)

http://www.earthtimes.org/articles/show/aware-inc-to-demonstra


te-groundbreaking-medical-imaging-streaming-solution-at- 
himss08,290686.shtml
  

-
JPEG 2000 FEATURES

The JPEG 2000 features that are interesting for 
GeoSpatial 
Imagery is of 
course the ability to achieve lossless compression, the 
scalability 
(lower quality and resolutions as well as spatial areas 
can 
be extracted 
from a compressed file, without 

Re: [OSGeo-Discuss] Google Summer of Code 2008

2008-02-27 Thread Erik Uzureau
For the record, Chris Schmidt has set up a page on the openlayers wiki
for project Ideas. Can/should we somehow integrate/link this to OSGEO?

http://trac.openlayers.org/wiki/SummerOfCode

e


On 2/27/08, Wolf Bergenheim [EMAIL PROTECTED] wrote:
 Google announced Summer of Code 2008 on Monday, mentor applications can
 be sent in on the 3rd. So we should get to work on creating the ideas
 lists and signing up as volunteer mentors! ;)

 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?
 

 Please start spreading the word. I hope we will have many cool projects
 done this summer!

 --Wolf

 --

 :3 ) Wolf Bergenheim ( 8:

 ___
 Discuss mailing list
 Discuss@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/discuss

___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] Google Summer of Code 2008

2008-02-27 Thread Christopher Schmidt
On Wed, Feb 27, 2008 at 10:55:47AM -0600, Erik Uzureau wrote:
 For the record, Chris Schmidt has set up a page on the openlayers wiki
 for project Ideas. Can/should we somehow integrate/link this to OSGEO?
 
 http://trac.openlayers.org/wiki/SummerOfCode

Now that we've got more than just me offering to mentor, I've gone ahead
and integrated OpenLayers into the list.

Regards,
-- 
Christopher Schmidt
Web Developer
___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] Google Summer of Code 2008

2008-02-27 Thread Wolf Bergenheim

I see you found the wiki page. :D great!

--Wolf

On 27.02.2008 18:55, Erik Uzureau wrote:

For the record, Chris Schmidt has set up a page on the openlayers wiki
for project Ideas. Can/should we somehow integrate/link this to OSGEO?

http://trac.openlayers.org/wiki/SummerOfCode



--

:3 ) Wolf Bergenheim ( 8:

___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] RE: OGC WPS and Amazon SQS

2008-02-27 Thread Raj Singh
I just attended an Open Grid Forum event (http://www.ogf.org/OGF22/)  
where lat-lon and 52north showed off some very nice WPS work. OGC  
plans to work more closely with the Grid community to further improve  
our service offerings for distributed computing, but it won't be a  
quick and easy process. There's a lot of work to be done in this area.


---
Raj


On Feb 27, 2008, at 9:04 PM, Dr. Markus Lupp wrote:


Hi Randy,

deegree has a WPS implementation (although by now it supports only  
WPS v. 0.4.0). We plan to publish an easy-to-install WPS Demo  
Release for deegree 2.2, coming in June (1st Release Candidate in  
April).



Regards,

Markus



Randy George schrieb:


I noticed OGC finalized the WPS spec: 
http://www.opengeospatial.org/pressroom/pressreleases/843

Does anyone know of projects working on WPS implementations?

The goal of WPS is apparently to provide a consistent framework for  
interchangeable service process algorithms that can potentially be  
chained together into answers to higher level questions than the  
typical ‘what’, ‘when’, and ‘where.’ Dealing with ‘why’, ‘how  
much’, and ‘what if’ modeling usually requires a process pipeline  
for convolutions, boolean band operations, and summary pixel  
calculations, all of which are cpu cycle intense, especially for  
large imagery sets. In fact cpu usage issues would make the usual  
service approach prohibitive. Even the little I have worked on JAI  
pipelines shows me the futility of a one cpu to many service  
requests approach for WPS.


However, looking at the AWS Simple Queue Service, SQS http://www.amazon.com/Simple-Queue-Service-home-page/b/ref=sc_fe_l_2?ie=UTF8node=13584001no=3435361me=A36L942TSJ2AJA 
 http://www.amazon.com/Simple-Queue-Service-home-page/b/ref=sc_fe_l_2?ie=UTF8node=13584001no=3435361me=A36L942TSJ2AJA 
, some interesting possibilities come to mind.


Locking message queues with AMI instance pools is essentially a  
poor man’s supercomputer. It would be interesting to look at  
harnessing the utility computing concept with instance pools  
available for each stage in a process pipeline connected using the  
asynchronous SQS service. This is a more or less controlled  
‘distributed computing model’ applied to WPS.


Ref here for some examples of existing distributed computing  
projects: http://distributedcomputing.info/projects.html


Here are a couple possible approaches to a WPS service model that  
might overcome the cpu bottle neck:


1) Sequential SQS pipeline with dedicated instance for each process  
node - this would work best for operations amenable to a streaming  
pipeline – Boolean band operations or pixel summary operations for  
instance


2) Distributed computing model with a chunk server feeding a  
pipeline and an array pool of instances processing the chunks  
coming down the SQS queue – this would be better suited to tiled  
operations


WPS is great when someone else provides the service. I imagine it  
would be very interesting to the academic scientific world and  
government groups tasked with providing access to all the myriad  
imagery coming off space sensor platforms.


Just thinking out loud. More thoughts here: http://www.cadmaps.com/gisblog/?p=28

randy



___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss




--
Dr. Markus Lupp
l a t / l o n  GmbH
Kupang-NTT
Indonesia
phone +62 (0)81 339 431666
http://www.lat-lon.de
http://www.deegree.org
--


___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] RE: OGC WPS and Amazon SQS

2008-02-27 Thread Luca Casagrande
Hello,

On Wed, Feb 27, 2008 at 5:11 PM, Randy George [EMAIL PROTECTED] wrote:

  I noticed OGC finalized the WPS spec:
 http://www.opengeospatial.org/pressroom/pressreleases/843



 Does anyone know of projects working on WPS implementations?




PyWPS: http://pywps.wald.intevation.org/

Bye
Luca
___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss