Jody wrote: "let us know when you get the data parsed and then tag
team someone in for a code review."
I should be getting close to this. I'll start unit testing soon.
You make a good point about getting help, I just don't want to too
severe a pain in the rear end.
Thanks for your patient guidan
Sunburned Surveyor wrote:
> Jody wrote: "So my question is - are you working too hard?"
>
> Yup. But I've learned a lot!
>
Good good; as long as you are having fun.
> I think I'll fall back to my original plan of just providing
> DataObjects for now. When I get this unit tested and working I can
Jody wrote: "So my question is - are you working too hard?"
Yup. But I've learned a lot!
I think I'll fall back to my original plan of just providing
DataObjects for now. When I get this unit tested and working I can
decide if I have the energy to pursue providing SimpleFeatures.
Thanks for all
How is it going? I am a bit worried that you are taking the wrong
approach here... implementing Attribute, Feature, SimpleFeature etc...
is not something any other DataStore writer has had to do? It is not
expected of you; it is not fun; etc...
- SimpleFeature is intended to be simple to use; n
Hey Saul,
As you know the command queue approach in trunk is being a success for the
DataStore implementation. Yet, I wonder if you'll have the time to make the
switch for the gce side of the fence.
And sorry I know it may be something that just wasn't on your schedule, and I
could help you as
My turn for a rant (see Saul I learn from the best).
For modules/unsupported/pom.xml:
Can I that we move modules into:
- pending profile - rather than just comment it out
- archive profile - for things that so broken they do not build
Thanks muchly,
Jody
Hello Daniele
Daniele Romagnoli a écrit :
> as a side note, can you provide me some info on the status/working of
> the Referencing3D module? (I have already downloaded the code but I'm
> not too familiar with it). Which types of transformations are actually
> supported? There is some documenta
Hi Martin,
as a side note, can you provide me some info on the status/working of the
Referencing3D module? (I have already downloaded the code but I'm not too
familiar with it). Which types of transformations are actually supported?
There is some documentation/links on that topic?
I'm investigatin
See http://gridlock.openplans.org:8080/hudson/job/geotools-trunk/668/changes
--
started
Updating http://svn.geotools.org/trunk
U demo/example/pom.xml
U modules/unsupported/gml3/pom.xml
U modules/unsupported/ogc/net.opengis.wps/wps.gen
See http://gridlock.openplans.org:8080/hudson/job/geotools-trunk/667/changes
Changes:
[desruisseaux] Added an org.geotools.console package as a home for utilities to
be launch from the command-line. Those utilities will migrate progressively.
This package will probably move to a "gt-util" modul
Hi lists,
we have slightly simplified the procedure for testing the unofficial
GeoServer release supporting GDAL through ImageIO-Ext. (A GeoServer version
supporting MrSID, JP2K (MrSID), JP2K (Kakadu), DTED, Erdas Imagine, NITF
Format).
The new release is available at
http://www.geo-solutions.it/li
Daniele Romagnoli a écrit :
> In this case (ellipsoidal height in vertical extent), since ISO 19111
> states "ellipsoidal heights (h) cannot be captured in a verticalCRS",
> what should VerticalExtent.getVerticalCRS() method return?
This is an area where ISO and OGC had different views. OGC 01-0
Hi Martin,
sorry for the late reply. Please, read below...
On Fri, May 30, 2008 at 5:55 PM, Martin Desruisseaux <
[EMAIL PROTECTED]> wrote:
> So I would suggest to store the 3rd component as a VerticalExtent like any
> kind
> of height (no special case for ellipsoidal height), create a Extent
> c
13 matches
Mail list logo
