Hi Jared Have you looked at http://code.google.com/apis/maps/articles/phpsqlsearch_v3.html This approach can be adapted to suit various scenarios including property.
Regards Davie On Jan 30, 4:20 am, hungerstar <jetshipju...@gmail.com> wrote: > I have a realty site that I am implementing Google Maps on. > > I would like some input on the two approaches that I am looking at > below. > > There is a search form to search properties based on the users > criteria and then display the matching results, simple enough. Each > property would have View Map link. The map would display with only > the properties that matched the search criteria with the current > property at the center. > > Currently I have two approaches in mind. > > 1.) Have a master XML file and parse it with XPath to get the > appropriate properties to plot. > > 2.) Generate an XML file for each query. > > I understand that having the XML intermediary helps with debugging > along with bypassing some caching issues that might arrive from > passing map marker information from the server side script (ie JSON). > Though I'm not completely sure I will be caching this page as the data > it relies on is updated every 3 hours. > > The issue with #1 is that I am new to XPath and parsing XML files. I > feel this approach may have a few issues that I am not aware of. I am > using JavaScript to load the XML file. I am using Javascript to build > my XPath expression based on the values in the search form. > > The issues with #2 are that I am generating an XML file for each query > if one does not already exist for that specific query. I also have to > tell my maps JavaScript which file it needs to load since there is > more than one, which kind of goes against the Google Maps API article > that suggests not passing info from the server side script. Though > this is just a file name vs a whole set of marker information. An > update of the local database is run every 3 hours. If property > information was added, changed or removed, we'd have to get rid of > some XML files as they would contain outdated information. I don't > like the idea of creating 100s of XML files. > > Any suggestions, ideas or input on this would be greatly appreciated. > > Let me know if you need a little more info to go off of. > > Thanks, > Jared -- 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 google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
