No plans at this point. How would JSON would be any more useful than raw KML? Afterall you can load the KML directly into the browser, parsing and modifying it as you wish. What JSON schema would we use?
On Tue, Jul 13, 2010 at 11:40 PM, bratliff <[email protected]> wrote: > Any plans to split the KML parsing & rendering services ? It was a > welcome change from V2 to V3 for the directions service. Your "gx" or > "sf" services already do it. It enables changing the attributes of > individual components of the KML file. > > Also, an off-line KML to JSONP conversion utility could be useful. > > -- > 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.
