Bing Maps: A New Look for Pushpins, Popups, and Transit

Bing Maps  just rolled out some exciting new updates to www.bing.com/maps that make it easier for you to find information on the map, explore the layouts of over 850 venues, as well as get to where you’re going with public transit (or transport). Read on to learn more!

Pushpin and Popup refresh

The pushpin. It’s the most common element overlaid on a map. And today, it’s getting an update. In making these changes, to both the pushpin and corresponding popup, our goals were simple: enable you to find the information you want, more quickly and efficiently, while at the same time minimizing obstruction of the map. Let’s take a deeper look at some before and after examples.

The updated pushpins are designed to better overlay on top of our base map color scheme and make it easier to find results when you perform a search. Search related content appears in blue, while user-generated and saved content (such as “My places”) use an orange colored pin. The contrast changes are more pronounced on hover (and for business searches, the corresponding item in the left-hand panel is adjusted as well), and we’ve also added a new small popup to tell you the name or location or the pin you’re hovering over. Now it’s much easier to quickly scan a bunch of pins to see what they are.

 

 

When you click to select a pin, it actually shrinks so as to expose more of the map underneath, and unveil our streamlined popup. Here, we’ve made a number of changes to more compactly display the relevant business or location information and stand out against the backdrop. The most popular actions available for each item have been simplified and consistently placed at the bottom. For most users (except those in the UK), the interaction has changed from a hover-only model to a click-based model for showing the full popup contents. (For users in the UK, where you already had to click to see the popup, we’ve simply added the new smaller hover popup in addition to the layout and style changes.) Overall, these improvements allow you to keep a popup visible while panning/adjusting the map, and even hover over other pins to see what they correspond to, ultimately making it easier for you to find the place you want more efficiently.

 

One final change you may have noticed is that the pushpins and popups dynamically adjust based on the current map style in order to ensure the information does not get lost on the map.

 

Enhanced Transit Experience

Public transit (and UK transport) users will find a handful of subtle improvements to our directions experience that make it easier to get where you’re going, and make sure you’re on the right line to get there. We’ve changed the way we represent each transit line to better reflect the actual colors and signage used by the line, both for our US and UK markets. You’ll see this reflected both in the on-map waypoints as well as our enhanced directions list.

 

 

More sharing options

We’ve also extended our ability to send directions to your mobile phone (via SMS) to support transit directions. This functionality is accessible via the “Send: Mobile” link at the bottom of the directions panel. You’ll receive a link on your mobile phone which loads the directions on m.bing.com, and works for all devices which can access m.bing.com (unfortunately, Windows Phone does not currently support transit).

 

Drag to modify your route

Users can now easily modify their directions routes by clicking and dragging on start, end, or waypoints. You’ll see a helpful tooltip appear when you hover over an element that can be adjusted simply by dragging and dropping—and the route will be recalculated automatically!

Explore venues

Did you know Bing Maps now has over 850 venue maps of airports, malls, shopping districts, and more? Browsing through them is now easier than ever! Just click on the “explore venue maps” link on Bing Maps, or visitwww.bing.com/maps/venues to get there directly, to browse a categorized listing of available venue maps. You can filter them by country, sort them by location (or alphabetically), and browse through them spatially on the map. If you want to have your venue be part of Bing Venue maps, please contact us for details.

 

We’re excited about this next step in the evolution of our visual design and believe it is a big step forward for simplifying user interaction with the map, and helping users find the information they want quickly and efficiently. We’ll be rolling out these changes to bring consistency across the broader Bing network over the next few weeks.

Google Summer of Code & OpenIntents


This year was the first year OpenIntents participated in the Google Summer of Code. We are an open source organization which creates software for Android mobile phones and tablets, with special emphasis on interoperability with other software components.

As an organization we’ve found involvement in the Google Summer of Code extremely rewarding. The students have been able to improve their skills and gain practical experience in the stages of a software project, our organization has benefited from the interest generated from the students’ work, and the wider community will continue to benefit from the code the students have delivered.

We particularly enjoyed the international aspect of the program. All students, mentors, and co-mentors lived in different countries which did not prevent us from having a great time discussing the projects through Skype and live chat sessions. We received a great number of excellent proposals, from which two very different projects were chosen for the program.

Elena Burceanu’s project aimed to enhance the Sensor Simulator. During the first weeks, the GUI was polished, both in appearance and through clever code restructuring. After enhancing the GUI the number of supported sensors was increased and now includes Android sensors for gyroscope and general rotation vector. Finally, a scenario simulator was added, which creates sensor output from a set of initial states and the ability to change the time intervals between them. The sensor’s values are smoothly interpolated between the key frames. The final product was released as version 2.0. The source code and documentation for Elena’s project are now available to view.

