Hmm. Hints.FEATURE_2D exists on trunk, with "@since 2.4.1", but it is
not referenced from anywhere in the code. Could it be, that it was
introduced in 2.4.1, but the usages where not "foreward-ported"?
Peter
Bolla, Péter wrote:
> I revoke this question. I overlooked the fact, that there is an
I revoke this question. I overlooked the fact, that there is an
overloaded version of getFeatureReader(...) which takes the Query as
parameter.
Peter
Bolla, Péter wrote:
>
> Jody Garnett wrote:
>> My understanding is:
>> - your DataStore/FeatureSource has a "get supported hints" method; you
Jody Garnett wrote:
>
> My understanding is:
> - your DataStore/FeatureSource has a "get supported hints" method; you
> need to advertise the fact that you understand the FEATURE_2D hint
> - when your FeatureSource is a getFeatures( Query ) call you can check
> the Hints provided by the client
Bolla, Péter wrote:
> I'm getting back to this Hint.
> Jody Garnett wrote:
>> Thus was born the Hints.FORCE_2D - so if your datastore can support
>> this hint (which is used by the renderer) we should be able to cut
>> off the data before the render gets confused.
> Did you mean Hints.FEATURE_2D?
I'm getting back to this Hint.
Jody Garnett wrote:
> Thus was born the Hints.FORCE_2D - so if your datastore can support this
> hint (which is used by the renderer) we should be able to cut off the
> data before the render gets confused.
Did you mean Hints.FEATURE_2D?
And how can I use the hint
Bolla, Péter wrote:
>> The rendering engine would set that Hints.FORCE_2D hint; and thus the
>> DataStore would drop the excess ordinates before returning the data
>> for rendering. The hard part for me is the handling of the
>> CoordinateReferneceSystem ...
>> - we really should have a Coordina
I'm afraid I'm not a regular UDig user. (I don't even know if I still
have it installed on my computer.) So I'm probably not the best person
for this task.
I'm really the most interested in making low-level access available to
GPX files, although I do want to study how you made GPX entities
availa
Jody Garnett wrote:
> The rendering engine would set that Hints.FORCE_2D hint; and thus the
> DataStore would drop the excess ordinates before returning the data for
> rendering. The hard part for me is the handling of the
> CoordinateReferneceSystem ...
> - we really should have a CoordinateR
Bolla, Péter wrote:
> Jody Garnett wrote:
>> Oh! We have actual progress to report on that front; I have been
>> trying to let GeoServer work with 3D data; and one of the
>> optimizations Andrea asked for was the ability to throw away any data
>> beyond X and Y (since it was not going to be used
Jody Garnett wrote:
> Oh! We have actual progress to report on that front; I have been trying
> to let GeoServer work with 3D data; and one of the optimizations Andrea
> asked for was the ability to throw away any data beyond X and Y (since
> it was not going to be used for rendering).
>
> Thu
Bolla, Péter wrote:
>> Here is an alternative; you can ask a JTS CoordinateSequence to hold
>> your own Coordinates that can include x,y,z and a time stamp. While
>> this is easier with ISO Geometry (where your CRS could literally be
>> x,y,time) you can certaintly fake it with JTS right now.
>
Peter,
You wrote: "The problem with the timestamps come up in the case of the
tracks. For waypoints - a point feature - you can store the geographic
coordinates in the geometry, and the timestamp as an attributte. But
with tracks - which intuitively should be a linestring - you can have
timestamps
Oh! We have actual progress to report on that front; I have been trying
to let GeoServer work with 3D data; and one of the optimizations Andrea
asked for was the ability to throw away any data beyond X and Y (since
it was not going to be used for rendering).
Thus was born the Hints.FORCE_2D - s
Jody Garnett wrote:
> Do you have specifics? It sounds fine to me; you may uncover some bugs
> along the way .. but the OracleDataStore does similar tricks when
> working with x,y,z,m data (ie from LRS datasets). I think the other fun
> bit of info would be a new GeoTools Function to "grab" th
Jody Garnett wrote:
> Bolla, Péter wrote:
[...]
>> current implementation of the GPX datastore in the repository extends
>> JTS to use 4 coordinates for every point, so it can store the
>> timestamp along with the geometry, and I could even define a compound
>> CRS with 4 axes (lat, lon, eleva
Bolla, Péter wrote:
> Hi,
>
> The problem with the timestamps come up in the case of the tracks. For
> waypoints - a point feature - you can store the geographic coordinates
> in the geometry, and the timestamp as an attributte. But with tracks -
> which intuitively should be a linestring - you
Hi,
The problem with the timestamps come up in the case of the tracks. For
waypoints - a point feature - you can store the geographic coordinates
in the geometry, and the timestamp as an attributte. But with tracks -
which intuitively should be a linestring - you can have timestamps for
every
Peter,
You wrote: "So if I might suggest a path how to get involved, there is
a much more GIS related problem with the GPX datastore, than the xml
parsing. It is the temporal capabilities, that is only very coarsly
supported by geotools (and I guess by any other GIS toolkit), and
makes it hard to
Hi,
I just read this thread, and as the "owner" of the code I would clarify
some points :)
First, what I meant by "Though Justin said that even he doesn't use
that now, but an other way." in my answer to Landon, is that the method,
how I _generated_ the beans were outdated, but as far as I know
I'm starting to see more of the puzzle now, based on your comments.
I think JAXB might be overkill at this point. I don't really need a
binding framework. I think I might use JDOM initially, although I know
this will impose a RAM limitation on the size of the GPX files that
can be supported. Howev
Sunburned Surveyor wrote:
> Jody wrote: Interesting; do you know what parser Peter was using?
>
> I should have included an excerpt of my conversation with Peter. Here it is...
>
> Landon asked Peter: Thanks so much for taking the time to respond! I
> look forward to working on the GPX module for G
Jody wrote: Interesting; do you know what parser Peter was using?
I should have included an excerpt of my conversation with Peter. Here it is...
Landon asked Peter: Thanks so much for taking the time to respond! I
look forward to
working on the GPX module for GeoTools. I've got a quick question f
Sunburned Surveyor wrote:
> Jody wrote: "Nice work! It is so much easier to proceed when there is
> someone who "owns" the code."
>
> Peter sounds like he'll be able to answer questions, but I don't think
> he currently has the time to actively maintain the module. Maybe that
> is why work on the m
Jody wrote: "Nice work! It is so much easier to proceed when there is
someone who "owns" the code."
Peter sounds like he'll be able to answer questions, but I don't think
he currently has the time to actively maintain the module. Maybe that
is why work on the modile has tappered off.
After lookin
We managed to fall off the list with your last reply ...
Sunburned Surveyor wrote:
> Jody,
>
> Thanks for answering all of my questions. Additional comments can be
> found below:
>
> Jody wrote: "The user guide has instructions for using maven to "ask"
> what the dependencies are for a given plug-
On Wed, 2008-05-14 at 16:20 -0700, Sunburned Surveyor wrote:
> I finally got the export of a PDF version of the GeoTools developer
> guide to work after singing up with Codehaus. Perhaps we should add a
> note indicating that the document conversion will only work for
> registered users of the site
Sunburned Surveyor a écrit :
> [2] Where would I find a list of third party JARS already included as
> a dependency in GeoTools? The Developer's Guide mentioned this site:
> http://mvnrepository.com/. I'm not sure if that is what I am really
> looking for. Isn't that a list of all the Jars in some
Sunburned Surveyor wrote:
> I finally got the export of a PDF version of the GeoTools developer
> guide to work after singing up with Codehaus. Perhaps we should add a
> note indicating that the document conversion will only work for
> registered users of the site?
Or I can just remove the button a
28 matches
Mail list logo
