[Geoserver-users] Geoserver BoundingBox

GeoServer GeoServer User
1

Hi all,

In geoserver, the values of the Boundingbox of the Editor FeatureTypes are calculated as? My SRS just only in Lat/Long? So, as I can use dataset in XY?

For example, if I have my dataset in system of coordinated in XY, how can define my boundingbox?

When I rendering my data, Boundingbox have to be in Lat/Long?

Thanks,

Vieira

2

Diogo Vieira ha scritto:

Hi all,

In geoserver, the values of the Boundingbox of the Editor FeatureTypes are calculated as? My SRS just only in Lat/Long? So, as I can use dataset in XY?

For example, if I have my dataset in system of coordinated in XY, how can define my boundingbox?

When I rendering my data, Boundingbox have to be in Lat/Long?

All OGC specs requires us to publish data bounding box in lat/lon.
If you have data that's just x/y, and you don't have any projection
info in your dataset saying otherwise, you can simply declare
that your data is in 4326 and be happy with it.

Cheers
Andrea

3

Hi,

But I have my dataset in system of coordinated that's:

PROJCS["Portuguese National System (D73)", GEOGCS [ "Melrica 1973 (D73)",
DATUM ["Melrica 1973 (D73)", SPHEROID ["International 1924", 6378388, 297]],
PRIMEM [ "Greenwich", 0.000000 ], UNIT ["Decimal Degree",
0.01745329251994330]], PROJECTION ["Transverse Mercator"], PARAMETER
["Scale_Factor", 1.000000], PARAMETER ["Central_Meridian", -8.131906],
PARAMETER ["Latitude_Of_Origin", 39.666667], PARAMETER ["False_Easting",
180.598000], PARAMETER ["False_Northing", -86.990000], UNIT ["Meter",
1.000000000000]]
, where dataset in system Cartesian (X/Y).
So what need to do for publish my data? I have to convert all to Lat/Long? I
have no other choice?

Thanks,
Diogo

-----Original Message-----
From: Andrea Aime [mailto:aaime@anonymised.com]
Sent: terça-feira, 23 de Janeiro de 2007 8:30
To: Diogo Vieira
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Geoserver BoundingBox

Diogo Vieira ha scritto:

Hi all,

In geoserver, the values of the Boundingbox of the Editor FeatureTypes
are calculated as? My SRS just only in Lat/Long? So, as I can use
dataset in XY?

For example, if I have my dataset in system of coordinated in XY, how
can define my boundingbox?

When I rendering my data, Boundingbox have to be in Lat/Long?

All OGC specs requires us to publish data bounding box in lat/lon.
If you have data that's just x/y, and you don't have any projection
info in your dataset saying otherwise, you can simply declare
that your data is in 4326 and be happy with it.

Cheers
Andrea

4

Diogo Vieira ha scritto:

Hi,

But I have my dataset in system of coordinated that's:

PROJCS["Portuguese National System (D73)", GEOGCS [ "Melrica 1973 (D73)",
DATUM ["Melrica 1973 (D73)", SPHEROID ["International 1924", 6378388, 297]],
PRIMEM [ "Greenwich", 0.000000 ], UNIT ["Decimal Degree",
0.01745329251994330]], PROJECTION ["Transverse Mercator"], PARAMETER
["Scale_Factor", 1.000000], PARAMETER ["Central_Meridian", -8.131906],
PARAMETER ["Latitude_Of_Origin", 39.666667], PARAMETER ["False_Easting",
180.598000], PARAMETER ["False_Northing", -86.990000], UNIT ["Meter",
1.000000000000]]
, where dataset in system Cartesian (X/Y).
So what need to do for publish my data? I have to convert all to Lat/Long? I
have no other choice?

No, you just have to declare the proper epsg code for your reference system. Looking at the srs list you'll discover that the espg code for your dataset is 27492 (searched with the browser for "Portuguese" and
after a find try I found one matching your parameters, as far as I can
tell).

