From: Yingqi T. <ana...@gm...> - 2010-08-30 23:05:19
|
Just made it work, the problem turns out to be that I didn't include gt-epsg-wkt as dependency. Once I add it, the srid 4326 is recognized as WGS84. <dependency> <groupId>org.geotools</groupId> <artifactId>gt-epsg-wkt</artifactId> <version>${project.version}</version> </dependency> Thanks you all for the helpful info. On Mon, Aug 30, 2010 at 3:42 PM, Yingqi Tang <ana...@gm...> wrote: > I saw this exception in the log: > > org.opengis.referencing.NoSuchAuthorityCodeException: Authority "EPSG" is > unknown or doesn't match the supplied hints. Maybe it is defined in an > unreachable JAR file? > > Is there a local EPSG database GeoTools is trying to match "EPSG" to? > > > On Fri, Aug 27, 2010 at 11:26 PM, Andrea Aime <aa...@op...> wrote: > >> Jody Garnett ha scritto: >> >> The old datastore was a bit more forgiving in places; and may be >>> "guessing" your srid was an EPSG code number? >>> >> >> Another possible reason is that the user GS is using to access the db >> does not have rights to read the geometry_columns table, or that >> the schema in the geometry_columns table does not correspond >> to the actual one for the table at hand. >> >> The old store made a number of unwarranted assumptions that were >> removed. For example, assuming that all the geometry in the table >> were the same type as the first row when the geometry_columns >> was missing. >> >> >> Do you have your postgis spatial ref system table sorted out? The >>> "correct" thing to do is to look up the code there and then parse the WKT >>> back on the java side of things. >>> >> >> Oh boy no, that's not the correct thing, that's the broken one. >> The PostGIS database misses most towgs84 parameters in the WKT >> definitions, they might be used, but only as a desperate last >> resort if the code does not match one record in the official >> EPSG database >> >> Cheers >> Andrea >> >> >> -- >> Andrea Aime >> OpenGeo - http://opengeo.org >> Expert service straight from the developers. >> > > |