Hi,
Thanks for this! I have updated to ArcSDE 9.x Java client Jar files in WEB-INF\lib\ and everything is now working. Maybe the doco should be updated to that effect.
Anyway on another note I noticed that Geoserver doesn't auto populate the ESPG code for ArcSDE layers even though the information is stored in ArcSDE?
Is it because the SRTEXT used by GeoServer and ArcSDE is different or is it because GeoServer fails to look it up in SDE?
SDE stores the information here:
SELECT SDE.LAYERS.OWNER, SDE.LAYERS.TABLE_NAME, SDE.SPATIAL_REFERENCES.SRTEXT
FROM SDE.LAYERS, SDE.GEOMETRY_COLUMNS, SDE.SPATIAL_REFERENCES
WHERE SDE.LAYERS.OWNER = SDE.GEOMETRY_COLUMNS.F_TABLE_SCHEMA
AND SDE.LAYERS.TABLE_NAME = SDE.GEOMETRY_COLUMNS.F_TABLE_NAME
AND SDE.GEOMETRY_COLUMNS.SRID = SDE.SPATIAL_REFERENCES.SRID ;
In my corner of the world it stores these values in ArcSDE for ESPG-4283:
GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]]
Geoserver ESPG-4283:
GEOGCS["GDA94", DATUM["Geocentric_Datum_of_Australia_1994", SPHEROID["GRS 1980", 6378137.0, 298.257222101, AUTHORITY["EPSG","7019"]], TOWGS84[0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0], AUTHORITY["EPSG","6283"]], PRIMEM["Greenwich", 0.0, AUTHORITY["EPSG","8901"]], UNIT["degree", 0.017453292519943295], AXIS["Lon", EAST], AXIS["Lat", NORTH], AUTHORITY["EPSG","4283"]]
So the strings are quite different I guess....
Anyway just a thought. Thanks for the help, much appreciated.
/Jesper
BTW. The problem I encountered with the location of the states shapefile was in the WAR download from sourceforge.
From: Gabriel Roldán <groldan@anonymised.com>
To: Saul Farber <Saul.Farber@anonymised.com>
CC: Chris Holmes <cholmes@anonymised.com>, Jesper Nielsen <jkn_73@anonymised.com>, geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] ArcSDE Support
Date: Thu, 6 Jul 2006 22:08:33 +0200
Hi guys,
unfortunately the arcsde plugin does depends on the arcsde 9.x jars, in order
to be compatible with both 8.x and 9.x. Making it working with the 8.3 jars
would require having a separate build for the arcsde plugin, since I remember
I had to use the new geometry types constants introduced in 9.x in order to
correctly identify the geometry flags of an SeLayer. I remember having to do
that when I was working with Brent in some performance anhancements for the
plugin and I only had access to 8.x but he had to 9.x.
So Jesper, is there any possibility that you get the 9.x jars legally from
somewhere? I know they come, for example, in service packs for ArcIMS,
ArcExplorer Java, and of course the ArcSDE 9.x client CD.
I am still not sure if you're allowed to copy the jars that comes with
ArcExplorer Java to be used by other application, may be you can read the
license file to figure it out?
Gabriel
On Thursday 06 July 2006 21:05, Saul Farber wrote:
> That is indeed a good question.
>
> I don't think there's anything that depends on SDE 9.x jars...but I
> haven't looked through the new 'auto-magically detect' ArcSDE code. I'm
> still running on a version of the GS code that's 1.3.1/GT-2.1.x based.
>
> I'll be moving to the GS trunk when the 1.4.x merge happens, so I'm sure
> I'll have a good answer at that point!
>
> --saul
>
> Chris Holmes wrote:
> > Hmmm... Just tried it myself, and I think that 8.3 may no longer work?
> > Which shouldn't be the case I don't believe, but I think it's now
> > checking for a file that is only in 9.x? Gabriel or Saul? Any insight
> > into whether we actually really depend on something in 9.x, or if that
> > requirement accidentally got added in the code? I think everything's
> > supposed to be backwards compatible with their jars, and it should with
> > our code as well.
> >
> > Chris
--
Gabriel Roldán (groldan@anonymised.com)
Axios Engineering (http://www.axios.es)
Tel. +34 944 41 63 84
Fax. +34 944 41 64 90
_________________________________________________________________
New year, new job there's more than 100,00 jobs at SEEK http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn.seek.com.au&_t=752315885&_r=Jan05_tagline&_m=EXT