our company

Contact Us

Navigation Arts Location Map


Find out more about our consulting services. McLean. Boston. New York.

What's New

tessco rail


NavigationArts Wins 3 Web Marketing Association Awards for our clients!


Thinking Big

Clark Construction

Digital Innovation

Reimagining how our clients can do business in the digital world.

Thinking Small

University Website Design

Mobile & Responsive

A responsive design approach engages users wherever they are. Web. Tablets. Mobile.

User Experience

Left Brain

PFC Energy

Critical Thinking

User-centered digital strategies help our clients surpass their competition.

Right Brain

National Aquarium

Immersive Design

Exciting and memorable visual experiences guide users through digital channels.




Platinum Partner

NavArts is one of only 7 Sitecore partners in the USA with 4 or more certifications.


Drupal 7 Content Management


NavArts brings proven process and UX skills to the popular open-source platform.

our work

Case Study


Marriott International

Multisite design creates seamless booking across more than 3,000 properties.




Cutting-edge design to revolutionize the world of user experience.


Content Guide

content migration whitepaper


Give content as much attention as the design, code and testing of your site.

DrupalCon 2015


Webinar: DrupalCon Los Angeles 2015- How Drupal secured the defense sector


Google Maps API v2 or v3 by:

September 29th, 2009

For those of you who deal with mapping functionality, I’ve worked with both Microsoft and Google products for this. My app of choice is Google Maps (although when going down this road, you have to sacrifice some level of control for their efficiency optimizations – this is usually a very reasonable trade-off). Anyway, Google came out with v3 for its API this year, which has some slimming down of its codebase, and probably has some back-end improvements on their server as well (although I’ve seen mixed reports on v2 vs. v3 latency).

What v3 does not yet have is a standard tool for aggregating markers. While this seems like a minor issue, considering v3 might host a few desirable new features, from a scaling standpoint, this is a critical drawback. In order to use an API, you’re essentially sending a gigantic block of objects from the client to the server, to which the server responds with a dynamically generated map. If you have thousands of markers (which you could, depending on the site / use case), you’re essentially sending all of those over the pipe for every redrawing of the map. Marker managers aggregate and minimize the amount of information that’s sent in each request, and also simplify the UI that’s presented to the user.

It could be that markers that exceed the map view aren’t included in the map request (which would be an obvious optimization for them to build into v3), but I haven’t seen any reporting of this being the case. Even if they’ve built this in, it’s a wonderfully useful feature to ‘group’ markers that are too close in proximity to be interacted with.

They’re building this functionality into v3, but it’s low on Google’s priority list. Until it’s built and tested, I’m probably going to be recommending v2 for any mapping functionality.

Here’s an example of a useful marker manager.

Tags: Web Development

November 2015
« Sep