On Jun 3, 2014, at 3:24 PM, James Davis, PhD wrote:
Not true. The information is there in the form of ‘locations’ or ‘places’ via
Google or some other mapping service. Suppose you wanted to show users a list of
their local pizza restaurants. Instead of trying to build and maintaining a table
containing every pizza restaurant in the country, just use a mapping service that
allows them to select the restaurant. All I want to capture/maintain is which one
the user selects.
Now take the above example and replace ‘pizza restaurant’ with ‘physician’ or
‘dentist’. That is what I want to do. The options come from the mapping service
and I only capture the selection…essentially externalizing the
Excellent feedback. Thanks Colin & Walter.
So my original question was which mapping service might work best for doing
Probably Google’s, since OSM is more about location / way finding than a
business listing service. That said, you’re going to have to hook up
selection from their click. The map arrives at you fully populated, and
hooked to the rest of the Google universe in terms of what happens when
you click one of the pins. You’re going to have to capture those clicks,
do whatever you do to capture the content and context of the clicks, and
then what happens for your user after that instant? Do they carry on to
Google, or do you somehow redirect them into your application? What’s
the goal of your app?
Depending on what that is, you may want to consider scraping the Google
map for your target locations, and build your own database anyway. In
the long run it may be less complicated. You’ll certainly not run out of
API clicks should you get popular if you do that.