Stories
Slash Boxes
Comments

In+ersec+ion for Spatial People

Better KML Rendering With Google Maps API For Flash?

posted by lxnyce on Thursday June 12, @04:48PM   Printer-friendly   Email story  Permalink  Trackback URI  Slashdotthis  Diggthis  Del.icio.us
from the i-see-no-difference dept.
The thematicmapping blog updates us on a previous article with an example of displaying vectors using the Google Maps Flash API. From their summary : "Most of the current map APIs quite cleverly use use the build-in vector support in Firefox and Internet Explorer (and others). Firefox supports Scalable Vector Graphics (SVG), while Microsoft use the obsolete Vector Markup Language (VML). The Google Maps API and OpenLayers API automatically check your browser and draws the vectors with the appropriate technology.

But the SVG/VML/DOM technology has some serious performance issues - if you add many complex polygons the browser will run terribly slow. While we wait for HTML 5 (and browsers to support it), Flash APIs might be a better solution."


For more information and relative links, please visit the article link above.

Related Stories

Industry: Google Maps API for Flash [+]
The Map Room blog informs us about this new Google API meant to embed Google Maps in flash applications. From their summary : "So, what do I like about the API for Flash? Smoothness and speed are a big part of it. We’ve designed it so that Flash graphics can be used for each tile layer, marker and info window — opening up possibilities like dynamic shading, shadowing, animation, and video. When the user zooms the map, magnification changes happen smoothly and place names fade in. After the user drags a marker, it gently bounces to a halt. Generally, Flash allows for much greater embellishment, and, well … “flashiness.” I get excited just thinking about the creative ways developers might take advantage of having a Flash API for Google Maps."

To check it out, please visit the Map Room blog.
Display Options Threshold:
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.