[Xastir-Dev] Administrative Notes

[Gerry Creager N5JXS]

I'd vote that, at this juncture, and WRT a code freeze, that problems 
with non-FGDC-compliant geotiffs is *not* a bug to resolve now.  If 
there's a general solution down the road, we'll find it.

gerry

Derrick J Brashear wrote:
>>All developers should consider this a time to finish up on anything that
>>you are currently working on and get it submitted.  Please refrain from
>>adding additional functionality to existing code.
>>
>>Users, please submit _any_ bugs to this list so that they can be
>>addressed.
> 
> 
> Is the issue that non-fgd geotiffs aren't properly rotated a bug?
> 
> I still don't understand how the code in maps.c is supposed to be working,
> and I assume that this will be dropped because no one else really
> understands what the right fix is, but this is what I've been using
> approximately forever.
> 
> Index: maps.c
> ===================================================================
> RCS file: /cvsroot/xastir/xastir/src/maps.c,v
> retrieving revision 1.110
> diff -u -r1.110 maps.c
> --- maps.c	3 Jul 2002 19:16:21 -0000	1.110
> +++ maps.c	4 Jul 2002 01:34:59 -0000
> @@ -6796,7 +6796,7 @@
>       */
>      if (!have_fgd)      // Not a USGS map or perhaps a newer spec
>      {
> -        crop_it = 0;        /* Do NOT crop this map image */
> +        crop_it = 1;        /* crop this map image */
> 
>          /*
>           * Snag and parse ImageDescription tag here.
> @@ -6893,12 +6893,41 @@
>          }
>          f_SE_x_bounding = (float)xxx;
>          f_SE_y_bounding = (float)yyy;
> +
> +        if (f_NW_y_bounding > 0) {
> +          yyy=((f_NW_y_bounding > f_NE_y_bounding) ? f_NE_y_bounding
> +               : f_NW_y_bounding);
> +          xxx=((f_SW_y_bounding < f_SE_y_bounding) ? f_SE_y_bounding
> +               : f_SW_y_bounding);
> +        } else {
> +          yyy=((f_NW_y_bounding < f_NE_y_bounding) ? f_NE_y_bounding
> +               : f_NW_y_bounding);
> +          xxx=((f_SW_y_bounding > f_SE_y_bounding) ? f_SE_y_bounding
> +               : f_SW_y_bounding);
> +        }
> +        f_north_bounding = (float)yyy;
> +        f_south_bounding = (float)xxx;
> +        if (f_NE_x_bounding > 0) {
> +          xxx=((f_NE_x_bounding < f_SE_x_bounding) ? f_SE_x_bounding
> +               : f_NE_x_bounding);
> +          yyy=((f_NW_x_bounding > f_SW_x_bounding) ? f_SW_x_bounding
> +               : f_NW_x_bounding);
> +        } else {
> +          xxx=((f_NE_x_bounding > f_SE_x_bounding) ? f_SE_x_bounding
> +               : f_NE_x_bounding);
> +          yyy=((f_NW_x_bounding < f_SW_x_bounding) ? f_SW_x_bounding
> +               : f_NW_x_bounding);
> +        }
> +        f_west_bounding = (float)yyy;
> +        f_east_bounding = (float)xxx;
>      }
> 
> +#if 0
>      // Handle special USGS geoTIFF case here.  We only have
>      // four boundaries because the edges are aligned with
>      // lat/long.
>      else    // have_fgd
> +#endif
>      {
>          f_NW_x_bounding = f_west_bounding;
>          f_NW_y_bounding = f_north_bounding;
> _______________________________________________
> Xastir-dev mailing list
> Xastir-dev at xastir.org
> http://krypton.hscs.virginia.edu/mailman/listinfo/xastir-dev

-- 
Gerry Creager -- gerry.creager at tamu.edu
Network Engineering -- AATLT, Texas A&M University	
Cell: 979.229.5301 Office: 979.458.4020 FAX: 979.847.8578
Page: 979.228.0173
Office: 903A Eller Bldg, TAMU, College Station, TX 77843