Improving parsing of Mercator_1SP / Mercator_2SP projection on geotiff metadata
adapters
Key: GEOT-2163
URL: http://jira.codehaus.org/browse/GEOT-2163
Project:
Shapefile does not use charset when writing the shapefile
-
Key: GEOT-2164
URL: http://jira.codehaus.org/browse/GEOT-2164
Project: GeoTools
Issue Type: New Feature
Make jdbc-ng parameters compatible with the old jdbc datastores
---
Key: GEOT-2165
URL: http://jira.codehaus.org/browse/GEOT-2165
Project: GeoTools
Issue Type: New Feature
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1135/changes
Changes:
[aaime] GEOT-2165 Make jdbc-ng parameters compatible withthe old jdbc datastores
--
[...truncated 19231 lines...]
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
There is a list of changes at doc OGC 07-061
first, the theory...
Note that since the target is backwards compatibility of the
instances and not the application schemas, outdated types (and
abstract elements) have been removed and not deprecated whenever
possible.
Moist changes seem to be
We should take that discussion to the uDig devel list; I would need to
talk to you about how the datastore is configured by the user (do we
need to create a wizard etc?). If you have a standalone dataset that we
could use for testing that would also be good. Gabriel has done a bit of
work to
Exception during rendering svg file udig/geotools
-
Key: GEOT-2166
URL: http://jira.codehaus.org/browse/GEOT-2166
Project: GeoTools
Issue Type: Bug
Components: core render, core
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1136/changes
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great
Jody,
we do not yet have a standalone dataset. Configuration is painful, and
in flux. Hopefully when we have feature chaining implemented and have a
working GeoServer we should be able to make a standalone configuration
that might be useful to you.
Kind regards,
Ben.
Jody Garnett wrote:
We
