| 1. | Feature | Added support of 5 Hz and 10 Hz GPS receivers. |
| 2. | Feature | New coordinates parser was implemented. More formats are now supported. A few bugs were fixed. To search a location by its coordinates enter latitude and longitude in the search field on the toolbar and press Enter. |
| 3. | Change | The Photo Viewer dialog was slightly redesigned. New Thumbnail Viewer dialog was implemented. Now you can view trip photos not only on the map. |
| 4. | Improvement | Now you can rotate photos in the Photo Geocoding dialog by pressing Alt + Ctrl + left (right) arrow. |
| 5. | Improvement | There are context menus in photo dialogs. To open the page of a photo in a browser, right click on it and choose Open photo page. |
| 6. | Change | Left click on the map does not display menu anymore. You should use right click for the context menu. |
| 7. | Change | The MapSphere user interface was updated according to Microsoft guidelines. |
| 8. | Improvement | MapSphere proposes to choose another destination folder if a track file could not be saved. |
| 9. | Fixed | The application crashed if a plugin DLL was not found. |
| 10. | Fixed | MapSphere exhausted the system resources if there was no internet connection. It crashed or hung after several hours. |
| 11. | Fixed | MapSphere could crash if a user attempted to log-in while there was no internet connection. |
| 12. | Fixed | If the search failed the corresponding message appeared only after 20 seconds timeout. Now it is displayed immediately. |
| 13. | Fixed | Some long GPRMC NMEA messages could be processed incorrectly. |
| 14. | Fixed | Sometimes a track file was not closed after open or save operations. The next operations with the file could fail. |
| 15. | Fixed | If the EXIF block of a photo contained the camera orientation value, the photo could be improperly rotated in some dialogs. |
| 16. | Fixed | GPS auto detection could be terminated incorrectly if it displayed a message box. |
| 17. | Change | Now a message is displayed if there were no points in a track. |
| 18. | Fixed | MapSphere crashed if a user attempted to open a GPX file larger than 100 MB. Now a warning message is displayed in this case. |
| 19. | Fixed | Ctrl + F combination did not invoke the Search toolbar panel if it was previously closed. |
| 20. | Fixed | Auto locate did not work in the Search Results dialog if the results were taken from cache. |
| 21. | Fixed | After the file was opened or saved its folder became blocked by the system. |
| 22. | Fixed | Measure tool line could be displayed incorrectly in 2D mode. |
| 23. | Fixed | A GPX file with multiple tracks was opened incorrectly. |
| 24. | Fixed | The track length and location were wrong if it contained invalid points. |
| 25. | Fixed | MapSphere crashed if the area download requested too much cells. Now there is a limitation of 300,000 cells to be downloaded at once. |
| 26. | Fixed | If track did not contain time information, a wrong value was displayed when inspecting track points on the map. |
| 27. | Fixed | The application could crash on exit if there was no internet connection. |
| 28. | Fixed | GPS EPE (Estimated Position Error) was displayed in wrong measurement units. The total time value was erroneously displayed with A.M. / P.M. markers. |
| 29. | Fixed | A comment to a photo could be lost when the timestamp of the photo was updated. |
| 30. | Fixed | There were several bugs in coordinates representation (lost minus sign, 60 for the minutes value). |
| 31. | Fixed | The application crashed if the Trip Photo dialog was closed while updating the trip cover. |
| 32. | Fixed | In some cases MapSphere created poor quality thumbnails. |
| 33. | Fixed | After pressing F1 key two identical browser pages could be displayed. In some other cases MapSphere reported that help file was not found. |
