summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorkrakenrf <78108016+krakenrf@users.noreply.github.com>2022-10-18 11:29:20 +0200
committerkrakenrf <78108016+krakenrf@users.noreply.github.com>2022-10-18 11:29:20 +0200
commit00a0df4bd6ac5724c23cd0982bd1264465a23863 (patch)
tree262219074b41208d2a3b48b96c2bf7a2b1113eec
parentUpdated 12. Kraken Pro Cloud Mapper (markdown) (diff)
downloadkrakensdr_docs.wiki-00a0df4bd6ac5724c23cd0982bd1264465a23863.tar
krakensdr_docs.wiki-00a0df4bd6ac5724c23cd0982bd1264465a23863.tar.gz
krakensdr_docs.wiki-00a0df4bd6ac5724c23cd0982bd1264465a23863.tar.bz2
krakensdr_docs.wiki-00a0df4bd6ac5724c23cd0982bd1264465a23863.tar.lz
krakensdr_docs.wiki-00a0df4bd6ac5724c23cd0982bd1264465a23863.tar.xz
krakensdr_docs.wiki-00a0df4bd6ac5724c23cd0982bd1264465a23863.tar.zst
krakensdr_docs.wiki-00a0df4bd6ac5724c23cd0982bd1264465a23863.zip
-rw-r--r--12.-Kraken-Pro-Cloud-Mapper.md14
1 files changed, 14 insertions, 0 deletions
diff --git a/12.-Kraken-Pro-Cloud-Mapper.md b/12.-Kraken-Pro-Cloud-Mapper.md
index a53b4c1..c4da69e 100644
--- a/12.-Kraken-Pro-Cloud-Mapper.md
+++ b/12.-Kraken-Pro-Cloud-Mapper.md
@@ -66,6 +66,7 @@ After a few minutes you should see the DOA lobe and bearing lines on the map.
### Main configure button (top right gear icon)
**Heatmap Size:** Total size from edge to edge in kilometers of the heatmap grid. Set appropriately for your expected search space.
+
**Heatmap Resolution:** Number of cells per axis on the grid. A higher value can result in more precise TX localization. But setting it too high can make offline logfile calculations too slow. Maximum resolution is currently capped at 500.
It's important to note that setting a smaller heatmap size naturally results in a higher resolution grid too. For example, if you set your grid to 100km and resolution to 500, each grid cell has a size of 100,000/500 = 200 x 200 meters.
@@ -79,6 +80,7 @@ Now if you set the grid size to 10km, each cell has a size of 20 x 20 meters.
If you double click on the map a menu will pop up.
**Add Marker:** Adds a reference marker on the map. Useful for marking to location of known transmitters.
+
**Center Heatmap:** Centers the heatmap grid wherever you clicked.
### Layer Options
@@ -102,6 +104,18 @@ After a few moments you should see the logfile load in. The heatmap calculation
You can click on individual data points on the map for more information about that particular point, as well as a drawing of the lobe.
+## Moving Markers with Data
+You can upload coordinate data to the KrakenSDR server and have it plotted as a marker on the map. This is useful for verifying a KrakenSDR setup, for example by driving around your target area with a beacon and GPS, or using a weather balloon radiosonde.
+
+A Python script that shows an example of how to upload data to the server can be found at https://github.com/krakenrf/krakensdr_docs/blob/main/misc_scripts/sondehub_krakenmap.py. The script uses the SondeHub API to receive GPS coordinates of a weather balloon. The GPS coordinates are then forwarded to the Kraken Pro Cloud server.
+
+# Future Features
+Our developer is currently working on new advanced features, some of which may require a subscription payment. These features include
+- Long Term History: The ability to rewind in time and see where the bearings where crossing at some time in the past. Useful for analyzing moving objects.
+- Object Tracking: The ability to automatically track an object.
+- Multi-VFO Layering: The ability to receive data from multiple VFOs or frequencies at once, or via the KrakenSDR sweeping. With layering options to choose frequencies to display on the map.
+- More than three KrakenSDRs
+- Beacon ID: The ability to track KrakenSDR beacons that may be transmitting unique IDs but on the same frequency.
DOCS IN DEVELOPMENT \ No newline at end of file