On Wednesday, 3 January 2024 5:35:42 AM AEDT Torben Barsballe wrote:
> Wicket 9 upgrade
>
> https://github.com/geoserver/geoserver/pull/7154
>
> Need to collect all pages and panels that need to be tested, make a list,
> and divide the list amongst participants to the testing effort. First we
> n
As flagged in gitter, I am (virtually) attending the OGC Vector API code
sprint. There is interest in an OGC Moving Features JSON implementation for
GeoTools. Moving Features is (simplistically) like OGC Simple Features with a
time attribute, except the time attribute is really a temporal geome
Thanks for your interest in GeoTools.
Procedures for contributing are given in
https://github.com/geotools/geotools/blob/master/CONTRIBUTING.md
That will point you off to
http://docs.geotools.org/latest/developer/procedures/contribute.html which
provides more detail on how to proceed.
Most of the easy ones (including some old “revert” branches, from reverting on
github) are removed.
There are a bunch of additional branches where I will put a simple message on
the PR to flag it as requiring attention.
We also have some really old feature branches. I’ll flag those later
That seems like something I could do on a tired Friday night.
Brad
From: Andrea Aime
Sent: Friday, 12 July 2019 7:32 PM
To: Geoserver-devel ; Geotools-Devel
list
Subject: [Geotools-devel] The dark side of the backport plugin: remember to
delete that branch! (and some cleanup needed)
As part of the https://osgeo-org.atlassian.net/browse/GEOT-5859 upgrade
from commons httpclient to httpcomponents 4.x I've noted some broken modules
(won't build because of AbstractDataStoreFactory) that use that API, such as
couchdb and the app-schema webservice.
Not related to httpclient up
> Sorry if this hits the wrong email list, but I am not getting responses
from users,
> and the one response I did get pointed at a third party product. I need to
know
> if Geotools will support POINT M and POINT Z WKT values. eg. POINT Z(48.44
-
> 123.37 123)
Your response is at:
https://sourcefor
I'd like to emphasise that I have no strong feeling one way or the other.
It was just a "something to consider" rather than an objection to the current
proposal.
Brad
> -Original Message-
> From: Andrea Aime [mailto:andrea.a...@geo-solutions.it]
> Sent: Monday, 5 June 2017 15:52
> To: Be
0530 local - please accept my apologies.
Brad
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_
Please accept my apologies for this meeting.
Brad
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Can the copyright really be 2003 for OSGEO when it didn't exist (with that
name) until 2006?
Brad
> -Original Message-
> From: Jody Garnett [mailto:jody.garn...@gmail.com]
> Sent: Friday, 2 December 2016 10:47
> To: GeoTools Developers ; James
> Macgill
> Cc: Martin Davis
> Subject: Re
> Oooh... does that mean we also get rid of the blasted merge commit and
> retain
> a more linear history? :-)
Indeed it does.
https://github.com/codice/imaging-nitf/commits/master shows a couple of recent
samples.
I note that it modifies the commit message "headline" to include a ref to the
p
0130 is definitely out unless it’s a major / significant activity, where I can
do the occasional all-night effort.
I sleep 2200 to 0600 local, sometimes more.
Brad
--
What NetFlow Analyzer can do for you? Monitors netw
Title: Message Title
Brad Hards created
> The GeoTools team is pleased to announce GeoTools 14-RC1:
Perhaps you wanted 15 or 15.0 here
> New features and improvements:
> • Ignore NetCDF grid_mapping_name that is present but unsupported
This is arguably a bug fix. Not that concerned though.
> • Java 8 is now required. Please view t
Title: Message Title
Brad Hards created
On Wed, 4 Nov 2015 10:24:59 AM Ben Caradoc-Davies wrote:
> GeoTools and GeoServer master are moving to Java 8, once CITE tests and
> builds are working again. This will include moving to Java 8 JDK,
> setting source+target to 1.8, cleaning up failures on Jenkins, and
> sanity testing of build artif
Title: Message Title
Brad Hards created an issue
Title: Message Title
Brad Hards created an issue
On Thu, 1 Oct 2015 10:04:28 AM Andrea Aime wrote:
> On Thu, Oct 1, 2015 at 7:42 AM, Brad Hards wrote:
> > That does appear to work, but its way too slow - it makes the WMS module
> > build 6 times slower.
> >
> > So I'm thinking of caching results. Howeve
There is a very wide range of EPSG codes supported in GeoServer, based on the
underlying Geotools support.
The problem is that a few don't work. There are bug reports about this:
https://osgeo-org.atlassian.net/browse/GEOS-3935
https://osgeo-org.atlassian.net/browse/GEOS-4010
and perhaps others.
Title: Message Title
Brad Hards created an issue
Title: Message Title
Brad Hards created an issue
Title: Message Title
Brad Hards created an issue
Title: Message Title
Brad Hards created an issue
http://docs.geotools.org/latest/userguide/_downloads/locations.csv appears to
be missing a row.
Do we have official numbers and a representative location for 2015?
Brad
--
Monitor Your Dynamic Infrastructure at Any Sca
On Thu, 17 Sep 2015 04:02:38 PM Christian Mueller wrote:
> Hi
>
> I have a mandate to develop/maintain a WMTS client. At the moment I am
> unsure where to start. WMS is an extension and I think WMTS is also a
> candidate for an extension.
Based on the WMTS implementation I did for OWSlib
(https:
I downloaded all the artifacts off the geotools.org (which SourceForge
redirected me to a mirror in Japan), unpacked them all successfully.
I build the project files (i.e. mvn clean install) for the following
configurations:
- mvn clean install
- mvn clean install -Dall
- mvn clean install -D
Following on from the discussion on relative times, I've come across an
weather display that might benefit from reference_time and named elevation
levels, vaguely like the way OGC 12-111r1 describes it.
Its pretty common to get weather data with two time dimensions:
- the date / time that the f
On Thu, 6 Nov 2014 03:20:24 PM you wrote:
> Rename MultiMap.remove(Object,Object) to something that doesn't conflict
> with with the new method on Map. At the same time ensure that the all the
> callers of the method are also updated.
I was planning to do that (maybe renaming to removeValueFromColl
Since JDK7 is potentially EOL in about 6 months
(http://www.oracle.com/technetwork/java/eol-135779.html), I
thought I'd look at JDK8 builds for geotools.
As it turns out, there are only two problems. One set of tests
for HTTPUtil fails because of hashing algorithm changes. Easy
to fix (assuming
Title: Message Title
Brad Hards created an issue
32 matches
Mail list logo
