[GRASSLIST:2419] Re: v.proj problems

[Ian Macmillan]

Hey all, thanks a ton for your responses.  It was most helpful.  Turns out I
finally just erased the old southern hemisphere utm location, and made a new
utm location (zone 19) in the northern hemisphere.  I imported everything into
the new location (r.in.gdal) and was able to use v.proj without any hitches. 
All my regions show up as negative north and south values, but that is ok with
me.  Things show where they are supposed to and everything!

Thanks again.
Ian


> GROUP = METADATA_FILE
> 		...
> 		SCENE_UL_CORNER_MAPX = 232531.500
> 		SCENE_UL_CORNER_MAPY = -3727258.500
> 		SCENE_UR_CORNER_MAPX = 415957.500 
> 		SCENE_UR_CORNER_MAPY = -3755644.500
> 		SCENE_LL_CORNER_MAPX = 194484.000
> 		SCENE_LL_CORNER_MAPY = -3906609.000
> 		SCENE_LR_CORNER_MAPX = 378223.500
> 		SCENE_LR_CORNER_MAPY = -3934966.500
> 		...
> 		GROUP = PROJECTION_PARAMETERS 
> 			...
> 			FALSE_NORTHING = 0      
> 			...
> 			MAP_PROJECTION = "UTM"
> 		END_GROUP = PROJECTION_PARAMETERS 
> 		GROUP = UTM_PARAMETERS 
> 			ZONE_NUMBER = +19
> 
> This indicates that it is using a northern-hemisphere UTM zone for
> southern-hemisphere data. Some software may cope with it, but I
> wouldn't rely upon it. In particular, "south: defined" will completely
> mess things up (the data *should* be using a southern-hemisphere zone,
> but it isn't).