On 2 December 2010 21:00, Lee Zoumas <[email protected]> wrote: > I aprreciate your feedback. And although that's not the answer I wanted to > hear, it makes perfect sense. When you mention perform geocoding on the > client what are you referring to? basically i need the user to enter an > address, and get the latitude and longitude, from the address, then look > that up against a database to determine which matches are in the area the > user entered. So in a sense, it always needs to do a server request to take > the user input and get the coordinates. I found this web service...
Yes: you need to geocode the user's input. But you can do that in the browser, and then send the result back to the server to look up matches. You don't need to do the geocoding at the server. All the "store locator" examples work like this. That is: you do need a server request to find matches in the area; but you can send the user's *coordinates* to the server to do that. You don't need to send the user's *input* back to the server. I appreciate this may be an issue with ASP.NET blurring the distinction between what happens in the browser and what happens at the server. Use GClientGeocoder to do the geocoding (which means it happens in the browser) and GDownloadUrl to send the data to the server and receive the result -- which means the search is done in the server and the result processed in the browser. The server processing could even be done with an ASP script, although the store-locator examples generally use PHP. The principles are the same. -- You received this message because you are subscribed to the Google Groups "Google Maps API V2" 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-api?hl=en.
