One thing I have been mulling over lately is if we might be able to make it
easier to go from a single image to an image mosiac / image pyramid.
Like from a user's perspective they don't really feel like distinct
'stores', they feel more like advanced configuration options for an image.
Like ideally I'd like to be able to upload an big image, and then maybe
have it pyramided in GeoServer for me, instead of creating it and
uploading. I guess you guys have built some stuff to do that with the
importer. And maybe that's just the way we present it.
The use case I've been thinking about a decent bit is MapStory. Most
everything is time based, so we need image mosiacs to handle them - we want
one layer with different time slices. It's all crowd sourced / user
contributed. And one of our big use cases is taking scanned maps and
rectifying them, using the warper built for nypl (see
http://warper.mapstory.org). What we'd ideally like to do is have people be
able to upload more scanned maps to an existing layer.
Now I think we'll be fine - we'll just create everything as an image mosiac
to start, even if it's just one layer, so we can add more in the future.
But from a user or even programmatic client perspective it'd be nice if
GeoServer handled that abstraction. You just have an image layer, and you
could choose to add mosiacs to it, or add pyramids to it. Or have it
generate pyramids, etc.
I realize this is a big topic, just curious on current thinking, if it's a
goal to unite image stuff in some way. Or if that's just unrealistic. Or if
there's better routes to achieve it.
C
On Mon, Jun 17, 2013 at 1:31 PM, Chris Holmes <[email protected]> wrote:
> +1, makes good sense to me.
>
>
> On Mon, Jun 17, 2013 at 1:29 PM, Andrea Aime <[email protected]
> > wrote:
>
>> Hi,
>> the image pyramid extension is a bit of a oddball: it has an extension
>> release package but does not have an extension module.
>>
>> I wanted to add a file browser for its GUI, so I guess I can roll an
>> extension module to contain it.
>>
>> However I'm wondering... the pyramid module has been around for a long
>> while and does not add much to the download and nothing to the dependencies
>> (it's just a thin wrapper around image mosaic): how do people feel about
>> adding it as a standard store in GeoServer?
>>
>> Cheers
>> Andrea
>>
>> --
>> ==
>> Our support, Your Success! Visit http://opensdi.geo-solutions.it for
>> more information.
>> ==
>>
>> Ing. Andrea Aime
>> @geowolf
>> Technical Lead
>>
>> GeoSolutions S.A.S.
>> Via Poggio alle Viti 1187
>> 55054 Massarosa (LU)
>> Italy
>> phone: +39 0584 962313
>> fax: +39 0584 1660272
>> mob: +39 339 8844549
>>
>> http://www.geo-solutions.it
>> http://twitter.com/geosolutions_it
>>
>> -------------------------------------------------------
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> Geoserver-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>>
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
