With no Raster CS, Maestro returns default extents.

[tysonk]

It appears that unless a raster has a set coordinate system, the default extents are always assigned.

For example, In a GeoTIFF, a raster that has a defined coordinate system will be projected correctly and Maestro will report the correct extents of the raster. However, if the raster only has spatial information concerning the extents of the raster and no coordinate system, such as in a .TIF and .TFW scenario, Maestro will assign a default coordinate system, and the default extents to the raster:

<ExtentType>Static</ExtentType>

<Extent>

<LowerLeftCoordinate>

<X>-10000000</X> <Y>-10000000</Y>

</LowerLeftCoordinate> <UpperRightCoordinate>

<X>10000000</X> <Y>10000000</Y>

</UpperRightCoordinate>

</Extent>

Is this an issue with Maestro, or do you believe this is an issue with my dataset(s)? Sample data can be provided if needed.

As a side note gdalinfo.exe always reports the correct extents of the raster regardless of whether there is a coordinate system defined or not, and running the debugging options on GDAL while the dataconnections are being made reveals no obvious errors.

Mapguide Open Source version - 2.0.2 MapGuide Maestro Version - 1.0.9.29819

[crispinatime]

This is a duplicate of 740

I do agree this is a major issue though as at the moment all rasters based on flat files (all of our implementations) will build invalid "config.xml" files in Maestro - meaning all the great performance gains in MG2.1 will not be realised. We have our own World-To-Config to get around the issue but I can't redistribute that unfortunately.

See ​http://trac.osgeo.org/mapguide/ticket/740

[tysonk]

I have read Ticket #740 before I created this current ticket, but I wanted to make sure that the issue had been addressed as it seemed that the Masetro version was different in ticket 740 as opposed to my ticket.

Thank you very much for the quick response, and could I assume that the problem will be corrected in MG2.1?

Thanks again!