Added a Wiki page about the axis order issue. I wrote it mostly from the material found in various
emails from Paul, Jody, Bryce and others.
http://docs.codehaus.org/display/GEOTOOLS/The+axis+order+issue
Note: the FORCE_LONGITUDE_FIRST_AXIS_ORDER hint is not yet implemented. This is a proposal that may
change according feedback received.
Adrian Custer a écrit :
(edited)
2) Would it make sense to change plugin/gt2-epsg-wkt to plugin/gt2-geotools-wkt?
It seems the WKT authority plugin is (1) a fork and (2) altered
in terms of what axes are returned. Doesn't this make it a new
data source with a parallel naming scheme to the EPSG data base
but different results? Wouldn't changing the authority name help
clarify its distinct status?
Maybe. The gt2-epsg-wkt plugin was wrote at a time where gt2-epsg-hsql was not functional. A
possible path that I would like to suggest is:
- See if gt2-epsg-hsql (after the axis order issue
is fixed) can meet the uDig and Geoserver needs.
- Refactor gt2-epsg-wkt as something like "gt2-epsg-extension", because it
contains CRS
not defined in the official EPSG database (I assume that it was in order to
meet some
client needs). All CRS defined in "gt2-epsg-hsql" would be removed from
"gt2-epsg-extension",
so the later would contains only custom CRS. As the name imply, it would
provide an
extension to the usual EPSG database.
Note: EPSG explicitly allows the addition of custom CRS in some specific code range (I forgot the
code range).
Martin.
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
