Quote:
|
The problem was with my locale. My decimal symbol was ",". When kismet was generating GPS coordinates they were something like this: 21,40080541, 41,99460001
|
hmm.. interesting. Most of the sample kismet files I used came from users all over the world.
I didn't notice any CSV using commas as decimal points for floating point numbers.
From what I could tell, all kismet CSVs used chr(59) semi-colon as a delimiter which should have no bearing on your problem.
I think your problem becomes an issue when knsgem converters your lat/long strings into numbers. Ex "14,34521" evaluates to the number 14 because knsgem doesn't recognize a comma as a legal decimal point.
Do your xml and gps files use the comma as a decimal point as well?
Side note. Knsgem only works with decimal degrees using a period as a decimal point.
Unless I get a lot of complaints I'll probably not fix. As a work around I'd suggest loading a copy of the CSV into a text editor and do a auto search for (commas) and replace with (periods).