WiFiDB Alpha 0.16 Build 1

[pferland]

Just a minute, bear with me....

-Phil

[pferland]

OK so sorry about the long wait, had a few bugs pop up that i didn't expect. found them and the ones that i saw are now gone.
This Release has a lot of Fixes and additions. I spent the better part of last week and the weekend testing it out, running multiple installs/ upgrades / patches. Had Andrew take a crack at it also over the weekend, to do some testing on it. There are about 26 total major changes, and numerous small changes.

I have included a tools folder:
convert.exe[convert_vs1.php] is to convert txt files from vistumbler to VS1 files.
import.php is experimental, so use at your own risk, it is to do a batch import of multiple VS1 files (really it was for all the older txt files that I had and didnt want to use the web page and do them one by one.)
manufmac.exe [manufmac.php] is to generate a new manufactures.inc.php [for WiFiDB] and manufactures.ini [for vistumbler]

More details are in the read me file in the tools folder.

If you already have WiFiDB running, you can just extract the files on top of the existing install and continue on without any issues.

you can grab the tar or zip files over here at:
https://sourceforge.net/project/showfil ... _id=669476

or the SVN here :
http://vistumbler.svn.sourceforge.net/v ... athrev=263

Changes:

• 1. Started moving all HTML code outside PHP code.
  2. Fixed an error in the GPS conversion.
  3. Added a footer function to take over the "*THIS PAGE* has been last edited on..." at the end of all forms, to standardize it, seeing how it was on all forms anyway.
  4. Moved the "*THIS PAGE* was last modified on: YYYY-MMM-DD @ HH:MM:SS" to the bottom of the page in the bottom cell.
  5. Working on changing the layout of the AP fetch page.
  • 1.---------------------------------------
    Assosiated list
    |_> Signal history for that list
    |_> GPS points for that Signal
    ---------------------------------------
    2. Would like to have it so the GPS history is hide able via JavaScript or something.
    3. So far the changes are, all the previous separate functions (fetch gps, fetch associate list, and fetch signal) are all now one function (fetch ap).
    4. Unfortunately this is going to require a change in the backed. Previous databases will not be compatible with this update.
    5. Reason being, in the previous versions (0.14 & 0.15[all builds]) did not store the signal history row in the Users table.
    • 1. Old way ex 1,1-0,2-0,6-1,10-... / 0,6 : 0 is the update or new flag 1 = Updated AP 0 = New AP, the 6 is the AP ID number in the Database
      2. New way ex 1,6:1-0,2:2-0,6:3-1,10:1-... /
      0,6:2 ; 0 is the update or new flag 1 = Updated AP / 0 = New AP, the 6 is the Unique Access Point ID (UAPID) in the Database, and the 2 is the Signal History row number for the access point.)
  6. The users table holds all the list imports for each user.
  7. Fixed a bug when a search has no results, the page would output a PHP error, now it says "There where no results, please try again".
  8. Fixed an issue, where on install there would be an SQL error and fail to install.
  9. Added link to Last User on Index page.
  10. Cleaned up the tables on the new version page.
  11. Dates are now standardized as YYYY-MM-DD, to coincide with Vistumblers save file.
  12. Fixed up the List KML export, there is a link to the KML file now.
  13. Finished KML export for entire database.
  14. Added option for a black background on the Signal Graphs.
  15. Empty Imports are no longer allowed (should have been like that since the beginning). Also if there were any empty imports, they will not be printed out on the All Users page.
  16. Added some friendly informational links.
  17. Set the default values for function variables, in case one value is left out.
  18. Initial code for Export Newest AP to KML is written, not tested yet.
  19. Added Export Page at /opt/export.php, also a link on the left hand side.
  • 1. Have Export users list to KML, all APs for a user to KML, export all APs in the DB to KML, and export a single AP to KML.
    2. Going to add the same for export to VS1.
  20. The warning for the install folder still being available was not added into the installer. It now is, and also in the upgrader too.
  21. Made the Default App internal timezone, GMT+0(Zulu).
  • 1. Soon you will be able to make the viewing time as your local timezon.
    2. greenwichmeantime.com
    3. wikipedia -> Greenwich_Mean_Time
  22. GPS Update Issue has been resolved. Problem was PHP had an issue comparing the Time stamp from the DB and the VS1 file.
  • 1. Sample Before: N 0.00000-E 0.00000-2009-03-19-17:51:56 [lat-long-date-time]
    2. Sample After: 00000000000020090319175156 [latlongdatetime]
    • 1. The Sample strings are the lat, long, date, and time all crammed into one long string.
      2. Sample Before was how I was comparing the GPS before the fix.
      3. Sample After is how the comparison is done now.
      4. With all the non-numerical data removed, GPS comparisons are done correctly.
      5. Even when it had non-numerical data, but no time stamp the compare was successful, but we're not going to do that.
  23. Fixed an issue where if there where removed rows in the users table, the index page would have a problem retrieving the Title, and User name of the last import.
  24. Added Plotting of Signal history for an APs Import to KML.
  25. Altered the Chan Column in the Pointers table to be Integer not Varchar. This fixes the sorting issue where 10 would be before 1.
  26. Altered AP Fetch Page table layout.

And like always, please leave feedback if you have used this, I would like to know what people think, and what they would like to see.

-Phil

[pferland]

Even if you have not installed WiFiDB,
Please take a run through
http://www.randomintervals.com/wifidb/
And let me know what you would like to see, what you see is wrong or any bugs that you can create \ observe. The more eyes on it the better.

Thanks,

_Phil

[pferland]

Just noticed a bug, if you have run the GPS repair script and removed signal history that does not have any good GPS points or Signal history, an import of the data again will result in the Row number being one or more then what it is supposed to be. Example

Screen shot of users Import list

users_list.PNG (17.21 KiB) Viewed 9428 times

screen shot of AP with only one row, where in the users import list it says it has 3 rows of Signal

ap_fetch.PNG (20.57 KiB) Viewed 9428 times

This will result in failed exports of User Import lists, to KML, because when exporting to KML the GPS is taken from the Signal history for that Import. If it is pointing to a row that does not exist, the AP will not be plotted in the KML (no valid GPS Cords)

But if you have done a fresh install, you will not see this problem , only if you have done an upgrade.

Working on a fix, will post when it is finished and tested.

-Phil