Extent not changing in RasterConfigurationDocument

[gBecker]

When creating/updating a GDAL FeatureSource of type composite the bounding box of the valid area

<gml:validArea>

<gml:boundingBox>

<gml:pos>-10000000 -10000000</gml:pos>

<gml:pos>10000000 10000000</gml:pos>

</gml:boundingBox>

</gml:validArea>

does not reflect the extent of the raster files added to this featuresource. It always shows the initial boundingBox. The references of the raster files below the validArea-Tag are all correct.

I've tried via "Browse Folder" and also "Browse Aliased Folder". Doesn't make a difference.

This worked in Maestro 2.x

[jng]

Is this the extent of the default spatial context?

In Maestro 2.x was this the aggregate combined extent of all the added raster imagery?

[gBecker]

Replying to jng:

Is this the extent of the default spatial context?

In Maestro 2.x was this the aggregate combined extent of all the added raster imagery?

Yes, it is the aggregate combined extent of the added raster files

[jng]

Can you build from source? If so, give r5770 a go.

Note that if a default FDO extent [-10000000, 10000000] is encountered in one of the images, the calculated extent will most likely be the same.

[gBecker]

I've tested rr5770 but unfortunately the extent didn't change.

But I've recognised that in this version the extent of the selected rasterimages are not correct anymore and maybe because of that the creation of the combined extent fails.

The coordinates of a single rasterimages in r5770 is for example:

<Image frame="1" name="fnp_1000.tif">

<Bounds>

<MinX>3,46200000000034E+16</MinX> <MinY>5,54399999999966E+15</MinY> <MaxX>3,46300000000034E+16</MaxX> <MaxY>5,54499999999966E+15</MaxY>

</Bounds>

</Image>

but it has to be like this (Maestro 2.1.4):

<Image frame="1" name="fnp_1000.tif">

<Bounds>

<MinX>3462000.00000034</MinX> <MinY>5543999.99999966</MinY> <MaxX>3463000.00000034</MaxX> <MaxY>5544999.99999966</MaxY>

</Bounds>

</Image>

[jng]

Thanks for the heads up, this gives me more information to work with

[jng]

Give r5827 a shot. This fixes raster bounds being written with current locale settings.

For more reliability, try this in conjunction with the updated GDAL provider dll I attached for #740 which should correctly report extents of most raster images.

[gBecker]

Extent is created but not correct!

It's to late to do localization in GdalRasterItem.cs. I debugged the code and found out that you have to replace lines 302-305 in CompositeFileCtrl.cs with the following lines:

raster.MinX = Convert.ToDouble(scList.SpatialContext[0].Extent.LowerLeftCoordinate.X, System.Globalization.CultureInfo.InvariantCulture);
raster.MinY = Convert.ToDouble(scList.SpatialContext[0].Extent.LowerLeftCoordinate.Y, System.Globalization.CultureInfo.InvariantCulture);
raster.MaxX = Convert.ToDouble(scList.SpatialContext[0].Extent.UpperRightCoordinate.X, System.Globalization.CultureInfo.InvariantCulture);
raster.MaxY = Convert.ToDouble(scList.SpatialContext[0].Extent.UpperRightCoordinate.Y, System.Globalization.CultureInfo.InvariantCulture);

This fixes the issue.

BTW the updated GDAL Provider dll doesn't work for me (MGOS 2.2 final/64Bit). When trying to create a Raster-FeatureSource I get the message that the GdalProvider couldn't be loaded.

[jng]

Ok see if r5830 does the trick.

About the updated GDAL provider dll. The zip of updated dlls I attached to #740 were 32-bit only. If you're able to build FDO from source, I have already committed the GDAL provider changes for the 3.5 branch (​http://trac.osgeo.org/fdo/changeset/6067). Otherwise if I have time, I'll build and attach the 64-bit dlls to that ticket.

[gBecker]

Yes it does, thanks!

[jng]

Cool, I'll mark this as closed. Thanks for the assistance!