BaseCamp Address Searching

Discussion in 'Mapping & Navigation' started by Emoto, Apr 22, 2013.

  1. Emoto

    Emoto Sure, why not?

    Joined:
    Feb 24, 2004
    Oddometer:
    19,954
    Location:
    SE Mass
    So, I plugged in an address for a town hall and senior center that was holding a class I wanted to attend. Here is the address, try it!

    135 School St., Walpole, MA 02032

    BaseCamp sends me to VT!!!! :baldy

    After much hopping around and gnashing of teeth, I discovered that BaseCamp would only find the correct place if I put the address in this way:

    135 School St., Walpole Twn, MA 02032

    How idiotic is that? How can one know whether Twn is needed or not? :huh
    #1
  2. dlh62c

    dlh62c Long timer

    Joined:
    Jan 11, 2006
    Oddometer:
    1,603
    I did. BC seemed to work fine. It didn't send me to VT.

    BC displayed '135 School St., Walpole Twn, MA 02032' at the top of the search list.

    daryl
    #2
  3. Emoto

    Emoto Sure, why not?

    Joined:
    Feb 24, 2004
    Oddometer:
    19,954
    Location:
    SE Mass
    Really? It sends me to Westminster VT! :lol3

    What on earth am I doing wrong? :eek1

    Give me a minute and I'll upload a pic of my results. Maybe you or someone can point out the error in my ways.

    ETA: Ok, here is what I get:

    [​IMG]
    #3
  4. Emoto

    Emoto Sure, why not?

    Joined:
    Feb 24, 2004
    Oddometer:
    19,954
    Location:
    SE Mass
    So... upon further poking around...

    If on the main menu along the top of BaseCamp, I choose FIND > FIND OPTIONS

    [​IMG]

    Then, over on the right hand side of the screen, I select the radio button for Addresses:

    [​IMG]

    And then, start to type the town name into the text box, a list of available towns will appear, and I can choose one by clicking on it:

    [​IMG]

    With the town selected as shown above, if I enter the number and street in the top text box, I can then hit the search icon, and I will get the correct results! :clap :lol3

    [​IMG]

    Correct result:

    [​IMG]

    So... to summarize, putting the full address in the search box fails to return the correct result, unless you know to put "TWN" in the text box after the town name. Not every town requires this. OTOH, if you build your search under find options > addresses, you can choose the town and see if it has (needs) a TWN or not, then add the rest of the street address above, and voila, good result.

    How far from intuitive can they possibly make things? :yikes :rofl
    #4
  5. DRTBYK

    DRTBYK All Things GPS

    Joined:
    Mar 26, 2003
    Oddometer:
    6,318
    Location:
    47°50′15.8″N, 119°56′21.9″W
    Considering that BaseCamp doesn't have a very large array of computers with Natural Language Search capabilities, I think it does OK with the map data it has to work with - it can and will get better in v4.2. But, as you have discovered, the best way to use search in BaseCamp is to start your search with minimal info in the search field along with narrowing your search objective (Addresses for example) is the most productive. Remember, BaseCamp isn't going to know what you "meant". It only knows what you type and then tries to find the match in the map data.

    The more info you give BC to look for [an exact match] the lower the odds of finding it if there is an error in your search string - like TWN. Oh, and remember that the data in the map may not be correct - or the way the locals write it.

    Cheers,
    #5
  6. Emoto

    Emoto Sure, why not?

    Joined:
    Feb 24, 2004
    Oddometer:
    19,954
    Location:
    SE Mass
    I guess I was fooled by the nice big search box that looked just right for a complete address. :lol3

    Silly me. :baldy

    The "Twn" thing is somewhat baffling to me. I suspect that it is an artifact of Navtech (sp?) map data that is not being handled gracefully. Having seen a few places on the Garmin maps where Twn follows the town name when it is not used in real life, it would seem like they ought to do a little mapping or defines work in the BaseCamp db so that Twn can be a separate field in the name that is optional.

    Now that I have figured out how to do a search it is no longer problematic, but Garmin should really get their DBAs to classify this type of data element in such a way as to make it not a show stopper when searching. It can be done. :nod
    #6
  7. Emmbeedee

    Emmbeedee Procrastinators

    Joined:
    Mar 19, 2008
    Oddometer:
    10,108
    Location:
    Near Ottawa, ON, Canada
    That seems to be the way for any search; the more data you put in, the less likely it is to find it. When I was in IT, I often had people complain that when they used an online staff directory, and put in a whole persons name and other search criteria, they never found the person. I had to tell them to enter only enough information to make the search fairly unique, to cut down on false positives...

    But often the less you put in, the better.
    #7
  8. Emoto

    Emoto Sure, why not?

    Joined:
    Feb 24, 2004
    Oddometer:
    19,954
    Location:
    SE Mass
    It is certainly a process getting to know how to use BaseCamp effectively. I note that in MapSource, it forces you to build an address search piece by piece, therefore sidestepping the problem.

    IMO, the problem I ran into is the pesky "Twn" appended to some town names but not others. Again, "135 School St., Walpole, MA 02032" fails to find that place, but "135 School St., Walpole Twn, MA 02032" finds the correct place.

    I brought this up in the Garmin forums and it seems to have gotten some interest. I don't know the players over there well enough to know who is really connected to Garmin, but I did get a response from someone saying he thought "we could fix it" so maybe that will happen. :dunno

    At any rate,at least now I know how to search effectively, and I hope this thread might help someone else who is scratching their head.
    #8
  9. Britome

    Britome Get Free

    Joined:
    Nov 7, 2009
    Oddometer:
    1,206
    Location:
    Cincinnati, OH
    The only way to get this and many other problems solved are to put our hopes in Google.

    There needs to be a competitive platform. Basecamp sucks and there is no incentive for Garmin to improve it.
    #9
  10. DRTBYK

    DRTBYK All Things GPS

    Joined:
    Mar 26, 2003
    Oddometer:
    6,318
    Location:
    47°50′15.8″N, 119°56′21.9″W
    Put my hopes in Google? Now that's funny...:rofl
    #10
  11. Emmbeedee

    Emmbeedee Procrastinators

    Joined:
    Mar 19, 2008
    Oddometer:
    10,108
    Location:
    Near Ottawa, ON, Canada
    I suppose you don't believe in Santa Claus too?
    #11
  12. guavadude

    guavadude de-composer

    Joined:
    Aug 31, 2009
    Oddometer:
    915
    Location:
    Dallas, TX
    I don't know about putting my hopes in Google, but I gave up on BC after a few tries to find locations. I doubt if Garmin will ever have the database that Google has. I think the best plan is learn how to integrate the two or just use google and then transfer the route to the GPS in BC.
    #12
  13. Emoto

    Emoto Sure, why not?

    Joined:
    Feb 24, 2004
    Oddometer:
    19,954
    Location:
    SE Mass
    If you do it like I outlined above, it works fine. Mind you, I am not calling it wonderful, but it does work.
    #13
  14. DRTBYK

    DRTBYK All Things GPS

    Joined:
    Mar 26, 2003
    Oddometer:
    6,318
    Location:
    47°50′15.8″N, 119°56′21.9″W
    Keep in mind that BaseCamp currently only searches the data coded in the Map you have active. But, the latest BaseCamp beta for version 4.2 does have a Yelp! search that goes outside the map data (if you are connected to the 'net) and your map is address search capable. In addition, once you've found that POI you're interested in you can create a Waypoint of it - just like a Google search! Of course it is limited to Yelp! search algorithms but at least it's a start.
    #14
  15. Emoto

    Emoto Sure, why not?

    Joined:
    Feb 24, 2004
    Oddometer:
    19,954
    Location:
    SE Mass
    They chose Yelp? :huh

    I guess Webcrawler didn't pick up the phone? :lol3
    #15
  16. DRTBYK

    DRTBYK All Things GPS

    Joined:
    Mar 26, 2003
    Oddometer:
    6,318
    Location:
    47°50′15.8″N, 119°56′21.9″W
    I don't fault them for Yelp! because it's about travel. But if Yelp! why not TripAdvisor?
    #16
  17. cyberdos

    cyberdos Easy Bonus Loop

    Joined:
    Sep 2, 2005
    Oddometer:
    28,241
    Location:
    Queen Creek, AZ
    GoogleMaps is about as easy as it gets when searching for an address. I know this offers nothing to the discussion but I'm not sure where the Google hate comes from when it works really well for this application.

    BC's address search is taking it back to MS-DOS. It just plain sucks and mapsource was even worse.
    #17
  18. cyberdos

    cyberdos Easy Bonus Loop

    Joined:
    Sep 2, 2005
    Oddometer:
    28,241
    Location:
    Queen Creek, AZ
    Just so I don't leave without making some sort of contribution...

    what I've been doing is looking up the address in GoogleMaps.

    Right clicking on the marker and selecting "what's here?"
    That will give you the coordinates in GM's address bar.

    Pop those coordinates into BC and you've got your waypoint.

    So for your example it took me 5 seconds to get the coordinates: 42.144998,-71.249689

    pop those into BC and you're done.
    #18
  19. DRTBYK

    DRTBYK All Things GPS

    Joined:
    Mar 26, 2003
    Oddometer:
    6,318
    Location:
    47°50′15.8″N, 119°56′21.9″W
    You're really talking "apples and oranges" here when it comes to search.

    BaseCamp, unlike Garmin's earlier products, is a work in progress much like Google is a perpetual Beta application. The "Google hate" as you refer to my earlier post, was sarcasm. As you so adroitly pointed out, you offered nothing to the OP's topic of BaseCamp Address Searching.

    If one has address searchable maps installed in BaseCamp, it's quite simple to find what you want - when you learn how to construct your search. And, of course, the data needs to be coded into the maps properly. It's really no different than any other search engine currently open to the public.
    #19
  20. guavadude

    guavadude de-composer

    Joined:
    Aug 31, 2009
    Oddometer:
    915
    Location:
    Dallas, TX
    cool. thx
    #20