Hello,
Don't worry, I'm not offended that easily :)
The modules I'm talking about are the GeoTools module structure modules:
gt-xml-gpx under modules/unsupported/xml-gpx, providing packages:
org.geotools.gpx
org.geotools.gpx.bean
org.geotools.gpx.binding
and
gt-gpx under modules/unsupported/gpx
Sunburned Surveyor wrote:
> I was definitely interested in providing programmer friendly access at
> a lower level. This allows different FOSS programs to do with the GPX
> entities what they desire. I couldn't do this if I only provided a
> GeoTools SimpleFeature implementation from GPX files.
>
>
Jody wrote: "Landon did I understand your aims correctly?"
Yes.
I did'nt realize that a gt-xml-gpx package existed, or I would have
taken a closer look at it. I thought there was only the following
three (3) packages:
org.geotools.gpx
org.geotools.gpx.bean
org.geotools.gpx.binding
I was looking
That is an approach we take often Peter; for example the gt-wps module
is going to offer a "no abstraction" access to a web processing service.
Then a high level gt-process module can offer the easier api for Java
programmers.
Landon is trying to do something slightly different (ie he has diffe
Hello,
I think that you give a much greater importance to the low level access
of the file, than you should. I'm not a GeoTools expert, but my
understanding is that the point in the whole thing is to generalize the
way the data could be accessed. This is why I didn't care about names of
proper
You can find my experimental GPX code here:
http://surveyos.svn.sourceforge.net/viewvc/surveyos/java/gpx/src/
The code is documented or unit tested yet, and some of the methods are
stubs. I'm fooling around with some techniques for accessing and
managing GPX that are a little different from the o
