Hi there,
Some freshly loaded caches in the Netherlands get an elevation of about 255 meter after database>update elevation where they should be about 0m. The seems to be correct after a force elevation refresh
Steps to reproduce:
- delete elevation.db3 (just in case)
- database new <any name>
- API download (full) of these caches: GC20NHT,GC2N6CY,GC36BF0,GC1K32J,GC1FH8X (these are examples, list can be longer, I guess about 1% of the caches in the Netherlands)
After the download the elevation for these 5 caches are now 0,0 meter, resolution is still empty
- database > update elevation (button always is selected)
GSAK now downloads and updates the previously deleted elevation.db3. Thereafter: 1 cache now has elevation 0,0m the four others are 254 or 255 meter (resolution is now 30m or 90m)
As these elevations are much higher then expected, I continue:
-force elevation refresh (one by one) now updates the elevation to 0,0m or -2,0m which is the more or less expected elevation value.
My question is, is this the to be expected behavior of the elevation system, or should the elevation already be correct after the 'update elevation'?
Nb: These caches are located in the Netherlands. Only a small part of this country is elevated above 250 meter, but most of it is much lower, even below sealevel sometimes, the 5 caches in this example are all well below 10 meter. Many more caches (>50) have the same thing happening..
GSAK 8.3.1.43, Win 7
Some freshly loaded caches in the Netherlands get an elevation of about 255 meter after database>update elevation where they should be about 0m. The seems to be correct after a force elevation refresh
Steps to reproduce:
- delete elevation.db3 (just in case)
- database new <any name>
- API download (full) of these caches: GC20NHT,GC2N6CY,GC36BF0,GC1K32J,GC1FH8X (these are examples, list can be longer, I guess about 1% of the caches in the Netherlands)
After the download the elevation for these 5 caches are now 0,0 meter, resolution is still empty
- database > update elevation (button always is selected)
GSAK now downloads and updates the previously deleted elevation.db3. Thereafter: 1 cache now has elevation 0,0m the four others are 254 or 255 meter (resolution is now 30m or 90m)
As these elevations are much higher then expected, I continue:
-force elevation refresh (one by one) now updates the elevation to 0,0m or -2,0m which is the more or less expected elevation value.
My question is, is this the to be expected behavior of the elevation system, or should the elevation already be correct after the 'update elevation'?
Nb: These caches are located in the Netherlands. Only a small part of this country is elevated above 250 meter, but most of it is much lower, even below sealevel sometimes, the 5 caches in this example are all well below 10 meter. Many more caches (>50) have the same thing happening..
GSAK 8.3.1.43, Win 7