This is a great project, definitely what is needed to get the
'geospatial web' to take off. Some of our GeoServer users have had
success just sticking GeoServer's WMS behind squid and making standard
requests with ka-map.
What's really needed next are projects just like this, and then a firm
specification on how clients should divide up tiles. Definitely make
sure that part of the program is flexible, so that when we do get around
to codifying how to do it uDig can place nice from the start.
I'd be interested in your WFS caching system. My thoughts have been
that for something like uDig it actually makes more sense to just
download the whole dataset and save it locally. We're working on
something like a 'versioning table' in geoserver, that would
automatically be updated when a new insert comes in. This could be
perfectly complemented by a caching system, like in uDig, where it would
just check the version table whenever it fires up, and continue to use
its locally cached copy until there is a feature to be updated.
Anyways, I ramble on, but be sure to share the results of this project,
this is exciting stuff. And apologies, I'm not a udig developer, so I
can't help you with anything more than encouragement...
best regards,
Chris
On 3/28/06, Jeffrey Bergamini <[EMAIL PROTECTED]> wrote:
> Hi everybody,
>
> First, congratulations on all that uDig has become! It's a great tool.
>
> I'm working on an academic project that involves a WMS/WFS proxy/cache
> system that imposes some regulation on the bounding boxes of
requests, i.e.
> they must be along certain grid lines (defined in WGS 84). I'd like
to use
> uDig as a demonstration client, so that means I need to hook into the
> zooming/selection mechanisms and make sure uDig is making requests along
> those boundaries.
>
> What I have in mind (for an initial, simple, just-works demonstration) is
> that a user should be able to either:
>
>
> Press the Zoom button, and uDig will zoom to the most appropriate
next tile;
> or
> Use the Adjust Current Zoom tool to select a new area, and uDig will make
> minor adjustments so that the area's boundaries lie along the grid lines.
> I'm using standard WMS/WFS with a simple extended Capabilities doc
element
> that notifies a client that this tiling scheme is available.
>
> I've begun looking the at the plugin development tutorials and
skimming some
> of the uDig source, but I think asking this list would be a more
efficient
> way of getting started. Can anyone point me in the right direction as
far as
> where this can and should be accomplished in code? Can it be
developed as a
> plugin, or should I make a custom version of uDig for myself?
>
> Any help is greatly appreciated, and I figure that a couple minutes of
> typing time from those of you who are pretty familiar with uDig will
save me
> many hours of wading through docs and code.
>
> Thanks a lot, and again, keep up the good work.
>
> Jeff Bergamini
> _______________________________________________
> User-friendly Desktop Internet GIS (uDig)
> http://udig.refractions.net
> http://lists.refractions.net/mailman/listinfo/udig-devel
>
>
>
--
Chris Holmes
The Open Planning Project
thoughts at: http://cholmes.wordpress.com
begin:vcard
fn:Chris Holmes
n:Holmes;Chris
org:The Open Planning Project
adr:;;377 Broadway, 11th Floor;New York;NY;10013;USA
email;internet:[EMAIL PROTECTED]
title:VP, Strategic Development
x-mozilla-html:FALSE
url:http://topp.openplans.org
version:2.1
end:vcard
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
