Apparently the archives can be slurped over to the new hardware as well.
Jody
Adrian Custer wrote:
> Jody Garnett wrote:
>> So we have three "votes" for moving the mailing list to osgeo
>> hardware. Talking to Paul it seems such a thing is possible/easy ...
>> so here is a formal motion. It cov
Super - thanks Adrian. That's both encouraging and terrifically informative.
Re-reading my previous post, I'm sorry for the pessimistic tone. I'm a
scientist presently in hiding from the bureaucracy that pays me (or at
least keeping a very low profile) and I sometimes think years of
dealing with
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1202/changes
--
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to hel
Well I would say that since there are no people currently using the
module (that I know of), and no module maintainer around that you should
be able to commit to it directly.
Emily Gouge wrote:
> I'm not sure how "back to life" I'll be able to bring it, but at least I
> can submit updates to ma
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1201/changes
--
[...truncated 18647 lines...]
[INFO]
[INFO] [clean:clean]
[INFO] [resources:resources]
[INFO] Using default encod
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1200/changes
--
started
Updating http://svn.osgeo.org/geotools/trunk
ERROR: Failed to update http://svn.osgeo.org/geotools/trunk
org.tmatesoft.svn.core.SVNException: svn: This client is too old to work
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1199/changes
--
started
Updating http://svn.osgeo.org/geotools/trunk
ERROR: Failed to update http://svn.osgeo.org/geotools/trunk
org.tmatesoft.svn.core.SVNException: svn: This client is too old to work
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1198/changes
Changes:
[jdeolive] GEOT-2225, xml configuration moved to 1.1 specific configuration
[jdeolive] GEOT-2225, seperated wfs 1.0 and 1.1 xml configurations
--
[...truncated 5070 lines...]
--
Michael Bedward wrote:
> Hi Adrian,
>
> Please excuse this slight hijack of the topic, but there have been
> mentions of eventually back-porting the new and beautiful code to work
> against Java5. Do you have any feelings on how realistic that idea is
> ? My guess is that it's unlikely to happen
Hi Adrian,
Please excuse this slight hijack of the topic, but there have been
mentions of eventually back-porting the new and beautiful code to work
against Java5. Do you have any feelings on how realistic that idea is
? My guess is that it's unlikely to happen for all of the usual, real
world r
Hello,
Jody has essentially answered you already but I'll add my take which may
flesh out the explanation.
The style specification evolved greatly from its earlier incarnation
which involved a fairly extensive re-design of the system in place.
During that work the author of the new style syste
I'm not sure how "back to life" I'll be able to bring it, but at least I
can submit updates to make it buildable and hopefully get the test cases
running again.
What's the best way for me to submit changes? Should I create bug
reports and patches or see if I can commit to it directly?
Thanks.
Jody Garnett wrote:
> So we have three "votes" for moving the mailing list to osgeo hardware.
> Talking to Paul it seems such a thing is possible/easy ... so here is a
> formal motion. It covers two things:
> 1. moving the mailing lists to osgeo hardware
> 2. changing the names so they are less c
Hi guys,
Take a look at http://jira.codehaus.org/browse/GEOT-2226. I found
that running intersection filter was REALLY slow so I decided to see
how it would work using Prepared Geometries. The improvement was
incredible.
Obviously not all spatial filters will get this improvement since
> Od: [email protected]
>
>
>Ah, I misunderstood then... Just looked on the information provided at
>http://www.epsg-registry.org/ - clicking on "retrieve by code", entering "9819"
>in the field, clicking on "Retrieve", clicking on "view" on the retrieved line,
>and finally clicking
Hi,
The shapefile system is in need of some work that I plan on doing at
some point in the future. The problem is that when the datastore was
written it did not use the mechanism for deleting records that is
built into the spec where you can null out a geometry indicated it was
deleted.
Hi All,
I am testing GeoTools for creating shape files. I typically have to deal
with a couple million points (~1 - 3 millions). Therefore, I am looking for
a way to sequentially write features to the shape-file. I repeatedly
generate a "FeatureCollection collection",
add the collection to the "Fe
17 matches
Mail list logo
