John Preston ha scritto:
Nope, it does not mean it does not understand it, it means it's not
an exact match for an official EPSG code. It's actually quite common,
one parameter could be slightly different, or the ellipsoid name could
be different.OK. It was a mismatch in the datum name. So now, when I click the
"Lookup SRS" button it returns the correct SRS code.
I know it is working because when I set the SRS handling to reproject
and enter the 4326 SRS code and then click on the "generate" button to
generate the bounding box in Lat/Lon as opposed to my native units.So now this works.
Nice.. hem, can you keep geoserver-users cc'ed?
Two more questions if you can.
1) How can I toggle the SRSHandling option of the feature so that I
can set it to use native SRS sometimes, but reproject to 4326 (WGS84)
at other times.
You cannot. Reprojection usually occurs because the request
asks for it. There are ways to ask for reprojection in both
the WMS and the WFS protocols, check the OGC specifications for
the details (hint, WMS, add srs=EPSG:XXXX, WFS, add srsName=EPSG:XXXX
to your requests).
2) How can I get the feature exported in KML as lines.
If they are lines they will be exported as lines, otherwise they
won't. The GeoServer KML generation engine
tries hard to mimick what occurs in a plain WMS request, it does
not do geometry mapping (like turning a polygon into a line).
Not sure what you're trying to do here?
Cheers
Andrea