rossengeorgiev / habitat-mobile-tracker Goto Github PK

Use Google Maps API3 to create a custom marker class.
Should be able to efficiently handle:

1. balloons w/ payloads, multi payload balloons, open chute and landed
2. chase cars
3. current location
4. optionally custom markers; possibly specified in the flight doc

Note 1: Images should be optimized, perhaps as sprites.
Note 2: Make it possible to select any color with HEX triplet.

Have ability to put your location in without the need for a GPS. Click on map ?

MT seems to have rendering issues in Firefox on Android. Layers that should not be overlapping, overlap causing all sort of visual nonsense.

I have to assume the problem is in Firefox itself, as MT renders fine on all modern browser, both mobile and desktop, including desktop Firefox.

Tested device running: Android 4.1.2 with Firefox (20.0.1 Latest version)

Can't drag the map around on my Android tablet (Google Nexus 7). I can on my Windows PC using Google Chrome browser.

MT should be able to load partially, or nearly complete in the absence of an internet connection, as long as it has loaded once before while online.

Testing device: Android 4.1.2 / Chrome 34.0.1847.114

Reproduce:

• Open MT once in Chrome, while online
• go offline, by disabling data connection and wifi
• Try open MT in Chrome

Expected result:

• MT loads up, interface, map
• MT also loads the last seen balloons/chasecars/stations

Actual result:

• Chrome spits out a simple error: You are offline

Have the ability next to a payload to have a hires (all the points) or lores (1/10th plus the last 10 ?) tracks ?

The app should cache position data for the following reasons:

1. Always available, even if there isn't a network connection
2. Reduce the load on spacenear.us server

Pitfalls:

There needs to be a way to remove vehicles, that are not longer available from the map.
Possible solution would be to have them timeout. Or have a button to force re-download of position data.

Firefox 24.6.0 (debian iceweasel)

Not sure if this is possible, but it'd be cool if you could click on the coordinates of the payload (or any coordinates that may be listed) and it would open it up in Apple Maps, Google Maps or TomTom app (or whatever) as destination. This would be convenient for getting directions to the payload.

Currently there are only 4 - blue, red, green and yellow.

To remove payloads, amend flight descriptions.

Currenlty, the habitat couchdb does not support CORS (Cross-origin resource sharing). This is preventing the app from sending position updates to habitat.

The only way to fully test the app you need chrome with disabled security.
run chrome --disable-web-security

There needs to be some sort of UI element to enable/disable this overlay

Have a way to view/compare archived flight data. Once the feature is available in habitat.

ukhas/habitat#286

It has come to my attention that regular refreshing of the prediction data, especially on a busy day, would eat a lot of bandwidth. Perhaps, disable the feature by default for mobile devices and have an option to re-enable it.

Over the 3 day the mobile tracker has managed to eat around 600 mb of bandwidth. That;s when fetching every 28sec. That's puts the average data per request at ~60-65kb.

The app launches and the status bar finishes, it then loads all of the map data - where there are balloons or not, it crashes and returns to home screen. If however you quickly tap one of the top icons before the map finishes loading and then return to the map after then it seems ok.

Between Bing OS/OSM/Google
See http://habmap.philcrump.co.uk/?vehicles=EDUHAB2

When the option is enabled either lower opacity or completely hide, polyline and horizon circles for vehicles other than the selected one. If none are selected, all elements should be visible

Currently the format is %H:%M
When telemetry spans over only a couple of hours, then would make sense to have seconds as well. Or perhaps, for floater balloon, where the data spans over the a couple of days, a different format might be better. Say, Day of the month + hour:minutes.

Essentially, scale axis format based on the time span of the data being displayed.

Thanks for the nice app. However, using it in landscape mode on an Android smartphone waists a lot of screen real estate. Suggestions:

• provide a button to slide away the list of payloads / cars (e.g. to the top)
• suppress the browser headline

• apirs.fi has a API that returns in JSON format
• Have a field where the user inputs callsigns, comma separated, and switch to enable the functionality

Selecting and panning on desktops is currently tricky as it is hooked to expanding and collapsing vehicles in the left panel. There seems to be enough space for two extra buttons, which will act as toggles.

Additionally, option to only view certain callsigns, and hide GUI elements. For example:

...mobile-tracker/?callsigns=DERP1 - only DERP1 data is fetched
&hidemenu=1 - Hide top menu
&hidelist=1 - Hide the side list of vehicles, maybe when tracking just one.
&hidegraph=1 - Hide the bottom tab for showing up the telemetry graph
&hidessdv=1 - Hide ssdv box
&expandgraph=1 - When hidegraph is not 1, open the telemetry graph on startup

Finally, add a new button to the top menu, which helps anyone configure the embedding options.

This way map zoom is available on machines that have no mouse, or any ability to emulate scrolling.

See "Refactor the code milestone"

When there are > 20000 points (a guess) opening the mobile tracker on the iPhone (5S) it gets the logo, opens the map displays no vehicles then closes down.

Suggest a "low resolution" mode for Safari mobile users that only displays 1/10th of the points ? (Maybe 1/10th of track then the last 10 ?)

One feature I missed on the old map was having the little scale Google maps usually have at bottom. Would be nice to see on the new tracker if you can.

