Jody - Thanks for the enlightening answers. I like chicken-and-eggs: You have 'your' (Geo)Tools and some discovery services - say that's the chicken - and I can finally release my eggs, namely GMDB (not the music db!) as open source metadata editor and
geometa.info as a discovery portal (nice term
Jody Garnett wrote:
> Cory Horner wrote:
>
>> I noticed the geotools version on trunk is still 2.3-SNAPSHOT.
>> Should this be 2.4-SNAPSHOT, or are we waiting for the release first?
>
> Well we should of related for a 2.3.RC, but yes since they made the
> branch lets call trunk 2.4-SNAPSHOT.
1 non-critical goal for 2.4 I'd like to add/offer is re-enabling the
geometryless data store. I've updated it so it compiles and runs tests,
yet to check against a geoserver build - whats the timeframe for
geoserver trunk to run against 2.4 ?
Rob
Jody Garnett wrote:
> Cory Horner wrote:
>
Justin Deoliveira wrote:
>Sorry for the late reply, but this commit already went through I take it.
>I was hoping to get a chance to review it first. With Chris bringing up
>policy, I am having some issues with commit and ask questions later style
>we seem to have adopted.
>
>
Fair enough i
Ok Luca,
I found some time (actually it is 1:21 am in Italy and I manage to
find 1h to check your problem :-) ).
You actually ran into an issue with ImageIO and jpeg that was actually
creating an incorrect mosaic.properties file. Now the issue is fixed.
I tried myself with the data you provided a
Cory Horner wrote:
> I noticed the geotools version on trunk is still 2.3-SNAPSHOT. Should
> this be 2.4-SNAPSHOT, or are we waiting for the release first?
>
Well we should of related for a 2.3.RC, but yes since they made the
branch lets call trunk 2.4-SNAPSHOT.
2.4-SNAPSHOT has a very small
Apply minor postgis changes
---
Key: GEOT-954
URL: http://jira.codehaus.org/browse/GEOT-954
Project: GeoTools
Issue Type: Task
Components: data postgis
Affects Versions: 2.2.0
Reporter: Cory
PostGISAutoIncrementFIDMapper doesn't support non-serial primary keys
-
Key: GEOT-953
URL: http://jira.codehaus.org/browse/GEOT-953
Project: GeoTools
Issue Type: Bug
What about declaring an interface with a minimal set of test methods
that must be implemented per data store?
This would make it hard to comment out individual tests whilst
developing, but maybe we allow the test suite to be built without
declaring the interface, and only insist on it by time m
Adrian Custer wrote:
> Hey all,
>
> Moving right along, I'm trying to outline the Data Storage system, that
> is DataStore and its ilk. Could someone walk through the packages below
> and answer my questions? [WARNING: For this work, my writeup will ignore
> Catalog despite my recent emails on that
On Mon, 2006-25-09 at 13:23 +0200, Adrian Custer wrote:
>
> org.geotools.data.ows
> *) Is this infrastructure for WMS and WFS, or is it
> something else?
> *) Why is this here and not in a plugin?
> *) How does this com
I noticed the geotools version on trunk is still 2.3-SNAPSHOT. Should
this be 2.4-SNAPSHOT, or are we waiting for the release first?
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel
Hi lists,
a very first version of the ImagePyramid plugin has been committed to
geotoold trunk.
This plugin is a read-only coverage plugin to seamlessly create
coverages out of a pyramid of mosaics of georeferenced images or
geotiffs.
For this week i will not be able to write any documentation (w
Stefan F. Keller wrote:
> This approach sounds reasonable. So, let me make a cross walk again
> with DC (see below). Perhaps there is some mutual input.
>
>
> > - How is the local catalog built? From usage? Can it be
> externalised?
> > E.g. posted to a remote indexing service? Wou
Justin Deoliveira ha scritto:
> Andrea Aime wrote:
>> Justin Deoliveira ha scritto:
>>> Hi all,
>>>
>>> The idea of a datastore compliance test has been kicking around for some
>>> time now. The idea is to create an abstract test case which tests all
>>> aspects of the datastore api, and then subcl
Justin Deoliveira wrote:
> Fair enough. My point was that having the schema around implies that the
> filter can only be executed against features of a particular type. For
> instance.
>
Indeed I expect the expression to operate against many things - like
java beans? This is why the factory.att
Gabriels reply was much more to the point, how about we set up an Wiki
page or break out IRC and get this puppy done.
Justin would geotools trunk be appropriate for this work? Or do you need
GeoTools 2.2.x
Jody
> Jody Garnett ha scritto:
>> Sure it amounts to *not* making use of our constr
Sure it amounts to *not* making use of our constructor based reflection
(ie can we find a constructor that takes a string?). Gabriel recommended
a jakarta commons implementation that was more open ended, but we could
also roll our own (ends up being something similar to a hibernate
"UserType"),
Hi Justin,
I think that the lack of boolean is a problem that almost we all thought about
more than one, so it would be great to finally have a solution, mostly when
it is so simple.
I could be just ranting, but had the following idea:
AttributeType already has a class binding, so why don't we
Justin Deoliveira wrote:
> The idea of a datastore compliance test has been kicking around for some
> time now. The idea is to create an abstract test case which tests all
> aspects of the datastore api, and then subclass for each data store.
>
> Jody implemented such a test for memory data store s
> Adrian Custer wrote:
> > Hey,
> >
> > TemporalAttributeType seems like a total hack. It should look a whole
> > lot like GeometryAttributeType. That is, it should provide access to a
> > TemporalReferencingSystem and should allow lots of different forms: an
> > instant (point), an interval (lin
Sure, can you jog my memory as to what that is?
-Justin
Jody Garnett wrote:
> Can we look into Gabriel's suggestion for literal parsing? The further
> we move away from TemporalAttributeType.parse( Object ) the better.
> Jody
>> Hi all,
>>
>> Currently, TemporalAttributeType just tries the defaul
I would like to step back and handle literals correctly, and
independently of a "defined" XXXAttributeType, Gabriel has made the
suggestion several times now
I would like to ensure that we can work *just* from a AttributeType with
.getType() == Boolean.class
Jody
> I would like to create
Can we look into Gabriel's suggestion for literal parsing? The further
we move away from TemporalAttributeType.parse( Object ) the better.
Jody
> Hi all,
>
> Currently, TemporalAttributeType just tries the default java date format
> when trying to parse a date value from a string. I would like to
Hi Adrian,
I think the issue is that this attribute type is poorly named. It should
be named DateAttributeType.
Having "temporal" attributes is an entirely different ball of wax.
-Justin
Adrian Custer wrote:
> Hey,
>
> TemporalAttributeType seems like a total hack. It should look a whole
> lot
Hey,
TemporalAttributeType seems like a total hack. It should look a whole
lot like GeometryAttributeType. That is, it should provide access to a
TemporalReferencingSystem and should allow lots of different forms: an
instant (point), an interval (line), a collection (collection: series
(multipoint
Jody, Jo,
2006/9/25, Jody Garnett [EMAIL PROTECTED]:
...
> GeoTools has a Catalog abstraction. This can point to a remote or local> Service. A Service offers an interface through to GeoStuffOfSomeKind.
> This can be an OWS but also an SLD resource or some metadata service.Actuallly the "point to"
Andrea Aime wrote:
> Justin Deoliveira ha scritto:
>> Hi all,
>>
>> The idea of a datastore compliance test has been kicking around for some
>> time now. The idea is to create an abstract test case which tests all
>> aspects of the datastore api, and then subclass for each data store.
>>
>> Jody im
On Mon, 2006-09-25 at 12:04 -0400, Justin Deoliveira wrote:
> Hi Adrian,
>
> I can take care of this.
Well you could but then it wouldn't fit into the framework I'm
developing for the Geotools Users' Manual (yes good manuals have
frameworks too). It's also a question of understanding how the pie
Justin Deoliveira ha scritto:
> Hi all,
>
> The idea of a datastore compliance test has been kicking around for some
> time now. The idea is to create an abstract test case which tests all
> aspects of the datastore api, and then subclass for each data store.
>
> Jody implemented such a test for
Hi all,
The idea of a datastore compliance test has been kicking around for some
time now. The idea is to create an abstract test case which tests all
aspects of the datastore api, and then subclass for each data store.
Jody implemented such a test for memory data store some time back. I
ported t
Hi all,
Currently, TemporalAttributeType just tries the default java date format
when trying to parse a date value from a string. I would like to
slightly modify this to include a set of "common" date formats to try
(including the default).
Any objections?
-Justin
--
Justin Deoliveira
[EMAIL P
Justin Deoliveira ha scritto:
> I would like to create an attribute type for booleans, similar to the
> attribute types for the other primitives. textual, temporal, numeric, etc...
>
> Then add some logic in DefaultAttributeTypeFactory to create intsances
> of these when a boolean value is encount
I would like to create an attribute type for booleans, similar to the
attribute types for the other primitives. textual, temporal, numeric, etc...
Then add some logic in DefaultAttributeTypeFactory to create intsances
of these when a boolean value is encountered.
Any objections?
-Justin
--
Jus
Hi Adrian,
I can take care of this. I need a good tutorial for geoserver docs
anyways. So I will throw this on the list of things to do.
-Justin
Adrian Custer wrote:
> Hey all,
>
> This email is an overview of the Catalog system with lots of questions.
>
> The Catalog+Tutorial needs some love.
Fair enough. My point was that having the schema around implies that the
filter can only be executed against features of a particular type. For
instance.
Currently:
FeatureType type1 = ...;
Feature f1 = type1.create( ... );
AttributeExpression e1 = factory.attribteExpression( type1, "foo" );
Att
View results here ->
http://geo.openplans.org:9090/buildresults/geotools?log=log20060925105336Lbuild.34
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to s
Andrea Aime wrote:
> Justin Deoliveira ha scritto:
>> So what applications must do
>> on startup is the following:
>>
>> FactoryFinder.addServiceIterator( new SpringServiceIteratorProvider() )
>> in geoserver
>>
>> FactoryFinder.addServiceIterator( new UdigServiceIteratorProvider() ) in
>> udig
>>
Andrea Aime wrote:
> Justin Deoliveira ha scritto:
>> Hi all,
>>
>> I wanted to write this up while it is still fresh in my mind. For those
>> of us unfamiliar with the problem, the "factory problem" is this:
>>
>> How do we enable the user to supplement geotools code with custom
>> factories. Why
View results here ->
http://geo.openplans.org:9090/buildresults/geotools?log=log20060925104432
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
Frank Warmerdam wrote:
> Jody Garnett wrote:
>> Another thing that came up in conversation last week was - why be
>> involved in OSGEO? After all so far it has mostly been requests for
>> work, on some problems we were comfortable ignoring previously...
>>
>> Here are some of the answers:
>> - so
Hi Jo & Adrian,
(Playing router for a couple of rounds, if only to show that the geodata
list is not mythical)
> dear Jody, Adrian, thanks for this startling level of Java API detail.
Sorry to throw you guys into the middle of it, I have pictures sitting here
that need to go up on the web.
> On
Jody Garnett wrote:
> Another thing that came up in conversation last week was - why be
> involved in OSGEO? After all so far it has mostly been requests for
> work, on some problems we were comfortable ignoring previously...
>
> Here are some of the answers:
> - source of funding for the "grunt
Adrian Custer wrote:
> Hello all,
>
> A link for Jody, who must be tired since his creativity doesn't extend
> into the web site he knows so well,
>
> http://docs.codehaus.org/display/GEOTOOLS/Catalog+Tutorial
>
Thanks, there is also a long section on the udig developers guide (w/
pictures).
Sorry for the late reply, but this commit already went through I take it.
I was hoping to get a chance to review it first. With Chris bringing up
policy, I am having some issues with commit and ask questions later style
we seem to have adopted.
One thing I would like to ask is that before any more
Hey all,
Moving right along, I'm trying to outline the Data Storage system, that
is DataStore and its ilk. Could someone walk through the packages below
and answer my questions? [WARNING: For this work, my writeup will ignore
Catalog despite my recent emails on that subject.]
org.geotool
Hi all,
I've added a global variable and a maven profile to avoid window popups during
the build
by default, but allow them to be seen on user choice.
Setting the org.geotools.test.interactive system variable to true when
launching a single test,
it will show popup windows (-Dorg.geotools.test.i
Jody Garnett ha scritto:
> Thanks Mr Custer, (sending your reply onto the appropriate osgeo list)
>> Hey Jody,
>> Here's my take on the migration proposal doc:
>> 1) Web site:
>> Moving to a website without ads would be good. Drupal seems
>> reasonable except that we should consider
Hello all,
A link for Jody, who must be tired since his creativity doesn't extend
into the web site he knows so well,
http://docs.codehaus.org/display/GEOTOOLS/Catalog+Tutorial
that is:
http://docs.codehaus.org/display/GEOTOOLS/ and Catalog+Tutorial
--adrian
P.S. Not sure what the 'G
49 matches
Mail list logo