Andras Berke’s project consists of a new application called Historify which displays the user’s activities with others over a variety of communication methods (Voice, SMS, Facebook, etc.), and provides a method for third party applications to supply other activity events showing the interoperability of Android applications. During the summer Andras went through the whole application design process from the UI wireframes to a first beta release including documentation along the way. In addition, he provided demo applications to show how third party developers can interact with Historify. You can now view the source code and documentation from Andras’ summer project.

Google Places: “We currently do not support the location”

 

When working in Places the message that we all dread to hear: We do currently do not support the location is a Google message that instills the fear of god in the most expert of us. In normal situations it will show when a newly created listing has not yet been integrated in the Maps index. Give it 48 hours and the message goes away.

However there has been a more sinister occurrence where it will show up all of the sudden on a long claimed and stable record and it’s the bane of who ever runs into it . Until now it was not known what caused it or how to fix it. It is a message that shows up all too often in the forums raising its head there 3 or 4 times a week.

Fortunately for all concerned, a frequent contributor to the German Places Forums, Spinatmensch has discoved a work around for this most devastating of Google Places Bugs. Here are the instructions as detailed by EHG, another frequent contributor:

1. go into the GooglePlace account containing the “unsuported” location.
2. click the name of the entry to get the URL of the analytics site of the entry opened in a new tab of the browser.
Its URL should look like:
http://www.google.com/local/add/analytics?storeid=[the numbered Place identifier]&hl=en&gl=US
3. Now enter any  content into the field below the line “Share an update on your place page” and hit the button Share” to publish the new content.

I have tested this recently with Andrew Baker whose Places Page was experiencing the problem. This solution may actually recover some of the listings that were edited during the Pending problem as well.

Disasters and maps

7 February 2011 marked the second anniversary of the worst bushfire tragedy in Australian history – 173 people died and 414 were injured as the result of infernos raging around the State of Victoria. The Black Saturday Bushfire was a very traumatic event for many Australians, those directly affected by the fires but also those thousands who got emotionally and personally involved in post event forensic studies, clean up, counselling, rebuilding, Royal Commission and general assistance through voluntary work or collection of donations. The whole nation felt the pain and helplessness in the wake of such an enormous tragedy.

After a period of a relative calm over the last two years Australia has been struck again by several major natural disasters, such as flush floods in Queensland and Victoria, tropical cyclone Yasi, or bushfires in Western Australia. Events like these bring online crowds of people: those caught inadvertently in the incidents, or those concerned about safety of their family members and friends, but above all, “curious onlookers” from around the world who just would like to know what is happening. All those people are looking for basic information, such as maps of places to identify where “these things” reported in commercial and social media are happening, as well as anything that relates to progress of the event, likely scenarios it may evolve into and the impact on people, infrastructure and the surrounding environment.

In the first instance they turn to official sites run by State authorities – those that issue the alerts and warnings – and of course the Australian Bureau of Meteorology. When they can’t find what they are looking for, or the information is not in the format that is meaningful, they turn to online search engines seeking more details about the event. It is therefore not a coincidence that during the times of natural disasters the traffic to sites providing information on maps goes through the roof. A question comes to mind if there really is enough tools in the public domain to keep general public fully informed. Has anything changed since Victorian bushfires of 2009?

In an ideal world, all the relevant information would be provided by the authorities, along with alerts, warnings, evacuation orders, road closures and detour routes, situation briefs etc. And through all possible channels: online, stationary and mobile phones, radio and TV, and in all formats: text, audio and video broadcasts and online streaming, printed as well as static and interactive maps, and above all, web services for republishing the information through media and social channels. But that is still only a distant dream. The reality is that information is very fragmented, differs in formats and content from State to State and ultimately in reliability, accuracy and timeliness.

So, what information is actually available, in spatial format, to an average person interested in a particular event? Let’s start with bushfire related information as there is quite a few resources available…

Part 1: Mapping Bushfires

Detection of fire hotspots from satellites has been around for quite a while and Australia has two systems delivering such information that pre-dates Victorian bushfires of 2009: Geoscience Australia’s Sentinel and Landgate’s FireWatch. Both are using data obtained from the NASA Earth Observation Satellites Terra and Aqua which pass over Australia up to three times a day (although a revisit of the same area is only two times a day). Although data has some limitations, like timeliness due to infrequent revisit cycle or inability to detect hotspots through thick smoke and clouds, these applications provide excellent location reference for larger fire outbreaks throughout Australia. Geoscience Australia publishes the data in KML, WFS and WMS formats. I use those in my Hazard Monitor Bushfire Incidents map to publish an alternative view of the information. FireLocator from PitneyBowes provides yet another version of the same data in Silverlight format and with Bing Map in the background.