Like the existing tracker we could do with a flights info box. If it could have 2 sections, firstly importing from Habitat with details , and then a section for authorised admins to put manual information. Possibly a new icon on the top ?

Currently, using simply a 2d circle over the projected map. Visualization is increasingly inaccurate as the vehicle location approaches the Earth's poles.

empty

After a prolonged use, base stations who are no longer active will still stay on the map as there is no method to remove them. A refresh of the page is will remedy the problem.

Case:

Mobile tracker is running in a mobile browser, the browser is suspended for a few days, when we relaunch the app, it will fetch the latest data since the suspension. The will be cluttered with base stations of which only a few are currently active.

It would be great to have the equivalent of the old Google Maps measurement ruler to allow measurement between two or more points on the map.

This is useful for measuring a distance from

• a tracking station to a balloon,
• a tracking station to a point on the balloons path,
• for measuring a balloons path length.

This would probably only be suited to desktop browsers.

The bug appears on long duration flights. It seem Google's image chart servers limit the url to ~2048 characters in length, anything longer will return error 414.

Error example:

"NetworkError: 414 Request-URI Too Large - http://chart.googleapis.com/chart?chf=bg,s,67676700&chxr=0,0,46|1,0,0|2,0,45&chxs=0,676767,0,0,_,000000|1,676767,0,0,t,676767|2,676767,0,0,_,676767&chxt=r,y,x&chs=300x80&cht=lc&chco=33B5E5&chds=0,12442&chls=2&chm=B,33B5E533,0,0,0,-1&chd=s:AACDDEFGHIJJKLMNOOQRSTUVWYZabcdefghijyzzzzzz00000000001111112222223333333344444444444444444444444444444444444444344433443434444434444443444444444444434444444444444443444344444344444443444444444434444334433343443444444444444444444433333333333433334433333333333333333r33333333323333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333332333233222222222121121222222212212222212221112221111112212222122112222211222222222222212222112222222222222222222201222121211221111111111111111221121222223332233333333343333333333333333333333333333333333333333333333333333333333333333333333333333333333333344444333334334344443444444444455554555555555555555555555555555555555555555554444444443433443344444444444443433434334344433444444444334344443443434444454544445455555555555555555555555555555555555555555555555555555555555555555556555555555555555555555566666666666666666666666777777777777777777777777777777878788888878888888888888888887888888888888888888888888888887877878777787787777777777777777777666666765666666777767776776666666666666676666676666666667666667666666666666666776676667666666667667666676776677766676766666666766676666666667677777577777677777777777777777777777778777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777877777787777777777777777777777777767666566565666666666666666666666666666666666666666666666656666666666566656656664666456666666666656666666566665566666666666666677677776777777777777778777777777777777777777777777777777778778788888888888888888888888888888888889889888888888888888888888888989988888888888888888888888988889898888888999988898888998988988989888888888888878777877767777776777767676777777777777777777777777777777777777767777777777787777777777777777777777776767765777776667787777777677767777777776777777777777777677777777677789888878888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888878888888877888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888878888878887777777777767777767777777777776776777778777777777777777777777777787777777776677777777777"

Possible solutions to this problem:

1. Replace the API, after all it's deprecated and will last to around 2017 iirc
2. Trim the data points so that the url length is under 2048 characters.

All tracker logic should be separated into its own class.
The class should handle:

1. All pulling of telemetry from habitat
2. Handle all placement/removal/updating of map elements (such as markers and paths)
3. ability to enable/disable, otherwise customization and selection of various features
   (this will be used on based on the devices running the webapp - deskstop, pad or phone)

Note: Should help in implementing #15

Can we make sure we keep a link to either individual track KML files, or as present for the entire set of tracks for download/updating in KML format please ?
A nice bonus would be to choose different colours for each track as well, rather than the present "Blue" for everything ;-)

Maintaining the custom font is cumbersome. Most browsers support SVG, which makes the process of adding/modifying vector icons - a breeze. After all font based icons are only useful if we are using them on multiple places on the same page and around the site.

The tracker should pull position data from habitat, rather than using the spacenear.us/tracker API.

Use habiatat to pull:

1. Vehicles list (balloons and chase cars)
2. Position and telemetry data
3. Listener data
4. Live prediction data

http://habitat.readthedocs.org/en/latest/database.html#using-views-example
http://habitat.readthedocs.org/en/latest/habitat/habitat/habitat.views.html

The outer blue circle is the one degree footprint. This gives the range of the balloon approximately from ground level. The inner green circle is the five degree footprint. Not currently available on this tracker.

Just noticed that when the weather overlays are selected for Europe, they overlay the world image to the right of the image selected when zooming in

If you now zoom in further then image isn't seen at all .....
The only exception to this appears to be when zooming in on the USA i.e. B-64 currently, it seems perhaps that the weather tiles don't overlay the same "zoomed" tiles ?

1. portrait mode
2. vehicle list is long
3. unable to scroll to the end

landscape is unaffected

Suggest some method of being able to filter the payloads off, maybe a drop down on the balloon icon top left and the ability to select all/ deselect all and check the payloads you want to see. Selection method will need to work on touch screens.

Speed is shown to 15 digits behind the decimal. I think this could be rounded to 0.1 m/s or even whole numbers in this screen. Same with the altitude.

Probably best done only in the landscape mode as portrait has really limited space.

Either messed up calculation of the date or due to calculation inaccuracy.