Once you've declared the proper EPSG code, make Geoserver compute
the lat/lon bouding box (it'll compute the bbox in your reference system, and then convert it to lat/lon).

Hope this helps
Cheers
Andrea

5

Diogo Vieira ha scritto:

Hi,

But I have my dataset in system of coordinated that's:

PROJCS["Portuguese National System (D73)", GEOGCS [ "Melrica 1973 (D73)",
DATUM ["Melrica 1973 (D73)", SPHEROID ["International 1924", 6378388, 297]],
PRIMEM [ "Greenwich", 0.000000 ], UNIT ["Decimal Degree",
0.01745329251994330]], PROJECTION ["Transverse Mercator"], PARAMETER
["Scale_Factor", 1.000000], PARAMETER ["Central_Meridian", -8.131906],
PARAMETER ["Latitude_Of_Origin", 39.666667], PARAMETER ["False_Easting",
180.598000], PARAMETER ["False_Northing", -86.990000], UNIT ["Meter",
1.000000000000]]
, where dataset in system Cartesian (X/Y).
So what need to do for publish my data? I have to convert all to Lat/Long? I
have no other choice?

No, you just have to declare the proper epsg code for your reference system. Looking at the srs list you'll discover that the espg code for your dataset is 27492 (searched with the browser for "Portuguese" and
after a few tries I found one matching your parameters, as far as I can
tell):

PROJCS["Datum 73 / Modified Portuguese Grid",
   GEOGCS["Datum 73",
     DATUM["Datum 73",
       SPHEROID["International 1924", 6378388.0, 297.0, AUTHORITY["EPSG","7022"]],
       TOWGS84[-239.749, 88.181, 30.488, 0.263, -0.082, -1.211, 0.4597642531247778],
       AUTHORITY["EPSG","6274"]],
     PRIMEM["Greenwich", 0.0, AUTHORITY["EPSG","8901"]],
     UNIT["degree", 0.017453292519943295],
     AXIS["Geodetic longitude", EAST],
     AXIS["Geodetic latitude", NORTH],
     AUTHORITY["EPSG","4274"]],
   PROJECTION["Transverse Mercator", AUTHORITY["EPSG","9807"]],
   PARAMETER["central_meridian", -8.131906111111114],
   PARAMETER["latitude_of_origin", 39.666666666666664],
   PARAMETER["scale_factor", 1.0],
   PARAMETER["false_easting", 180.598],
   PARAMETER["false_northing", -86.99],
   UNIT["m", 1.0],
   AXIS["Easting", EAST],
   AXIS["Northing", NORTH],
   AUTHORITY["EPSG","27492"]]

