With the introduction of the Fenix layout and the legacy layout I decided to retire the thin layout - however I optimized the clas and clas legacy layout to work better on some older edge devices which before were used best with the thin layout. So I backported some important improvements to the old wide/clas layout and they are now included as wide legacy and clas legacy layout. While many people really like the new layouts introduced in July - others preferred the higher contrast of the old layout style. contourlines are 2 pixels wide instead of 1. Also due to the high DPI the Fenix layout now uses the widest lines I've ever used. For hiking it's great and much better than other smartwatches due to the great battery life - which could not be achieved with OLED display). they reflect sunlight much worse due to high DPI - with say 60% the resolution things would still be very sharp from normal viewing distance - but with better contrast (Still the Fenix 6x is really good for hiking - for mtbiking I think it is a backup only. I actually feel the problem is the pretty high DPI of the Fenix watches. So I had to really look for the poppiest of the 64 colors to get a nice rendering. Notice how the vivid the colors are on the screenshots - other Garmin GPS devices do not have such a huge difference in screenshot vs real life. Here are some pictures of the map with the new fenix layout - reflecting pretty accurately how the maps look in reality (the sunlight is already a bit low, with stronger sun contrast is better, in shadow contrast is worse - as normal for Garmin transreflective displays): Planning a route or a track on the Fenix is pretty cumbersome - but following a route/track downloaded from the net / created in Basecamp works very well now. Yes the map display on the Fenix cannot compete with dedicated devices - but with the optimized layout it works pretty well to not get lost. The resulting colours are a bit different from the other maps - and look horrible on Mac/Windows PCs - but work pretty well on the watch itself. I've listened to both user feedback and also got a Fenix 6x to work on it locally. This was rather complicated as the Fenix watches not only, only have 64 colours - but many of them are hard to distinguish while other colours are so low in contrast that they are hardly visible. I still recommend to only install 6-8GB of maps to a device for speed at boot and search functions (deactivating a map in the GPS device menu does not help with speed of boot or search) but bigger tiles are always a good thing.īesides countless bugfixes I also worked on a map layout compatible with the 64 colour display of the Fenix 5/6 watches. Devices with 4096 or higher possible tile limit should now be fine with map tiles averaging around 8-10MB (so 4096*8 > 32GB sd card limit of Garmin devices). This excessive writes became apparent with the introduction of the 10m contourlines, and the VeloMap buildings layer).Īlso I reworked the whole map creation to create bigger tiles so that you can install larger areas to your devices without suddenly missing an area without any notice because of hitting the 2048 or 4096 tile limit. I noticed that the map compilation was causing way too many writes to the NVME disks and had to optimize many steps and move things to ramdisk away from NVME in order to not prematurely destroy the NVME drives. I then decided to also upgrade the map compilation server and optimize a lot of processes (e.g. The broken fan on the PSU was really troublesome as the server provider did not find it first as the server would run just fine in rescue mode - but overheat quickly in real use then shut down. After a broken power supply fan caused the websites to be down for 20 hours in August I decided that I should, after 4.5 years migrate the website to a new server (server hardware is usually good for about 5 years of 24/7 use - then it should be replaced as failures are becoming likely). The past few months most of the work has been done on optimizing the map creation and on updating things on the website and website server. (Deutsch) Allgemeiner – Support auf Deutsch (members only).Quick Introduction ID-Editor, Josm and Potlach2.Send maps with Basecamp (Mapinstall) or Mapsource.Install Garmin Basecamp (and maybe Mapsource).How to install the Openmtbmaps – Windows.Send Maps to GPS with Mkgmap (Cross-Platform).Screenshots from the very first openmtbmap in 2009.Garmin Transalpin Review and Interesting News.Premium DEM Relief Shading Maps for Garmin GPS devices.Premium Windows/Linux – Velomap Downloads.Premium Gmapsupp.img – directly for Garmin GPS units.Windows/Linux – OpenMtbMap Map Download.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |