[Geoserver-users] Geoserver v1.5.3 & 900913

Hi Guys,

I tested v1.5.2-rc1 and now v1.5.3 with 900913 (aka spherical mercator)… Unfortunately I can’t see 900913 aligning with google like it should. I tested this with OpenLayers and have a sucessful overlay already using mapserver.

Not sure what more info I can give, or how I can help out…

Andrew Hughes ha scritto:

Hi Guys,

I tested v1.5.2-rc1 and now v1.5.3 with 900913 (aka spherical mercator).... Unfortunately I can't see 900913 aligning with google like it should. I tested this with OpenLayers and have a sucessful overlay already using mapserver.

Andrew,
any chance you can give me a sample dataset and an image generated
with mapserver that has the correct alignment? Private mail would
be ok, I won't divulge the dataset.

Cheers
Andrea

I’m having similar problems as well. Geoserver now recognizes the 900913 projection when using the trunk version (from 8/13/07), but when I overlay my layers with Google, I’m getting a unexpected results. My layers are in NAD83. I did notice some warnings being reported by the server:

14 Aug 22:17:20 WARN [org.geotools] - Ambiguity between inverse flattening and semi minor axis length. Using inverse flattening.

I don’t know if this helps, but here is an example of the shift that I’m seeing:
GoogleMercator Point (lat/lon): 4738637.1308, -9402595.2850
Geoserver Point`` (lat/lon)`` : 4723196.8511, -9371065.0109

Andrea Aime wrote:

···
__________________________________
Jeremy Nix
Senior Application Developer
Southwest Financial Services, Ltd.
(513) 621-6699

Andrew Hughes ha scritto:
  
Hi Guys,

I tested v1.5.2-rc1 and now v1.5.3 with 900913 (aka spherical 
mercator)....  Unfortunately I can't see 900913 aligning with google 
like it should. I tested this with OpenLayers and have a sucessful 
overlay already using mapserver.
    

Andrew,
any chance you can give me a sample dataset and an image generated
with mapserver that has the correct alignment? Private mail would
be ok, I won't divulge the dataset.

