Page 1 of 9

KNSGEM is now released!!

PostPosted: Fri Apr 07, 2006 10:29 am
by Scruge
If you like mapping the networks you've stumbled you might try Knsgem.

[SIZE="5"][color="Red"]KNSGEM 2[/color][/SIZE]


It processes your NS1, WiFiHopper and Kismet csv, xml and gps files into Google Earth kml files.

Current Version 2.001 03/22/09



[SIZE="1"][color="green"]Be sure to delete old .DBF files before upgrading[/color][/SIZE]

PostPosted: Fri Apr 07, 2006 10:42 am
by Dutch
Scruge wrote:If you like mapping the networks you've stumbled you might like to try Knsgem.

http://www.rjpi.com/knsgem.htm

It processes your NS1 and Kismet csv, xml and gps files into Google Earth kml files.

Great work Scruge.. Now go out and stumble, so you can upload to Wigle. It's been 3 months, you slacker ;)

Dutch

PostPosted: Fri Apr 07, 2006 11:14 am
by Scruge
[quote="Dutch"]Great work Scruge.. Now go out and stumble, so you can upload to Wigle. It's been 3 months, you slacker ]
Hey, I would've had it done sooner but you kept feeding me new ideas.:cool:

PostPosted: Fri Apr 07, 2006 11:15 am
by Dutch
Scruge wrote:Hey, I would've had it done sooner but you kept feeding me new ideas.:cool:

Riiiight.. Just blame it on the old guys...

Dutch

PostPosted: Fri Apr 07, 2006 11:20 am
by streaker69
Dutch wrote:Riiiight.. Just blame it on the old guys...

Dutch


I didn't see him mention Thorn.

PostPosted: Fri Apr 07, 2006 1:46 pm
by audit
Mirrored at http://www.personalwireless.org/tools/Knsgem

<start plug>
Click on the google ads to help pay for it.
</end plug>

PostPosted: Sat Apr 08, 2006 12:52 pm
by Scruge
Thanks Audit,

Found a couple of bugs this morning, I'm sure it won't be the last. Current version is 1.02a

Be advised, GE seems to start choking with upwards of 2-3 thousand nets within a single kml. You might consider breaking your logs down to smaller chunks. I'll see if I can't provide the capability within knsgem.

PostPosted: Sat Apr 08, 2006 3:30 pm
by Mark57
Good work. I'll download when I get back in town. Too many virgin nets out here begging to be discovered. :cool:

PostPosted: Sat Apr 08, 2006 4:07 pm
by Dutch
Mark57 wrote:Good work. I'll download when I get back in town. Too many virgin nets out here begging to be discovered. :cool:

Watch it... Using the "V"-word will ensure that you have to disclose your location to G8t...

Dutch

PostPosted: Sat Apr 08, 2006 4:20 pm
by Mark57
Dutch wrote:Watch it... Using the "V"-word will ensure that you have to disclose your location to G8t...

Dutch


LOL, they're not ahh . . . ummm, well "untouched" anymore.

PostPosted: Sat Apr 08, 2006 5:09 pm
by audit
Scruge wrote:Thanks Audit,

Found a couple of bugs this morning, I'm sure it won't be the last. Current version is 1.02a


Mirrors are updated. When you update it again, let us at over at personalwireless so we can update our mirrors.

PostPosted: Sat Apr 08, 2006 6:43 pm
by King_Ice_Flash
[quote="Dutch"]Great work Scruge.. Now go out and stumble, so you can upload to Wigle. It's been 3 months, you slacker ]
Just got a new indash LCD/Nav unit. Should have some new numbers and pics after I get Kismet and 0.13e working again. I accidently filled up the HD while recompiling and rebuilding the kernel RPM (FC5) working on the howto, so had to start over. :D

PostPosted: Mon Apr 17, 2006 2:43 pm
by gocenik
I lost days trying to figure why knsgem didn't work. I installed linux and kismet, the same.

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

PostPosted: Mon Apr 17, 2006 3:17 pm
by beakmyn
gocenik wrote:I lost days trying to figure why knsgem didn't work. I installed linux and kismet, the same.

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


That's a common issue when reading a CSV (Comma seperated variable) file. That bare spot on your forehead is for you the heal of your hand to strike against :D

PostPosted: Tue Apr 18, 2006 7:55 am
by Scruge
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).