glaskugel
(Themenstarter)
Anmeldungsdatum: 8. Juli 2010
Beiträge: 3453
|
Das war ja nur ein Beispiel für einen Spezialfall, wo ich mir dachte, ich poste das. denn du hast ja schon soviel Problemlösungen geschafft, für die es bis jetzt keine Lösung gab.
ich fürchte ohne Kombination mit einem Trägheitsnavigationssystem hat man in Tunneln, Gebäuden und anderen Umgebungen ohne Kontakt zu den Satelliten wenig Chancen den Routenverlauf automatisiert zu ermitteln.
Ich hatte schon GPS-Empfänger, die ein paar Meter nach dem Tunnel wieder die richtige Position loggten. Leider sind die ausverkauft. Dieses Beispiel ist von einem Handy, das sonst sehr gut ist. Es wird neben US-GPS auch Glonass und Baidu unterstützt. Die Problematik nach Aufenthalt in Gebäuden ist aber sicher ein Thema, das viele trifft. Mir ist aufgefallen, dass ein Ausschalten und wieder Einschalten zu wesentlich besseren Ergebnissen führt, aber da vergisst man dann oft darauf. So ein Stadtbummel mit vielen historischen Gebäuden liefert in der Regel chaotische Tracks. In diesem Fall waren die Ausreißer aber nicht extrem, sodass man die nicht so leicht eliminieren kann.
Wenn man aber von einer halbwegs gleichmäßigen Geschwindigkeit zwischen den Punkten außerhalb des Tunnels ausgehen kann und den Tunnelverlauf kennt, sollte man die fehlenden Punkte mit recht brauchbarer Genauigkeit ergänzen können
Das ist auch noch etwas, das ich nicht sicher verstanden habe. Der Abgleich erfolgt immer zum zeitlich nächsten Punkt und es wird nichts interpoliert? Eigentlich sollte da zwischen den Punkten interpoliert werden, speziell im Flugzeug wäre das interessant. Nach 10 Sekunden ist man da schon ganz wo anders, wenn zB alle 15 Sekunden mindestens geloggt wird.
|
glaskugel
(Themenstarter)
Anmeldungsdatum: 8. Juli 2010
Beiträge: 3453
|
Wenn es nicht zu schwierig / aufwendig ist. Könntest du beim Zeitzonen-Split noch eine Version erstellen, bei der alle definitiv falschen Daten entfernt wurden, also nicht nach Zeitzonen-IDs geteilt, sondern alles.
|
glaskugel
(Themenstarter)
Anmeldungsdatum: 8. Juli 2010
Beiträge: 3453
|
Mit der neuesten Version werden im Bereich Ayamonte keine Algier-Zeitzonen mehr gefunden, allerdings an 1 anderen Tag, wo du gefragt hast, ob das eine Bootsfahrt war. Ich habe von der "großen" gpx einen Zeizonen-Split gemacht und die Algier-Datei in test.gpx umbenannt. Ich hänge die Datei an. Ist eiegentlich die Reihenfolge der Optionen wichtig? Danach: $ python3 /usr/local/bin/geoinfo.py -s test.gpx
trying to open test.cache...
initializing tzwhere...
created tzwhere object
could not caculate timezone id for TP10243 at 37.1198132, -7.5324112
could not caculate timezone id for TP10244 at 37.1197961, -7.533344
could not caculate timezone id for TP10245 at 37.1198285, -7.5358952
could not caculate timezone id for TP10246 at 37.1195956, -7.5362224
could not caculate timezone id for TP10247 at 37.1196344, -7.5366078
could not caculate timezone id for TP10248 at 37.1283476, -7.5395024
could not caculate timezone id for TP10249 at 37.1282712, -7.5397952
could not caculate timezone id for TP10250 at 37.1278882, -7.542784
could not caculate timezone id for TP10251 at 37.1279121, -7.5430868
could not caculate timezone id for TP10252 at 37.1278225, -7.5429728
could not caculate timezone id for TP10253 at 37.1278856, -7.5429628
could not caculate timezone id for TP10254 at 37.1277874, -7.5431852
could not caculate timezone id for TP10255 at 37.1277972, -7.5431647
could not caculate timezone id for TP10256 at 37.1282512, -7.5464704
could not caculate timezone id for TP10257 at 37.1282998, -7.5467444
could not caculate timezone id for TP10258 at 37.1282948, -7.5467566
could not caculate timezone id for TP10259 at 37.1284992, -7.5468283
could not caculate timezone id for TP10260 at 37.1285008, -7.5468288
could not caculate timezone id for TP10261 at 37.1285024, -7.5468734
could not caculate timezone id for TP10262 at 37.1285106, -7.5467196
could not caculate timezone id for TP10263 at 37.1284992, -7.5467776
could not caculate timezone id for TP10264 at 37.1277866, -7.5468251
could not caculate timezone id for TP10265 at 37.1284969, -7.547136
could not caculate timezone id for TP10266 at 37.1285057, -7.5472316
could not caculate timezone id for TP10267 at 37.1283982, -7.547136
could not caculate timezone id for TP10268 at 37.1284198, -7.5471808
could not caculate timezone id for TP10269 at 37.1284018, -7.5471743
could not caculate timezone id for TP10270 at 37.1283985, -7.5471824
could not caculate timezone id for TP10271 at 37.1285012, -7.5471864
could not caculate timezone id for TP10272 at 37.1284, -7.5471712
could not caculate timezone id for TP10273 at 37.1284928, -7.5472214
could not caculate timezone id for TP10274 at 37.128436, -7.5471964
could not caculate timezone id for TP10275 at 37.128252, -7.5472008
could not caculate timezone id for TP10276 at 37.1282593, -7.5472766
could not caculate timezone id for TP10277 at 37.1281963, -7.5472315
could not caculate timezone id for TP10278 at 37.1279618, -7.5472799
could not caculate timezone id for TP10279 at 37.1278344, -7.5479936
could not caculate timezone id for TP10280 at 37.1280913, -7.5479803
could not caculate timezone id for TP10281 at 37.1280193, -7.54803
could not caculate timezone id for TP10282 at 37.1279168, -7.5480822
could not caculate timezone id for TP10283 at 37.1278353, -7.5488684
could not caculate timezone id for TP10284 at 37.1264528, -7.5497111
could not caculate timezone id for TP10285 at 37.126221, -7.5497147
could not caculate timezone id for TP10286 at 37.1263488, -7.5472888
could not caculate timezone id for TP10287 at 37.1262577, -7.5481078
could not caculate timezone id for TP10288 at 37.1261956, -7.5489262
could not caculate timezone id for TP10289 at 37.1278008, -7.5495806
could not caculate timezone id for TP10290 at 37.1266068, -7.4494976
could not caculate timezone id for TP10291 at 37.1275778, -7.449342
could not caculate timezone id for TP10292 at 37.1270693, -7.4508663
could not caculate timezone id for TP10293 at 37.126555, -7.4507257
could not caculate timezone id for TP10294 at 37.1261632, -7.4514431
could not caculate timezone id for TP10295 at 37.1208459, -7.4495983
could not caculate timezone id for TP10296 at 37.1209992, -7.4493776
could not caculate timezone id for TP10297 at 37.1261476, -7.4497744
could not caculate timezone id for TP10298 at 37.1266562, -7.4507258
could not caculate timezone id for TP10299 at 37.1269722, -7.449478
could not caculate timezone id for TP10300 at 37.1269636, -7.4496717
could not caculate timezone id for TP10301 at 37.1264262, -7.4491904
could not caculate timezone id for TP10302 at 37.1262222, -7.4489851
could not caculate timezone id for TP10303 at 37.1206657, -7.448864
could not caculate timezone id for TP10304 at 37.1196166, -7.4488928
could not caculate timezone id for TP10305 at 37.1204112, -7.4489211
could not caculate timezone id for TP10306 at 37.1196168, -7.451328
could not caculate timezone id for TP10307 at 37.1204096, -7.4506174
could not caculate timezone id for TP10308 at 37.1197952, -7.4505453
could not caculate timezone id for TP10309 at 37.120416, -7.4497723
could not caculate timezone id for TP10310 at 37.1196128, -7.4489024
could not caculate timezone id for TP11073 at 36.9920149, -7.7124499
could not caculate timezone id for TP11074 at 36.9931833, -7.703205
could not caculate timezone id for TP11075 at 36.9942833, -7.6939383
could not caculate timezone id for TP11076 at 37.0380399, -7.6752383
could not caculate timezone id for TP11077 at 37.0402083, -7.6656899
could not caculate timezone id for TP11078 at 37.042515, -7.6560666
could not caculate timezone id for TP11079 at 37.0448049, -7.6464116
could not caculate timezone id for TP11080 at 37.0470416, -7.63674
could not caculate timezone id for TP11081 at 37.0492699, -7.6270366
could not caculate timezone id for TP11082 at 37.0515183, -7.6173032
could not caculate timezone id for TP11083 at 37.0537866, -7.6075583
could not caculate timezone id for TP11084 at 37.0560549, -7.5978016
could not caculate timezone id for TP11085 at 37.0583266, -7.5880199
could not caculate timezone id for TP11086 at 37.0606066, -7.5782149
could not caculate timezone id for TP11087 at 37.0628833, -7.568385
could not caculate timezone id for TP11088 at 37.0651616, -7.5585333
could not caculate timezone id for TP11089 at 37.0674399, -7.5486633
could not caculate timezone id for TP11090 at 37.0697266, -7.5387716
could not caculate timezone id for TP11091 at 37.07202, -7.5288466
could not caculate timezone id for TP11092 at 37.07432, -7.5188649
could not caculate timezone id for TP11093 at 37.0766383, -7.5088233
could not caculate timezone id for TP11094 at 37.0789633, -7.4987249
could not caculate timezone id for TP11095 at 37.0813066, -7.48857
could not caculate timezone id for TP11096 at 37.083665, -7.4783466
could not caculate timezone id for TP11097 at 37.0860316, -7.4680466
could not caculate timezone id for TP11098 at 37.0884116, -7.4576816
could not caculate timezone id for TP11099 at 37.0907933, -7.4472533
could not caculate timezone id for TP11100 at 37.0931849, -7.4367649
could not caculate timezone id for TP11101 at 37.0955933, -7.4262366
could not caculate timezone id for TP11102 at 37.0980049, -7.4156733
could not caculate timezone id for TP11103 at 37.1004216, -7.4050566
could not caculate timezone id for TP11104 at 37.1028566, -7.3944049
could not caculate timezone id for TP11105 at 37.1052983, -7.3837533
could not caculate timezone id for TP11106 at 37.107735, -7.3731066
could not caculate timezone id for TP11107 at 37.11017, -7.3624549
could not caculate timezone id for TP11108 at 37.1126083, -7.3517866
could not caculate timezone id for TP11109 at 37.1150583, -7.3410899
could not caculate timezone id for TP11110 at 37.1175183, -7.3303699
could not caculate timezone id for TP11111 at 37.1199816, -7.3196349
could not caculate timezone id for TP11112 at 37.1224499, -7.30887
could not caculate timezone id for TP11113 at 37.1249266, -7.2980549
could not caculate timezone id for TP11114 at 37.1274166, -7.2871933
could not caculate timezone id for TP11115 at 37.129915, -7.276295
could not caculate timezone id for TP11116 at 37.1324183, -7.265365
could not caculate timezone id for TP11117 at 37.1349299, -7.2544066
could not caculate timezone id for TP11118 at 37.1374499, -7.2434166
could not caculate timezone id for TP11119 at 37.1399766, -7.2323983
could not caculate timezone id for TP11120 at 37.1425066, -7.221355
could not caculate timezone id for TP11121 at 37.1450449, -7.2102883
could not caculate timezone id for TP11122 at 37.147575, -7.1991949
could not caculate timezone id for TP11123 at 37.1501066, -7.1880733
could not caculate timezone id for TP11124 at 37.152645, -7.1769199
could not caculate timezone id for TP11125 at 37.1551866, -7.1657249
could not caculate timezone id for TP11126 at 37.1577299, -7.15448
could not caculate timezone id for TP11127 at 37.1602816, -7.143185
could not caculate timezone id for TP11128 at 37.1628449, -7.131845
could not caculate timezone id for TP11129 at 37.1654199, -7.1204633
could not caculate timezone id for TP11130 at 37.1680033, -7.109045
could not caculate timezone id for TP11131 at 37.1705949, -7.0975933
could not caculate timezone id for TP11132 at 37.1731916, -7.0861166
could not caculate timezone id for TP11133 at 37.1757916, -7.0746083
could not caculate timezone id for TP11134 at 37.1783899, -7.0630783
could not caculate timezone id for TP11135 at 37.1809849, -7.0515416
creating cache file...
successfully created cache file test.cache
2011-07-24 16:08:00: changed to timezone Africa/Algiers at point TP10243 (37.1198132, -7.5324112)
guessed 131 points
### track elevation stats ###
elevation_maximum=5295
elevation_minimum=1
elevation_mean=1693
elevation_median=17
elevation_stdev=1905
elevation_variance=3601930
### end track elevation stats ###
processing trackpoints for tzname 'Africa/Algiers'
creating test_Africa_Algiers.gpx for timezone Africa/Algiers Und nun soll alles über 200m rausfliegen: python3 /usr/local/bin/geoinfo.py -s -E 200 test.gpx
initializing tzwhere...
created tzwhere object
could not caculate timezone id for TP10243 at 37.1198132, -7.5324112
could not caculate timezone id for TP10244 at 37.1197961, -7.533344
could not caculate timezone id for TP10245 at 37.1198285, -7.5358952
could not caculate timezone id for TP10246 at 37.1195956, -7.5362224
could not caculate timezone id for TP10247 at 37.1196344, -7.5366078
could not caculate timezone id for TP10248 at 37.1283476, -7.5395024
could not caculate timezone id for TP10249 at 37.1282712, -7.5397952
could not caculate timezone id for TP10250 at 37.1278882, -7.542784
could not caculate timezone id for TP10251 at 37.1279121, -7.5430868
could not caculate timezone id for TP10252 at 37.1278225, -7.5429728
unorderable types: NoneType() > float()
creating cache file...
successfully created cache file test.cache
Traceback (most recent call last):
File "/usr/local/bin/geoinfo.py", line 808, in <module>
main()
File "/usr/local/bin/geoinfo.py", line 798, in main
geoinfo.split_gpx_data_by_tz(gpx_data, calculated_data, args.gpx_file)
File "/usr/local/bin/geoinfo.py", line 512, in split_gpx_data_by_tz
timezone_names = {point.timezone_name for point in calculated_data}
TypeError: 'NoneType' object is not iterable Gibt es Probleme, weil da vielleicht gar nichts gültiges mehr übrig bleibt? Aber elevation_minimum=1, also sollte es da was unter 200 geben. Wären da auch negative Werte bei -E möglich? Bitte die "track elevation stats" in die Textdatei schreiben, da will man später auch noch mal nachschauen können, wenn das Terminal bereits zu ist.
- test.gpx.tar.gz (2.7 KiB)
- Download test.gpx.tar.gz
|
seahawk1986
Anmeldungsdatum: 27. Oktober 2006
Beiträge: 11179
Wohnort: München
|
Ok, da gab es noch einige Unstimmigkeiten im Skript - die gpx-Datei enthält ein paar Punkte ohne Höheninformation, was in der Funktion, die die Höhen vergleicht, noch nicht abgefangen wurde und ich hatte vergessen eine Variable umzubenennen, die den Fallback auf die Google Maps Timezone API ermöglicht. Jetzt habe ich auch noch eine Abfrage der Zeitzone über die Geonames API eingebaut, die gegenüber der Google Maps API bevorzugt genutzt wird, wenn ein --geonames-username gesetzt ist.
- geoinfo.tar.xz (7.7 KiB)
- Download geoinfo.tar.xz
|
glaskugel
(Themenstarter)
Anmeldungsdatum: 8. Juli 2010
Beiträge: 3453
|
Ich verstehe da noch was nicht. $ python3 /usr/local/bin/geoinfo.py -E 20 -K 120 -s test.gpx
initializing tzwhere...
created tzwhere object
could not calculate timezone id for TP10243 at 37.1198132, -7.5324112
could not calculate timezone id for TP10244 at 37.1197961, -7.533344
could not calculate timezone id for TP10245 at 37.1198285, -7.5358952
could not calculate timezone id for TP10246 at 37.1195956, -7.5362224
could not calculate timezone id for TP10247 at 37.1196344, -7.5366078
could not calculate timezone id for TP10248 at 37.1283476, -7.5395024
could not calculate timezone id for TP10249 at 37.1282712, -7.5397952
could not calculate timezone id for TP10250 at 37.1278882, -7.542784
could not calculate timezone id for TP10251 at 37.1279121, -7.5430868
could not calculate timezone id for TP10252 at 37.1278225, -7.5429728
ignoring TP10253, no elevation data.
could not calculate timezone id for TP10254 at 37.1277874, -7.5431852
could not calculate timezone id for TP10255 at 37.1277972, -7.5431647
could not calculate timezone id for TP10256 at 37.1282512, -7.5464704
could not calculate timezone id for TP10257 at 37.1282998, -7.5467444
could not calculate timezone id for TP10258 at 37.1282948, -7.5467566
could not calculate timezone id for TP10259 at 37.1284992, -7.5468283
could not calculate timezone id for TP10260 at 37.1285008, -7.5468288
could not calculate timezone id for TP10261 at 37.1285024, -7.5468734
could not calculate timezone id for TP10262 at 37.1285106, -7.5467196
could not calculate timezone id for TP10263 at 37.1284992, -7.5467776
could not calculate timezone id for TP10264 at 37.1277866, -7.5468251
could not calculate timezone id for TP10265 at 37.1284969, -7.547136
could not calculate timezone id for TP10266 at 37.1285057, -7.5472316
could not calculate timezone id for TP10267 at 37.1283982, -7.547136
could not calculate timezone id for TP10268 at 37.1284198, -7.5471808
could not calculate timezone id for TP10269 at 37.1284018, -7.5471743
could not calculate timezone id for TP10270 at 37.1283985, -7.5471824
could not calculate timezone id for TP10271 at 37.1285012, -7.5471864
could not calculate timezone id for TP10272 at 37.1284, -7.5471712
could not calculate timezone id for TP10273 at 37.1284928, -7.5472214
could not calculate timezone id for TP10274 at 37.128436, -7.5471964
could not calculate timezone id for TP10275 at 37.128252, -7.5472008
could not calculate timezone id for TP10276 at 37.1282593, -7.5472766
could not calculate timezone id for TP10277 at 37.1281963, -7.5472315
could not calculate timezone id for TP10278 at 37.1279618, -7.5472799
could not calculate timezone id for TP10279 at 37.1278344, -7.5479936
could not calculate timezone id for TP10280 at 37.1280913, -7.5479803
could not calculate timezone id for TP10281 at 37.1280193, -7.54803
could not calculate timezone id for TP10282 at 37.1279168, -7.5480822
could not calculate timezone id for TP10283 at 37.1278353, -7.5488684
could not calculate timezone id for TP10284 at 37.1264528, -7.5497111
could not calculate timezone id for TP10285 at 37.126221, -7.5497147
could not calculate timezone id for TP10286 at 37.1263488, -7.5472888
could not calculate timezone id for TP10287 at 37.1262577, -7.5481078
could not calculate timezone id for TP10288 at 37.1261956, -7.5489262
could not calculate timezone id for TP10289 at 37.1278008, -7.5495806
ignoring TP10290, speed above limit: 1266.86 m/s = 4560.68 km/h
could not calculate timezone id for TP10291 at 37.1275778, -7.449342
could not calculate timezone id for TP10292 at 37.1270693, -7.4508663
could not calculate timezone id for TP10293 at 37.126555, -7.4507257
ignoring TP10294, no elevation data.
could not calculate timezone id for TP10295 at 37.1208459, -7.4495983
could not calculate timezone id for TP10296 at 37.1209992, -7.4493776
ignoring TP10297, no elevation data.
ignoring TP10298, no elevation data.
could not calculate timezone id for TP10299 at 37.1269722, -7.449478
could not calculate timezone id for TP10300 at 37.1269636, -7.4496717
could not calculate timezone id for TP10301 at 37.1264262, -7.4491904
could not calculate timezone id for TP10302 at 37.1262222, -7.4489851
could not calculate timezone id for TP10303 at 37.1206657, -7.448864
could not calculate timezone id for TP10304 at 37.1196166, -7.4488928
could not calculate timezone id for TP10305 at 37.1204112, -7.4489211
could not calculate timezone id for TP10306 at 37.1196168, -7.451328
could not calculate timezone id for TP10307 at 37.1204096, -7.4506174
could not calculate timezone id for TP10308 at 37.1197952, -7.4505453
could not calculate timezone id for TP10309 at 37.120416, -7.4497723
ignoring TP10310, no elevation data.
could not calculate timezone id for TP11073 at 36.9920149, -7.7124499
could not calculate timezone id for TP11074 at 36.9931833, -7.703205
could not calculate timezone id for TP11075 at 36.9942833, -7.6939383
ignoring TP11076, elevation above limit: 1771.00
ignoring TP11077, elevation above limit: 1821.00
ignoring TP11078, elevation above limit: 1883.00
ignoring TP11079, elevation above limit: 1953.00
ignoring TP11080, elevation above limit: 2020.00
ignoring TP11081, elevation above limit: 2083.00
ignoring TP11082, elevation above limit: 2146.00
ignoring TP11083, elevation above limit: 2214.00
ignoring TP11084, elevation above limit: 2282.00
ignoring TP11085, elevation above limit: 2347.00
ignoring TP11086, elevation above limit: 2412.00
ignoring TP11087, elevation above limit: 2477.00
ignoring TP11088, elevation above limit: 2545.00
ignoring TP11089, elevation above limit: 2614.00
ignoring TP11090, elevation above limit: 2680.00
ignoring TP11091, elevation above limit: 2741.00
ignoring TP11092, elevation above limit: 2796.00
ignoring TP11093, elevation above limit: 2850.00
ignoring TP11094, elevation above limit: 2905.00
ignoring TP11095, elevation above limit: 2958.00
ignoring TP11096, elevation above limit: 3007.00
ignoring TP11097, elevation above limit: 3056.00
ignoring TP11098, elevation above limit: 3107.00
ignoring TP11099, elevation above limit: 3157.00
ignoring TP11100, elevation above limit: 3209.00
ignoring TP11101, elevation above limit: 3267.00
ignoring TP11102, elevation above limit: 3322.00
ignoring TP11103, elevation above limit: 3371.00
ignoring TP11104, elevation above limit: 3428.00
ignoring TP11105, elevation above limit: 3494.00
ignoring TP11106, elevation above limit: 3562.00
ignoring TP11107, elevation above limit: 3627.00
ignoring TP11108, elevation above limit: 3688.00
ignoring TP11109, elevation above limit: 3744.00
ignoring TP11110, elevation above limit: 3804.00
ignoring TP11111, elevation above limit: 3866.00
ignoring TP11112, elevation above limit: 3924.00
ignoring TP11113, elevation above limit: 3976.00
ignoring TP11114, elevation above limit: 4030.00
ignoring TP11115, elevation above limit: 4087.00
ignoring TP11116, elevation above limit: 4146.00
ignoring TP11117, elevation above limit: 4206.00
ignoring TP11118, elevation above limit: 4265.00
ignoring TP11119, elevation above limit: 4326.00
ignoring TP11120, elevation above limit: 4388.00
ignoring TP11121, elevation above limit: 4450.00
ignoring TP11122, elevation above limit: 4513.00
ignoring TP11123, elevation above limit: 4575.00
ignoring TP11124, elevation above limit: 4635.00
ignoring TP11125, elevation above limit: 4693.00
ignoring TP11126, elevation above limit: 4747.00
ignoring TP11127, elevation above limit: 4803.00
ignoring TP11128, elevation above limit: 4859.00
ignoring TP11129, elevation above limit: 4917.00
ignoring TP11130, elevation above limit: 4976.00
ignoring TP11131, elevation above limit: 5037.00
ignoring TP11132, elevation above limit: 5098.00
ignoring TP11133, elevation above limit: 5160.00
ignoring TP11134, elevation above limit: 5226.00
ignoring TP11135, elevation above limit: 5295.00
creating cache file...
successfully created cache file test.cache
2011-07-24 16:08:00: changed to timezone Africa/Algiers at point TP10243 (37.1198132, -7.5324112)
guessed 65 points
### track elevation stats ###
elevation_maximum=17
elevation_minimum=1
elevation_mean=11
elevation_median=12
elevation_stdev=4
elevation_variance=23
### end track elevation stats ###
processing trackpoints for tzname 'Africa/Algiers'
creating test_Africa_Algiers.gpx for timezone Africa/Algiers Es läuft problemlos durch und von der Höhenstatistik sollte es auch passen. gpsbabel -i gpx -f test_Africa_Algiers.gpx -o kml,units=m -F test_Africa_Algiers.kml Warum finden sich in der kml-Datei Werte, die es nicht geben sollte? zB
<tr><td><b>Max Speed</b> 1071.8 km/hour </td></tr>
<tr><td>Altitude: 8.000 meters </td></tr> kml-Datei im Anhang. Ziel ist es die gpx-Datei möglichst klein werden zu lassen, wenn möglich gar keine Koordinaten mehr zu erhalten.
- test_Africa_Algiers.kml.tar.gz (4.7 KiB)
- Download test_Africa_Algiers.kml.tar.gz
|
seahawk1986
Anmeldungsdatum: 27. Oktober 2006
Beiträge: 11179
Wohnort: München
|
KML nutzt einen Punkt als Dezimaltrennzeichen - 8.000 meters sind 8 Meter - das passt zu den Angaben in der gpx-Datei.
Bei der km/h-Umrechnung hatte ich aus Versehen den Kehrwert des Umrechnungsfaktors genommen, eine korrigierte Version ist angehängt. Dann gibt es das Problem, dass es in der GPX-Datei mehrfach Datenpunkte mit identischem Zeitstempel aber abweichenden Koordinaten gibt - da ist dann die Frage, wie das von gpxbabel bei der Umwandlung gerechnet wird. Mein Skript arbeitet die Wegpunkte bislang in Reihenfolge ab, ohne sie nach Zeitstempeln zu sortieren - dementsprechend zählt nur die Zeitdifferenz und Strecke zwischen zwei aufeinander folgenden Punkten - wenn man sich das mit ausgeben lässt, sieht das für die Datei z.B. so aus:
Speed at waypoint TP10243 is 0.00 km/h (0.00 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10243 at 37.1198132, -7.5324112
Speed at waypoint TP10244 is 297.64 km/h (82.68 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP10244, speed above limit: 82.68 m/s = 297.64 km/h
Speed at waypoint TP10245 is 813.87 km/h (226.08 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP10245, speed above limit: 226.08 m/s = 813.87 km/h
Speed at waypoint TP10246 is 27.99 km/h (7.78 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10246 at 37.1195956, -7.5362224
Speed at waypoint TP10247 is 11.34 km/h (3.15 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10247 at 37.1196344, -7.5366078
Speed at waypoint TP10248 is 400.64 km/h (111.29 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP10248, speed above limit: 111.29 m/s = 400.64 km/h
Speed at waypoint TP10249 is 4.68 km/h (1.30 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10249 at 37.1282712, -7.5397952
Speed at waypoint TP10250 is 33.29 km/h (9.25 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10250 at 37.1278882, -7.542784
Speed at waypoint TP10251 is 13.86 km/h (3.85 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10251 at 37.1279121, -7.5430868
Speed at waypoint TP10252 is 7.31 km/h (2.03 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10252 at 37.1278225, -7.5429728
Speed at waypoint TP10253 is 1.70 km/h (0.47 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP10253, no elevation data.
Speed at waypoint TP10254 is 1.11 km/h (0.31 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10254 at 37.1277874, -7.5431852
Speed at waypoint TP10255 is 8.43 km/h (2.34 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10255 at 37.1277972, -7.5431647
Speed at waypoint TP10256 is 1069.85 km/h (297.18 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP10256, speed above limit: 297.18 m/s = 1069.85 km/h
Speed at waypoint TP10257 is 89.53 km/h (24.87 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10257 at 37.1282998, -7.5467444
Speed at waypoint TP10258 is 0.73 km/h (0.20 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10258 at 37.1282948, -7.5467566
Speed at waypoint TP10259 is 0.00 km/h (0.00 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10259 at 37.1284992, -7.5468283
Speed at waypoint TP10260 is 0.05 km/h (0.01 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10260 at 37.1285008, -7.5468288
Speed at waypoint TP10261 is 0.43 km/h (0.12 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10261 at 37.1285024, -7.5468734
Speed at waypoint TP10262 is 16.39 km/h (4.55 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10262 at 37.1285106, -7.5467196
Speed at waypoint TP10263 is 0.06 km/h (0.02 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10263 at 37.1284992, -7.5467776
Speed at waypoint TP10264 is 142.73 km/h (39.65 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP10264, speed above limit: 39.65 m/s = 142.73 km/h
Speed at waypoint TP10265 is 50.16 km/h (13.93 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10265 at 37.1284969, -7.547136
Speed at waypoint TP10266 is 4.38 km/h (1.22 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10266 at 37.1285057, -7.5472316
Speed at waypoint TP10267 is 52.72 km/h (14.64 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10267 at 37.1283982, -7.547136
Speed at waypoint TP10268 is 0.00 km/h (0.00 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10268 at 37.1284198, -7.5471808
Speed at waypoint TP10269 is 13.14 km/h (3.65 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10269 at 37.1284018, -7.5471743
Speed at waypoint TP10270 is 0.27 km/h (0.08 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10270 at 37.1283985, -7.5471824
Speed at waypoint TP10271 is 41.26 km/h (11.46 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10271 at 37.1285012, -7.5471864
Speed at waypoint TP10272 is 1.10 km/h (0.31 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10272 at 37.1284, -7.5471712
Speed at waypoint TP10273 is 40.43 km/h (11.23 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10273 at 37.1284928, -7.5472214
Speed at waypoint TP10274 is 2.68 km/h (0.74 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10274 at 37.128436, -7.5471964
Speed at waypoint TP10275 is 10.52 km/h (2.92 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10275 at 37.128252, -7.5472008
Speed at waypoint TP10276 is 24.62 km/h (6.84 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10276 at 37.1282593, -7.5472766
Speed at waypoint TP10277 is 3.22 km/h (0.90 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10277 at 37.1281963, -7.5472315
Speed at waypoint TP10278 is 1.15 km/h (0.32 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10278 at 37.1279618, -7.5472799
Speed at waypoint TP10279 is 46.65 km/h (12.96 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10279 at 37.1278344, -7.5479936
Speed at waypoint TP10280 is 20.57 km/h (5.71 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10280 at 37.1280913, -7.5479803
Speed at waypoint TP10281 is 6.58 km/h (1.83 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10281 at 37.1280193, -7.54803
Speed at waypoint TP10282 is 8.85 km/h (2.46 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10282 at 37.1279168, -7.5480822
Speed at waypoint TP10283 is 10.99 km/h (3.05 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10283 at 37.1278353, -7.5488684
Speed at waypoint TP10284 is 614.90 km/h (170.80 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP10284, speed above limit: 170.80 m/s = 614.90 km/h
Speed at waypoint TP10285 is 92.73 km/h (25.76 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10285 at 37.126221, -7.5497147
Speed at waypoint TP10286 is 155.09 km/h (43.08 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP10286, speed above limit: 43.08 m/s = 155.09 km/h
Speed at waypoint TP10287 is 23.98 km/h (6.66 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10287 at 37.1262577, -7.5481078
Speed at waypoint TP10288 is 17.48 km/h (4.86 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10288 at 37.1261956, -7.5489262
Speed at waypoint TP10289 is 96.46 km/h (26.79 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10289 at 37.1278008, -7.5495806
Speed at waypoint TP10290 is 4560.68 km/h (1266.86 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP10290, speed above limit: 1266.86 m/s = 4560.68 km/h
Speed at waypoint TP10291 is 391.61 km/h (108.78 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP10291, speed above limit: 108.78 m/s = 391.61 km/h
Speed at waypoint TP10292 is 105.40 km/h (29.28 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10292 at 37.1270693, -7.4508663
Speed at waypoint TP10293 is 19.15 km/h (5.32 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10293 at 37.126555, -7.4507257
Speed at waypoint TP10294 is 16.31 km/h (4.53 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP10294, no elevation data.
Speed at waypoint TP10295 is 81.74 km/h (22.71 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10295 at 37.1208459, -7.4495983
Speed at waypoint TP10296 is 0.00 km/h (0.00 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10296 at 37.1209992, -7.4493776
Speed at waypoint TP10297 is 0.00 km/h (0.00 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP10297, no elevation data.
Speed at waypoint TP10298 is 36.53 km/h (10.15 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP10298, no elevation data.
Speed at waypoint TP10299 is 8.35 km/h (2.32 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10299 at 37.1269722, -7.449478
Speed at waypoint TP10300 is 7.73 km/h (2.15 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10300 at 37.1269636, -7.4496717
Speed at waypoint TP10301 is 66.04 km/h (18.34 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10301 at 37.1264262, -7.4491904
Speed at waypoint TP10302 is 11.94 km/h (3.32 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10302 at 37.1262222, -7.4489851
Speed at waypoint TP10303 is 1111.56 km/h (308.77 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP10303, speed above limit: 308.77 m/s = 1111.56 km/h
Speed at waypoint TP10304 is 13.12 km/h (3.64 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10304 at 37.1196166, -7.4488928
Speed at waypoint TP10305 is 5.13 km/h (1.42 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10305 at 37.1204112, -7.4489211
Speed at waypoint TP10306 is 166.18 km/h (46.16 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP10306, speed above limit: 46.16 m/s = 166.18 km/h
Speed at waypoint TP10307 is 18.56 km/h (5.16 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10307 at 37.1204096, -7.4506174
Speed at waypoint TP10308 is 0.34 km/h (0.10 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10308 at 37.1197952, -7.4505453
Speed at waypoint TP10309 is 43.75 km/h (12.15 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP10309 at 37.120416, -7.4497723
Speed at waypoint TP10310 is 60.65 km/h (16.85 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP10310, no elevation data.
Speed at waypoint TP11073 is 0.00 km/h (0.00 m/s), max speed 120.00 km/h (33.33 m/s)
could not calculate timezone id for TP11073 at 36.9920149, -7.7124499
Speed at waypoint TP11074 is 598.12 km/h (166.14 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11074, speed above limit: 166.14 m/s = 598.12 km/h
Speed at waypoint TP11075 is 598.65 km/h (166.29 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11075, speed above limit: 166.29 m/s = 598.65 km/h
Speed at waypoint TP11076 is 3257.32 km/h (904.81 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11076, speed above limit: 904.81 m/s = 3257.32 km/h
Speed at waypoint TP11077 is 635.00 km/h (176.39 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11077, speed above limit: 176.39 m/s = 635.00 km/h
Speed at waypoint TP11078 is 643.21 km/h (178.67 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11078, speed above limit: 178.67 m/s = 643.21 km/h
Speed at waypoint TP11079 is 645.17 km/h (179.21 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11079, speed above limit: 179.21 m/s = 645.17 km/h
Speed at waypoint TP11080 is 644.80 km/h (179.11 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11080, speed above limit: 179.11 m/s = 644.80 km/h
Speed at waypoint TP11081 is 646.34 km/h (179.54 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11081, speed above limit: 179.54 m/s = 646.34 km/h
Speed at waypoint TP11082 is 648.60 km/h (180.17 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11082, speed above limit: 180.17 m/s = 648.60 km/h
Speed at waypoint TP11083 is 649.99 km/h (180.55 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11083, speed above limit: 180.55 m/s = 649.99 km/h
Speed at waypoint TP11084 is 650.69 km/h (180.75 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11084, speed above limit: 180.75 m/s = 650.69 km/h
Speed at waypoint TP11085 is 652.12 km/h (181.14 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11085, speed above limit: 181.14 m/s = 652.12 km/h
Speed at waypoint TP11086 is 653.71 km/h (181.59 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11086, speed above limit: 181.59 m/s = 653.71 km/h
Speed at waypoint TP11087 is 655.14 km/h (181.98 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11087, speed above limit: 181.98 m/s = 655.14 km/h
Speed at waypoint TP11088 is 656.65 km/h (182.40 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11088, speed above limit: 182.40 m/s = 656.65 km/h
Speed at waypoint TP11089 is 657.81 km/h (182.72 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11089, speed above limit: 182.72 m/s = 657.81 km/h
Speed at waypoint TP11090 is 659.14 km/h (183.10 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11090, speed above limit: 183.10 m/s = 659.14 km/h
Speed at waypoint TP11091 is 661.06 km/h (183.63 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11091, speed above limit: 183.63 m/s = 661.06 km/h
Speed at waypoint TP11092 is 664.39 km/h (184.55 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11092, speed above limit: 184.55 m/s = 664.39 km/h
Speed at waypoint TP11093 is 668.40 km/h (185.67 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11093, speed above limit: 185.67 m/s = 668.40 km/h
Speed at waypoint TP11094 is 672.05 km/h (186.68 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11094, speed above limit: 186.68 m/s = 672.05 km/h
Speed at waypoint TP11095 is 675.81 km/h (187.73 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11095, speed above limit: 187.73 m/s = 675.81 km/h
Speed at waypoint TP11096 is 680.16 km/h (188.93 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11096, speed above limit: 188.93 m/s = 680.16 km/h
Speed at waypoint TP11097 is 685.02 km/h (190.28 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11097, speed above limit: 190.28 m/s = 685.02 km/h
Speed at waypoint TP11098 is 689.35 km/h (191.49 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11098, speed above limit: 191.49 m/s = 689.35 km/h
Speed at waypoint TP11099 is 693.21 km/h (192.56 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11099, speed above limit: 192.56 m/s = 693.21 km/h
Speed at waypoint TP11100 is 697.16 km/h (193.66 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11100, speed above limit: 193.66 m/s = 697.16 km/h
Speed at waypoint TP11101 is 700.20 km/h (194.50 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11101, speed above limit: 194.50 m/s = 700.20 km/h
Speed at waypoint TP11102 is 702.27 km/h (195.07 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11102, speed above limit: 195.07 m/s = 702.27 km/h
Speed at waypoint TP11103 is 705.40 km/h (195.94 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11103, speed above limit: 195.94 m/s = 705.40 km/h
Speed at waypoint TP11104 is 708.24 km/h (196.73 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11104, speed above limit: 196.73 m/s = 708.24 km/h
Speed at waypoint TP11105 is 708.76 km/h (196.88 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11105, speed above limit: 196.88 m/s = 708.76 km/h
Speed at waypoint TP11106 is 708.43 km/h (196.79 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11106, speed above limit: 196.79 m/s = 708.43 km/h
Speed at waypoint TP11107 is 708.53 km/h (196.81 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11107, speed above limit: 196.81 m/s = 708.53 km/h
Speed at waypoint TP11108 is 709.42 km/h (197.06 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11108, speed above limit: 197.06 m/s = 709.42 km/h
Speed at waypoint TP11109 is 711.18 km/h (197.55 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11109, speed above limit: 197.55 m/s = 711.18 km/h
Speed at waypoint TP11110 is 712.97 km/h (198.05 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11110, speed above limit: 198.05 m/s = 712.97 km/h
Speed at waypoint TP11111 is 714.03 km/h (198.34 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11111, speed above limit: 198.34 m/s = 714.03 km/h
Speed at waypoint TP11112 is 715.77 km/h (198.83 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11112, speed above limit: 198.83 m/s = 715.77 km/h
Speed at waypoint TP11113 is 718.77 km/h (199.66 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11113, speed above limit: 199.66 m/s = 718.77 km/h
Speed at waypoint TP11114 is 721.97 km/h (200.55 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11114, speed above limit: 200.55 m/s = 721.97 km/h
Speed at waypoint TP11115 is 724.50 km/h (201.25 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11115, speed above limit: 201.25 m/s = 724.50 km/h
Speed at waypoint TP11116 is 726.61 km/h (201.83 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11116, speed above limit: 201.83 m/s = 726.61 km/h
Speed at waypoint TP11117 is 728.55 km/h (202.37 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11117, speed above limit: 202.37 m/s = 728.55 km/h
Speed at waypoint TP11118 is 730.60 km/h (202.94 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11118, speed above limit: 202.94 m/s = 730.60 km/h
Speed at waypoint TP11119 is 732.54 km/h (203.48 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11119, speed above limit: 203.48 m/s = 732.54 km/h
Speed at waypoint TP11120 is 734.17 km/h (203.94 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11120, speed above limit: 203.94 m/s = 734.17 km/h
Speed at waypoint TP11121 is 735.76 km/h (204.38 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11121, speed above limit: 204.38 m/s = 735.76 km/h
Speed at waypoint TP11122 is 737.23 km/h (204.79 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11122, speed above limit: 204.79 m/s = 737.23 km/h
Speed at waypoint TP11123 is 738.92 km/h (205.26 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11123, speed above limit: 205.26 m/s = 738.92 km/h
Speed at waypoint TP11124 is 740.91 km/h (205.81 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11124, speed above limit: 205.81 m/s = 740.91 km/h
Speed at waypoint TP11125 is 743.42 km/h (206.51 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11125, speed above limit: 206.51 m/s = 743.42 km/h
Speed at waypoint TP11126 is 746.34 km/h (207.32 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11126, speed above limit: 207.32 m/s = 746.34 km/h
Speed at waypoint TP11127 is 749.64 km/h (208.23 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11127, speed above limit: 208.23 m/s = 749.64 km/h
Speed at waypoint TP11128 is 752.63 km/h (209.06 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11128, speed above limit: 209.06 m/s = 752.63 km/h
Speed at waypoint TP11129 is 755.49 km/h (209.86 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11129, speed above limit: 209.86 m/s = 755.49 km/h
Speed at waypoint TP11130 is 757.93 km/h (210.54 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11130, speed above limit: 210.54 m/s = 757.93 km/h
Speed at waypoint TP11131 is 760.21 km/h (211.17 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11131, speed above limit: 211.17 m/s = 760.21 km/h
Speed at waypoint TP11132 is 761.83 km/h (211.62 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11132, speed above limit: 211.62 m/s = 761.83 km/h
Speed at waypoint TP11133 is 763.86 km/h (212.18 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11133, speed above limit: 212.18 m/s = 763.86 km/h
Speed at waypoint TP11134 is 765.30 km/h (212.58 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11134, speed above limit: 212.58 m/s = 765.30 km/h
Speed at waypoint TP11135 is 765.75 km/h (212.71 m/s), max speed 120.00 km/h (33.33 m/s)
ignoring TP11135, speed above limit: 212.71 m/s = 765.75 km/h
Wenn es so total kaputte Daten gibt, kann man die doch eigentlich einfach so löschen, ohne Filter darauf anzuwenden.
- geoinfo.tar.xz (7.7 KiB)
- Download geoinfo.tar.xz
|
glaskugel
(Themenstarter)
Anmeldungsdatum: 8. Juli 2010
Beiträge: 3453
|
Wenn es so total kaputte Daten gibt, kann man die doch eigentlich einfach so löschen, ohne Filter darauf anzuwenden.
In der Praxis natürlich. Die komplette Algier-Datei ist für den Müll, da bei den dortigen Koordinaten niemand war, aber eine schöne Testdatei um die Grenzen der Logik von Filtern zu sehen 😉 Was mir bei einer anderen gpx-Datei aufgefallen ist, Zeit später als die aktuelle Zeit, kann man rauswerfen, ich glaube, da hatten wir schon mal so einen Fall. Auch kann man eine negative Elevation von -1000 sicher rauswerfen, hatte da was konkret. Die Frage ist nur, bis welche negative Elevation man Tracks behalten soll.
Mein Skript arbeitet die Wegpunkte bislang in Reihenfolge ab, ohne sie nach Zeitstempeln zu sortieren - dementsprechend zählt nur die Zeitdifferenz und Strecke zwischen zwei aufeinander folgenden Punkten
Das finde ich so gut. Kennst du eigentlich was besseres als Marble um Trackpoints mit Informationen darzustellen? Marble fangt mir immer zu wandern an, wenn ich ins Bild zoome und dann ist es irgendwo. Edit man könnte für die elevation auch 2 Grenzen machen, das scheint mir in Verbindung mit einem Defaultwert die flexibelste Variante. Edit2: Beispielscreenshot für negative Elevation angehängt.
- Bilder
|
seahawk1986
Anmeldungsdatum: 27. Oktober 2006
Beiträge: 11179
Wohnort: München
|
glaskugel schrieb: Was mir bei einer anderen gpx-Datei aufgefallen ist, Zeit später als die aktuelle Zeit, kann man rauswerfen, ich glaube, da hatten wir schon mal so einen Fall.
Dann ändert sich aber der gefilterte Datensatz abhängig von der Systemzeit... Auch kann man eine negative Elevation von -1000 sicher rauswerfen, hatte da was konkret. Die Frage ist nur, bis welche negative Elevation man Tracks behalten soll.
Das hängt davon ab, ob man auch in Stollen, Höhlensystemen und der Tiefsee unterwegs ist (es gibt ja tolle Geräte, die verschiedene Messverfahren für die Positionsbestimmung kombinieren) - wenn es nur um Landsenken geht, kommt man normalerweise so bis ca. -420m: Erde/Daten_und_Zahlen
Kennst du eigentlich was besseres als Marble um Trackpoints mit Informationen darzustellen? Marble fangt mir immer zu wandern an, wenn ich ins Bild zoome und dann ist es irgendwo.
Google Earth kann das recht passabel, aber bei Datensalat leidet die Übersichtlichkeit ziemlich. Edit man könnte für die elevation auch 2 Grenzen machen, das scheint mir in Verbindung mit einem Defaultwert die flexibelste Variante.
Meinetwegen - wobei eine bessere Messtechnik sicherlich auch kein Nachteil wäre - mit GPS in Kobination mit GLONASS und einer gut positionierten Antenne am Autodach bzw. an der Kopfbedeckung müsste eigentlich einiges bringen...
|
glaskugel
(Themenstarter)
Anmeldungsdatum: 8. Juli 2010
Beiträge: 3453
|
Dann ändert sich aber der gefilterte Datensatz abhängig von der Systemzeit...
Ist klar, aber 2060 ist jedenfalls ein Kandidat für Müll. Ich denke, es reicht auch +24 oder +48h zu nehmen, hatte bis jetzt immer Extremwerte in der Zukunft
Meinetwegen - wobei eine bessere Messtechnik sicherlich auch kein Nachteil wäre - mit GPS in Kobination mit GLONASS
Oh ja, hatte dazu schon auch im Thread mein Problem angesprochen, dass es IMHO zur Zeit nichts brauchbares zu kaufen gibt. Hast du eine Empfehlung? War letztens im Zug unterwegs, mit dem Handy (Zuk Z1 mit Glonass und Baidu zusätzlich) kein brauchbarer Sync, aber 20 Satelliten gefunden, obwohl das bei mir zu Hause auch innen relativ schnell einen Fix hat, interessanter Weise kamen im Zug hauptsächliche Baidu-Satelliten, die werden sonst nur selten gelistet. Ich möchte aber max. nicht viel mehr als 100€ ausgeben. Unabhängig davon, muss man mit den alten gpx-Dateien auch irgendwie klar kommen und natürlich nehme ich zum Testen problematische gpx-Dateien, wo Leute den Logger einfach eingesteckt hatten. Ich denke eine Antenne am Autodach braucht es nicht, hatte bei meinen GPS-Aufzeichnungen noch nie Probleme, wenn das GPS in der Fototasche am Rücksitz des Autos war oder unten in der Konsole lag. In der Praxis gibt es meist nur Probleme nach dem Besuch von Gebäuden und kurz darauf einem Foto.
|
glaskugel
(Themenstarter)
Anmeldungsdatum: 8. Juli 2010
Beiträge: 3453
|
Ist klar, aber 2060 ist jedenfalls ein Kandidat für Müll. Ich denke, es reicht auch +24 oder +48h zu nehmen, hatte bis jetzt immer Extremwerte in der Zukunft
Das ist aber doch ein Denkfehler von mir, zur Zeit eher kein Problem, aber irgendwann kann das ein Problem werden, wenn man nicht nach Datum, ich denke Jahr reicht, filtern kann.
|
seahawk1986
Anmeldungsdatum: 27. Oktober 2006
Beiträge: 11179
Wohnort: München
|
gpsbabel kann soweit ich das gelesen habe nach Datum filtern - https://www.gpsbabel.org/htmldoc-1.5.3/filter_track.html Beispiel 4.10
|
glaskugel
(Themenstarter)
Anmeldungsdatum: 8. Juli 2010
Beiträge: 3453
|
Da hast du natürlich recht, verwende ich ja sehr viel, aber man muss dann doppelt in 2 Abfragen filtern.
|
glaskugel
(Themenstarter)
Anmeldungsdatum: 8. Juli 2010
Beiträge: 3453
|
invalid response from geonames elevation api
invalid literal for int() with base 10: 'ERR:19:the hourly limit of 2000 credits for ... has been exceeded. Please throttle your requests or use the commercial service.' Könntest du vielleicht in diesem Fall eine Meldung ähnlich "successfully queried googlemaps" bzw. eine Meldung ausgeben, dass die Google-Abfrage auch nicht erfolgreich war. Ich habe trotzdem einen Höhenwert in meiner Variablen, kann aber zur Zeit nicht testen, ob die dann von Google kam oder Geonames tolerant ist und noch ein paar Abfragen toleriert. Es könnte sein, dass ich die vielen Abfragen beim Aufbauen des Caches mache. Ich werte jetzt "elevation_source=" aus und da kommt in der Regel gpx. Ich muss aber auch dazu sagen, dass ich noch ohne Filtern teste um zu schauen, wo es Probleme gibt. Insofern wäre eine Warnung gut, wenn der Cache nicht richtig aufgebaut werden konnte und beim nächsten Mal sollte der Cache automatisch neu gebildert werden (Wenn so was nicht allzu schwer umzusetzen ist) Eventuell könnte das Script auch 1h warten, wenn Google auch verbraucht ist. Das ist speziell dann interessant, wenn automatisiert viele Fotoalben berechnet werden sollen.
|
glaskugel
(Themenstarter)
Anmeldungsdatum: 8. Juli 2010
Beiträge: 3453
|
In der Praxis kann man also schon Probleme mit den Credits bekommen, daher habe ich mir ein Bash-Script gebaut, dass das gpx-File nach Tagen splittet. Im Urlaub kann es ja oft sein, dass man den einen Tag einen Ausflug nach A macht und den anderen nach B und man die Fotos dazu jeweils in ein eigenes Album gibt. Dadurch reduziert man die benötigten Credits deutlich, wenn man nicht in jedem Album alle Tracks des Urlaubs hat, Habe gerade festgestellt, dass das nicht mit allen gpx-Dateien funktionieren muss! 1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48 | #!/bin/bash
# das Script sucht unterhalb eines Verzeichnisses alle gpx-files und splittet es nach Tagen
# In einem 2. Schritt teilt geoinfo.py den Tag nach Zeitzonen auf und eliminiert ungültige Daten
# in einem nächsten Schritt könnte man dann manuell weiter filtern
MYGEOINFO="/usr/local/bin/geoinfo.py"
NUTZER=`whoami`
if [ $NUTZER = "xx" ]; then
GOOGLEAPI="bla"
GEONAMESUSER="aa"
elif [ $NUTZER = "yy" ]; then
GOOGLEAPI="blub"
GEONAMESUSER="bb"
fi
find "$1" -type f -name "*.gpx" | sort -u | while read -r gpxfile; do
cd "$1"
outputdirpart=`pwd`"_daysplits"
filepart=`basename "$gpxfile" ".gpx"`
echo "splitting $gpxfile"
#splitdays=`grep time "$gpxfile" | cut -f2 -d">" | cut -f1 -d"T" | sort -u | sed 's/-//g' | tr '\n' ' '`
# passt bis jetzt bei allen gpx-Files, mit denen ich das Script probiert habe, kann aber durchaus noch gpx-Files geben, die nicht funktionieren!
splitdays=`grep time "$gpxfile" | sed -e 's/<time>/#/g' -e 's/<\/time>/#/g' | cut -f2 -d"#" | cut -f2 -d">" | cut -f1 -d"T" | sort -u | sed 's/-//g' | tr '\n' ' '`
for day in $splitdays; do
echo
echo "Day $day"
outputdir="$outputdirpart""/$day"
mkdir -p "$outputdir"
starttime="$day"00
# Achtung, da gibt es noch Fehler am Letzten des Monats!
endtime=$(($day+1))00
gpxoutputfile="$outputdir""/$filepart""_$day"".gpx"
kmloutputfile="$outputdir""/$filepart""_$day"".kml"
logfile="$outputdir""/$filepart""_$day"".log"
echo "creating $gpxoutputfile"
gpsbabel -i gpx -f "$gpxfile" -x track,start=$starttime,stop=$endtime -o gpx -F "$gpxoutputfile"
gpsbabel -i gpx -f "$gpxoutputfile" -o kml,units=m -F "$kmloutputfile"
#python3 $MYGEOINFO -a "$GOOGLEAPI" -u "$GEONAMESUSER" --tzsplit "$gpxoutputfile"
python3 $MYGEOINFO -a "$GOOGLEAPI" -u "$GEONAMESUSER" --tzsplit "$gpxoutputfile" 2>&1 > "$logfile"
done
done
|
Kritik am Script ist ausdrücklich erwünscht.
|
glaskugel
(Themenstarter)
Anmeldungsdatum: 8. Juli 2010
Beiträge: 3453
|
Ich habe gerade festgestellt, das mit einem gpx-File aus dem Handy --tzsplit nicht funktioniert, dh Länder werden nicht getrennt. Das gpx-File hat einen anderen Aufbau als "gewöhnlich". Testfile im Anhang. Interessanterweise gab es da bei sintflutartigem Regen und vielen Tunnel keine extremen Ausreißer, obwohl das Handy unten in der Konsole im Auto lag und lief solange der Akku hielt. Auch der Katschbergtunnel ist ok. Die Handyapp wurde einfach vergessen auszuschalten und wurde eigentlich nur in Piran verwendet, da der GPS-Logger im Parkhaus vergessen wurde. Es ist das gleiche Handy wie bei dem Beispiel mit den Tunnel um Linz. Ich glaube, dass in diesem Fall, dass Logginintervall sehr lang war, 30 sec?
- piran_handy.gpx.tar.gz (9.1 KiB)
- Download piran_handy.gpx.tar.gz
|