On Apr 29, 1:48 pm, Dommer <[email protected]> wrote: > Okay, that is a great starting place, I think I could make a go from > there. > > Another issue was mentioned, the "garden shed accuracy problem," and > someone suggested: > > "There are settings in there you can tweak > on the encoding used by the GeoXml class > .. the default values used are > geoxml.verySmall = 0.0000001; > geoxml.ZoomFactor = 2; > geoxml.NumLevels = 18; > set them on your GeoXml object > before calling parse" > > How would you do this - and does it seem likely that altering these > constrainst would resolve the inaccuracies that I am observing WITHOUT > having to reparse the data manually?
The documentation refers to Mark McClure's description and tools: http://facstaff.unca.edu/mcmcclur/GoogleMaps/EncodePolyline/ > > Dominic > > On Apr 29, 1:42 pm, Andrew Leach <[email protected]> > wrote: > > > On Apr 29, 8:07 pm, Dommer <[email protected]> wrote: > > > > Nah, the KMLs are generated dynamically as each request is made by the > > > PhP and DOM. Making KMLs to be displayed by GGeoXML() was just that > > > the only way I knew to make polygons show up. > > > That's fine. GDownloadUrl just gets from a url. If your KML is made by > > PHP, the script can serve the result. > > > var q=1101850; > > GDownloadUrl("kmlmap4.php?q="+q,processit(data)); > > > function processit(kmlfile) { ... } > > > Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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 -~----------~----~----~----~------~----~------~--~---
