Hello everyone ... I am finally getting around to doing some planning.
These pictures show the current state of play - these pictures have been
past the uDig and GeoServer developer lists (so this picture should
be pretty good). And more importantly present a picture of what changes
are expected to GeoAPI before we present to the working group.
So far I have the following blanks:
- Summer: GeoAPI 2.1.RC0 and report to working group (Martin do you have a exact day/time?)
- An ISO Geometry reference implementation has been constructed as part of GeoTools (so now there are two public implementations - perfect!) There are some performance concerns with the GeometryFactory interface so expect some review & discussion.
- An ISO Feature reference implementation is being made available this quarter; the javadocs and change report need to be made ready. There is also a knock-down-beat-em up discussion of TypeName to look forward to.
- OpenLS GeoReferencing / Reverse GeoReferencing and associated ISO Address models are on the schedule. I am not sure if they are going to make the Summer deadline, but I thought you should know.
If there is any other work going on (especially with deadlines) please
reply to this email and I will try to fold it in.
We have the following backlog items for GeoAPI (things we know need to happen but right now nobody is paid to fix):
- Style interfaces (need to collapse to just one and bring interfaces in line with SLD specification again)
- "Naming" design conflict between TypeName and GenericName
Ignore me - accidentally did an Andrea (ie sent email to the wrong list).
Cheers,
Jody
Jody Garnett wrote:
Hello everyone ... I am finally getting around to doing some planning.
These pictures show the current state of play - these pictures have been
past the uDig and GeoServer developer lists (so this picture should
be pretty good). And more importantly present a picture of what changes
are expected to GeoAPI before we present to the working group.
Question with regards to the pictures (very clear by the way), the items in italics in each box, are those all separate items that do not have a dependency on the underlying framework? ie. Geoserver UI doesn't depend on Geotools geocoder.
Hello everyone ... I am finally getting around to doing some planning.
These pictures show the current state of play - these pictures have been
past the uDig and GeoServer developer lists (so this picture should
be pretty good). And more importantly present a picture of what changes
are expected to GeoAPI before we present to the working group.
So far I have the following blanks:
- Summer: GeoAPI 2.1.RC0 and report to working group (Martin do you have a exact day/time?)
- An ISO Geometry reference implementation has been constructed as part of GeoTools (so now there are two public implementations - perfect!) There are some performance concerns with the GeometryFactory interface so expect some review & discussion.
- An ISO Feature reference implementation is being made available this quarter; the javadocs and change report need to be made ready. There is also a knock-down-beat-em up discussion of TypeName to look forward to.
- OpenLS GeoReferencing / Reverse GeoReferencing and associated ISO Address models are on the schedule. I am not sure if they are going to make the Summer deadline, but I thought you should know.
If there is any other work going on (especially with deadlines) please
reply to this email and I will try to fold it in.
We have the following backlog items for GeoAPI (things we know need to happen but right now nobody is paid to fix):
- Style interfaces (need to collapse to just one and bring interfaces in line with SLD specification again)
- "Naming" design conflict between TypeName and GenericName
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
------------------------------------------------------------------------
Question with regards to the pictures (very clear by the way), the items in italics in each box, are those all separate items that do not have a dependency on the underlying framework? ie. Geoserver UI doesn't depend on Geotools geocoder.
Correct .. .the items in italics are "scheduled" but I am not sure if I believe it yet. As far as I know GeoServer is still trying to sort out
in what order persistence, catalog and web ui should (or even can?) occur in.
I am glad you find the pictures clear. I am tempted to do another diagram that shows the Supported / Unsupported split. So can
look at how some of the unsupported plans to migrate into an actual release. Would there be interest in this? Bah I would need to throw
in GeoAPI and possible documentation into the mix to illustrate a useful plan.
The "road blocks" with nobody working on them are the ones that concern me...
Jody
