AW: AW: AW: [mapguide-users] MrSID problem: RasterIO skipped foroddwindowor buffer size

[G.E.O.-Consulting / Hans Mörschell]

Hallo Frank,

thanks a lot for your information, it was really helpful.

Thanks and best regards, Hans



############################################################
#         G.E.O.-Consulting GmbH / Hans Mörschell          #
#                                                          #
# Heinrichstrasse 119/8  Tel: ++43 (0) 316 - 34 85 80 - 15 #
# A - 8010 Graz          Fax: ++43 (0) 316 - 34 85 80 - 4  #
#                                                          #
# Email: moerschell at geo.co.at   Inet: http://www.geo.co.at #
############################################################
 
 

-----Ursprüngliche Nachricht-----
Von: mapguide-users-bounces at lists.osgeo.org
[mailto:mapguide-users-bounces at lists.osgeo.org] Im Auftrag von Frank
Warmerdam
Gesendet: Mittwoch, 20. Juni 2007 17:00
An: MapGuide Users Mail List
Betreff: Re: AW: AW: [mapguide-users] MrSID problem: RasterIO skipped
foroddwindowor buffer size

G.E.O.-Consulting / Hans Mörschell wrote:
> Hallo Frank,
> 
> yes, my MapGuide mapextent is based on the world file because of other
> datasets in that coordinate system.
> 
> If GDAL uses the internal georeferencing is there a way to control this
> behaviour ????

Hans,

There is currently no mechanism to make GDAL use worldfiles in preference
to internal georeferencing in a .sid file within the MrSID driver.  If
you construct an XML config file to for the datasource you can override
the origin and pixel size information by editing the XML.  But I'm not
sure how end users are expected to construct such XML config files
currently.

You can also construct a "GDAL virtual xml file" which wraps another
dataset,
and can be used to alter metadata, georeferencing, etc.

With FWTools you might do something like the following:

   gdal_translate -of VRT your_big.sid your_big.vrt

edit your_big.vrt and change the origin in the <GeoTransform> element.

Then point your MapGuide/FDO datasource at your_big.vrt instead of at
your_big.sid.

If you are operating on whole directories, you will need to keep the .vrt
files in a seperate directory.  Make sure you create the .vrt's from the
start in this new directory so that the .xml file will have proper relative
paths to the .sid files.

Best regards,
-- 
---------------------------------------+------------------------------------
--
I set the clouds in motion - turn up   | Frank Warmerdam,
warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | President OSGeo, http://osgeo.org

_______________________________________________
mapguide-users mailing list
mapguide-users at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users