bratliff wrote: > On Nov 19, 11:31 pm, Lara <[EMAIL PROTECTED]> wrote: > >> OK. Thanks Bratliff and Garthan. I've figured out how to query my WFS >> and create a static XML, which I can save and upload to my site. Here >> is my >> query:http://geodata.epa.gov/wfsconnector/com.esri.wfs.Esrimap/NPL_FS?reque... >> >> and here is the XML up on a modified version of your orginal GeoXML >> code.http://www.tchdgis.org/googlemaps/testgeoxml.html >> >> I am totally stoked, because I've never used WFS or GeoXML! >> >> So, you are saying that I need to create a proxy script that creates >> my XML using the GetFeature request and writes it to my server, right? >> I can search for how to do this, but if you have any tips/hints/ >> examples, I would be very appreciative. Thanks for all your help >> already! >> >> Lara >> > > Unless your XML document changes frequently and/or you have to access > different XML documents on the fly, a proxy is overkill. You can use > "GDownLoadUrl" to pull from your own server an XML file you have built > previously. > > I believe Mike Williams has an example of basic XML parsing. JSON is > another option to consider. > You can even use the "responseText" > property of your "XMLHttpRequest" to capture a raw text file like > CSV. A 100K JS file (half the size of the API itself) is a lot of > extra overhead for simply parsing an XML document. > GeoXml compresses down to approximately 25kb. ... yippeee.. about the size of one of the more complicated jpegs in a sattellite layer...
If you are targetting 56kb modem users.. you will find.. there isnt a map service in existance that is small enough as the data itself is too much and is overwhelmingly bigger than googles API. (I am annoyingly in a beggers cant be choosers stance on dyasdesigns so software compression isnt turned on ... and the argument is still out as to whether hardware compression makes that step unnecessary or not... ie the pure get the code time might be the equivalent without turning on compress In other words.. javascript/text/xml is far smaller in terms of transmission time than jpegs or similar things people are likely to be comparing it to. http://www.dyasdesigns.com/geoxml/c2020.htm?openbyname=Babcock%20Ranch The above is a use case where I just stripped out xml processing and polyline encoding and some wms support so it just loads most kjson created with a more fully featured build ( but it still creates a side bar and clusters points and processes the url..etc ) The advantage of things where you have the source code.. is you can use what you need and ditch the rest, but yes you have to make and active choice to do it. The above reduced build compresses to about 12kb. or if I recall slightly smaller than the size of a very simple sattellite jpeg. Shrug. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
