Hello,
i am just writing an info.xml for a Streets-Feature-Type in
Gauss Krüger projection with a bounding box of
BOX3D(3427000.29 5787594.24 0,3444004 5800876.47 0)
in GAUSS-KRÜGER coordinates.
Should I transform this coordinates to LatLon to define
the boundingbox or is there another element for do
that with Gauss Krüger coordinates.
Thank you for help
Björn
--
Björn Voigt Tel: +49-3943-626654
Dipl.-Wi-Inf e-mail: bvoigt@anonymised.com
Hochschule Harz oder: bjoern-voigt@anonymised.com
Friedrichstrasse 57-59 http://www.bjoern-voigt.de
38855 Wernigerode
Right now the latlong bounding box isn't used for anything affecting the
performance of geoserver, it is just reported out in the GetCapabilities
document. In the future we're looking to have our datasources
automatically figure out their bounding boxes, so users will not have to
specify. But for now, yes, just transform the coords into LatLon. It
doesn't even have to be very accurate, an approximation of the latlon box
will do, since like I said, it's not used internally for geoserver at all,
just for reporting to clients about where the features in the featureType
occur.
Chris
On Wed, 29 Oct 2003, Björn Voigt wrote:
Hello,
i am just writing an info.xml for a Streets-Feature-Type in
Gauss Krüger projection with a bounding box of
BOX3D(3427000.29 5787594.24 0,3444004 5800876.47 0)
in GAUSS-KRÜGER coordinates.
Should I transform this coordinates to LatLon to define
the boundingbox or is there another element for do
that with Gauss Krüger coordinates.
Thank you for help
Björn
--