On Mon, Aug 23, 2010 at 13:57, Harsha <[email protected]> wrote:

> Miguel,
> thanks for the reply. i will tell u the exact scenario
>
> we have a search page where the users can search for say some
> commercial establishments in an area and we show 20 results per page,
> now the new requirement is that i have to show these 20 results on a
> google map.
>
> these addresses come from the database, (but we cannot convert them
> into latitudes and longitudes as of now due to some problems) so i
> have to depend on the addresses only, so when i send these 20
> addresses i get the error OVER_QUERY_LIMIT, so i was looking for a
> solution where i can still send 20 addresses and get them populated on
> the map without trouble.
>

Whenever addresses come from a database, you should be looking at
batch-geocoding them and give users their LatLng positions long with the
addresses. This is exactly what batch-geocoding is for: a known set of
addresses that you already have.

We should probably focus on those problems that are preventing you
from batch-geocoding those addresses in your database, because that is the
right approach in your case.

is there any solution other than pre-geocoding? like creating some
> delays between requests or something similar?
>

You would need quite some delay, probably more than enough to make users
unhappy, if you really wanted to client-geocode 20 addresses each time. It's
just not the right approach.

On Aug 23, 2:39 pm, Miguel Angel Vilela <[email protected]> wrote:
> > On Mon, Aug 23, 2010 at 11:31, Harsha <[email protected]> wrote:
> > > Larry,
> > > I am afraid that i may not know what exactly pre-geocoding means,
> > > please correct me if i am wrong.
> >
> > > i assume by the term pre-geocoding is that we have to convert the
> > > known address into Latitude and longitudes and the pass the available
> > > lat and long into the map to display the addresses.
> >
> > That's the idea, you can batch-geocode them beforea hand and give users
> just
> > the LatLng positions to display on the map. The article I linked before
> > explains this.
> >
> > but my problem here is that the 20 addresses that i have to show are
> >
> > > dynamic and it differs everytime depending upon the user criteria :
> > > ( so i have no clue what should i do now :(
> >
> > Are those address always unique to each user and each time?
> >
> > It sounds hard for each user to generate 20 textual addresses, that no
> other
> > user will never generate, and fast enough to run out of client-side
> > geocoding quota.
> >
> > as you said i will get in touch with the google rep and ask him wat to
> >
> > > do...but it would be very helpful if you can provide me someother
> > > solution ...
> >
> > A Maps API Premier client id (please remember: there is no such a thing
> as a
> > "premier key") will give you higher usage limits, but your use case
> sounds
> > prone to run out of those as well:
> >
> > What are the usage limits for the Google Maps API Web Services?
> http://code.google.com/apis/maps/documentation/premier/faq.html#usage...
> >
> > How many users will be doing this geocode-20-addresses-right-now using
> this
> > application concurrently?
> >
> > Regards,
> >
> >
> >
> > > Harsha
> >
> > > On Aug 21, 3:38 am, "[email protected]" <[email protected]>
> > > wrote:
> > > > On Aug 20, 9:36 am, Harsha <[email protected]> wrote:
> >
> > > > > Hey thanks a lot for reply, but my problem is that.
> >
> > > > > i have a list of addresses in a arraylist (Approximately 20
> addresses)
> > > > > and i have to show them on google maps, so when i am looping 20
> > > > > addresses and displaying them on the map i get this
> Query_Over_limit
> > > > > error.
> >
> > > > > so can you please help how i can pass these 20 addresses onto the
> map
> > > > > without getting an error?
> >
> > > > Did you read his suggestion:
> > > > + If you need to display more than 10 locations on a map, consider
> > > > + pre-geocoding them.
> >
> > > > > we have also paid google and got a preimer
> > > > > service key, will this help us?
> >
> > > > I would think so, but you would need to talk to your google rep.  You
> > > > really shouldn't geocode 20 known addresses on the fly every time
> your
> > > > page loads, that is just wasteful.  Geocode the addresses off-line
> and
> > > > store the resulting locations in your database along with the
> > > > addresses.
> >
> > > >   -- Larry
> >
> > > > > On Aug 20, 4:28 pm, Miguel Angel Vilela <[email protected]> wrote:
> >
> > > > > > On Fri, Aug 20, 2010 at 13:19, Harsha <[email protected]>
> wrote:
> > > > > > > Hi,
> > > > > > > i have a problem when i am sending more than 10 requests
> through a
> > > for
> > > > > > > loop from java script to the goecoder service. i get back the
> > > message
> > > > > > > saying QUERY_OVER_LIMIT after 10 requests.
> >
> > > > > > If you need to display more than 10 locations on a map, consider
> > > > > > per-geocoding them.
> > > > > > If you can't because they come from end-user interaction (e.g. a
> user
> > > clicks
> > > > > > on 20 points on the map, but sounds unlikely) then you need to
> wait
> > > (e.g.
> > > > > > for a second) each time you get that error.
> >
> > > > > > how can i get rid of this, i tried introducing the time delays in
> the
> >
> > > > > > > javascript but was not successful in removing this error.
> >
> > > > > > You cannot get rid of this, this is normal behavior, see this:
> >
> > > > > > Is there a limit to the number of geocode requests I can submit?
> > >http://code.google.com/apis/maps/faq.html#geocoder_limit
> >
> > > > > > it would be really helpful if some one can help in in finding the
> >
> > > > > > > solution as i am running out of time.
> >
> > > > > > Quick! Tell us what you want to do exactly :)
> >
> > > > > > --
> >
> > > > > > > You received this message because you are subscribed to the
> Google
> > > Groups
> > > > > > > "Google Maps JavaScript API v3" group.
> > > > > > > To post to this group, send email to
> > > > > > > [email protected].
> > > > > > > To unsubscribe from this group, send email to
> > > > > > > [email protected]<google-maps-js-api-v3%[email protected]>
> <google-maps-js-api-v3%2b­[email protected]
> ><google-maps-js-api-v3%2B
> > > ­[email protected]>
> > > > > > > .
> > > > > > > For more options, visit this group at
> >
> > >
> http://groups.google.com/group/google-maps-js-api-v3?hl=en.-Hidequote...-
> >
> > > > > > - Show quoted text -- Hide quoted text -
> >
> > > > - Show quoted text -
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Google Maps JavaScript API v3" group.
> > > To post to this group, send email to
> > > [email protected].
> > > To unsubscribe from this group, send email to
> > > [email protected]<google-maps-js-api-v3%[email protected]>
> <google-maps-js-api-v3%2b­[email protected]>
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-maps-js-api-v3?hl=en.- Hide
> quoted text -
> >
> > - Show quoted text -
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Maps JavaScript API v3" group.
> To post to this group, send email to
> [email protected].
> To unsubscribe from this group, send email to
> [email protected]<google-maps-js-api-v3%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-maps-js-api-v3?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Maps JavaScript API v3" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-maps-js-api-v3?hl=en.

Reply via email to