[gps-talkusers] Re: problem with address lookup

Folks,

I believe that, in keeping with BN jargon, it would be helpful to say that key stroke as known, space with E, and not escape. Once we start mixing and matching and muddying waters, down will go standards. (One key stroke wrongly described becomes the next . . ..) I know Carl wouldn't want this to be the case as Sendero want to keep high standards. <Smile>

Well, that's what I think.

As for time and effort in fixing it . . . I don't have a clue about that, so in the end, I guess Sendero must judge.

--
Carol
carol.pearson@xxxxxxxxxxxx




----- Original Message ----- From: "Sarah Lanier" <bioinstructor02@xxxxxxxxx>
To: <gps-talkusers@xxxxxxxxxxxxx>
Sent: Tuesday, September 19, 2006 2:00 AM
Subject: [gps-talkusers] Re: problem with address lookup


Hi Carl,

I think just a note in the manual that explains the space with e=escape key
would be handy, because honestly, I had no idea what it meant, myself, and
I've been a Braile Keyboard users from the beginning--of my use with such
devices. I only really remember this issue cropping up once or twice, and
as I recall, I had to perform a reset to exit the program and fix the
problem--but I don't remember the circumstances surrounding it--and I was
just learning, so I probably just figured I had no clue.

Sarah


-----Original Message-----
From: gps-talkusers-bounce@xxxxxxxxxxxxx
[mailto:gps-talkusers-bounce@xxxxxxxxxxxxx] On Behalf Of Carl Simmons
Sent: Monday, September 18, 2006 11:48 AM
To: gps-talkusers@xxxxxxxxxxxxx
Subject: [gps-talkusers] Re: problem with address lookup

Sarai,

I will admit if this is directed to the escape key it would not be correct
for the BT keyboard.  Many Braille keyboard users refer to the cord E
command as escape, as other keyboard commands like the cord dot 4 and cord
dot 1 as up and down keys.

These terms have been derived from many Braille users and I question if
there should be a change. I will keep an open mind about this subject. I
would like to hear from our users if this wording change would be of use or
justify the time and expense required to make the change.

Carl Simmons
Sendero Group Training and Technical Support 1-888-757-6810 Ext. 106
carl@xxxxxxxxxxxxxxxx



-----Original Message-----
From: gps-talkusers-bounce@xxxxxxxxxxxxx
[mailto:gps-talkusers-bounce@xxxxxxxxxxxxx] On Behalf Of Sarai
Sent: Monday, September 18, 2006 6:57 AM
To: gps-talkusers@xxxxxxxxxxxxx
Subject: [gps-talkusers] Re: problem with address lookup

Another problem, on the BT units, is when you abort a look up, or can't find
what your looking for; you receive the message saying press escape to use
the nearest address. That's a QT command.

Sarai D. Bucciarelli

-----Original Message-----
From: gps-talkusers-bounce@xxxxxxxxxxxxx
[mailto:gps-talkusers-bounce@xxxxxxxxxxxxx] On Behalf Of Carl Simmons
Sent: Monday, September 18, 2006 1:12 AM
To: gps-talkusers@xxxxxxxxxxxxx
Subject: [gps-talkusers] Re: problem with address lookup


Phil,
I have reproduced this error and I have found two issues with this address
lookup. I think you were looking for the Holiday Inn zip code
29223 at that address. When I place my virtual position to the HOLIDAY Inn
at that address, I check the city and find it is in the city of Dentsville.
The address of the POI states the city is Columbia. This appears to be a
map issue. I do not suspect a Keysoft 7.2 issue or a Version 3.5 issue.

The address lookup aborted message issue does appear to be a problem in the
Sendero GPS program. I will be following up on this tomorrow.

Thank you for bringing this problem to my attention and we will be back to
as soon as I have additional information.

Carl Simmons
Sendero Group Training and Technical Support 1-888-757-6810 Ext. 106
carl@xxxxxxxxxxxxxxxx

-----Original Message-----
From: gps-talkusers-bounce@xxxxxxxxxxxxx
[mailto:gps-talkusers-bounce@xxxxxxxxxxxxx] On Behalf Of Kevin Chao
Sent: Sunday, September 17, 2006 9:53 PM
To: gps-talkusers@xxxxxxxxxxxxx
Subject: [gps-talkusers] Re: problem with address lookup

Phil,

I just tried what you outlined below, with the same results. I am not sure
as to why this is happening, but I can say that the address lookup function
has worked for me in the past flawlessly. The only thing that I can say is
that it is excellent that you have found a work-around by using the POI
lookup, this is the route that I would also go if I were you. It is a very
nice thing that there exist such a thing as multiple-modes of looking up

information. Some of the ways including by lat/lon, POI's, and address.

Kevin
----- Original Message -----
From: "Philip Hall" <phall1246@xxxxxxxxxxxxx>
To: <gps-talkusers@xxxxxxxxxxxxx>
Sent: Sunday, September 17, 2006 5:56 PM
Subject: [gps-talkusers] problem with address lookup


Hi. I am trying to use address lookup. I have an MPower bt running
keysoft


7.2 and gps v3.5.
I press s-chord, select the state:  south carolina.
I enter the city:  columbia
I enter the street name:  two notch rd
I then try to enter an address: 7510
i immediately get a message,   address lookup aborted.

the address does exist, i can just use f-chord
and find the particular hotel manually, and set it as my virtual
address.

but, why doesn't address lookup work?
I have tried other known addresses and it doesn't seem to work. I
usually have to just let it find cross streets and then use lookup
around mode to find the location before setting it as my virtual
position.

phil












Other related posts: