My rough idea of a project plan for the FM branch would be:
- write test cases for everything up to "SimpleFeature"
- port shapefile and postgis over to use SimpleFeature
- slam the change onto trunk, and explore the rest of the API as
aspects of the orphaned complex-feature branch trickle in o
It would be great if they could reply and say what there interest is in
FM (even if just "I think it will be good in the future"), what type of
timeline constraints they have (if any), and what kind of resources they
have that they could throw at it (if any).
Complex-features is 90% of what i
David Blasby wrote:
(resending because my email was having problems)
My rough idea of a project plan for the FM branch would be:
- write test cases for everything up to "SimpleFeature"
- port shapefile and postgis over to use SimpleFeature
- slam the change onto trunk, and explore the rest of t
David Blasby wrote:
Here's a quick question for you, jody. When is udig planning on
transitioning to the FM? I'm not sure if you have a enough info to
answer that, but what does your gut say?
I have been waiting for a clear progress on FM, much like you.
Stated back in November that we would
Here's a quick question for you, jody. When is udig planning on
transitioning to the FM? I'm not sure if you have a enough info to
answer that, but what does your gut say?
dave
---
Using Tomcat but need to do more? Need to support web serv
Bryce L Nordgren wrote:
The main thing I lack, due largely to my own failure to keep close track of
the FM effort, is a warm fuzzy that I understand the relationship between
Features and Coverages in GT. I think I have a pretty good handle on how
the ISO 19100 / OGC standards view the issue. I
[EMAIL PROTECTED] wrote on 05/02/2006 03:06:24 PM:
> > ps. At least two people mentioned that GC 'requires' or affects FM,
> > which (if true) would mean that there needs to be some planning
> > between FM and GC. This could really throw a "wrench in the works" if
> > FM need modification to pr
David Blasby wrote:
My rough idea of a project plan for the FM branch would be:
- write test cases for everything up to "SimpleFeature"
- port shapefile and postgis over to use SimpleFeature
- slam the change onto trunk, and explore the rest of the API as
aspects of the orphaned complex-featur
(resending because my email was having problems)
My rough idea of a project plan for the FM branch would be:
- write test cases for everything up to "SimpleFeature"
- port shapefile and postgis over to use SimpleFeature
- slam the change onto trunk, and explore the rest of the API as
aspects of
