Userfound info not consistant????

[scruge]

Got any ideas why?

When I click on show "Only my networks" on the wigle query page I get a mix of "Yes" and "No" for the "USERFOUND" field. I notice this occurs with jigle and digle as well.

00:0c:41:f6:66:84 N
00:0c:41:d5:e4:ee Y
00:12:17:bf:6e:db N
00:0f:66:49:89:d4 N
00:13:10:e9:ec:4d Y
00:0c:41:b0:a8:50 N

[uhtu]

appears to be a case sensitivity issue in the display code.

[scruge]

What does case have to do with how the server reports the "userfound" data?

If I'm logged in and requesting via the "Query" page all Nets I discovered, shouldn't I expect all nets listed would have a "Y" in the "userfound" field.

Doesn't "USERFOUND" mean the same thing as "Nets I discovered" ????

[uhtu]

some of those nets are Scruge. some scruge. display issue.
good find! we'll see if we can work that into the next round of fixes.

[scruge]

btw, would this problem have anything to do with why I have a lot of "first seen" dates with 0000000000?
All my posted logs reflect a "first seen" date/time, but I don't understand why they aren't showing up in the wigle database.

This problem occurs with both "Discovered nets" and "Recorded nets".

[uhtu]

er, lacking any specifics: probably not.

[scruge]

Here's an example of output from Query page for just my nets.
The "Lastupdate" time matches my logs. But for some reason about 15K-20K of them report "00000000000" for first seen.

map it netid ssid comment name type freenet paynet firsttime flags wep trilat trilong dhcp lastupdt channel active bcninterval qos userfound
Get Map 00:12:7f:6a:eb:10 Vanilla ???? ? ? 0000-00-00 00:00:00 0031 Y 29.78450394 -95.62439728 ? 20051219164324 11 Y 100 0 Y
Get Map 00:14:bf:0b:fa:74 ? ? 0000-00-00 00:00:00 2021 Y 29.78401756 -95.51945496 ? 20051001212833 11 Y 100 0 Y
Get Map 00:0c:41:cc:00:4d camacho BSS ? ? 0000-00-00 00:00:00 0411 Y 29.76107788 -95.71095276 ? 20050929171627 6 Y 100 1 Y
Get Map 00:0d:72:d3:c8:89 2WIRE171 BSS ? ? 2005-07-04 04:14:33 0471 Y 30.01659584 -95.47058868 ? 20050831225914 6 Y 100 2 Y

[mark571]

I can give you 20,443 with "first seen" dates with 0000-00-00 00:00:00 in Oklahoma County, OK alone, among others. Just download the county with DiGLE and look at the list. Some are mine, some aren't. 20,443 out of 58,794 in that county are like that. If you need info from me, let me know.

PS, everyone have a great New Year!

[mark571]

er, lacking any specifics: probably not.

As to the issue of "first seen" dates being 0000-00-00 00:00:00, I've been doing some testing. Look at WiGLE transaction ID 20060214-00023. Any new networks I upload in NS1 native format have 0000-00-00 00:00:00 as the date first seen. New networks I upload from Kismet in CSV, XML, or GPS file formats are reflected correctly. Exporting the NS1 to text shows the date line
# $DateGMT: 2006-02-14 and time in GMT. Is the parser not reading the NS1 files correctly? Or is there something I'm doing wrong on my end. If you need something more I'll provide it.