Once you've declared the proper EPSG code, make Geoserver compute
the lat/lon bouding box (it'll compute the bbox in your reference system, and then convert it to lat/lon).

Hope this helps
Cheers
Andrea

6

But the epsg code 27492 is a system of coordinated that's declared in
Lat/Long, and my dataset use the same system of coordinated but is declared
in X/Y. The system of coordinated it's the same, but is declared in
different ways, you understand me? The same system of coordinated can be
declare in Lat/Long, in X/Y or in Eastings/Northings.
So, when I load my dataset in geoserver and I make Geoserver compute the
lat/long bouding box, the values of bounding box in lat/long it's could be
correct in Lat/Long, but because my dataset it's in X/Y, the min and max
values not encloses my dataset and I can't see nothing.
What can I do?

Thanks,
Diogo

-----Original Message-----
From: Andrea Aime [mailto:aaime@anonymised.com]
Sent: terça-feira, 23 de Janeiro de 2007 10:46
To: Diogo Vieira
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Geoserver BoundingBox

Diogo Vieira ha scritto:

Hi,

But I have my dataset in system of coordinated that's:

PROJCS["Portuguese National System (D73)", GEOGCS [ "Melrica 1973 (D73)",
DATUM ["Melrica 1973 (D73)", SPHEROID ["International 1924", 6378388,

297]],

PRIMEM [ "Greenwich", 0.000000 ], UNIT ["Decimal Degree",
0.01745329251994330]], PROJECTION ["Transverse Mercator"], PARAMETER
["Scale_Factor", 1.000000], PARAMETER ["Central_Meridian", -8.131906],
PARAMETER ["Latitude_Of_Origin", 39.666667], PARAMETER ["False_Easting",
180.598000], PARAMETER ["False_Northing", -86.990000], UNIT ["Meter",
1.000000000000]]
, where dataset in system Cartesian (X/Y).
So what need to do for publish my data? I have to convert all to Lat/Long?

I

have no other choice?

No, you just have to declare the proper epsg code for your reference
system. Looking at the srs list you'll discover that the espg code for
your dataset is 27492 (searched with the browser for "Portuguese" and
after a few tries I found one matching your parameters, as far as I can
tell):

PROJCS["Datum 73 / Modified Portuguese Grid",
   GEOGCS["Datum 73",
     DATUM["Datum 73",
       SPHEROID["International 1924", 6378388.0, 297.0,
AUTHORITY["EPSG","7022"]],
       TOWGS84[-239.749, 88.181, 30.488, 0.263, -0.082, -1.211,
0.4597642531247778],
       AUTHORITY["EPSG","6274"]],
     PRIMEM["Greenwich", 0.0, AUTHORITY["EPSG","8901"]],
     UNIT["degree", 0.017453292519943295],
     AXIS["Geodetic longitude", EAST],
     AXIS["Geodetic latitude", NORTH],
     AUTHORITY["EPSG","4274"]],
   PROJECTION["Transverse Mercator", AUTHORITY["EPSG","9807"]],
   PARAMETER["central_meridian", -8.131906111111114],
   PARAMETER["latitude_of_origin", 39.666666666666664],
   PARAMETER["scale_factor", 1.0],
   PARAMETER["false_easting", 180.598],
   PARAMETER["false_northing", -86.99],
   UNIT["m", 1.0],
   AXIS["Easting", EAST],
   AXIS["Northing", NORTH],
   AUTHORITY["EPSG","27492"]]

Once you've declared the proper EPSG code, make Geoserver compute
the lat/lon bouding box (it'll compute the bbox in your reference
system, and then convert it to lat/lon).

Hope this helps
Cheers
Andrea

7

Diogo Vieira ha scritto:

But the epsg code 27492 is a system of coordinated that's declared in
Lat/Long, and my dataset use the same system of coordinated but is declared
in X/Y. The system of coordinated it's the same, but is declared in
different ways, you understand me? The same system of coordinated can be
declare in Lat/Long, in X/Y or in Eastings/Northings.

A projected system like 27492 is _never_ lat/lon, usually it's meters, and you can see that by the UNIT["m", 1.0] declaration.

So, when I load my dataset in geoserver and I make Geoserver compute the
lat/long bouding box, the values of bounding box in lat/long it's could be
correct in Lat/Long, but because my dataset it's in X/Y, the min and max
values not encloses my dataset and I can't see nothing.
What can I do?

Oh hum, have you declared 27492 in your feature type configuration _before_ asking geoserver to compute the bounding box?
Is your dataset a shapefile? Is the WKT you provided me declared
in the .prj file?

Cheers
Andrea

8

But the epsg code 27492 is a system of coordinated that's declared in
Lat/Long, and my dataset use the same system of coordinated but is declared
in X/Y. The system of coordinated it's the same, but is declared in
different ways, you understand me? The same system of coordinated can be
declare in Lat/Long, in X/Y or in Eastings/Northings.

So, when I load my dataset in geoserver and I make Geoserver compute the
lat/long bouding box, the values of bounding box in lat/long it's could be
correct in Lat/Long, but because my dataset it's in X/Y, the min and max
values not encloses my dataset and I can't see nothing.

What can I do?

Here's an example:

1º SRS=27492 (bounding box not encloses my dataset)

2º SRS=4326 (bounding box encloses my dataset)

Thanks,

Diogo

-----Original Message-----

From: Andrea Aime [mailto:aaime@anonymised.com]

Sent: terça-feira, 23 de Janeiro de 2007 10:46

To: Diogo Vieira

Cc: geoserver-users@lists.sourceforge.net

Subject: Re: [Geoserver-users] Geoserver BoundingBox

Diogo Vieira ha scritto:

Hi,

But I have my dataset in system of coordinated that's:

PROJCS["Portuguese National System (D73)", GEOGCS [ "Melrica 1973 (D73)",

DATUM ["Melrica 1973 (D73)", SPHEROID ["International 1924", 6378388,

297]],

PRIMEM [ "Greenwich", 0.000000 ], UNIT ["Decimal Degree",

0.01745329251994330]], PROJECTION ["Transverse Mercator"], PARAMETER

["Scale_Factor", 1.000000], PARAMETER ["Central_Meridian", -8.131906],

PARAMETER ["Latitude_Of_Origin", 39.666667], PARAMETER ["False_Easting",

180.598000], PARAMETER ["False_Northing", -86.990000], UNIT ["Meter",

1.000000000000]]

, where dataset in system Cartesian (X/Y).

So what need to do for publish my data? I have to convert all to Lat/Long?

I

have no other choice?

No, you just have to declare the proper epsg code for your reference

system. Looking at the srs list you'll discover that the espg code for

your dataset is 27492 (searched with the browser for "Portuguese" and

after a few tries I found one matching your parameters, as far as I can

tell):

PROJCS["Datum 73 / Modified Portuguese Grid",

   GEOGCS["Datum 73",

     DATUM["Datum 73",

       SPHEROID["International 1924", 6378388.0, 297.0,

AUTHORITY["EPSG","7022"]],

       TOWGS84[-239.749, 88.181, 30.488, 0.263, -0.082, -1.211,

0.4597642531247778],

       AUTHORITY["EPSG","6274"]],

     PRIMEM["Greenwich", 0.0, AUTHORITY["EPSG","8901"]],

     UNIT["degree", 0.017453292519943295],

     AXIS["Geodetic longitude", EAST],

     AXIS["Geodetic latitude", NORTH],

     AUTHORITY["EPSG","4274"]],

   PROJECTION["Transverse Mercator", AUTHORITY["EPSG","9807"]],

   PARAMETER["central_meridian", -8.131906111111114],

   PARAMETER["latitude_of_origin", 39.666666666666664],

   PARAMETER["scale_factor", 1.0],

   PARAMETER["false_easting", 180.598],

   PARAMETER["false_northing", -86.99],

   UNIT["m", 1.0],

   AXIS["Easting", EAST],

   AXIS["Northing", NORTH],

   AUTHORITY["EPSG","27492"]]

Once you've declared the proper EPSG code, make Geoserver compute

the lat/lon bouding box (it'll compute the bbox in your reference

system, and then convert it to lat/lon).

Hope this helps

Cheers

Andrea

image001.jpg

image002.jpg

9

My dataset it's in oracle spatial....and SRID it's defined like 27492.

-----Original Message-----
From: Andrea Aime [mailto:aaime@anonymised.com]
Sent: terça-feira, 23 de Janeiro de 2007 11:17
To: Diogo Vieira
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Geoserver BoundingBox

Diogo Vieira ha scritto:

But the epsg code 27492 is a system of coordinated that's declared in
Lat/Long, and my dataset use the same system of coordinated but is

declared

in X/Y. The system of coordinated it's the same, but is declared in
different ways, you understand me? The same system of coordinated can be
declare in Lat/Long, in X/Y or in Eastings/Northings.

A projected system like 27492 is _never_ lat/lon, usually it's meters,
and you can see that by the UNIT["m", 1.0] declaration.

So, when I load my dataset in geoserver and I make Geoserver compute the
lat/long bouding box, the values of bounding box in lat/long it's could be
correct in Lat/Long, but because my dataset it's in X/Y, the min and max
values not encloses my dataset and I can't see nothing.
What can I do?

Oh hum, have you declared 27492 in your feature type configuration
_before_ asking geoserver to compute the bounding box?
Is your dataset a shapefile? Is the WKT you provided me declared
in the .prj file?

Cheers
Andrea

10

My dataset is in Oracle spatial with SRID = 27492.

Here’s an example of my geoserver configuration:

1º SRS=27492 (bounding box not encloses my dataset)

This configuration generates an image blank. What is wrong? I need define another SRS?

2º SRS=4326 (bounding box encloses my dataset)

Thanks,

Diogo

11

Diogo Vieira ha scritto:

But the epsg code 27492 is a system of coordinated that's declared in Lat/Long, and my dataset use the same system of coordinated but is declared in X/Y. The system of coordinated it's the same, but is declared in different ways, you understand me? The same system of coordinated can be declare in Lat/Long, in X/Y or in Eastings/Northings.

I think we're going in circles and not understanding each other...
Ok, deep breath and let's start again.

The EPSG code 27492 is declared as a projected system. Even from the screenshot you've sent me, you can see that it's declared as a projected
system on top of a geographic one, which is obviously defined as lat/lon (well, it may be lon/lat, but that's a different issue).
If you look at the end of the wkt, you can see that the axis of the
projected system are Northing/Easting.
I really never seen in the wild something using X/Y (besides pure cartesian data coming from CAD systems), is this something Oracle specific?

So, when I load my dataset in geoserver and I make Geoserver compute the lat/long bouding box, the values of bounding box in lat/long it's could be correct in Lat/Long, but because my dataset it's in X/Y, the min and max values not encloses my dataset and I can't see nothing.

First thing, I'd check it's axis order. Are you using Geoserver 1.5.x beta? If so, make sure your web container is started with the:
-Dorg.geotools.referencing.forceXY=true
which makes it use lon/lat orientation (easting/northing, x/y) instead
of lat/lon as declared in the EPSG database.
(Geoserver 1.4 should not suffer from this issue since it's using
another CRS provider).

Second thing is, what are you doing to preview your data?
Do you see any errors in the console?

Cheers
Andrea

12

First thing, I'd check it's axis order. Are you using Geoserver 1.5.x
beta? If so, make sure your web container is started with the:
-Dorg.geotools.referencing.forceXY=true
which makes it use lon/lat orientation (easting/northing, x/y) instead
of lat/lon as declared in the EPSG database.
(Geoserver 1.4 should not suffer from this issue since it's using
another CRS provider).

Second thing is, what are you doing to preview your data?

Diogo, can you paste the request you are making for viewing your data?

Alex

13

I use Geoserver 1.5.x beta 1, and I set
  -Xms256M -Xmx512M -Dorg.geotools.referencing.forceXY=true
First, I repaired that I have an error when I start my Geoserver:

org.geotools.referencing.factory.epsg.HSQLDataSource
23/Jan/2007 15:43:18 null createBackingStore
WARNING: Failed to bind a "jdbc/EPSG" entry.
javax.naming.NameNotFoundException: Name jdbc is not bound in this Context
  at org.apache.naming.NamingContext.bind(NamingContext.java:842)
  at org.apache.naming.NamingContext.bind(NamingContext.java:170)
  at org.apache.naming.NamingContext.bind(NamingContext.java:186)
  at org.apache.naming.SelectorContext.bind(SelectorContext.java:170)
  at javax.naming.InitialContext.bind(InitialContext.java:355)
  at
org.geotools.referencing.factory.epsg.DefaultFactory.createFactory(DefaultFa
ctory.java:316)
  at
org.geotools.referencing.factory.epsg.DefaultFactory.createBackingStore(Defa
ultFactory.java:354)
  at
org.geotools.referencing.factory.DeferredAuthorityFactory.getBackingStore(De
ferredAuthorityFactory.java:136)
  at
org.geotools.referencing.factory.BufferedAuthorityFactory.isAvailable(
(...)

So, the database HSQL is not recognized and it's probably the cause of my
problem, no??
What I need to do for geoserver to recognize the database?

Diogo

-----Original Message-----
From: Andrea Aime [mailto:aaime@anonymised.com]
Sent: terça-feira, 23 de Janeiro de 2007 13:47
To: Diogo Vieira
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Geoserver BoundingBox

Diogo Vieira ha scritto:

But the epsg code 27492 is a system of coordinated that's declared in
Lat/Long, and my dataset use the same system of coordinated but is
declared in X/Y. The system of coordinated it's the same, but is
declared in different ways, you understand me? The same system of
coordinated can be declare in Lat/Long, in X/Y or in Eastings/Northings.

I think we're going in circles and not understanding each other...
Ok, deep breath and let's start again.

The EPSG code 27492 is declared as a projected system. Even from the
screenshot you've sent me, you can see that it's declared as a projected
system on top of a geographic one, which is obviously defined as lat/lon
(well, it may be lon/lat, but that's a different issue).
If you look at the end of the wkt, you can see that the axis of the
projected system are Northing/Easting.
I really never seen in the wild something using X/Y (besides pure
cartesian data coming from CAD systems), is this something Oracle specific?

So, when I load my dataset in geoserver and I make Geoserver compute the
lat/long bouding box, the values of bounding box in lat/long it's could
be correct in Lat/Long, but because my dataset it's in X/Y, the min and
max values not encloses my dataset and I can't see nothing.

First thing, I'd check it's axis order. Are you using Geoserver 1.5.x
beta? If so, make sure your web container is started with the:
-Dorg.geotools.referencing.forceXY=true
which makes it use lon/lat orientation (easting/northing, x/y) instead
of lat/lon as declared in the EPSG database.
(Geoserver 1.4 should not suffer from this issue since it's using
another CRS provider).

Second thing is, what are you doing to preview your data?
Do you see any errors in the console?

Cheers
Andrea

14

URL:

http://localhost:8888/geoserver/wms?bbox=39,-8.7,42,-8&request=GetMap&layers
=topp:FORUM_LATLONG&width=800&height=400&srs=EPSG:27492&styles=point&Format=
image/png

My dataset is one point with coordinates X=-8,3903 Y=40,3828 in oracle
spatial.

-----Original Message-----
From: Alexander Petkov [mailto:greenkov@anonymised.com]
Sent: terça-feira, 23 de Janeiro de 2007 15:28
To: Andrea Aime
Cc: Diogo Vieira; geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Geoserver BoundingBox

First thing, I'd check it's axis order. Are you using Geoserver 1.5.x
beta? If so, make sure your web container is started with the:
-Dorg.geotools.referencing.forceXY=true
which makes it use lon/lat orientation (easting/northing, x/y) instead
of lat/lon as declared in the EPSG database.
(Geoserver 1.4 should not suffer from this issue since it's using
another CRS provider).

Second thing is, what are you doing to preview your data?

Diogo, can you paste the request you are making for viewing your data?

Alex

15

So, the database HSQL is not recognized and it's probably the cause of my
problem, no??
What I need to do for geoserver to recognize the database?

1) You do get a SRS list in localhost:8080/geoserver/srsHelp.do
correct? If, so, it is recognizing the database.

2) Can you paste the request you are making for viewing your data?

Alex

16

On 1/23/07, Diogo Vieira <dvieira@anonymised.com> wrote:

URL:

http://localhost:8888/geoserver/wms?bbox=39,-8.7,42,-8&request=GetMap&layers
=topp:FORUM_LATLONG&width=800&height=400&srs=EPSG:27492&styles=point&Format=
image/png

My dataset is one point with coordinates X=-8,3903 Y=40,3828 in oracle
spatial.

Common error is to specify a BBOX in units different than the units
for the SRS you are targeting. Specify your bbox in meters, since
EPSG:27492 is in meters.

Alex

17

So, the database HSQL is not recognized and it's probably the cause of my
problem, no??
What I need to do for geoserver to recognize the database?

1) You do get a SRS list in localhost:8080/geoserver/srsHelp.do
correct? If, so, it is recognizing the database.

Yes, I get a SRS list...so, why it appears this error? (Failed to bind a
"jdbc/EPSG" entry)

2) Can you paste the request you are making for viewing your data?

When I type url:
  
http://localhost:8888/geoserver/wms?bbox=39,-8.7,42,-8&request=GetMap&layers
=topp:FORUM_LATLONG&width=800&height=400&srs=EPSG:27492&styles=point&Format=
image/png

,give-me this error:
  org.geotools.feature.DefaultFeatureTypeFactory
7641 [WARNING] org.geotools.data.oracle.OracleDataStore - Could not map
SRID 27492 to CRS:java.io.IOException: Unabled to parse WKTEXT into a
CRS:PROJCS["Datum 73 / Modified Portuguese Grid", GEOGCS [ "Datum 73", DATUM
["Datum 73 (EPSG ID 6274)", SPHEROID ["International 1924 (EPSG ID 7022)",
6378388, 297], -231, 102.6, 29.8, .6149999999999993660366746131394108039579,
-.1979999999999997958947342656936639661522,
.8809999999999990918346509498793836069706, .99999821], PRIMEM [ "Greenwich",
0.000000 ], UNIT ["Decimal Degree", 0.01745329251994328]], PROJECTION
["Modified Portuguese Grid (EPSG OP 19974)"], PARAMETER
["Latitude_Of_Origin", 39.66666666666666666666666666666666666667], PARAMETER
["Central_Meridian", -8.13190611111111111111111111111111111111], PARAMETER
["Scale_Factor", 1], PARAMETER ["False_Easting", 180.598], PARAMETER
["False_Northing", -86.99], UNIT ["Meter", 1]]
  

