Hi,
I have noticed what seems to be a problem with the EPSG WKT definitions in Geoserver 1.5 (RC4). It appears that all of the EPSG definition have the 'UNIT' set to metres. I had been trying to use EPSG #2913 (NAD83 HARN, Oregon State Plane North, feet) and noticed incorrect bounding box calculations in the FeatureType Editor. I looked more closely at the WKT and saw that the units were metres instead of feet and that the false easting was incorrect. All of this information was correct in Geoserver 1.4. My present workaround is the use of a custom SRS (actually the WKT from v1.4) but this only works for datasets (shapefiles, mostly) where the SRS is 'unknown.'
Regards,
Nathan
Nathan Banks
Portland, Oregon
Hi Nathan,
Looking at the WKT definition of EPSG 2913, they seem to be identical in GeoServer 1.4.x as they are in GeoServer 1.5.x. Both with a false easting of 8202099.738, and both specify "ft" as the units.
Apologies if i am missing something... where are you getting the wkt from. Could you include it. Thanks.
-Justin
Banks, Nathan wrote:
Hi,
I have noticed what seems to be a problem with the EPSG WKT definitions in Geoserver 1.5 (RC4). It appears that all of the EPSG definition have the 'UNIT' set to metres. I had been trying to use EPSG #2913 (NAD83 HARN, Oregon State Plane North, feet) and noticed incorrect bounding box calculations in the FeatureType Editor. I looked more closely at the WKT and saw that the units were metres instead of feet and that the false easting was incorrect. All of this information was correct in Geoserver 1.4. My present workaround is the use of a custom SRS (actually the WKT from v1.4) but this only works for datasets (shapefiles, mostly) where the SRS is 'unknown.'
Regards,
Nathan
Nathan Banks
Portland, Oregon
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Banks, Nathan ha scritto:
Hi,
I have noticed what seems to be a problem with the EPSG WKT definitions in Geoserver 1.5 (RC4). It appears that all of the EPSG definition have the
'UNIT' set to metres. I had been trying to use EPSG #2913 (NAD83 HARN, Oregon State Plane North, feet) and noticed incorrect bounding box
calculations in the FeatureType Editor. I looked more closely at the WKT and saw that the units were metres instead of feet and that the false
easting was incorrect. All of this information was correct in Geoserver 1.4. My present workaround is the use of a custom SRS (actually the WKT
from v1.4) but this only works for datasets (shapefiles, mostly) where the SRS is 'unknown.'
Oh... I knew this was going to bite us... this is because if the dataset has it
own projection system we trust it, and we just reproject to the one declared.
This was added to handle datasets whose CRS is unknown to Geoserver, and allow
to present them to the world with a known CRS (and by extension, a known CRS
code).
I guess this is too late for 1.5.0, but we'll have to schedule a change for
1.5.1 where we allow the user to either reproject or override. Or maybe,
just override, since if you want to keep the original one, you can simply
add it to the list of user projections (with a random EPSG code).
Cheers
Andrea