Re: [Openev-discuss] OpenEV2 plans (revised)

[Chris N. <cgn...@al...>]

>
>
>I would note that there are other applications, such as uDig that are already
>good WFS-T clients.  It might be more practical to use them for such
>applications.
>  
>
But it sucks for handling huge rasters, or better yet,  seamlessly 
browsing a project area of high-res j2k orthos on a shared drive, like 
one can do with 'tindex''d layers in Mapserver.  For this particular 
client,  really basic overlay editing would be just fine; they just need 
to digitize, annotate,  and share things.  The basic ogr2ogr capabiity 
to get/put things into a single PostGIS table, or import/export to/from  
shapefile and CSV's.

As for authentication, simple/straightforward libcurl http rfc2617 for 
WMS/WFS would be fine too...

Now, as far as imagery encryption, that's a whole wunderworld unto 
itself...and more properly discussed on the gdal list or OGC DRM forum, 
but photomapper does indeed have some simple/stupid shared key mechanism 
to "unlock" imagery; they probably just tweeked the Kakadu i/o routine 
to do some sneaky rotor stuff; not sure, and not sure how important this 
is to this customer...but I'm sure its secondary to just 
panning/zooming/annotating collections of big j2k  imagery files.

Other question while I'm at it; what the state of 12-bit channel 
support? ...for Vexcel ...I mean Microsoft aerial sensors (why does that 
sound wierd?)

Chris

>Best regards,
>  
>