Moving to new location
|
Jon W7SEA
I’m trying to follow the Wiki’s instructions on how to move my location, but, when I click “Transmit,” “Move ME to Center” does not appear? Can’t seem to figure out how to move it….
|
|
|
|
Adam Mahnke
Try zooming in further. It has to be zoomed in quite a ways, I just don't remember how far. Adam KC2ANT On Mon, Jan 23, 2023 at 5:17 PM Jon W7SEA <jonw7sea@...> wrote: I’m trying to follow the Wiki’s instructions on how to move my location, but, when I click “Transmit,” “Move ME to Center” does not appear? Can’t seem to figure out how to move it…. |
|
|
|
Jon W7SEA
Adam, thank you--that was the problem.
|
|
|
|
Adam Mahnke
No problem, been there, done that. 73 Adam KC2ANT On Mon, Jan 23, 2023, 17:52 Jon W7SEA <jonw7sea@...> wrote: Adam, thank you--that was the problem. |
|
|
|
Lynn Deffenbaugh
The reason for requiring a pretty-tight zoom before offering to
Move ME is to make sure you are really centered where you want to
be. If you're zoomed out too far, one pixel on the map is a
pretty large area within which to solve for a specific coordinate. Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 1/23/2023 5:54 PM, Adam Mahnke
wrote:
|
|
|
|
Greg D
A thought for a feature enhancement...? APRS includes the concept
of location ambiguity. Perhaps the amount you're zoomed in could be
reflected in an initial setting for that? Less zoom, fewer digits.
toggle quoted message
Show quoted text
Greg KO6TH Lynn Deffenbaugh wrote:
|
|
|
|
Adam Mahnke
Only downside is when I want to force a beacon when I'm not centered on myself Adam KC2ANT On Mon, Jan 23, 2023, 21:05 Greg D <ko6th.greg@...> wrote:
|
|
|
|
Lynn Deffenbaugh
Transmit is still there at the further out zooms, it's just that
it doesn't offer the "Move ME" question. Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 1/23/2023 9:07 PM, Adam Mahnke
wrote:
|
|
|
|
Lynn Deffenbaugh
Personally, I find APRS's ambiguity rather humorous for a lot of stations that are using it. For instance, digipeater towers that transmit ambiguity when you can probably see the tower from anywhere within the ambiguous distance. And mobiles that transmit ambiguity when it only affects one of the lat/lon values while the other is fully transmitted. And if your mobile along a road, it's usually pretty obvious from your (ambiguous) track which road you're actually following. But for those that want to do it, there is Configure / Beacon /
Precision with the +/- options that generate ambiguous posit
packets. Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 1/23/2023 9:05 PM, Greg D wrote:
A thought for a feature enhancement...? APRS includes the concept of location ambiguity. Perhaps the amount you're zoomed in could be reflected in an initial setting for that? Less zoom, fewer digits. |
|
|
|
Greg D
Sure. I was just thinking that accepting a zoom level not
acceptable by the current code could be turned into a "feature"
where it's accepted and turned into a less precise mapping. Of
course, then you have the potential for a service call due to an
apparently incorrect placement, which could have been prevented by
annoying them into zooming in enough in the first place. Choice of
poison, I guess.
toggle quoted message
Show quoted text
Greg KO6TH Lynn Deffenbaugh wrote:
|
|
|
|
Rob Giuliano
On Mon, Jan 23, 2023 at 10:41 PM, Greg D wrote:
Sure. I was just thinking that accepting a zoom level not acceptable by the current code could be turned into a "feature" where it's accepted and turned into a less precise mapping. Of course, then you have the potential for a service call due to an apparently incorrect placement, which could have been prevented by annoying them into zooming in enough in the first place. Choice of poison, I guess.EXACTLY! I am pretty sure that kind of option would draw more headaches than it solves. I can't say how long APRSIS32 has been around, but I can count on just both hands how many times I've seen this question in the MANY years I have been a part of the group. I go back until at least August of 2010. ----- Rob KB8RCO |
|
|