I added a section with a table listing the deprecated methods I had to
change (and any other well-documented ones I found in the diff):
http://docs.codehaus.org/display/GEOTOOLS/Upgrade+to+8.0#Upgradeto8.0-gtopengis%2Cgtreferencing%3Adeprecatedmethodsremoved
I have no examples, but simboss
On Wed, May 18, 2011 at 5:49 AM, Jody Garnett jody.garn...@gmail.comwrote:
Ben can you reply with an example of:
- what has been removed
- what the replacement is
We need to update the Update to 8 page.
- http://docs.codehaus.org/display/GEOTOOLS/Upgrade+to+8.0
Simboss as you do this
+1. That is where it belongs.
On 18/05/11 15:10, Andrea Aime wrote:
Afaik Simone cannot access the wiki anymore. Should we migrate that page to
sphinx too?
--
Ben Caradoc-Davies ben.caradoc-dav...@csiro.au
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
I want to propose Steve Way for commit access on the imagemosaic-jdbc
module. He has a lot of experience with Oracle Georaster (I have
not). Oracle Georaster changes its behavior and API like a chameleon
its color.
We have some further targets (supporting time series an example).
@Steve,
Does Steve have commit access yet? if not he will need to go through the normal
procedure before working on imagemoasic-jdbc (as it is a supported module).
To review we need to see a number of patches (example 3). Things to look for
when reviewing; geotools formatting, test case use (consistent
You could; we would need to think about where to place it; currently the
Welcome section seems the most appropriate; since we have a Welcome page for
specific groups of users; we could have a Welcome GeoTools Developers page
helping people upgrade? A child page for each set of update to
Hi all,
Another strange thing I realized is that exactly this gt-geojson library
packaged from GeoTools v2.7.0 up to v2.7.1 is no more able to return the
defaultGeometry for a GeoJSON String read by a SimpleFeature. In GeoTools
v2.7-RC2 the gt-geojson library provides the defaultGeometry of a
The base wiki site is controlled with xicles for the most part; looks like he
last edited on April 3 (the Skip GeoTools 3 page). Has anything changed since
then to prevent access?
In anycase I have forced the setting; he should be able to edit :-)
--
Jody Garnett
On Wednesday, 18 May 2011 at
Quoting Jody Garnett jody.garn...@gmail.com:
Does Steve have commit access yet?
No, I thought he head already started with a community module, but he did not.
if not he will need to go through the normal procedure before
working on imagemoasic-jdbc (as it is a supported module).
Yep, I
Ciao Christian,
assumig this work will proceed on trunk, I strongly suggest we take
the opportunity to merge the various imagemosaic/imagepyramid plugins
into a single one where we have multiple backends to pull tiles
but still one single plugin that does the heavy lifting (background
color,
Ciao Christian,
assumig this work will proceed on trunk, I strongly suggest we take
the opportunity to merge the various imagemosaic/imagepyramid plugins
into a single one where we have multiple backends to pull tiles
but still one single plugin that does the heavy lifting (background
color,
Ciao Simone,
I noticed you reinstated spatailite into the build. Note that people had
issues compiling it on java6 so you might get some some complaints. I never
quite had time to figure out why the build was failing.
-Justin
On Tue, May 17, 2011 at 4:28 PM, svn_geoto...@osgeo.org wrote:
Ciao, the never ending story reloaded :-)
Quoting Simone Giannecchini simone.giannecch...@geo-solutions.it:
Ciao Christian,
assumig this work will proceed on trunk, I strongly suggest we take
the opportunity to merge the various imagemosaic/imagepyramid plugins
into a single one where we
In my view, I think the user and developer docs should contain facts and
information about things that are, not proposals, goals, or forward
looking statements, which might cause confusion. Would goals in the
stable branch docs still be goals if they are not in the trunk docs?
The docs should
14 matches
Mail list logo