North Australia Fire Information is an application dedicated to monitoring fires in the northern part of Australia. In addition to satellite detected fire hotspots it also includes information on fire scars from past bushfires. Some of the information available on this site can be accessed in KML and WMS formats.

State authorities responsible for emergency alerts and response to natural disasters are publishing on their respective websites summaries of information on the latest incidents. Victorian Country Fire Authority (CFA) publishes a summary of incidents in a tabular format and on a Google Map. The information is also available as RSS feeds (locations are not georeferenced, hence cannot be directly imported into maps).

In NSW Rural Fire Service (RFS) publishes its version of summary of incidents – as a list and a map. Georeferenced RSS feed is also provided.

Both Bushfire Incidents map and FireLocator (developed in late 2009) are using the above feeds to display information about the latest incidents on the maps. During the peak of Victorian bushfires Google released its own application that mapped these feeds and showed satellite imagery of smoke and cloud cover.

Tasmania Fire Service (TFS) is another agency that publishes fire incidents information and a map as well as distributes the information via RSS (non-georeferenced) and KML. And South Australian Country Fire Service (CFS) publishes map and incidents in a similar fashion to already mentioned States (their RSS feed is also not georeferenced).


There are no interactive maps with the latest incidents for Queensland and Western Australia and those states do not publish RSS feeds in the format that could be easily reused for displaying the information in third party mapping applications.

The most recent additions to the list of online bushfire related information sources are BushfireConnect and everymap.com.au. Built with Ushahidi, these online mapping applications aim to publish information supplied by the public located in the affected areas, either by lodging reports online, or via SMS or Twitter (ie. crowd sourcing). They also republish RSS alerts from State authorities. Not the easiest and the most intuitive tools to use but these initiatives are attempting to engage a wider community in reporting of incidents so, deserving all the support.

At the time of major disasters media and private individuals create maps and various applications to share the information about a particular event. Examples include a Black Saturday feature created by ABC that allows users to explore timeline of events on an interactive map, or Google’s MyMap version created by a private individual as a static record of events (presented here on aus-emaps.com shareable map).

 

 

Android: Moving accessibility forward

For the last 8 years we at Code Factory have been making software that helps the blind and the visually impaired access their mobile phones. We’ve created this software for several different platforms. Last year we decided it was time to start doing something for the Android platform, due to its growing popularity and variety of devices.

From our past experience, developing a screen reader for a new platform required a lot of work, hacks, and investigation. Almost none of the previous platforms we supported implemented any sort of Accessibility API that we could use. Android, we thought, would be no exception to this rule. We were very wrong.

Starting at version 1.6, the Android operating system comes with a built-in Accessibility API that makes our application a lot easier to develop. All you do is create a service, which implements the AccessibilityService interface, declare it in your manifest and voilà! The system will start sending events, such as button presses, list navigation, focus changes, etc. to your service. You then convert this information to voice using a Text-to-Speech engine, and you have a screen reader.

The Accessibility API is not yet as complete as what you can find on a desktop PC, but it’s good enough to provide the users with basic user interface navigation, and we have no doubt that, as the Android platform evolves, so will the built-in Accessibility API.

We also wanted our application to go beyond a screen reader and provide an intuitive, easy-to-use UI that allowed the blind and visually impaired access to most of the phone’s functionality, such as messaging, web browsing, contact management, and so on.

We were pleased to see that we could do this Android. The existing set of UI controls, such as buttons and lists, can be overridden in order to provide custom functionality, such as speaking the text of the control. This made it possible for us to keep the user interface of our application consistent with Android, while at the same time providing the speech feedback that our users require.

By intercepting touch events within our application and using the gesture detectors that Android provides to developers, we were also able to make the touch screen accessible to our users, so they can use gestures like swipes to move through items of lists, or double-taps to activate items.

We really like how much we can accomplish with Android with so little code. Want to let a blind person create an SMS or email using voice? Simply use the SpeechRecognizer class. Want blind users who are walking on the street to know their exact location? Just use the LocationManager and Geocoder classes to give their exact street name and number.

Android lets us do a lot in a very efficient way. It wraps a whole bunch of cool technology into well-defined classes and interfaces. And if at any given time you need to know how something works behind the scenes, you just take a look at the source code, which is freely available to everyone.