![]() Please contact me if such errors occur since I'd like to fix them as fast as possible. Some formats are too greedy and interpret all data even if they cannot understand them - Garmin's POI database format quite often presents garbage to the user. Some formats are too strict and reject files that were actually intended for them - this happens quite often with the XML-based formats such as GPX and KML. Which version of RouteConverter have you've been using (, 17:41) Stav Wrote: I know I have a java problem - it closes down RouteConverter, very annoying especially if route not saved, but I never had the. Then all the supported formats try to read the given file. That's the Google Maps Directions API claiming that RouteConverter sent 26 waypoints while the limit is 23 plus start and end. The file extension is taken as a first indicator which formats to read first. So I've made a feature out of it: RouteConverter automatically detects the format of an arbitrary file and reads the GPS data from the file. This robustness is not visible to the user but it costs a lot of effort in programming. In order not to crash it would have to apply a lot of checks and tests to validate the read data. If RouteConverter would stick to the file extension when reading files or rely on the user to choose the format that could lead to wrong results since RouteConverter would try to fill the internal data structures from the data found in the file. Multiple position lists within one file are supported for the following formats:Ī computer science principle when implementing robust programs is:īe lenient when reading data and strict when writing data. The sum of all ascends between its positions is 1427 meters, the sum of all descends between its positions is 1355 meters.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |