[...]
>> Hi Simone; I understand we are all stressed for time. I don't think we mind
>> building for the mac - I simply just have not had a chance to try yet. I
>> understand there are now some build instructions.
>
> Andrea (Antonello) and Daniele should have done some work in this
> direction,
Justin, you are a champ! It looks like your xmlcodegen changes and
instructions are just what we needed.
Generated GMLSchema members are now non-static, which is an API change.
More notes below.
We still have to look at some details (ClientProperty/attribute
handling, fixing app-schema breakag
JMapPane and MapLayerTable problems
---
Key: GEOT-2862
URL: http://jira.codehaus.org/browse/GEOT-2862
Project: GeoTools
Issue Type: Bug
Components: ext mappane
Affects Versions: 2.6.0
Rememeber you are not alone in the paperwork; ask questions early and
often on the devel list here - we are interested in making it as easy
as possible to contribute to geotools.
I am very excited about your contribution it sounds like a nice clean
functionality that will be of value to a lot of or
Since I stopped using Windows at the time where NT 4.0 was the actual
version, I have no Windows license.
Milton Jonathan writes:
> Hey there
>
> First of all, amazing work Justin! Using the SQLServer driver is a big
> possibility for us here, and thus we may soon be included in the "pleas
Densify long straight segments before reprojection
--
Key: GEOT-2861
URL: http://jira.codehaus.org/browse/GEOT-2861
Project: GeoTools
Issue Type: Improvement
Components: core render
Hey there
First of all, amazing work Justin! Using the SQLServer driver is a big
possibility for us here, and thus we may soon be included in the
"pleased sqlserver users" Ben was talking about..
About Christian's e-mail, just wanted to ask: do you lack licenses for
Windows itself or SQLServer
Cache getBounds in MemoryFeatureCollection
--
Key: GEOT-2860
URL: http://jira.codehaus.org/browse/GEOT-2860
Project: GeoTools
Issue Type: Improvement
Components: core feature
Repo
FilterToCQL adds UPPER to LIKE oparator and is then not valid CQL anymore
-
Key: GEOT-2859
URL: http://jira.codehaus.org/browse/GEOT-2859
Project: GeoTools
Issue Type: B
equals() broken for LiteralExpressionImpl of type LONG
--
Key: GEOT-2858
URL: http://jira.codehaus.org/browse/GEOT-2858
Project: GeoTools
Issue Type: Bug
Components: core filter
Hi Jody,
thx.
I guess you can use something like "GC Module to handle JP2K format. (using
Kakadu when available)"
PS: Sorry for the late reply. I have found that email on GMAIL's draft. Not
sure why this has never been sent by gmail... maybe some connection issue.
On Thu, Nov 19, 2009 at 5:26 PM
rini.angre...@csiro.au ha scritto:
> Hi Justin,
>
> Thank's for looking at this.
> I don't think e can be null, because on the very top of the method, it's
> doing something to it.
>
> if ( e instanceof PropertyName ) {
> name = (PropertyName) e;
> }
>
> It would throw NullPointerException
Hi Justin,
Thank's for looking at this.
I don't think e can be null, because on the very top of the method, it's doing
something to it.
if ( e instanceof PropertyName ) {
name = (PropertyName) e;
}
It would throw NullPointerException before it gets to the null checking bit.
Is it OK to com
LabelCache Exceptions should not use System.out but report to RenderListener
Key: GEOT-2857
URL: http://jira.codehaus.org/browse/GEOT-2857
Project: GeoTools
Issue T
OK, I will try to get through the paper work, hopefully it will run smoothly
;-).
/Mauritz
-Ursprungligt meddelande-
Från: Jody Garnett [mailto:jody.garn...@gmail.com]
Skickat: den 26 november 2009 02:06
Till: Andrea Aime
Kopia: Bomark Mauritz; geotools-devel@lists.sourceforge.net
Ämn
Ciao Jody,
my opinion is that the long term goal is to have temporal part of
referencing since we need to rely on the notion of temporalcrs and in
the end what iso 19108 can be seen as a companion to direct position
classes and the like.
This of course involves working also at the geoapi level, the
> About this last sentence, I propose also to merge directly the temporal
> stuff into the referencing module instead of having a separate module on
> library.
> What do you think about that?
> Cheers,
> Alessio.
It makes sense from an abstraction point of view; however right now we
are
17 matches
Mail list logo