Rahkonen Jukka wrote:
3) well, I'm sure there are other methods.
How about trying to motivate some clever developer to create the option I
mentioned... Point 1) might give me possibilities for making an investment.
I fear this feature is not too much of general interest.
Jukka,
From a coding point of view this is not complicated. The function
msGetGDALGeoTransform() is used for all code needing a gdal geotransform and
it is trivial to make the GDALGetGeoTransform() call lower priority than
the world file or ows metadata. I'm just not sure I could justify this
as a change to make to the core mapserver software.
If you wanted to keep this as a local change in your own builds of mapserver
you can change that function around somewhat. Of course, this might
introduce a configuration management issues on your end in the long term.
I don't really need any financial motivation in this case. It's more of a
concern that we may be introducing too many quirky behaviors in the software.
If you *really* need it I could add an undocumented PROCESSING option that
can be set on a layer and that msGetGDALGeoTransform() would use to decide
on priority of checks.
Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, [EMAIL PROTECTED]
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | President OSGeo, http://osgeo.org
