Hi again, see update below.
2011/4/13 Kenneth Gulbrandsoy <[email protected]>
> 2011/4/13 Jody Garnett <[email protected]>
>
>> That looks like good fun Kenneth - +1 from me.
>>
>> The next step is for me to make sure you have read the developers guide
>> (you have read the developers guide right?); and then ask you to send in a
>> code contribution agreement (the mailing address is included with the form).
>>
>
> I have read the developer guide yes, well most of it... Still a work in
> progress I guess :-)
>
>
>> When you tell me that is on the way we can go through getting you svn
>> access.
>>
>
> OK.
>
>
>>
>> You PDF is much more then we require in order to start an unsupported
>> module; hopefully you will keep some of that as documentation.
>>
>
> Yes. I'm going to document it further (part of my "materials and methods"
> section of my PhD :-)
>
>
>> Aside: I had actually though of doing a straight wrapper on to the EMF
>> model (ie rather than recreating feature and featuretype in EMF as you have
>> done); make a wrapper that translates feature.getAttribite( name ) into a
>> call for eobject.get( name ) etc...
>>
>
> That's an interesting approach. It would probably save memory for sure,
> which is critical in GIS. The actual mapping of EObjects to Features are not
> implented yet. My main concern have been the model structure mapping (EClass
> to SimpleFeatureType). I serialize each EFeatureInfo ("filtered EClass")
> into a feature specification string which DataUtilities use to create
> SimpleFeatureType instances from. Your suggestion does not conflict with
> this approach i think. I'll look into it. Thanks.
>
>
>>
>>
> Your approach looks good; and powerful. I would like to confirm (please)
>> that when you say your data structure is defined "same manner as in the
>> postgis module", can I check that you mean you are extending
>> ContentDataStore?
>>
>
> What I mean is that the EFeature Model structure is organized in the same
> manner as PostGIS: Database (EFeatureDataStore) -> Folders (EFeatureFolder)
> -> Tables (EFeature).
>
>
>> I just want to make sure another project does not start off using
>> AbstractDataStore....
>>
>>
> GeoTools is very feature rich, I was not aware of the ContentDataStore. The
> EFeatureDataStore is based on AbstractDataStore... I'll look into
> ContentDataStore.
>
Can't see any reason not to switch to ContentDataStore, Seems like
EFeatureDataStore == ContentDataStore and EFeatureFolder = ContentEntry.
> Jody Garnett
>>
>> On Wednesday, 13 April 2011 at 8:40 PM, Kenneth Gulbrandsoy wrote:
>>
>> *
>> Hi geotools-devel list!
>>
>> Model-driven engineering (MDE) requires flexible tools for design and
>> model instance generation.
>> *
>>
>> In the Eclipse world, EMF is one obvious choice, because of low
>> probability of being discontinued anytime soon, and the many tools and
>> extension like query, model validation, and persistence through CDO.However,
>> when the modeling involves both dynamic and ad-hoc temporal and spatial
>> data, EMF do not have any built-in support for geodata.
>>
>> My proposal is to add spatial support to EMF models using Geotools
>> DataStore capabilities.
>>
>> A "short" argumentation and description of the module is attached. I'm
>> adding this proposal to the RnD
>> page<http://docs.codehaus.org/display/GEOTOOLS/RnD>
>> shortly.
>>
>> Sincerely,
>>
>> Kenneth Gulbrandsøy
>> - PhD student
>> ----------------------------------------------------------------------
>> Department of Engineering Cybernetics
>> Norwegian University of Science and Technology
>> + mob: +47 932 58 930
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Forrester Wave Report - Recovery time is now measured in hours and minutes
>> not days. Key insights are discussed in the 2010 Forrester Wave Report as
>> part of an in-depth evaluation of disaster recovery service providers.
>> Forrester found the best-in-class provider in terms of services and
>> vision.
>> Read this report now! http://p.sf.net/sfu/ibm-webcastpromo
>> _______________________________________________
>> Geotools-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>
>> Attachments:
>> - geotools-module-proposal.pdf
>>
>> Kenneth
>>
>
Kenneth
------------------------------------------------------------------------------
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now! http://p.sf.net/sfu/ibm-webcastpromo
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
