![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]() john smith wrote: How can there be better terrain resolution when the screen resolution is the same? The terrain database resolution is independant of the screen resolution. |
#2
|
|||
|
|||
![]()
In article . com,
"Mike Granby" wrote: john smith wrote: How can there be better terrain resolution when the screen resolution is the same? The terrain database resolution is independant of the screen resolution. To me, resolution means greater detail. What is your interpretation? |
#3
|
|||
|
|||
![]() john smith wrote: How can there be better terrain resolution when the screen resolution is the same? The terrain database resolution is independant of the screen resolution. To me, resolution means greater detail. What is your interpretation? The terrain data is stored at some specific resolution ie. there is a height recorded for each square of land N by N feet in size. These N x N squares will correspond to a variable number of pixels on the display, depending on the zoom level. At lower zooms, multiple squares will contribute to a single pixel; at higher zooms, a single square will show as multiple pixels. Go to the terrain page and you'll see a "blocky" appearance on a 396 at the normal close-in zoom levels used on that page. Increasing the terrain resolution allows you to get closer before you get the blocking. It also allow better decisions about possible terrain conflicts. |
#4
|
|||
|
|||
![]()
In article .com,
"Mike Granby" wrote: john smith wrote: How can there be better terrain resolution when the screen resolution is the same? The terrain database resolution is independant of the screen resolution. To me, resolution means greater detail. What is your interpretation? The terrain data is stored at some specific resolution ie. there is a height recorded for each square of land N by N feet in size. These N x N squares will correspond to a variable number of pixels on the display, depending on the zoom level. At lower zooms, multiple squares will contribute to a single pixel; at higher zooms, a single square will show as multiple pixels. Go to the terrain page and you'll see a "blocky" appearance on a 396 at the normal close-in zoom levels used on that page. Increasing the terrain resolution allows you to get closer before you get the blocking. It also allow better decisions about possible terrain conflicts. If I understand you correctly, the increase in terrain resolution comes from packing more data into memory (more information per pixel) and redefining the zoom access? |
#5
|
|||
|
|||
![]() The terrain data is stored at some specific resolution ie. there is a height recorded for each square of land N by N feet in size. good stuff snipped If I understand you correctly, the increase in terrain resolution comes from packing more data into memory (more information per pixel) and redefining the zoom access? "pixels" and "zooming" are concepts orthogonal to the database resolution, which is what is claimed to be improved. It has nothing to do with the resolution of the display screen. |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Garmin GpsMap 396 - Flight Test #2 | Mike Spera | Owning | 17 | July 9th 06 01:21 PM |
Amateur Review of the Garmin GPSMAP 296 GPS | Rhett | Piloting | 10 | March 23rd 05 01:16 AM |
Pirep: Garmin GPSMAP 296 versus 295. (very long) | Jon Woellhaf | Piloting | 12 | September 4th 04 11:55 PM |
Amateur Review of the Garmin GPSMAP 296 GPS | Rhett | Products | 10 | April 29th 04 06:57 AM |
Garmin 90 Database Updates Discontinued | Val Christian | Piloting | 14 | August 20th 03 09:32 PM |