Cheers
Andrea

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  [http://get.splunk.com/](http://get.splunk.com/)
_______________________________________________
Geoserver-users mailing list
[Geoserver-users@lists.sourceforge.net](mailto:Geoserver-users@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-users](https://lists.sourceforge.net/lists/listinfo/geoserver-users)
  

Jeremy Nix ha scritto:

I'm having similar problems as well. Geoserver now recognizes the 900913 projection when using the trunk version (from 8/13/07), but when I overlay my layers with Google, I'm getting a unexpected results. My layers are in NAD83. I did notice some warnings being reported by the server:

14 Aug 22:17:20 WARN [org.geotools] - Ambiguity between inverse flattening and semi minor axis length. Using inverse flattening.

I don't know if this helps, but here is an example of the shift that I'm seeing:
GoogleMercator Point (lat/lon): 4738637.1308, -9402595.2850
Geoserver Point (lat/lon) : 4723196.8511, -9371065.0109

Jeremy, more than a single point it would be useful to have a sample
dataset (by private mail).

Cheers
Andrea

Hi all, I am experiencing the same problem with whatever dataset that are not in EPSG:4326. It seems that geoserver (or openlayer) get lost with reprojection with googlemap projections
gersh

On 15/08/07, Andrea Aime <aaime@anonymised.com> wrote:

Jeremy Nix ha scritto:

I’m having similar problems as well. Geoserver now recognizes the
900913 projection when using the trunk version (from 8/13/07), but when
I overlay my layers with Google, I’m getting a unexpected results. My
layers are in NAD83. I did notice some warnings being reported by the
server:

14 Aug 22:17:20 WARN [org.geotools] - Ambiguity between inverse
flattening and semi minor axis length. Using inverse flattening.

I don’t know if this helps, but here is an example of the shift that I’m
seeing:
GoogleMercator Point (lat/lon): 4738637.1308, -9402595.2850
Geoserver Point (lat/lon) : 4723196.8511, -9371065.0109

Jeremy, more than a single point it would be useful to have a sample
dataset (by private mail).

Cheers
Andrea


This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

gershwinou ha scritto:

Hi all, I am experiencing the same problem with whatever dataset that are not in EPSG:4326. It seems that geoserver (or openlayer) get lost with reprojection with googlemap projections
gersh

Ok,
I've created a new nightly build which appears to fix Andrew and probably Jeremy issues. Can you all download it from
http://geo.openplans.org/nightly/1.5.x/ (grab the "latest" build),
test it against your data again, and report back?

Cheers
Andrea

btw, same problem appears on 1.6beta2

gersh

On 16/08/07, Andrea Aime <aaime@anonymised.com> wrote:

gershwinou ha scritto:

Hi all, I am experiencing the same problem with whatever dataset that
are not in EPSG:4326. It seems that geoserver (or openlayer) get lost
with reprojection with googlemap projections
gersh

Ok,
I’ve created a new nightly build which appears to fix Andrew and
probably Jeremy issues. Can you all download it from
http://geo.openplans.org/nightly/1.5.x/ (grab the “latest” build),
test it against your data again, and report back?

Cheers
Andrea

gershwinou ha scritto:

btw, same problem appears on 1.6beta2

Of course it does, beta2 is even older than 1.5.2.
I need to know if it still happens in the nightly I pointed out,
that's where I may have fixed it.

Cheers
Andrea

Ok, i tried, but i met another problem:
my projection is not in the proj list (ETRS89-LAEA which is strange since it is a european standard). Before i updated the epsg.properties. but in your snapshot, geoserver does not seem to find it. Is there a new way to add your own projection?

gersh

On 16/08/07, Andrea Aime <aaime@anonymised.com> wrote:

gershwinou ha scritto:

btw, same problem appears on 1.6beta2

Of course it does, beta2 is even older than 1.5.2.
I need to know if it still happens in the nightly I pointed out,
that’s where I may have fixed it.

Cheers
Andrea

Tried with other data, now the google map shows the data ok.
but still my question in my previeous mail (epsg.properties not taken in account?) is pending.

gersh

On 16/08/07, gershwinou < gershwinou@anonymised.com> wrote:

Ok, i tried, but i met another problem:
my projection is not in the proj list (ETRS89-LAEA which is strange since it is a european standard). Before i updated the epsg.properties. but in your snapshot, geoserver does not seem to find it. Is there a new way to add your own projection?

gersh

On 16/08/07, Andrea Aime < aaime@anonymised.com> wrote:

gershwinou ha scritto:

btw, same problem appears on 1.6beta2

Of course it does, beta2 is even older than 1.5.2.
I need to know if it still happens in the nightly I pointed out,
that’s where I may have fixed it.

Cheers
Andrea

gershwinou ha scritto:

Ok, i tried, but i met another problem:
my projection is not in the proj list (ETRS89-LAEA which is strange since it is a european standard). Before i updated the epsg.properties. but in your snapshot, geoserver does not seem to find it. Is there a new way to add your own projection?

No, the way is the same, modify the epsg.properties in the data dir,
then restart GeoServer (the provider won't notice the file
has been updated at runtime).
Just tried with my local version, I added 900914 (as a copy of 900913)
to the user_projections/epsg.properties and it's there in the SRS list after the restart...

Cheers
Andrea

gershwinou ha scritto:

Ok, i tried, but i met another problem:
my projection is not in the proj list (ETRS89-LAEA which is strange since it is a european standard). Before i updated the epsg.properties. but in your snapshot, geoserver does not seem to find it. Is there a new way to add your own projection?

Not for this one. Lambert Azimutal Equal Area projection is a projection
we don't have the math for in GeoServer 1.5.x..
The projection has been added in GeoTools, the library we depend on for
most of the work, in the fore coming 2.4.0 release, which is used
by GeoServer 1.6.0 series (still unreleased, that one too).

I just picked its definition from the GeoServer 1.6.x branch, here it is:

PROJCS["ETRS89 / ETRS-LAEA",
   GEOGCS["ETRS89",
     DATUM["European Terrestrial Reference System 1989",
       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","6258"]],
     PRIMEM["Greenwich", 0.0, AUTHORITY["EPSG","8901"]],
     UNIT["degree", 0.017453292519943295],
     AXIS["Geodetic longitude", EAST],
     AXIS["Geodetic latitude", NORTH],
     AUTHORITY["EPSG","4258"]],
   PROJECTION["Lambert Azimuthal Equal Area", AUTHORITY["EPSG","9820"]],
   PARAMETER["latitude_of_center", 52.0],
   PARAMETER["longitude_of_center", 10.0],
   PARAMETER["false_easting", 4321000.0],
   PARAMETER["false_northing", 3210000.0],
   UNIT["m", 1.0],
   AXIS["Easting", EAST],
   AXIS["Northing", NORTH],
   AUTHORITY["EPSG","3035"]]

So, if you need it, I advise you grab a GeoServer 1.6.x nightly (starting from today late afternoon, european time, since that
nightly still have to be generated and you need the same fix
that I put in 1.5.x):
http://geo.openplans.org/nightly/trunk/

Cheers
Andrea Aime

for me it doe not work. I tried 900914, and it says:

Could not find an SRS Authority that understands your SRS. Please verify that your SRS is correct - you might need to consult the SRS authority plug ins to ensure that your SRS is listed.
No code “EPSG:900914” from authority “European Petroleum Survey Group” found for object of type “CoordinateReferenceSystem”.
EPSG:900914

here the line i added in epsg.properties:

900914=PROJCS[“ETRS89 / ETRS-LAEA”,GEOGCS[“ETRS89”,DATUM[“European Terrestrial Reference System 1989”,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”,“6258”]],PRIMEM[“Greenwich”, 0.0,AUTHORITY[“EPSG”,“8901”]],UNIT[“degree”, 0.017453292519943295],AXIS[“Geodetic longitude”, EAST],AXIS[“Geodetic latitude”, NORTH],AUTHORITY[“EPSG”,“4258”]],PROJECTION[“Lambert Azimuthal Equal Area”, AUTHORITY[“EPSG”,“9820”]],PARAMETER[“latitude_of_center”, 52.0],PARAMETER[“longitude_of_center”, 10.0],PARAMETER[“false_easting”, 4321000.0],PARAMETER[“false_northing”, 3210000.0],UNIT[“m”, 1.0],AXIS[“Easting”, EAST],AXIS[“Northing”, NORTH],AUTHORITY[“EPSG”,“3035”]]

any idea. It seems that is checking another file, or forget to check it.

gersh

On 16/08/07, Andrea Aime < aaime@anonymised.com> wrote:

gershwinou ha scritto:

Ok, i tried, but i met another problem:
my projection is not in the proj list (ETRS89-LAEA which is strange
since it is a european standard). Before i updated the epsg.properties.
but in your snapshot, geoserver does not seem to find it. Is there a new
way to add your own projection?

Not for this one. Lambert Azimutal Equal Area projection is a projection
we don’t have the math for in GeoServer 1.5.x…
The projection has been added in GeoTools, the library we depend on for
most of the work, in the fore coming 2.4.0 release, which is used
by GeoServer 1.6.0 series (still unreleased, that one too).

I just picked its definition from the GeoServer 1.6.x branch, here it is:

PROJCS[“ETRS89 / ETRS-LAEA”,
GEOGCS[“ETRS89”,
DATUM[“European Terrestrial Reference System 1989”,
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”,“6258”]],
PRIMEM[“Greenwich”, 0.0, AUTHORITY[“EPSG”,“8901”]],
UNIT[“degree”, 0.017453292519943295],
AXIS[“Geodetic longitude”, EAST],
AXIS[“Geodetic latitude”, NORTH],
AUTHORITY[“EPSG”,“4258”]],
PROJECTION[“Lambert Azimuthal Equal Area”, AUTHORITY[“EPSG”,“9820”]],
PARAMETER[“latitude_of_center”, 52.0],
PARAMETER[“longitude_of_center”, 10.0],
PARAMETER[“false_easting”, 4321000.0],
PARAMETER[“false_northing”, 3210000.0],
UNIT[“m”, 1.0],
AXIS[“Easting”, EAST],
AXIS[“Northing”, NORTH],
AUTHORITY[“EPSG”,“3035”]]

So, if you need it, I advise you grab a GeoServer 1.6.x nightly
(starting from today late afternoon, european time, since that
nightly still have to be generated and you need the same fix
that I put in 1.5.x):
http://geo.openplans.org/nightly/trunk/

Cheers
Andrea Aime

gershwinou ha scritto:

for me it doe not work. I tried 900914, and it says:

    Could not find an SRS Authority that understands your SRS. Please
    verify that your SRS is correct - you might need to consult the SRS
    authority plug ins to ensure that your SRS is listed.
    No code "EPSG:900914" from authority "European Petroleum Survey
    Group" found for object of type "CoordinateReferenceSystem".
    EPSG:900914

Tried means doing a GetMap? What if you list the SRS known by GeoServer?
(http://localhost:8080/geoserver/srsHelp.do, and be patient, the list
is very long and the everything in a single page very dumb...)

here the line i added in epsg.properties:

    900914=PROJCS["ETRS89 / ETRS-LAEA",GEOGCS["ETRS89",DATUM["European
    Terrestrial Reference System 1989",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","6258"]],PRIMEM["Greenwich",
    0.0,AUTHORITY["EPSG","8901"]],UNIT["degree",
    0.017453292519943295],AXIS["Geodetic longitude",
    EAST],AXIS["Geodetic latitude",
    NORTH],AUTHORITY["EPSG","4258"]],PROJECTION["Lambert Azimuthal Equal
    Area", AUTHORITY["EPSG","9820"]],PARAMETER["latitude_of_center",
    52.0],PARAMETER["longitude_of_center",
    10.0],PARAMETER["false_easting",
    4321000.0],PARAMETER["false_northing", 3210000.0],UNIT["m",
    1.0],AXIS["Easting", EAST],AXIS["Northing",
    NORTH],AUTHORITY["EPSG","3035"]]

I hope this is all in one line, right? Otherwise it won't work.
May it be that you're modifying the wrong Geoserver data directory?
During GeoServer startup there is a log stating the current data dir,
on my pc I read:

2007-08-16 16:40:37.312:/geoserver:INFO: Loading Spring root WebApplicationContext
----------------------------------
- GEOSERVER_DATA_DIR: C:\progetti\geoserver\src\1.5.x\configuration\release
----------------------------------

Cheers
Andrea

ok seems that 1.5.x cannot find a transformation for Lambert Azimuthal Equal Area
I downloaded the 1.6.x nightly builds and it works perfect

cheers,

Fix

On 16/08/07, Andrea Aime <aaime@anonymised.com> wrote:

gershwinou ha scritto:

for me it doe not work. I tried 900914, and it says:

Could not find an SRS Authority that understands your SRS. Please
verify that your SRS is correct - you might need to consult the SRS
authority plug ins to ensure that your SRS is listed.
No code “EPSG:900914” from authority “European Petroleum Survey
Group” found for object of type “CoordinateReferenceSystem”.
EPSG:900914

Tried means doing a GetMap? What if you list the SRS known by GeoServer?
(http://localhost:8080/geoserver/srsHelp.do, and be patient, the list
is very long and the everything in a single page very dumb…)

here the line i added in epsg.properties:

900914=PROJCS[“ETRS89 / ETRS-LAEA”,GEOGCS[“ETRS89”,DATUM[“European
Terrestrial Reference System 1989”,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”,“6258”]],PRIMEM[“Greenwich”,
0.0,AUTHORITY[“EPSG”,“8901”]],UNIT[“degree”,
0.017453292519943295],AXIS[“Geodetic longitude”,
EAST],AXIS[“Geodetic latitude”,
NORTH],AUTHORITY[“EPSG”,“4258”]],PROJECTION[“Lambert Azimuthal Equal
Area”, AUTHORITY[“EPSG”,“9820”]],PARAMETER[“latitude_of_center”,
52.0],PARAMETER[“longitude_of_center”,
10.0],PARAMETER[“false_easting”,
4321000.0],PARAMETER[“false_northing”, 3210000.0],UNIT[“m”,
1.0],AXIS[“Easting”, EAST],AXIS[“Northing”,
NORTH],AUTHORITY[“EPSG”,“3035”]]

I hope this is all in one line, right? Otherwise it won’t work.
May it be that you’re modifying the wrong Geoserver data directory?
During GeoServer startup there is a log stating the current data dir,
on my pc I read:

2007-08-16 16:40:37.312:/geoserver:INFO: Loading Spring root
WebApplicationContext

  • GEOSERVER_DATA_DIR: C:\progetti\geoserver\src\1.5.x\configuration\release

Cheers
Andrea