Hello all,
as warned on the users' list, I'm working on a(n unsupported) "Tile Client"
module for GeoTools.
My plan so far was to grab the tile code written for uDig, prototype a
proof-of-concept and refactor considering the ideas in
http://docs.codehaus.org/display/GEOTOOLS/Tile+Server+Client.
As far as the prototype is concerned, I have the basically tile-picking
mechanism in place. Work needs to be done in cleaning up, refactoring
(using the classes/interfaces from the link above), tile selection (optimal
scale) and caching (for which there's already some work already done).
The plan from now on:
- Formalities: contrib agreement, RnD page
- Technicalities: get going with git (I have forked the project into my
account @github, but ain't no git master myself)
- Code, code, code: for each prototyped class, add copyright notice, write
test, check in
- Wrap it in a coverage class. (We're cutting the tiles into a bbox, and
want to combine that with other data.)
So, this is going to take some time, due to the hobby nature of the
project. Eventually (soon?) we might get paid support and squeeze the
development into a few days.
The targeted package is
org.geotools.tile (from the link above)
The module might be called
gt-tile or gt-tile-client. It's your call. Feel free to comment.
Thanks!
Tupi
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
