Matthias Basler wrote:
> I was just very pleased to find that the user guide's page on shapefile 
> loading has been updated to reflect the new GT2.5 specific features. I find 
> this page 
> (http://docs.codehaus.org/display/GEOTDOC/04+How+to+Read+a+Shapefile) is 
> really useful for beginners to see that GeoTools is easy to use for easy 
> things.
>   
Thanks for the encouragement - the user list has been very good at 
providing feedback.
> What I would add to the explainations is the different levels of data 
> retrievel/processing. I can imagine a new user would question: What is the 
> difference between
> - DataStore,
> - FeatureSource/FeatureStore/FeatureLocking and
> - FeatureCollection?
>
> My understanding (from the JavaDoc and the proposal page) is that DataStore 
> is the old and FeatureSouce (and friends) the new interface for data 
> discovery while FeatureCollection is used within the application to work with 
> the data, f.e. it serves as a data model for one map layer.
>
> I just think this is worth a note on this page.
>   
I think there is a section at the end of the page that talks over these 
different topics ... "What Does ShapefileDataStore do" ...I have updated 
the section to cover FeatureSource and FeatureStore and link to a few 
pages where more information can be had.
> My second question on this topic is: The gt-shapefile module declares 
> velocity-1.4.jar and velocity-dep-1.4.jar as dependencies. This is reflected 
> by the image on the user guide page.
>
> However I seem unable to find where this dependency is actually used (I 
> searched the source files for "velocity" both in Explorer and in Eclipse) and 
> didn't find a single match.) Also the code example given runs smoothly 
> without this dependency.
>   
Interesting; we should be able to drop it then. I am not sure where/why 
velocity was used (perhaps it is left over from when velocity was needed 
in order to run maven?).
> So: Is velocity actually required to read and/or write shapefiles? If not, 
> can the dependency be removed or is there another specific reason it is 
> declared?
>   
For a while jdom was used to parse shape metdata (ie shape.shp.xml) 
files; that is my only guess ... but jdom is low level enough that it 
would not use velocity.

I am betting this is just a case of neglect from the maven 1.0 transition.
Jody


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to