18

My dataset is one point with coordinates X= -43584.6807 Y= 107207.047 in SRS
= 27492, stored in oracle spatial.

When I load my data in geoserver I get this:

For view my data, I send the request:

http://localhost:8888/geoserver/wms?bbox=-43585,107207,-43583,107208&request
=GetMap&layers=topp:FORUM_LATLONG&width=800&height=400&srs=EPSG:27492&styles
=point&Format=image/png

,and I get one image blank.

Note: in attached I send logs of geoserver.

Diogo

-----Original Message-----
From: Alexander Petkov [mailto:greenkov@anonymised.com]
Sent: terça-feira, 23 de Janeiro de 2007 16:06
To: Diogo Vieira
Cc: Andrea Aime; geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Geoserver BoundingBox

On 1/23/07, Diogo Vieira <dvieira@anonymised.com> wrote:

URL:

http://localhost:8888/geoserver/wms?bbox=39,-8.7,42,-8&request=GetMap&layers

=topp:FORUM_LATLONG&width=800&height=400&srs=EPSG:27492&styles=point&Format=

image/png

My dataset is one point with coordinates X=-8,3903 Y=40,3828 in oracle

spatial.

Common error is to specify a BBOX in units different than the units

for the SRS you are targeting. Specify your bbox in meters, since

