[OSGeo-Discuss] Open File Formats and Proprietary Algorithms

Michael P. Gerlek mpg at lizardtech.com
Tue Aug 25 17:34:01 EDT 2009


To be clear, it's not an effort I have the bandwidth for personally.  But if there were qualified developers interested in taking it on, I might be in a position to offer project guidance and a small amount of funding.

-mpg


-----Original Message-----
From: discuss-bounces at lists.osgeo.org [mailto:discuss-bounces at lists.osgeo.org] On Behalf Of Landon Blake
Sent: Tuesday, August 25, 2009 11:12 AM
To: OSGeo Discussions
Subject: RE: [OSGeo-Discuss] Open File Formats and Proprietary Algorithms

OK. I'm not an expert on images, but I'd be interested in working with
you. However, I avoid C++ like a lethal strain of the Swine Flu. :]

I may give some more thought to some of Bob's ideas about making it
easier to work with image tiles.

Thanks.

Landon
Office Phone Number: (209) 946-0268
Cell Phone Number: (209) 992-0658
 
 

-----Original Message-----
From: discuss-bounces at lists.osgeo.org
[mailto:discuss-bounces at lists.osgeo.org] On Behalf Of Michael P. Gerlek
Sent: Monday, August 24, 2009 3:19 PM
To: OSGeo Discussions
Subject: RE: [OSGeo-Discuss] Open File Formats and Proprietary
Algorithms

I've not given it much thought recently, to be honest.  I'd need to
review the current state of things in OpenJp2 (or whatever it's called)
to see where they are at, what changes would be realistic and viable,
how amenable they'd be to taking patches versus a fork, etc.  Done
properly, the work would have no "geo" specific component at all -- it
would just be a new version of some of the internal algorithms.  The
test case would simply be to encode and decode an 500 GB(?) raw file on
a box with 2 GB (?) of RAM.

I would certainly not want anyone to have to build a whole new jp2
library from scratch, if that's what you meant.  I'd really only be
interested in C++ (or possibly mono-safe C#).

-mpg


-----Original Message-----
From: discuss-bounces at lists.osgeo.org
[mailto:discuss-bounces at lists.osgeo.org] On Behalf Of Landon Blake
Sent: Monday, August 24, 2009 4:11 PM
To: OSGeo Discussions
Subject: RE: [OSGeo-Discuss] Open File Formats and Proprietary
Algorithms

MPG:

When you say "effort" do you mean some sort of library to support JP2
geo side of things?

What programming language would you be most interested in? C++?

Landon
Office Phone Number: (209) 946-0268
Cell Phone Number: (209) 992-0658
 
 

-----Original Message-----
From: discuss-bounces at lists.osgeo.org
[mailto:discuss-bounces at lists.osgeo.org] On Behalf Of Michael P. Gerlek
Sent: Monday, August 24, 2009 1:59 PM
To: OSGeo Discussions
Subject: RE: [OSGeo-Discuss] Open File Formats and Proprietary
Algorithms

It would not be a good SoC thing, due to the level of expertise and time
required.

I (LizardTech) would likely be willing to contribute to such an effort.

-mpg


-----Original Message-----
From: discuss-bounces at lists.osgeo.org
[mailto:discuss-bounces at lists.osgeo.org] On Behalf Of Fawcett, David
Sent: Monday, August 24, 2009 8:11 AM
To: OSGeo Discussions
Subject: RE: [OSGeo-Discuss] Open File Formats and Proprietary
Algorithms


I realize that there are likely not a large number of people who have
the expertise and experience to write this kind of code.  

Is this a project that should be shopped around for funding?  Google
Summer of Code?  A grant from our ~benevolent overlord Google?  Some
other foundation or org interested in open data formats?  

David.
-----Original Message-----
From: discuss-bounces at lists.osgeo.org
[mailto:discuss-bounces at lists.osgeo.org] On Behalf Of Michael P. Gerlek
Sent: Thursday, August 20, 2009 4:36 PM
To: OSGeo Discussions
Subject: RE: [OSGeo-Discuss] Open File Formats and Proprietary
Algorithms
<snip>


> Do you know why there hasn't been a broader adoption of JP2?

Not through lack of trying on my part :-)

I think the two biggest reasons are:

(1) The algorithms for handling large images in memory really are rocket
science, and no one in the FOSS community has gotten the "itch"
sufficiently bad enough to go and do the work needed inside the existing
open source packages.  Hopefully someday someone will.


_______________________________________________
Discuss mailing list
Discuss at lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/discuss
_______________________________________________
Discuss mailing list
Discuss at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss
_______________________________________________
Discuss mailing list
Discuss at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Warning:
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.
_______________________________________________
Discuss mailing list
Discuss at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss
_______________________________________________
Discuss mailing list
Discuss at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss
_______________________________________________
Discuss mailing list
Discuss at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


More information about the Discuss mailing list