NOTE: The galeon mailing list is no longer active. The list archives are made available for historical reasons.
Martin Daly wrote:
Sorry, I didn't explain myself very well. What I meant was, if the full extents of the coverage are in the range [0,180] and [0,90], then the client has no way of knowing what the origin is. That is, the client could detect longitudes > 180 and latitudes > 90 and deduce that the server is using the [0,360] and [0,180] ranges. But that hueristic breaks down for smaller extents. Like I said, the extents ranges should probably respect the CRS extents and origin. That way there is no guesswork involved. Just trusting the results might not be enough. For example, our client allows the user to clip the coverage request to the extents of the current view. We need the current view extents and the coverage extents to either be in the same domain, or to be able to know the domains. Regards,Martin
This reminds me of a question Ive been meaning to ask.Suppose the client asks for an area that is bigger than the actual data area. I assume that we should return the intersection?
What if the client asks for an area that doesnt intersect? Is that an illegal request? Do we return an empty file?
galeon archives: