Snevl Latitude Version 2

[stevea]

v2.7 Posted

The first message of this thread has been updated with v2.7 of Snevl Latitude. The only change in this version is to support the new subscription-based Web Service API for FollowMee. No other changes were made.

If you are upgrading from v2.6:

1. Only the main script (SnevlLatitude.vb) and the main web page (SnevlLatitude.aspx) have changed. No other files need to be copied over from the ZIP.
2. Before upgrading, disable the periodic event that runs SnevlLatitude.vb.
3. v2.7 will upgrade the schema of the database from v9 to v10. While this should go smoothly, I'd recommend making a backup of the database (Data/SnevlLatitude/SnevlLatitude.mdb) before doing the upgrade.
4. Copy over the two files mentioned in the first bullet.
5. Manually run the SnevlLatitude.vb script, via the now disabled event. Watch the Homeseer log. You should see messages that the database has been upgraded.
6. Now bring up the Snevl Latitude web page (SnevlLatitude.aspx) and click on the FollowMee tab. Follow the instructions on the bottom of the page to fill in the fields for the new API.
7. Re-enable the periodic event that runs SnevlLatitude.vb

If you have any issues or questions, post them in the discussion thread here.

Steve

[stevea]

v2.6 Posted

The first message of this thread has been updated with the ZIP file for v2.6 of Snevl Latitude. The changes are all bug fixes and minor debug additions:

• Removed some experimental code for Tasker that was causing some problems
• Fixed the edit of the Btraced/Backitude table, as it was wiping out the Backitude device ID
• When checking to see if HS devices need to be created, only give a warning once if the devices are not in the default location
• Allow for locales where comma is the decimal separator when dealing with the Backitude accuracy radius value
• Avoid DBNull problem with the Btraced device ID

As usual, post any issues or questions in the Discussion thread (here). Thanks.

Steve

[stevea]

v2.5.1 Replaced ASPX

Gogs discovered that I had left some experimental stuff in the ASPX web page, and it breaks when trying to update the Btraced/Backitude table. The replacement for the main web page is here. No other changes. My apologies.

Steve

[stevea]

v2.5

The first message of this thread has been updated with the ZIP file for v2.5 of Snevl Latitude, along with updated PDF files for Btraced and Backitude. The changes for v2.5 include:

• Added support for Backitude, an Android app that the author has modified to work directly applications like Snevl Latitude.
• Changed the "source" field of the track history to two letters: BA (Backitude), BT (Btraced), or FM (FollowMee)
• Don't updated devices if the current observation isn't the most recent.
• Check for malformed data from FollowMee.

As usual, post any issues or questions in the discussion thread for Snevl Latitude here.

Steve

[stevea]

v2.4 posted

The first message of this thread has been updated with version 2.4 of Snevl Latitude. The main changes in this version include:

• With the discontinuation of Google Latitude (effective today, 9-Aug-2013) removed references to Google Latitude.
• Added support for the FollowMee phone app, available for most phones.
• Added a "Last Source" field to the track history table. Currently this will display either a "B" (for Btraced) or "F" (for FollowMee) to indicate what source provided the most recent update.
• Added a sample capability to stream data from Snevl Latitude into Google Earth.

Be sure to follow the instructions, and if upgrading please run the script one time before attempting to bring up the web page. As always, please post any comments or issues in the discussion thread (here).

Steve

[stevea]

Attached here is a replacement Map ASPX page. The only thing changed is that the limit of points to plot was raised from 30 to 500. No other changes.

Steve

[stevea]

v2.2 posted

The top of this thread has been updated with the ZIP file for v2.2 of Snevl Latitude. The changes in this version are:

• The reverse geocode part of the script has been rewritten to replace the old Google API (which quit working) with v3 of the geocode API. This is probably the most significant change to v2.2.
• A few changes to how the code determines if the database needs to be upgraded, to prevent some problems a few users have discovered.
• Stopped the Btraced interface ASPX file from writting debug unless debug is turned on.

Post any comments, questions, or bug reports in the discussion thread: http://board.homeseer.com/showthread.php?t=156655

Steve

[stevea]

v2.1 posted

