Reponse in-line.
2011/4/19 Jody Garnett <[email protected]>
> Comments in line
>
> On Tue, Apr 19, 2011 at 2:41 AM, Kenneth Gulbrandsoy <
> [email protected]> wrote:
>
>> Status Priority Task Comments
>> Impl.
>> High Static definition of EFeatureDataStore structure. Eclipse plug-in
>> extension point.
>> Experimental.
>> Impl.
>> High EFeature EMF meta-model EFeature API. Enables easier infer
>> definition structure from EPackage.
>> Impl.
>> High EFeature as Eclipse plug-in. Experimental. Makes it easier to make
>> a uDig catalog plug-in (started).
>> Impl.
>> High EFeature data store factory (SPI).
>> Impl.
>> High EFeature data store. Based on AbstractDataStore for now.
>> Is changeing to ContentDataStore.
>>
> That is great; hopefully you find ContentDataStore easier? Please email
> questions as I would like to See ContentDataStore improved.
>
>
>> Impl.
>> High EFeature reader.
>> Impl.
>> High OpenGIS filter to EMF Query encoder.
>> Impl.
>> High EClass to SimpleFeatureType encoder.
>> High Feature writer.
>> High EObject to SimpleFeature mapper (read). Implement as encoder or as a
>>
>> wrapper around EObjects?
>>
>
> Go for a wrapper; why waste memory with a copy?
>
>
>> High SimpleFeature to EObject encoders (write).
>>
> Can your wrapper handle this one?
>
>> High Serialize geometries to XMI. Encoder implements WKT, but WKB
>> is more efficient with respect to EMF
>> resource r/w?
>>
> Sure whatever floats your boat. I tend to use WKT for ease in debugging;
> and then switch once I know it works.
>
>> High Test suite for most important classes. Default test battery for
>> DataStore,
>> DataSource, Queries and Filters would nice...
>>
> Copy MemoryDataStore Test; also you can review the test suite from the
> gt-jdbc module; indeed you may be able to pull up an abstract set of tests
> that you can contribute to the gt-data module?
>
>
>> -
>> Normal Coded definition of EFeatureDataStore structure. Add constructor
>> and "open" method
>> (~30 min job).
>> -
>> ? EFeature collection. Do I need it?
>>
> No; if you can make a FeatureReader then the result will be made available
> as a ContentFeatureCollection (ie it completely delegates to your feature
> reader).
>
>> -
>> Low Infer definition of EFeatureDataStore
>> structure from EMF Model EPackage.
>>
>> Next up is:
>>
>> - EFeature-SimpleFeature mappings
>> - Serialize geometries to XMI. As WKT or WKB, Which is most efficient?
>> - Test battery. A "standard-test" module would be nice, where the the
>> module capabilities determines which tests to run.
>>
>> So far, only Jody from PMC has given me a +1 on this module. But since I
>> need to complete this module now, I opted to continue working on it anyway
>> :-)
>>
>
> A +1 from a PMC was all you needed to start an unsupported module; other
> that we need need an email from you saying you mailed in your code
> contribution agreement - and then a PMC member (or indeed any committer) can
> set you up.
>
> As long as the module is not in a running state (only snippets are tested),
>> the svn access can wait. I believe that the module is ready for review a
>> little earlier than expected though. According to the procedure described in
>> the development guide, svn is now the next step.
>>
>
> Yep; see above. Often people can work in svn; and just hook the result up
> to unsupported/pom.xml when it actually compiles.
>
>
Thanks Jody, I'll do that. The development guide describes a "snail-mail"
approach for handing in a signed contribution agreement. Is it enough with a
scanned PDF of a signed agreement? My location in Norway, so it will take
some time before a hard copy arrives at OsGeo (maybe as much as a 7-10
days). Alternatively, scanned PDF for access to svn + hard copy as
confirmation?
> As always, feedback is much appreciated.
>>
>
> Cheers,
> Jody
>
>
Kenneth
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