EPSG:27492 is in meters.

Alex

image001.jpg

geoserver.log (294 KB)

19

Diogo Vieira ha scritto:

So, the database HSQL is not recognized and it's probably the cause of my
problem, no??
What I need to do for geoserver to recognize the database?

1) You do get a SRS list in localhost:8080/geoserver/srsHelp.do
correct? If, so, it is recognizing the database.

Yes, I get a SRS list...so, why it appears this error? (Failed to bind a
"jdbc/EPSG" entry)

It's just a warning, not an error. Something we would like to get rid
of, but not managed so far. You can safely ignore it.

2) Can you paste the request you are making for viewing your data?

When I type url:
  
http://localhost:8888/geoserver/wms?bbox=39,-8.7,42,-8&request=GetMap&layers
=topp:FORUM_LATLONG&width=800&height=400&srs=EPSG:27492&styles=point&Format=
image/png

,give-me this error: org.geotools.feature.DefaultFeatureTypeFactory
7641 [WARNING] org.geotools.data.oracle.OracleDataStore - Could not map
SRID 27492 to CRS:java.io.IOException: Unabled to parse WKTEXT into a
CRS:PROJCS["Datum 73 / Modified Portuguese Grid", GEOGCS [ "Datum 73", DATUM
["Datum 73 (EPSG ID 6274)", SPHEROID ["International 1924 (EPSG ID 7022)",
6378388, 297], -231, 102.6, 29.8, .6149999999999993660366746131394108039579,
-.1979999999999997958947342656936639661522,
.8809999999999990918346509498793836069706, .99999821], PRIMEM [ "Greenwich",
0.000000 ], UNIT ["Decimal Degree", 0.01745329251994328]], PROJECTION
["Modified Portuguese Grid (EPSG OP 19974)"], PARAMETER
["Latitude_Of_Origin", 39.66666666666666666666666666666666666667], PARAMETER
["Central_Meridian", -8.13190611111111111111111111111111111111], PARAMETER
["Scale_Factor", 1], PARAMETER ["False_Easting", 180.598], PARAMETER
["False_Northing", -86.99], UNIT ["Meter", 1]]

