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

GeoServer GeoServer User
1

-----Messaggio originale-----
Da: Andrea Aime [mailto:aaime@anonymised.com]
Inviato: lunedì 19 febbraio 2007 16.03
A: Fabio Da Soghe
Cc: 'geoserver-users@lists.sourceforge.net'; Alessio Fabiani
Oggetto: Re: [Geoserver-users] R: Problems with EPSG lookup

Fabio Da Soghe ha scritto:
> I understand, thank you for the explanation.
>
> That means I'm in a situation I don't know how to handle
properly. I
> have a tiff raster with a tfw file attached. The tfw, as
you probably
> know, hasn't CRS information, only information about the raster's
> position. So I thought I had to force a CRS because
Geoserver hasn't a
> secure way to guess it. Infact my raster is in EPSG:3003 CRS.

> Since Geoserver keeps forcing 4326 as CRS (pressing the lookup
> button), I think it is processing the raster in that CRS, as you
> stated, even if I force my correct SRID. Is it right?

Glab, I think it's right, maybe Alessio can confirm (I know
the reasoning works fine on the vector side, not sure about
the coverage one).
If your data has no CRS the coverage plugin should not report
4326. Guys, are we facing a bug? Image + tfw are still
painfully common around.

> If that is the case, I think it cannot process well my raster and
> infact I'm not able to get it displayed properly (it shows a white
> png, when I call it from the WMS interface).
>
> Have I to georeference my raster in WGS84 to go well? Or
maybe using
> geotiff (which, if I'm not wrong, does contain CRS information)?

Using a Geotiff will work, for sure.

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.

Now I'll try to convert that raster in 4326 and I'll keep you informed.

Thanks again,

Fabio

Cheers
Andrea

2

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.

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

3

I'm not sure, I will forward this onto the mapbuilder list.

Brent Owens
(The Open Planning Project)

Andrea Aime wrote:

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.

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