1
0
Fork 0
satnogs-network/network/base/views.py

498 lines
20 KiB
Python
Raw Normal View History

import urllib2
import ephem
import math
from operator import itemgetter
from datetime import datetime, timedelta
2015-07-22 05:16:15 -06:00
from StringIO import StringIO
2015-04-11 11:32:44 -06:00
from django.conf import settings
2014-12-13 11:45:52 -07:00
from django.contrib import messages
from django.views.decorators.http import require_POST
from django.shortcuts import get_object_or_404, render, redirect
from django.core.urlresolvers import reverse
from django.utils.timezone import now, make_aware, utc
from django.utils.text import slugify
2015-07-21 02:42:23 -06:00
from django.http import JsonResponse, HttpResponseNotFound, HttpResponseServerError, HttpResponse
from django.contrib.auth.decorators import login_required
2015-07-22 05:16:15 -06:00
from django.core.management import call_command
from rest_framework import serializers, viewsets
2015-07-23 09:18:01 -06:00
from network.base.models import (Station, Transmitter, Observation,
Data, Satellite, Antenna, Tle, Rig)
2016-04-07 16:05:50 -06:00
from network.base.forms import StationForm, SatelliteFilterForm
2015-07-22 05:16:15 -06:00
from network.base.decorators import admin_required
2014-09-08 11:36:12 -06:00
class StationSerializer(serializers.ModelSerializer):
class Meta:
model = Station
fields = ('name', 'lat', 'lng')
class StationAllView(viewsets.ReadOnlyModelViewSet):
queryset = Station.objects.all()
serializer_class = StationSerializer
def _resolve_overlaps(station, start, end):
data = Data.objects.filter(ground_station=station)
if data:
for datum in data:
if datum.is_past:
continue
if datum.start <= end and start <= datum.end:
if datum.start <= start and datum.end >= end:
return False
if start < datum.start and end > datum.end:
start1 = start
end1 = datum.start
start2 = datum.end
end2 = end
return start1, end1, start2, end2
if datum.start <= start:
start = datum.end
if datum.end >= end:
end = datum.start
return start, end
2014-09-08 11:36:12 -06:00
def index(request):
"""View to render index page."""
observations = Observation.objects.all()
try:
featured_station = Station.objects.filter(active=True).latest('featured_date')
except Station.DoesNotExist:
featured_station = None
2014-09-08 11:36:12 -06:00
ctx = {
'latest_observations': observations.filter(end__lt=now()),
'scheduled_observations': observations.filter(end__gte=now()),
2015-04-11 11:32:44 -06:00
'featured_station': featured_station,
'mapbox_id': settings.MAPBOX_MAP_ID,
'mapbox_token': settings.MAPBOX_TOKEN
2014-09-08 11:36:12 -06:00
}
return render(request, 'base/home.html', ctx)
2015-07-21 02:42:23 -06:00
def custom_404(request):
"""Custom 404 error handler."""
return HttpResponseNotFound(render(request, '404.html'))
def custom_500(request):
"""Custom 500 error handler."""
return HttpResponseServerError(render(request, '500.html'))
def robots(request):
data = render(request, 'robots.txt', {'environment': settings.ENVIRONMENT})
response = HttpResponse(data,
content_type='text/plain; charset=utf-8')
return response
2015-07-22 05:16:15 -06:00
@admin_required
def settings_site(request):
"""View to render settings page."""
if request.method == 'POST':
if request.POST['fetch']:
try:
2016-01-26 08:05:17 -07:00
data_out = StringIO()
tle_out = StringIO()
call_command('fetch_data', stdout=data_out)
call_command('update_all_tle', stdout=tle_out)
request.session['settings_out'] = data_out.getvalue() + tle_out.getvalue()
2015-07-22 05:16:15 -06:00
except:
messages.error(request, 'fetch command failed.')
return redirect(reverse('base:settings_site'))
2016-01-26 08:05:17 -07:00
fetch_out = request.session.get('settings_out', False)
2015-07-22 05:16:15 -06:00
if fetch_out:
2016-01-26 08:05:17 -07:00
del request.session['settings_out']
2015-07-22 05:16:15 -06:00
return render(request, 'base/settings_site.html', {'fetch_data': fetch_out})
return render(request, 'base/settings_site.html')
2014-09-18 07:34:39 -06:00
def observations_list(request):
"""View to render Observations page."""
observations = Observation.objects.all()
2016-04-07 16:05:50 -06:00
satellites = Satellite.objects.all()
if request.method == 'GET':
form = SatelliteFilterForm(request.GET)
if form.is_valid():
norad = form.cleaned_data['norad']
observations = observations.filter(satellite__norad_cat_id=norad)
return render(request, 'base/observations.html',
{'observations': observations, 'satellites': satellites, 'norad': int(norad)})
return render(request, 'base/observations.html',
{'observations': observations, 'satellites': satellites})
2014-09-18 07:34:39 -06:00
@login_required
def observation_new(request):
"""View for new observation"""
me = request.user
if request.method == 'POST':
2014-10-26 19:14:26 -06:00
sat_id = request.POST.get('satellite')
2015-07-23 09:18:01 -06:00
trans_id = request.POST.get('transmitter')
start_time = datetime.strptime(request.POST.get('start-time'), '%Y-%m-%d %H:%M')
start = make_aware(start_time, utc)
end_time = datetime.strptime(request.POST.get('end-time'), '%Y-%m-%d %H:%M')
end = make_aware(end_time, utc)
2014-10-26 19:14:26 -06:00
sat = Satellite.objects.get(norad_cat_id=sat_id)
2015-07-23 09:18:01 -06:00
trans = Transmitter.objects.get(id=trans_id)
2016-01-23 02:40:56 -07:00
tle = Tle.objects.get(id=sat.latest_tle.id)
obs = Observation(satellite=sat, transmitter=trans, tle=tle,
author=me, start=start, end=end)
obs.save()
total = int(request.POST.get('total'))
2014-10-26 19:14:26 -06:00
for item in range(total):
start = datetime.strptime(
request.POST.get('{0}-starting_time'.format(item)), '%Y-%m-%d %H:%M:%S.%f'
)
end = datetime.strptime(
request.POST.get('{}-ending_time'.format(item)), '%Y-%m-%d %H:%M:%S.%f'
)
2014-10-26 19:14:26 -06:00
station_id = request.POST.get('{}-station'.format(item))
ground_station = Station.objects.get(id=station_id)
Data.objects.create(start=make_aware(start, utc), end=make_aware(end, utc),
ground_station=ground_station, observation=obs)
2014-10-26 19:14:26 -06:00
2014-12-19 06:06:58 -07:00
return redirect(reverse('base:observation_view', kwargs={'id': obs.id}))
2015-07-23 09:18:01 -06:00
satellites = Satellite.objects.filter(transmitters__alive=True).distinct()
transmitters = Transmitter.objects.filter(alive=True)
norad = 0
if request.method == 'GET':
form = SatelliteFilterForm(request.GET)
if form.is_valid():
norad = form.cleaned_data['norad']
return render(request, 'base/observation_new.html',
{'satellites': satellites,
'transmitters': transmitters, 'norad': norad,
'date_min_start': settings.DATE_MIN_START,
'date_max_range': settings.DATE_MAX_RANGE})
2014-10-26 08:46:03 -06:00
def prediction_windows(request, sat_id, start_date, end_date):
try:
sat = Satellite.objects.filter(transmitters__alive=True). \
distinct().get(norad_cat_id=sat_id)
except:
data = {
'error': 'You should select a Satellite first.'
}
return JsonResponse(data, safe=False)
2016-01-22 10:48:07 -07:00
2016-01-26 06:52:06 -07:00
try:
satellite = ephem.readtle(
str(sat.latest_tle.tle0),
str(sat.latest_tle.tle1),
str(sat.latest_tle.tle2)
)
2016-01-26 06:52:06 -07:00
except:
data = {
'error': 'No TLEs for this satellite yet.'
}
return JsonResponse(data, safe=False)
2014-10-26 08:46:03 -06:00
end_date = datetime.strptime(end_date, '%Y-%m-%d %H:%M')
data = []
stations = Station.objects.all()
for station in stations:
if not station.online:
continue
observer = ephem.Observer()
observer.lon = str(station.lng)
observer.lat = str(station.lat)
observer.elevation = station.alt
2014-10-26 08:46:03 -06:00
observer.date = str(start_date)
station_match = False
keep_digging = True
while keep_digging:
try:
tr, azr, tt, altt, ts, azs = observer.next_pass(satellite)
except ValueError:
data = {
'error': 'That satellite seems to stay always below your horizon.'
}
break
# no match if the sat will not rise above the configured min horizon
elevation = format(math.degrees(altt), '.0f')
if float(elevation) >= station.horizon:
if ephem.Date(tr).datetime() < end_date:
if ephem.Date(ts).datetime() > end_date:
ts = end_date
keep_digging = False
else:
time_start_new = ephem.Date(ts).datetime() + timedelta(minutes=1)
observer.date = time_start_new.strftime("%Y-%m-%d %H:%M:%S.%f")
# Adjust or discard window if overlaps exist
window_start = make_aware(ephem.Date(tr).datetime(), utc)
window_end = make_aware(ephem.Date(ts).datetime(), utc)
window = _resolve_overlaps(station, window_start, window_end)
if window:
if not station_match:
station_windows = {
'id': station.id,
'name': station.name,
'window': []
}
station_match = True
window_start = window[0]
window_end = window[1]
station_windows['window'].append(
{
'start': window_start.strftime("%Y-%m-%d %H:%M:%S.%f"),
'end': window_end.strftime("%Y-%m-%d %H:%M:%S.%f"),
'az_start': azr
})
# In case our window was split in two
try:
window_start = window[2]
window_end = window[3]
station_windows['window'].append(
{
'start': window_start.strftime("%Y-%m-%d %H:%M:%S.%f"),
'end': window_end.strftime("%Y-%m-%d %H:%M:%S.%f"),
'az_start': azr
})
except:
pass
else:
# window start outside of window bounds
break
else:
# did not rise above user configured horizon
break
if station_match:
data.append(station_windows)
return JsonResponse(data, safe=False)
2014-12-19 06:06:58 -07:00
def observation_view(request, id):
2014-09-21 14:18:16 -06:00
"""View for single observation page."""
observation = get_object_or_404(Observation, id=id)
data = Data.objects.filter(observation=observation)
Initial data vetting/verification system Model change (with migration 0006) adds 3 fields to Data: vetted_status (charfield with options for data status, default "unknown") vetted_user (who vetted the data) vetted_datetime (when it was vetted) In addition, various boolean functions are added for the Data model to check statuses. More functions are added to the Observation model to check status of verification within an observation as well, assuming multiple data entries in an Observation. With these, I also changed "has_data" to "has_submitted_data" to be more specific alongside the others. For UX, we add a green check sign or red removal sign to the data header in Observation view (along with green/red datetime in the footer) if a data is verified good or bad, respectively. If there is an unknown status, the data header is given a thumbs-up and thumbs-down button to verify the data good or bad. These icons are only offered to is_staff, the observation requestor, and any station owner in the observation. These buttons trigger new URLs/functions in view: data_verify(id) data_mark_bad(id) Returning the user back to the originating Observation page. In the observation lists I changed the coloring of the ID button to be: Future: light blue (same) No uploaded data and/or all vetted bad data: red Some or all unvetted data with no verified good data: orange Some or all verified good data: green These changes are reflected in the observations.html, home.html, and user_detail.html templates. solves satnogs/satnogs-network#171
2016-03-25 13:52:45 -06:00
# not all users will be able to vet data within an observation, allow
# staff, observation requestors, and station owners
is_vetting_user = False
2016-03-26 08:46:50 -06:00
if request.user.is_authenticated():
if request.user == observation.author or \
data.filter(ground_station__in=Station.objects.filter(owner=request.user)).count or \
request.user.is_staff:
is_vetting_user = True
Initial data vetting/verification system Model change (with migration 0006) adds 3 fields to Data: vetted_status (charfield with options for data status, default "unknown") vetted_user (who vetted the data) vetted_datetime (when it was vetted) In addition, various boolean functions are added for the Data model to check statuses. More functions are added to the Observation model to check status of verification within an observation as well, assuming multiple data entries in an Observation. With these, I also changed "has_data" to "has_submitted_data" to be more specific alongside the others. For UX, we add a green check sign or red removal sign to the data header in Observation view (along with green/red datetime in the footer) if a data is verified good or bad, respectively. If there is an unknown status, the data header is given a thumbs-up and thumbs-down button to verify the data good or bad. These icons are only offered to is_staff, the observation requestor, and any station owner in the observation. These buttons trigger new URLs/functions in view: data_verify(id) data_mark_bad(id) Returning the user back to the originating Observation page. In the observation lists I changed the coloring of the ID button to be: Future: light blue (same) No uploaded data and/or all vetted bad data: red Some or all unvetted data with no verified good data: orange Some or all verified good data: green These changes are reflected in the observations.html, home.html, and user_detail.html templates. solves satnogs/satnogs-network#171
2016-03-25 13:52:45 -06:00
if settings.ENVIRONMENT == 'production':
discuss_slug = 'https://community.satnogs.org/t/observation-{0}-{1}-{2}' \
.format(observation.id, slugify(observation.satellite.name),
observation.satellite.norad_cat_id)
discuss_url = ('https://community.satnogs.org/new-topic?title=Observation {0}: {1} ({2})'
'&body=Regarding [Observation {3}](http://{4}{5}) ...&category=observations') \
.format(observation.id, observation.satellite.name,
observation.satellite.norad_cat_id, observation.id,
request.get_host(), request.path)
try:
apiurl = '{0}.json'.format(discuss_slug)
urllib2.urlopen(apiurl).read()
has_comments = True
except:
has_comments = False
return render(request, 'base/observation_view.html',
{'observation': observation, 'data': data, 'has_comments': has_comments,
Initial data vetting/verification system Model change (with migration 0006) adds 3 fields to Data: vetted_status (charfield with options for data status, default "unknown") vetted_user (who vetted the data) vetted_datetime (when it was vetted) In addition, various boolean functions are added for the Data model to check statuses. More functions are added to the Observation model to check status of verification within an observation as well, assuming multiple data entries in an Observation. With these, I also changed "has_data" to "has_submitted_data" to be more specific alongside the others. For UX, we add a green check sign or red removal sign to the data header in Observation view (along with green/red datetime in the footer) if a data is verified good or bad, respectively. If there is an unknown status, the data header is given a thumbs-up and thumbs-down button to verify the data good or bad. These icons are only offered to is_staff, the observation requestor, and any station owner in the observation. These buttons trigger new URLs/functions in view: data_verify(id) data_mark_bad(id) Returning the user back to the originating Observation page. In the observation lists I changed the coloring of the ID button to be: Future: light blue (same) No uploaded data and/or all vetted bad data: red Some or all unvetted data with no verified good data: orange Some or all verified good data: green These changes are reflected in the observations.html, home.html, and user_detail.html templates. solves satnogs/satnogs-network#171
2016-03-25 13:52:45 -06:00
'discuss_url': discuss_url, 'discuss_slug': discuss_slug,
'is_vetting_user': is_vetting_user})
2014-09-21 14:18:16 -06:00
2014-10-16 07:42:44 -06:00
return render(request, 'base/observation_view.html',
Initial data vetting/verification system Model change (with migration 0006) adds 3 fields to Data: vetted_status (charfield with options for data status, default "unknown") vetted_user (who vetted the data) vetted_datetime (when it was vetted) In addition, various boolean functions are added for the Data model to check statuses. More functions are added to the Observation model to check status of verification within an observation as well, assuming multiple data entries in an Observation. With these, I also changed "has_data" to "has_submitted_data" to be more specific alongside the others. For UX, we add a green check sign or red removal sign to the data header in Observation view (along with green/red datetime in the footer) if a data is verified good or bad, respectively. If there is an unknown status, the data header is given a thumbs-up and thumbs-down button to verify the data good or bad. These icons are only offered to is_staff, the observation requestor, and any station owner in the observation. These buttons trigger new URLs/functions in view: data_verify(id) data_mark_bad(id) Returning the user back to the originating Observation page. In the observation lists I changed the coloring of the ID button to be: Future: light blue (same) No uploaded data and/or all vetted bad data: red Some or all unvetted data with no verified good data: orange Some or all verified good data: green These changes are reflected in the observations.html, home.html, and user_detail.html templates. solves satnogs/satnogs-network#171
2016-03-25 13:52:45 -06:00
{'observation': observation, 'data': data, 'is_vetting_user': is_vetting_user})
2014-10-27 18:45:22 -06:00
@login_required
def observation_delete(request, id):
"""View for deleting observation."""
me = request.user
observation = get_object_or_404(Observation, id=id)
if observation.author == me and observation.is_deletable:
observation.delete()
messages.success(request, 'Observation deleted successfully.')
else:
messages.error(request, 'Permission denied.')
return redirect(reverse('base:observations_list'))
Initial data vetting/verification system Model change (with migration 0006) adds 3 fields to Data: vetted_status (charfield with options for data status, default "unknown") vetted_user (who vetted the data) vetted_datetime (when it was vetted) In addition, various boolean functions are added for the Data model to check statuses. More functions are added to the Observation model to check status of verification within an observation as well, assuming multiple data entries in an Observation. With these, I also changed "has_data" to "has_submitted_data" to be more specific alongside the others. For UX, we add a green check sign or red removal sign to the data header in Observation view (along with green/red datetime in the footer) if a data is verified good or bad, respectively. If there is an unknown status, the data header is given a thumbs-up and thumbs-down button to verify the data good or bad. These icons are only offered to is_staff, the observation requestor, and any station owner in the observation. These buttons trigger new URLs/functions in view: data_verify(id) data_mark_bad(id) Returning the user back to the originating Observation page. In the observation lists I changed the coloring of the ID button to be: Future: light blue (same) No uploaded data and/or all vetted bad data: red Some or all unvetted data with no verified good data: orange Some or all verified good data: green These changes are reflected in the observations.html, home.html, and user_detail.html templates. solves satnogs/satnogs-network#171
2016-03-25 13:52:45 -06:00
@login_required
def data_verify(request, id):
me = request.user
data = get_object_or_404(Data, id=id)
data.vetted_status = 'verified'
data.vetted_user = me
data.vetted_datetime = datetime.today()
data.save(update_fields=['vetted_status', 'vetted_user', 'vetted_datetime'])
return redirect(reverse('base:observation_view', kwargs={'id': data.observation}))
@login_required
def data_mark_bad(request, id):
me = request.user
data = get_object_or_404(Data, id=id)
data.vetted_status = 'no_data'
data.vetted_user = me
data.vetted_datetime = datetime.today()
data.save(update_fields=['vetted_status', 'vetted_user', 'vetted_datetime'])
return redirect(reverse('base:observation_view', kwargs={'id': data.observation}))
2014-10-27 18:45:22 -06:00
def stations_list(request):
"""View to render Stations page."""
stations = Station.objects.all()
2014-12-14 05:50:39 -07:00
form = StationForm()
antennas = Antenna.objects.all()
2014-10-27 18:45:22 -06:00
2014-12-14 05:50:39 -07:00
return render(request, 'base/stations.html',
{'stations': stations, 'form': form, 'antennas': antennas})
2014-12-19 06:06:58 -07:00
def station_view(request, id):
"""View for single station page."""
station = get_object_or_404(Station, id=id)
2014-12-13 11:45:52 -07:00
form = StationForm(instance=station)
2014-12-14 05:47:50 -07:00
antennas = Antenna.objects.all()
rigs = Rig.objects.all()
try:
satellites = Satellite.objects.filter(transmitters__alive=True).distinct()
except:
pass # we won't have any next passes to display
# Load the station information and invoke ephem so we can
# calculate upcoming passes for the station
observer = ephem.Observer()
observer.lon = str(station.lng)
observer.lat = str(station.lat)
observer.elevation = station.alt
nextpasses = []
passid = 0
for satellite in satellites:
observer.date = ephem.date(datetime.today())
try:
2016-01-23 02:40:56 -07:00
sat_ephem = ephem.readtle(str(satellite.latest_tle.tle0),
str(satellite.latest_tle.tle1),
str(satellite.latest_tle.tle2))
# Here we are going to iterate over each satellite to
# find its appropriate passes within a given time constraint
keep_digging = True
while keep_digging:
try:
tr, azr, tt, altt, ts, azs = observer.next_pass(sat_ephem)
if tr is None:
break
# bug in pyephem causes overhead sats to appear in the result
# mixing next-pass data with current pass data, resulting in
# satnogs/satnogs-network#199. As a workaround, pyephem does
# return set time for current pass while rise time for next
# pass so when this happens we want to toss the entry out
# not a break as this sat might have another valid pass
if ts < tr:
pass
# using the angles module convert the sexagesimal degree into
# something more easily read by a human
elevation = format(math.degrees(altt), '.0f')
azimuth = format(math.degrees(azr), '.0f')
passid += 1
# show only if >= configured horizon and in next 6 hours
if tr < ephem.date(datetime.today() + timedelta(hours=6)):
if float(elevation) >= station.horizon:
sat_pass = {'passid': passid,
'mytime': str(observer.date),
'debug': observer.next_pass(sat_ephem),
'name': str(satellite.name),
'id': str(satellite.id),
'tr': tr, # Rise time
'azr': azimuth, # Rise Azimuth
'tt': tt, # Max altitude time
'altt': elevation, # Max altitude
'ts': ts, # Set time
'azs': azs} # Set azimuth
nextpasses.append(sat_pass)
observer.date = ephem.Date(ts).datetime() + timedelta(minutes=1)
continue
else:
keep_digging = False
continue
except ValueError:
break # there will be sats in our list that fall below horizon, skip
except TypeError:
break # if there happens to be a non-EarthSatellite object in the list
except Exception:
break
except (ValueError, AttributeError):
pass # TODO: if something does not have a proper TLE line we need to know/fix
return render(request, 'base/station_view.html',
2015-04-11 11:32:44 -06:00
{'station': station, 'form': form, 'antennas': antennas,
'mapbox_id': settings.MAPBOX_MAP_ID,
'mapbox_token': settings.MAPBOX_TOKEN,
'nextpasses': sorted(nextpasses, key=itemgetter('tr')),
'rigs': rigs})
2014-12-13 11:45:52 -07:00
@require_POST
def station_edit(request):
2014-12-13 11:45:52 -07:00
"""Edit or add a single station."""
2014-12-14 05:47:50 -07:00
if request.POST['id']:
pk = request.POST.get('id')
station = get_object_or_404(Station, id=pk, owner=request.user)
form = StationForm(request.POST, request.FILES, instance=station)
else:
form = StationForm(request.POST, request.FILES)
2014-12-13 11:45:52 -07:00
if form.is_valid():
f = form.save(commit=False)
f.owner = request.user
f.save()
form.save_m2m()
if f.online:
messages.success(request, 'Successfully saved Ground Station.')
else:
messages.success(request, ('Successfully saved Ground Station. It will appear online '
'as soon as it connects with our API.'))
return redirect(reverse('base:station_view', kwargs={'id': f.id}))
2014-12-14 05:47:50 -07:00
else:
messages.error(request, 'Some fields missing on the form')
return redirect(reverse('users:view_user', kwargs={'username': request.user.username}))
2015-08-24 06:13:59 -06:00
@login_required
def station_delete(request, id):
"""View for deleting a station."""
me = request.user
station = get_object_or_404(Station, id=id, owner=request.user)
station.delete()
messages.success(request, 'Ground Station deleted successfully.')
return redirect(reverse('users:view_user', kwargs={'username': me}))