FIND doesn't

I must not grasp what FIND is supposed to do....or perhaps how.

I enter a street address say [FONT=Century Gothic]7400 Temple Hill Rd[/FONT], with Location [FONT=Century Gothic]center of screen[/FONT] and A[FONT=Century Gothic]ddresses[/FONT] set. [It's near Andrews AFB.]

(I'm looking at the address in question center-screen; I found it by dropping lat/long from Google Map into the Locate Coordinates, which does work.)

I hit [FONT=Century Gothic]search[/FONT]. It barber-poles as it searches, and searches, and searches. Nothing.

The address is shown in the middle of the screen; it keeps looking. Hitting [FONT=Arial Black]X[/FONT] or[FONT=Century Gothic] STOP[/FONT] does nothing. It keeps going.

I have similar results on most address searches, but not all. Some work.

Suggestions?

First, you should be using the latest version of BaseCamp; v4.2.2. Second BaseCamp searches are only as good as the data coding in the maps you are searching. Google has 300,000 computers and several hundred terabytes of map data and does natural language searches. Your little cheep computer has ... well, less.

Okay, sorry for the jab. Because of how data is coded in desktop/gps digital maps you need to give much less information in your search. Just start with the street name: e.g, Temple Hill. Then when you find it, you can enter the number but I've found marginal number indexing in most places using City Navigator North America.

Using "Temple Hill" I could not find the address in BC 4.2.2 (Mac) with the map centered on that part of MD. Using just "Temple" it found it in about 15 seconds on an iMac i3 3.2 gHz running OS 10.8.

But for the OP, there's another clue in his post: using X or Apple-period will not stop the search. That means something else is wrong here and needs to be corrected before even the existing clumsy search will work. I'd start by checking how much disk cache is in use by BC. It would also be useful to know what Mac with what processor and OS you are using. BC makes the machine work very hard.

Once that's squared away, another tip for searching is to specify city or town. With the map centered on my home on Cape Cod, I typed "Temple Hill" into the search box, then under Options began typing "Temple" into the Location box. I let it supply choices because it is very fussy about format and punctuation, and clicked on "Temple Hills, MD, USA" (requires the commas) and it found your address in two seconds.

-dan

There appears to be an issue with finding addresses in the next state. When I was centered in MD pretty much anywhere within 50 miles of the address, I found it almost immediately. As soon as I centered over Va it didn't work. We'll take a look at this. I had no issue stopping the search and restarting it using X or Cmnd-. . Can you try that again after just a few seconds of searching and see at what point it become non-responsive. Sorry for the inconvenience.

There appears to be an issue with finding addresses in the next state. When I was centered in MD pretty much anywhere within 50 miles of the address, I found it almost immediately. As soon as I centered over Va it didn't work. We'll take a look at this. I had no issue stopping the search and restarting it using X or Cmnd-. . Can you try that again after just a few seconds of searching and see at what point it become non-responsive. Sorry for the inconvenience.

It works fine if you are many states away, in case that helps. Centered on Cape Cod in MA and supplying the town in the Location window it grabbed the address right away.

-dan

A shot in the dark, but is the inability to stop the search happening with your GPS connected? If so, try it without. If it then stops properly, BC is apparently trying to load maps or data from the SD card and hanging during that process, maybe?

-dan

It works fine if you are many states away, in case that helps. Centered on Cape Cod in MA and supplying the town in the Location window it grabbed the address right away.

-dan

Yes I meant only in the case when you are using the center of the screen. If you specify the location, the first operation is to center the map at the specified location.

I use a MacBook Pro @ 2.7Ghz, 16GB Mem. I also set my BaseCamp Preferences->Advanced->Disk Cache Size to max: 5GB.

I usually construct my Address searches the way DANHAM mentioned, which is to put the City or State into the Location field (Options) and then type the Address into the search field. Seems to work most of the time for me. If I don't get a hit that's when I start removing info like Street Number. But, it would appear that you have another problem going on if you can't stop the search once started.

In the case of your search I just entered Andrews AFB into the Location field. If I don't get hits within a second or two I usually stop the search and adjust my search string. Obviously not something that is working of you at the moment.

"But, it would appear that you have another problem going on if you can't stop the search once started."

This is why I'm wondering if Mathesar's Mac is trying to "find" data, such as on a mounted external drive, and load it into BC, slowing everything to a crawl.

-dan

I recall once having similar searching issues with one of my maps (only one) so I deleted the map from my system and reinstalled it. Do you have multiple maps installed that you could check to see if your BC search hangs on them as well? Or, if you have the DVD for your map (CNNA I presume) and you have the latest update file you reinstall CNNA to see if that helps your issue.

Just "searching" for a solution...not sure it will help.

I have only one set of maps; CityNav V8.
(Garmin will not sell me anything newer, alas....)

CityNav v8 is part of your problem. But, try that again..."Garmin will not sell you anything newer?" Sure they will...but, maybe your GPS can't use anything newer. What model GPS do you have?