[Geoserver-users] R: R: R: Problems with EPSG lookup

Fabio · February 19, 2007, 4:35pm

-----Messaggio originale-----
Da: geoserver-users-bounces@lists.sourceforge.net
[mailto:geoserver-users-bounces@lists.sourceforge.net] Per
conto di Andrea Aime
Inviato: lunedì 19 febbraio 2007 16.25
A: Fabio Da Soghe
Cc: Brent Owens; 'geoserver-users@lists.sourceforge.net'
Oggetto: Re: [Geoserver-users] R: R: Problems with EPSG lookup

Fabio Da Soghe ha scritto:

> Eheh, I was just posting a little update: I tried a geotiff (WGS84)
> and it worked perfectly.

> Another little note: the first time I tried the 3003 raster
(forcing
> the SRID), I opened the web publishing interface embedded
in Geoserver
> (MapBuilder) and it showed a popup saying "unsupported map
> projection: EPSG:3003", and the map was white empty.

This is MapBuilder, not geoserver. MapBuilder tries to show
you the lat/lon of your mouse pointer independent of the
projection you chose, so it has to reproject the coordinates
from the native CRS to 4326. It does this in javascript code,
and supports a limited set of projections. 3003 is not among them.

My mispelling: that was what I meant. I was only reporting that, not assuming a bug in Geoserver.

Anyway, I did some other digging around the tif+tfw case. In the wms capabilities document I found:

<Layer queryable="0">
  <Name>ddm:cascinanuova2</Name>
  <Title>cascinanuova2 is a A raster file accompanied by a spatial data file</Title>
  <Abstract>Generated from SettimoPrg</Abstract>
  <KeywordList>
    <Keyword>WCS</Keyword>
    <Keyword>SettimoPrg</Keyword>
    <Keyword>cascinanuova2</Keyword>
  </KeywordList>
  
  <SRS>EPSG:3003</SRS>
  <LatLonBoundingBox minx="1402796.7678433256" miny="5000064.879096299" maxx="1404032.8544883041" maxy="5000626.033560928"/>
  <BoundingBox SRS="EPSG:3003" minx="1402796.7678433256" miny="5000064.879096299" maxx="1404032.8544883041" maxy="5000626.033560928"/>
  <Style>
    <Name>raster</Name>
        [...]
  </Style>
  </Layer>

It really seems it ignores my hand-input CRS and keep using 4326 for its calculation: it reports the same original coordinates in the LatLonBoundingBox, as if it should not transform it.

I wanted to try with a geotiff with EPSG:3003 coded into it, but I'm not able to find an application capable to generate it: noone knows of that CRS! Damned Murphy's Law...

I have plenty of rasters to publish, and the only way I see by now is to convert all of them to 4326. Is there any hope to have Geoserver take my tif+tfw and listen to me about the CRS?

Cheers,

Fabio

Brent, this keeps on confusing users, that do think Geoserver
does not support 3003 (instead of MapBuilder). Is there a way
to make MapBuilder show native coordinates instead?

Cheers
Andrea

--------------------------------------------------------------
-----------
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

Andrea_Aime3 · February 19, 2007, 5:36pm

Fabio Da Soghe ha scritto:

It really seems it ignores my hand-input CRS and keep using 4326 for
its calculation: it reports the same original coordinates in the
LatLonBoundingBox, as if it should not transform it.

I wanted to try with a geotiff with EPSG:3003 coded into it, but I'm
not able to find an application capable to generate it: noone knows
of that CRS! Damned Murphy's Law...

You can use gdal_translate and, if it does not understand EPSG:3003,
you can try with the equivalent WKT, on a single line.

I have plenty of rasters to publish, and the only way I see by now is
to convert all of them to 4326. Is there any hope to have Geoserver
take my tif+tfw and listen to me about the CRS?

Hum, I think if you provide a .prj file with the same WKT as reported
by Geoserver for 3003 it should work fine. Oh, to be sure, put the whole
WKT in a single line, not nicely formatted as in the Geoserver output.

Let me know if this helps.

Cheers
Andrea

Alessio_Fabiani · February 19, 2007, 9:39pm

Is it possible to have some sample data?

On 2/19/07, Fabio Da Soghe <fabio.dasoghe@anonymised.com> wrote:

-----Messaggio originale-----
Da: geoserver-users-bounces@lists.sourceforge.net
[mailto:geoserver-users-bounces@lists.sourceforge.net] Per
conto di Andrea Aime
Inviato: lunedì 19 febbraio 2007 16.25
A: Fabio Da Soghe
Cc: Brent Owens; ‘geoserver-users@anonymised.comge.net’
Oggetto: Re: [Geoserver-users] R: R: Problems with EPSG lookup

Fabio Da Soghe ha scritto:

Eheh, I was just posting a little update: I tried a geotiff (WGS84)
and it worked perfectly.

Another little note: the first time I tried the 3003 raster
(forcing
the SRID), I opened the web publishing interface embedded
in Geoserver
(MapBuilder) and it showed a popup saying “unsupported map
projection: EPSG:3003”, and the map was white empty.

This is MapBuilder, not geoserver. MapBuilder tries to show
you the lat/lon of your mouse pointer independent of the
projection you chose, so it has to reproject the coordinates
from the native CRS to 4326. It does this in javascript code,
and supports a limited set of projections. 3003 is not among them.

My mispelling: that was what I meant. I was only reporting that, not assuming a bug in Geoserver.

Anyway, I did some other digging around the tif+tfw case. In the wms capabilities document I found:
ddm:cascinanuova2 cascinanuova2 is a A raster file accompanied by a spatial data file Generated from SettimoPrg WCS SettimoPrg cascinanuova2 EPSG:3003 raster [...]
It really seems it ignores my hand-input CRS and keep using 4326 for its calculation: it reports the same original coordinates in the LatLonBoundingBox, as if it should not transform it.

I wanted to try with a geotiff with EPSG:3003 coded into it, but I’m not able to find an application capable to generate it: noone knows of that CRS! Damned Murphy’s Law…

I have plenty of rasters to publish, and the only way I see by now is to convert all of them to 4326. Is there any hope to have Geoserver take my tif+tfw and listen to me about the CRS?

Cheers,

Fabio

Brent, this keeps on confusing users, that do think Geoserver
does not support 3003 (instead of MapBuilder). Is there a way
to make MapBuilder show native coordinates instead?

Cheers
Andrea

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

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

–

Eng. Alessio Fabiani
Vice President/CTO GeoSolutions

http://www.geo-solutions.it