The first message of this thread has been updated with the ZIP file for v2.1 of Snevl Latitude. The changes since v2.0 are:

• Lots of changes to fix errors encountered by users who live where a comma (instead of a period) is used as the decimal separator.
• Similarly, changes made to ensure a period is used as the decimal separotor for data sent to Google for reverse geo.
• Fixed error for fresh installs, to not attempt to upgrade the database.
• Correct handling of the zoom level for second static map.
• Use the current locale culture info for formatting of the default config values.
• More debug and error trapping.

If upgrading from a previous version, install everything except the data directory to preserve your existing data.

As always, post any comments, problems, or questions in the discussion thread (here).

Steve

[stevea]

Attached is version 2.7 of Snevl Latitude, built upon the previous (v1.x) versions which had been posted here: http://board.homeseer.com/showthread.php?t=149363


Snevl Latitude gathers location information from your phone (and the phone of friends). The primary features:

• Maintains a track database of the location for each person (specifically, the location of their phone).
• Creates up to two static Google map images for each person, which can be placed in a device string for display on HSTouch. Maps can show either a track of the most recent locations (up to 20) or the most recent location reported. Road, satellite, or hybrid maps are supported. A handy way to use the two available maps for each person is to have one device show the track of the last N locations, and the other to show the most recent location.
• Also can create a static Google map showing a group of people, e.g. the location of everyone in the family on one map.
• An active javascript Google map page is provided, allowing annimation of a track, animation (bouncing) of the current location, zooming, panning, etc.
• You can create and maintain any number of "places" (e.g. home, work, mall, etc.) as well as a set of distances from any person to a places. These can be assigned to devices, and the distance value will be place in the appropriate device. In addition, a distance device will be turned ON when the associated person is "near" the associated "place", and turned off when the distance is no longer "near". You can use this ON/OFF to trigger events when someone approaches or departs a place.
• With the demise of Google Latitude (RIP), location information can be from either FollowMee, Btraced, Backitude or any combination of the three. FollowMee and Btraced apps support either Android or iOS devices, Backitude is Android only, and FollowMee also supports Windows Phones. For more information about BTraced, see the BTraced site (http://www.btraced.com) and/or read the attached document descriging how BTraced works with Snevl Latitude. For more information about FollowMee, see the FollowMee site (http://www.followmee.com). Note: FollowMee now only supports a subscription Web Service API, and v2.7 is required to interface to that service. For information about Backitude, see the Google Play Store.
• Several other data items can be kept in device strings for use in HSTouch. These include date/time of last update, latitude, longitude, position (a composite of street address, city, and state/province), GPS accuracy, and a few others. BTraced also reports a few other fields (e.g. altitude and phone battery status) which can also be put into devices.
• A simple capability to stream semi-realtime data from Snevl Latitude into Google Earth.

If you are upgrading, install everything from the attached ZIP except the data directory. Follow the instructions (in the docs directory) and your existing data should be preserved while upgrading your database, the web pages, and the main script. Instructions for setting up the for use with the specific apps are accessed via the FollowMee or Btraced/Backitude tabs of the web page.

NOTE: If you are upgrading, you will need to manually run the script once before attempting to bring up the web page. The web page expects the new database schema, and the script will automatically upgrade the database. (See the README)


The changes since the previous generation version, v1.x are:

• Significant restructure of the database, which had been keyed around the Google Latitude "badge" ID. This change was necessary to support BTraced.
• Added a new ASPX page that is used by BTraced to send location information to your HS Server.
• Restructured the tabs of the main web page to include "People", "Latitude", and "Btraced/Backitude" where you can define people to be tracked, where to get the tracking information, and what devices to create and populate for each person.
• Added the active javascript Google map page.
• Incorporated more error prevention / handling in several places (see the change log file for specifics)

See the bottom of this thread or the discussion thread for changes since v2.0.

Attached are the ZIP of the files to install, as well as a document describing how Btraced works (in case you want to understand it better before moving to v2).

Post any questions, comments, or issues with Version 2 of Snevl Latitude in the discussion thread (here:http://board.homeseer.com/showthread.php?t=156655).

Steve