Hello,
I have a general question about the behavior of geoserver getMap requests. Could somebody describe the default behavior if the requested BBOX is not completely inside the CRS BBOX. For example the CRS is WGS 84 (EPSG:4326) and the requested bbox values are greater/lower than (-)90 degree for longitude.
Could you point me to the source where it’s handled? I guess the server doesn’t return an error and renders up to maximum of CRS/SRS bounding box. Could you confirm that?
Thanks a lot
Frank
Frank Gasdorf ha scritto:
Hello,
I have a general question about the behavior of geoserver getMap requests. Could somebody describe the default behavior if the requested BBOX is not completely inside the CRS BBOX. For example the CRS is WGS 84 (EPSG:4326) and the requested bbox values are greater/lower than (-)90 degree for longitude.
Could you point me to the source where it's handled? I guess the server doesn't return an error and renders up to maximum of CRS/SRS bounding box. Could you confirm that?
In GeoServer 2.0.x there is no general special treatment.
There are exceptions specific to geographic data in particular cases
though:
- oracle cannot handle queries against geographic data that go beyond
the -180,-90,180,90 limits, so we cut the bbox to that area
- on trunk where "advanced projection handling" is enabled by default
a bbox that spans the dateline will be duplicated on the other
side to grab that that sits in legit coordinates at the other
end of the dateline.
This is at least what I can remember by heart.
It would be easier to help if you asked direct questions (e.g., I
don't believe you're just curious, what's the problem you're
seeing?)
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Thanks Andrea,
It was just a general question. We use in addition to geoserver an other map server and it throws exceptions in this case. So I don’t see any problem with geoserver at all! And I like the handling of geoserver in this case, because if not, the clients (like udig or even geotools) have to do this, but they don’t.
Cheers, Frank
2010/6/23 Andrea Aime <aaime@anonymised.com…>
Frank Gasdorf ha scritto:
Hello,
I have a general question about the behavior of geoserver getMap requests. Could somebody describe the default behavior if the requested BBOX is not completely inside the CRS BBOX. For example the CRS is WGS 84 (EPSG:4326) and the requested bbox values are greater/lower than (-)90 degree for longitude.
Could you point me to the source where it’s handled? I guess the server doesn’t return an error and renders up to maximum of CRS/SRS bounding box. Could you confirm that?
In GeoServer 2.0.x there is no general special treatment.
There are exceptions specific to geographic data in particular cases
though:
- oracle cannot handle queries against geographic data that go beyond
the -180,-90,180,90 limits, so we cut the bbox to that area
- on trunk where “advanced projection handling” is enabled by default
a bbox that spans the dateline will be duplicated on the other
side to grab that that sits in legit coordinates at the other
end of the dateline.
This is at least what I can remember by heart.
It would be easier to help if you asked direct questions (e.g., I
don’t believe you’re just curious, what’s the problem you’re
seeing?)
Cheers
Andrea
–
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.