From: Mike O'Toole <pdops@sh...> - 2005-01-11 22:18:41
Thanks Ron I should have noticed that myself.
> You should look at the dbname option, which lets you specify any
> name you like
> for the PDB file:
> gpsbabel.exe -i gpx -f GSAK.gpx -o gpilots,dbname=Alberta3 -F
> (This applies to the other Palm formats, too, except for Nav
> Ron Parker
Worked as advertised.
From: Mike O'Toole <pdops@sh...> - 2005-01-11 23:18:46
> You can override that if you want:
> gpsbabel -i gpx -f GSAK.gpx -o gpilots,dbname=waldo.pdb -F
> will write foo.pdb with an internal named of "waldo.pdb" - completely
> unrelated to its name on the local filestore.
Yup thanks. Ron Parker showed me the error of my ways too.
> > Note that the path name is not appended if the output is
> directed to
> > the directory where GPSBabel is installed.
> The language purist in me (occupational hazard) suspects that's a
> falsestatement and you're meaning "the current directory" instead
> of "where
> GPSBabel is installed", right? As it stands, whatever is after
> the -F
> goes - and that has nothing to do with where GPSBabel is installed.
Hmmm? OK. I think we're saying the same thing. I ran this
gpsbabel.exe -i gpx -f GSAK.gpx -o gpilots -F Alberta.pdb
in the directory where babel's installed and no path was appended to the PDB name when viewed in GPilots
> I'm not busting chops, I just want to be sure I understand what you're
> saying. :-)
Robert Lipe wrote:
>>>goes - and that has nothing to do with where GPSBabel is installed.
>>Hmmm? OK. I think we're saying the same thing. I ran this
>>gpsbabel.exe -i gpx -f GSAK.gpx -o gpilots -F Alberta.pdb
>>in the directory where babel's installed and no path was appended to
>>the PDB name when viewed in GPilots
> No path was given in your -F options.
That was intentional. Prior to using the dbname= switch the only way I could eliminate
having the path appended to the database name was to have the output directed to the
directory where GPSBabel was installed. I think this was because no path name is specified
in this instance Babel has no path to append.
> Where GPSBabel is installed and where you write the output have nothing
> to do with each other.
> If my current directory is f:\blabhalah and GPSBabel is in my path
> and I run
> gpsbabel ... -F Alberta.pdb
> or if GPSBabel isn't in my path and I explictly path it
> c:\gpsbabel\gpsbabel ... -F Alberta.pdb
> the output file will be 'Alberta.pdb', it wasn't run from where GPSBabel
> is installed in either case, right?
Sorry I haven't fooled with paths since my DOS days and have no idea how to define one in
XP. I've been using cd\ and cd in my batch files to define the correct directory.
> I suspect this is the kind of hair splitting only an engineer would
> undertake, though and you're really saying the same thing just in a less
> precise way. :-)
> I don't have an opinion on how this SHOULD work, so I'll make it do
> whatever you tell me it should do. Should we be writing only the
> basename instead of the fullname there?
If by basename you mean the same as what's now defined by the "dbname=" statement yes. In
my example I only want to see Alberta.pdp not C:\....\Alberta.pdp
> And Ron's assertion might technically be true in the land of infinite
> OSes, but in reality there are only two pathname styles that matter.
> We just start at the end of the string and stop at either the first
> slash, backslash, or the first of the string and we're done.
I can't imagine a need for having the path appended to the database name.
> Yes, technically I can name a file "xx\yy" in UNIX, but the number
> of people doing such things and then caring about GPilotS interop
> can't be huge...
Sometimes I feel like I'm the only one ;-). I do appreciate the efforts of the babel heads
to these isolated "one of" requests.