Ok, that's the real issue. But it seems you're not giving us the full stack trace. Don't you have other lines just like the hsql warning after
the text you've pasted?

Cheers
Andrea

20

Diogo Vieira ha scritto:

My dataset is one point with coordinates X= -43584.6807 Y= 107207.047 in SRS = 27492, stored in oracle spatial.

...

Note: in attached I send logs of geoserver.

I see in the logs you're using jdk 1.4.0. Pretty old, can't you use at
least 1.4.2_12? 1.5 is preferred thought (if you want better performance).

The error about the inability to parse the WKT is scarier, only now I
noticed the WKT that's coming from your database is malformed in a couple of ways:

PROJCS["Datum 73 / Modified Portuguese Grid", GEOGCS [ "Datum 73", DATUM ["Datum 73 (EPSG ID 6274)", SPHEROID ["International 1924 (EPSG ID 7022)", 6378388, 297], -231, 102.6, 29.8, .6149999999999993660366746131394108039579, -.1979999999999997958947342656936639661522, .8809999999999990918346509498793836069706, .99999821], PRIMEM [ "Greenwich", 0.000000 ], UNIT ["Decimal Degree", 0.01745329251994328]], PROJECTION ["Modified Portuguese Grid (EPSG OP 19974)"], PARAMETER ["Latitude_Of_Origin", 39.66666666666666666666666666666666666667], PARAMETER ["Central_Meridian", -8.13190611111111111111111111111111111111], PARAMETER ["Scale_Factor", 1], PARAMETER ["False_Easting", 180.598], PARAMETER ["False_Northing", -86.99], UNIT ["Meter", 1]]

After spheroid, there are a few numbers that should be the TOWGS84
parameter set. Plus, the projection is defined as
"Modified Portuguese Grid (EPSG OP 19974)" which is, again, wrong,
should be "Transverse Mercator".
Is this WKT shipped along with Oracle?

Geoserver should work even with this broken situation, but unfortunately
you're hitting the same error Fabio D'Ovidio found a couple of weeks ago, and that I still haven't managed to fix,
http://jira.codehaus.org/browse/GEOS-847 (the issue speaks about shapefiles, but your case is the same code-wise, the WKT is not
parseable and as a result the data store tells the renderer data has
no CRS information).

Fixing the WKT in your db should fix things for you
Cheers
Andrea