It's pretty obvious that there's some kind of a header and something that repeats every 16 bytes. The key trait of this class is a pattern of the repeat pops out when you just look at it the challenge is to find what's in the record. As an rough estimate, a developer can usually implement one of these formats (reverse engineering, implementation, testing) in about a day. Writers depend on the number of unknown pieces we find. 'this is a track taken in Mountain View, CA on the afternoon of August 9, 2010') and we know the size of each record, we can usually implement a a reader for these. They may be any of the above, but in a different datum. Sometimes they may use radians or semicircles instead of degrees. Sometimes they're integers with scales applied. Position is often stored as IEEE doubles, but may be big or little endian. Often a developer can figure out the length of the record and recognize the patterns. If you open the file in a binary editor or a hex dumper and you see a pattern or barber-pole effect which indicates that the file consists of fixed length records, it may be straight-forward to reverse-engineer it. Binary data that's easily recognizable.We have pretty good internal infrastructure for these, but a typical time to implement and test one of these is on the order of half a day. If you can read and explain everything in the file, but it's not really a something-separated format that can be represented by a GPSBabel style, it'll have to be done by a programmer. If you write a paragraph or two of explanation and send the resulting style definition to the GPSBabel list, we may add it to our next version, saving the next user of that program the effort. Long fields can be, allowable characters from the international glppys, such as Г€Г‰ГЉГ‹Д’Д–Д (an 'E' with five additional diactriticals).Д¬an it handles back to the year 16 and to the year 6039? These might be extreme sounding, but knowing the breaking point is always helpful It is worth some time to do some extras study to see how If the format is recognizable and trivial, a non-programmer can probably write a description for it with our style scheme in under an hour. If you can read and explain everything you see ('here's a longitude, there's a name, this is the altitude in meters, etc.'), it's probably pretty easy to add this format. Open a representative file in your favorite text editor such as TextEdit.app or Notepad. You can see which category your request falls into. In rough terms, most of our file formats fall into one of three categories. If you want something done badly enough and can't find volunteers to do it, contract programmers can often get it done. Reasonably sized, developers will implement things for you. Sometimes, if you ask nicely, and your request is Much of the development is done by people solving their own GPSBabel isn't developed by a company it's done by volunteers.

Generally, simpla and 'obvsious changes can be done and integrated Since our build system makes a snaphot every night, this is rarely a

Releae schedules can be harder to predict, but Once that's done, it'll be on board the cargo car awaiting the departureД¬ar of the next release. Work more like the rest of GPSBabel or to be better strutured internally. Have different skills, resources, and time) will need to integrate thatДЇeature into the main program, sometimes working together to make something Beyond that, additional programmers (that may As soon as programmer with the skill, resources,ДЄnd time implements it.

Gpsbabel faq