simone giannecchini wrote:
as well, but I think in our context is more correct say that feature
are both that same level as well as above coverages. As an instance,
in the Geoserver we develop we render coverages wrapping them inside a
feature, in order to follow strictly the specification.
Understood.
3. Geometry & JTS are kind of at the same level/or the same thing,
unless you are talking about the lite Java
Shape classes Martin uses in J2D Renderer (in which case they are
part of rendering)
I agree, but I wanted to keep third party libraries separated from the
rest f the stack. Do you think that keeping things this way is
misleading?
For right now - yes. If you want to be "pure" just say geometry, and the
fact that we are using JTS Geometry can be an accident of implementation
right now.
4. GML is built ontop of Features and XML
Mmmmhhh, I have a small experience with GML plugin, but shouldn't GML
be seen at least as a way to represent feature (we extract feature
from GML and we write features in GML)?
I am thinking in terms of layers right now. What are
you drawing a diagram of?
Besides this I am trying also to point out possible extension points
therefore, in case we implemented more of the GML spec GML modules
would be almost everywhere, am I right?
You should check out this:
http://udig.refractions.net/confluence/display/OWS3/GTXML+Article
5. Metadata is at the same level as CRS and Units.
I agree, but again I designed it this way because I was thinking about
a possible implementation of a catalog, therefore I thought it would
Now I am Jealous, I have been wanting to work on a Catalog for ages ;-)
Have fun!
But the only one that is really interesting is this - the Plugins happen
at each and everyone of those layers.
What do you mean exactly? I wanted here to remark the separation
between the plugins for the I/O for features and coverages and the
various other abstractions levels. Can you tell me a bit more about
your thoughts on this?
Well you can plugin new implementations behind anyone of these "layers",
alternate CRS implementations and factories, alternate Feature
implementations, alternate data sources, alteranate rendering systems
(not quite yet), etc...
That is kind of the point of this design, new data sources are added in
exactly the same way as new CRS Authorities are added or new Styling
implementations.
I will make some corrections but I will wait a bit before resending
it, your opinions as well as the opinions of anyone else are well
accepted.
Sweet, can you added it into the Architecture articles section, I love
having more pictures for users (chances are at least one will work)..
Jody
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
