Mapping Like Google Edward Svirsky Presented by Mark Scheel

Purpose –Display listings on map –Display surrounding information ( schools, parks, etc …) Mapping

Current Metrolist Mapping ESRI –Provides Metrolist with a map server –ESRI provides a way to put layers on the maps ( roads, parks, etc … ) –Static images and dynamic maps

Current Metrolist Mapping Current maps for listings are static 1.Calculate coordinates 2.Get map as image 3.Listings show up as part of image Metrolist’s dynamic map –The dynamic map allows full navigation –The dynamic map doesn’t show listings on it

Problems with current approach –Static maps don’t provide much information about surrounding region –Hard to tell precise location –Multiple listings on a single map make it hard to distinguish between listings Current Metrolist Mapping

Future Metrolist Mapping Dynamic maps with dynamic content –Navigation – zoom in/out, scrolling –Listing information available on the map –Polygon selection and search integration

Detailed Mapping Mapping DHTML –Dynamic navigation using JavaScript (on click coordinate recalculations) –IMG tag changes src element to get the correct image –Markers are loaded with information and info is hidden from view

Polygon Selection –Concave polygons –Graphics library - wz_jsgraphics by Walter Zorn –Line drawing and Vector collision detection Can’t intersect –Unlimited number of points –Client vs. Server Detailed Mapping

Challenges Compatibility issues –DHTML and browser compatibility –Current mapping browser support Speed –Client bottlenecks –Server bottlenecks –Transfer bottlenecks

Future Features Dynamic loading of large image blocks for instantaneous scrolling. Large Image Visible Image Load on Demand

Future features Integrated search engine –The Metrolist search engine will be integrated with the map.

Q&A