Tomtom navigasyon cihazları için kayıt-analiz programı (Event_Logger)
Arkadaşlar Tomtom navigasyon cihazı kullanan kişiler için bir program hakkında bilgi vermek istiyorum.Cihazınızın yapabildiği ne kadar yol kaldı? ne kadar yol yaptım? şeklindeki bilgilendirmelerden durumu, viraja kaç ile girmişim? yükseklik ne kadarmış? A noktasından B noktasına kadar olan arada ne kadar ivmelenmişim? gibi detaylı bilgilendirmelere taşıyor.Tomtom cihazlarının linux işletim sistemi altında çalışması Event_Logger gibi açık kaynaklı programların geliştirmesi için zemin hazırlamaktadır.3.Parti yazılımlarla cihazınızdan daha fazla verim almanız hoş bir şans kanımca.Ancak bunu sağlayan Tomtom'un Linux işletim sistemini kullanması. http://www.linux.org.tr/ Tomtom için başka tür yazılımlar hakkında bilgiyide isteyenlerle paylaşabilirim.Event_Logger'ı kendi sitesindeki tanıtımını buraya yapıştırıyorum.
Event_Logger provides end-to-end management of itineraries from planning to reporting, fully integrated with Google Maps and TomTom; Event_Logger includes a tracking and logging Agent enhancing all all-in-one TomTom GPS devices. It can log TomTom events to Itinerary files that are managed by TomTom like native Itinerary files created through the ordinary user interface; besides, Event_Logger can produce standard GPX XML files where events are represented as waypoints and the whole route is logged through a sequence of track points obtained by querying TomTom GO for location information at short periodical intervals; the produced tracking will result bound to the roads through the assistance of both the TomTom GO mapping and the ASN feature (if active) in order to normalize tracking even without proper GPS reception; other than this default process to produce snapped-to-road GPX tracks, an additional option allows retrieving raw GPS data not intermediated by TomTom GO, useful for off-road tracking and also including altitude; Itinerary records and GPX waypoints take account of boot, resume, suspend events and optionally other information generated by manually tapping on the available (and extensible) logging menu icons. Other than generating Itinerary and GPX files, Event_Logger can create POIs (Points of Interest) for each event (or for a configurable subset).
The production and archiving of Itinerary and GPX tracks is completely automatic; no user intervention is needed to regularly split files upon new paths, save and catalogue them as well as store old information in compressed archives. The history of all travelled paths can be accessed by browsing the Itn directory of the SD card (or HD).
As the power button of TomTom GO is actually a suspend/resume button, any related pressure is logged by Event_Logger. Besides, Event_Logger automatically defines a new path each time the TomTom device is switched off and then switched on again after six minutes or more. If the docking station is connected to the vehicle ignition, the driver’s interaction with the vehicle will automatically raise ‘resume’ and ‘suspend’ events, caught by Event_Logger. This means that each ignition will automatically catalogue a new path (unless a short break is performed).
A boot happens when the user manages the USB, the SD Card as well as the reset hole on the unit’s bottom (the last action also resets the TomTom GO system clock); boot events are accounted by Event_Logger too.
All Itinerary records include date and time of each event occurrence as well as the associated duration data and possibly the current position, altitude, speed, course and address. Depending on Event_Logger configuration settings (e.g., snap-to-road/off-road) and on the NavCore version, GPX data can potentially deal with all parameters produced by the GPS device, including also number of used satellites, HDOP, PDOP, VDOP, magnetic variation (when available) and geoid separation (see related description).
A special selection activates a snapshot report displaying advanced statistics related to the current trip, also including slope computation. An additional panel included in Event_Logger provides an astronomical calendar in textual format where data depend on the current local time and position. Besides, switching between day and night colours of TomTom GO is automatically performed according to the elevation of the sun.
For instance, Event_Logger helps answering the following questions:
* What itinerary did I travel yesterday?
* When did I start driving this morning?
* How long did I take?
* Which is the current altitude and speed?
* How can I remind precise positions?
* When exactly I travelled there?
* Which is the altitude of this place?
* Which was the maximum uphill and downhill slope of my previous trip?
* Where is the moon now?
And so on.
The GPX files collected by Event_Logger allow performing any kind of post-processing, batch analysis, statistics and file conversion together with XSLT stylesheets or external applications (file converter, GIS, mapping and analysis tools running on PC or legacy systems).
An XSL file included with Event_Logger allows Internet Explorer to automatically transform each GPX file into an HTML interactive report with zoomable graphical map from Google Maps, including coloured tracks and fully clickable waypoints; the map provides advanced functionalities and is followed by detailed tables analyzing almost all data registered inside the GPX file, with computation of distance, speed, altitude and slope related to each fix, segment, trace or whole file. Each table can be easily imported to Excel. Besides, two delimiters can be easily set over the map in order to allow interactive trip analysis.
Event_Logger virtually supports any all-in-one GPS TomTom device and is designed to be independent from specific models (e.g., display size and geometry), firmware versions (including NavCore v7) and GPS device (SiRF Star II, SiRF Star III, SiRF Star III with QuickGPSfix and Global Locate's Hammerhead GPS units are all supported).
The subsequent chapters describe all these functionalities in detail.
Event_Logger today delivers the most comprehensive set of functionalities that complement TomTom and is a reference for independent tools on top of the TomTom firmware and of the NavCore application.
Differently from the majority of similar applications, Event_Logger also provides fully commented source code, allowing verification of the implementation quality and sharing the innovation; with its pervasive documentation including development guide, Event_Logger not only details functions and customisation aspects to users, but also is a common reference for independent developers. Great care was taken in preparing the whole documentation, constantly updated upon each release of new features.
Pioneering the methods to add software into the TomTom device, Event_Logger was the first to automatically intercept and log TomTom events like “switch on”, “switch off” and “boot”, exploiting them in a core functional process that is able to automatically split trips through the analysis of the switch off time; any derived process of Event_Logger is based on this automation; this provides great help to users which have not to remind to manually mark the beginning of a new trip. This method, which is innovative on a TomTom device, has been inspired from the behaviour of software odometers embedded in some vehicles.
Event_Logger perfectly harmonizes with TomTom, avoiding any redundant information already provided by the standard application and introducing a lot of additional trip based data to users; it was the first application to successfully interface NavCore through its “file transportation layer” without requiring the SDK platform; the result was the implementation of a free method which allows NavCore to display messages and to retrieve normalized fixes through the TomTom map assistance (the basis of the “snap-to-road” method). Event_Logger was also the first application exploiting the Itinerary management of TomTom, to allow user reading externally collected fixes through the NavCore function “Itinerary Planning”, introduced with NavCore 5.
Besides, Event_Logger first introduced GPS tracking and since the beginning adopted the GPX standard; it is also the only application providing both “snap-to-road” and “off-road” collection methods.
Event_Logger v9 introduced a Web Application called GmapToItn, which allows designing an itinerary through Google Maps, with no restrictions. Not only Google waypoints are fully managed, but also draggable directions and points of interest (POI) are allowed. After designing the whole itinerary with the standard Google Maps web application, including multiple subsequent destinations and dragged points on the paths to customize each route, the TomTom Itinerary data is produced by selecting a simple bookmark: a panel appears presenting the ITN report ready to be copied to a file on the TomTom device; besides, data can be further customized through an easy user interface providing appropriate configuration switches. POIs produced by Google local searches are presented as multiple destinations and every point or destination includes the related description. GmapToItn is compatible with virtually any Internet browser and does not require installation (just a bookmark is needed).
Transferring the data produced by GmapToItn to the TomTom device requires a very simple manual operation consisting in creating an ITN file (e.g., with notepad) and pasting the acquired data; alternatively, Event_Logger 9.0 provides a separate tool called SendTomTom, which allows transferring data to TomTom via Bluetooth with only the need to provide a file name (it requires that BTConsole is installed and running on TomTom; the application supports UNIX, Mac OS X, Linux and PC through Cygwin).
The GPX Browser (gpx.xsl), already available in previous Event_Logger versions to allow interactive track analysis, now introduces many enhancements including draggable direction markers, Street view overlays as well as Panoramio, Wikipedia and YouTube overlays, reverse geocoding (translating coordinates and map points into addresses), GPX 1.1 support (other than GPX 1.0), right key mouse options, complete integration with Google Earth and many bug fixes.
Other than the widely used GPX Browser, Event_Logger v9 introduces a new reporting tool called ITN Browser. It consists of a comprehensive web application that offers a new way to review travels through detailed analysis of more ITN files even within long timeframes. It can browse any ITN file as well as the enriched ones produced by Event_Logger, aggregating data from more files and organizing the produced report in a very descriptive and readable table. ITN Browser is not only linked with GmapToItn (the Google Maps plugin allowing generating the TomTom itinerary data) but is also extensively integrated with Google Maps, exploiting all geodecoding and direction capabilities offered by Google. For instance, ITN Browser allows to quickly identify which and how many destinations have been travelled for work in the previous month, together with the related distances, tour durations and stay times.
With the goal to allow smooth execution into the limited resources of embedded systems (CPU, RAM memory, SD memory), Event_Logger singularly implemented the functional process through scripting and the building blocks by extending an efficient interpreter with C functions; zsh was selected as the basis for the script interpreter, not only because much tinier and lighter than external perl or java portings, but also because it outperforms the system tools available inside the TomTom firmware; a considerable set of customizations have been applied to zsh in order to increase functionalities and in parallel to further reduce its executable size. Event_Logger also integrates the infoZIP archiver into an unmatched functional management process to classify and incrementally save data on the SD card. The result is an architecture that provides robust functionalities without introducing performance degradation.
Notice that it is mandatory to carefully read and accept the disclaimer of warranty and license conditions at the end of this document before downloading and using Event_Logger.
Orjinal metin : http://web.tiscali.it/macri/Event_Logger/
