Having trouble with the new geoconvert tool; Please Read

  • Hi Rodeo,

    Thanks for your response. I remember reading something like that - that the coordinates might be wrong. I did a small area to try and get the hang of it to start with - here is the TFW:


    0.00000715255737304688

    0

    0

    -0.00000536441802978516

    167.878081798553

    -44.6379393339157


    and TMC:

    <[list][region_list][]


    <[tmcolormap_region][element][0]

    <[uint32] [level] [9]>

    <[vector2_float64] [lonlat_min] [-44.63 167.87]>

    <[vector2_float64] [lonlat_max] [-44.71 167.98]>


    Does that help? Thanks again,

    Tim

  • Let's face it - what does min and max really mean? Poor naming convention!

    The following is correct for the Northern hemisphere. Why don't we use lonlat_NW and lonlat_SE which should be useful anywhere


    <[tmcolormap_region][element][0]

    <[uint32] [level] [11]>

    <[vector2_float64] [lonlat_min] [-122.33642578125 48.583345413208]> <<< NW

    <[vector2_float64] [lonlat_max] [-120.97526550293 47.6949977874756]> <<<SE

    >

  • Exactly.

    Moreover, as long as lonlat_min is NW corner and lonlat_max is SE corner, whatever the hemisphere, min and max work for W and E (i.e. W<E), but for N and S it's the opposite => N>S !

    This can be pretty much confusing. For that reason I ignore the min / max and think NW / SE instead.


    Cheers

    Antoine

    Config : i7 6900K - 20MB currently set at 4.00GHz, Cooling Noctua NH-U14S, Motherboard ASUS Rampage V Extreme U3.1, RAM HyperX Savage Black Edition 16GB DDR4 3000 MHz, Graphic Card Gigabyte GeForce GTX 1080 8GB, Power supply Corsair RM Series 850W, Windows 10 64 bit.