Google Data » Monica Trean https://googledata.org Everything Google: News, Products, Services, Content, Culture Fri, 10 Apr 2015 22:28:52 +0000 en-US hourly 1 http://wordpress.org/?v=4.1.1 abbyputinski.com — Google Maps with a twist https://googledata.org/google-maps/abbyputinski-com-google-maps-with-a-twist/ https://googledata.org/google-maps/abbyputinski-com-google-maps-with-a-twist/#comments Fri, 04 Oct 2013 18:45:00 +0000 https://googledata.org/?guid=56a25cc33cd8130446a8a2d56f2e5397 We love the teamwork behind AbbyPutinski.com, designed by San Francisco illustrator Abby Putinski, and developed by her husband Adam. In this guest blog post, Adam will walk us through how he worked with Abby to give the map a unique, illustrated look, as well as fun-to-use animations.

 Abby is a designer and illustrator living in San Francisco. In building her site, Abby wanted to take users on a journey to discover and explore some of her favorite places in San Francisco, in a way that reflected her illustration style. Taking Abby’s design direction into account, I began building the site, working with the Google Maps API to make the visual experience come to life for visitors of the site. The app is powered by Ember.js, so the application template includes a helper to render a MapView. Custom Overlays are used to take users on a journey around San Francisco.


Designing in Reverse 
To make the map feel like an illustration, Abby used the Styled Maps Wizard to play with colors of the map. By using very few colors and disabling most of the roads and landmarks, she was able to give the map a flat, simple look. After exporting the JSON from the Styled Maps Wizard, Abby worked with screenshots of the map to design the rest of the experience.

 
Some of Abby’s favorite landmarks in San Francisco



The animated GIF in situ on the map as a custom overlay.

 Defining a custom overlay 
To create a fullscreen overlay, the bounds are set to the Southwest and Northeast corners.


Positioning the overlay on the map 
The MapView has two child views. The DOM element for a custom overlay actually needs to reside inside the markup generated by Google Maps, but the overlay is an Ember.View so the MapOverlayView is actually rendered as a sibling of the MapCanvas and then moved into the correct spot later.



Keep the overlay centered while panning 
The default behavior for a custom overlay is to re-calculate the styles when the map is panned, but to build an overlay that stays centered on the map, the overlay should only be drawn once and then pan with the map.



Creating the overlay 
Finally, once the overlay has been created and rendered, resolve a promise letting the application know the map is ready.



Final Thoughts 
This project was extremely fun and was successful due to the collaboration between design and development. The Google Maps API gave us the creative freedom to completely customize the map, while Custom Overlays really pulled the experience together.

Posted by Monica Tran, Google Maps API Marketing

Adam and Abby Putinski are a husband and wife design/dev team located in San Francisco. Learn more about their work at abbyputinski.com

]]> We love the teamwork behind AbbyPutinski.com, designed by San Francisco illustrator Abby Putinski, and developed by her husband Adam. In this guest blog post, Adam will walk us through how he worked with Abby to give the map a unique, illustrated look, as well as fun-to-use animations.

 Abby is a designer and illustrator living in San Francisco. In building her site, Abby wanted to take users on a journey to discover and explore some of her favorite places in San Francisco, in a way that reflected her illustration style. Taking Abby’s design direction into account, I began building the site, working with the Google Maps API to make the visual experience come to life for visitors of the site. The app is powered by Ember.js, so the application template includes a helper to render a MapView. Custom Overlays are used to take users on a journey around San Francisco.


Designing in Reverse 
To make the map feel like an illustration, Abby used the Styled Maps Wizard to play with colors of the map. By using very few colors and disabling most of the roads and landmarks, she was able to give the map a flat, simple look. After exporting the JSON from the Styled Maps Wizard, Abby worked with screenshots of the map to design the rest of the experience.

 
Some of Abby’s favorite landmarks in San Francisco



The animated GIF in situ on the map as a custom overlay.

 Defining a custom overlay 
To create a fullscreen overlay, the bounds are set to the Southwest and Northeast corners.


Positioning the overlay on the map 
The MapView has two child views. The DOM element for a custom overlay actually needs to reside inside the markup generated by Google Maps, but the overlay is an Ember.View so the MapOverlayView is actually rendered as a sibling of the MapCanvas and then moved into the correct spot later.



Keep the overlay centered while panning 
The default behavior for a custom overlay is to re-calculate the styles when the map is panned, but to build an overlay that stays centered on the map, the overlay should only be drawn once and then pan with the map.



Creating the overlay 
Finally, once the overlay has been created and rendered, resolve a promise letting the application know the map is ready.



Final Thoughts 
This project was extremely fun and was successful due to the collaboration between design and development. The Google Maps API gave us the creative freedom to completely customize the map, while Custom Overlays really pulled the experience together.

Posted by Monica Tran, Google Maps API Marketing

Adam and Abby Putinski are a husband and wife design/dev team located in San Francisco. Learn more about their work at abbyputinski.com

]]> https://googledata.org/google-maps/abbyputinski-com-google-maps-with-a-twist/feed/ 0 Sun Surveyor shines with Street View https://googledata.org/google-maps/sun-surveyor-shines-with-street-view/ https://googledata.org/google-maps/sun-surveyor-shines-with-street-view/#comments Mon, 16 Sep 2013 18:31:00 +0000 https://googledata.org/?guid=4de2f6e5b28d493e691a66c0747059aa In this guest blog post, we hear from Adam Ratana, a hobbyist photographer and software engineer by day, and developer of the Android and iOS Sun Surveyor apps by night. In this tutorial, Adam talks about his creative implementation of custom polylines on Street View panoramas in the Google Maps SDK for iOS.

 As a photography enthusiast, I’m always looking to capture images at the magic hour. My goal when creating Sun Surveyor was to give users an immersive way of visualizing the location of the sun and the moon, making it easy for anyone to figure out when the natural lighting is just right for the perfect shot.

When I set out to build Sun Surveyor, I knew I wanted to give users an easy way of visualizing the location of the sun and the moon. Sun Surveyor has an augmented reality (AR) feature, which overlays sun and moon paths on top of the device camera’s view. This is useful for understanding how light will change over time at a particular location. While I also created a Map View to show the paths on a Google Map for remote locations, it was not as intuitive as augmented reality.

Visualizing the sun and moon paths in augmented reality and map views

When Street View launched in the Google Maps SDK for iOS in v1.4.0 (July, 2013), I couldn’t wait to visualize the sun and moon paths within an interactive panorama. Street View panoramas bridge the gap between Sun Surveyor’s Map View and AR experiences by giving users an augmented reality experience, wherever they want to go.

Sun and moon paths with Street View panoramas

Implementing a sun path Overlay on Street View
I took a creative approach to working with the Google Maps SDK for iOs.  While polylines can be implemented in Map View, this isn’t yet possible in a Street View panorama. To display paths and other items that move with the Street View panorama, I needed to:
  1. Create an overlay on top of the panorama upon which to draw the items
  2. Synchronize the positions of the overlay items with the panorama as it moves
  3. Determine which data are visible and where on the screen to draw them
For this tutorial, I have provided a sample project that will get anyone started doing the same. Let’s walk through the steps.

I. Creating an Overlay

In our main UIViewController, we add a subclass of UIView for the overlay, make its background color transparent, and place the GMSPanoramaView below it in the view hierarchy.


Representing Overlay Items
We represent the overlay items with a protocol having two methods: updateWithPanoramaView and draw. The updateWithPanoramaView method updates an item’s screen location geometry, while draw draws it to the current graphics context.

We store all items to be drawn in a collection, update their positions based on the panorama position, and draw the collection in our view’s standard drawRect method.

If we want to make sure these items are drawn in a certain order that might change based on the data, we can add z-indexes to them and then sort the collection by z-index after we update them and before drawing.

II. Syncing the Overlay with the Panorama
To make sure this overlay view stays updated as the panorama moves beneath it, we can update the view’s data in an implementation of GMSPanoramaViewDelegate’s didMoveCamera method. We can use a CADisplayLink to ensure the overlay view is redrawn at regular intervals, and use a flag to make sure it is only redrawn when necessary.


Optimization
CoreGraphics can be a bottleneck. [UIBezierPath strokePath] and [NSString drawAtPoint] are expensive as you can see by profiling with Instruments. For performance intensive applications, an alternative is to use OpenGL. Avoiding overdraw is always a good idea, so the first optimization, if needed, is to carefully examine what is being drawn to the screen, and draw only what is necessary.

III. Mapping data to the panorama view
The GMSProjection class has a pointForCoordinate method that returns the screen pixel location for a coordinate on the Map. This is useful for overlaying elements on top of a GMSMapView, and is used in the Sun Surveyor Map View to draw text related to sun and moon paths on top of the Map.

GMSPanoramaView has a similar method, pointForOrientation. This method allows us to query the panorama for a screen pixel location given a GMSOrientation (bearing and pitch tuple) relative to the panorama location, where the camera is stationed, at ground level. This is useful to make sure an item we overlay onto the view remains in the same location relative to the scene, even as the camera moves and the view shifts.

Because the camera has a Field of View that determines what is visible on the screen, some orientations are not visible (such as behind the camera position). pointForOrientation helpfully returns NAN (not a number) for such orientations, so we know the given orientation is not visible.

With sun path data already expressed in terms of orientation relative to the ground level of the viewer, drawing corresponding paths with screen pixel locations is easy. We map our data with pointForOrientation, and draw what is visible by checking the result for NAN.



The sample project uses a panorama of Sydney, Australia, looking west, with a sun path for 12/20/2013.


Bonus: altering the Field of View
Version 1.4.1 of the SDK added support for changing the GMSPanoramaCamera’s field of view (FOV). The field of view determines how much of the scene is visible on a device screen, as well as how much distortion around the edges of the view is present. Smaller values for FOV are the equivalent of having a telephoto lens on a real camera: it brings distant objects closer.


Left: FOV of 60 degrees. Middle: 90 degrees (default). Right: 130 degrees.


Street View Panoramas are awesome and easy
The Street View panorama viewer in the Google Maps SDK for iOS is an example of a great API. The GMSPanoramaView class is simple to understand and use. In the course of a weekend, I was able to deliver a fun, interactive and highly requested feature to Sun Surveyor’s iOS users. I can’t wait to see what people are able to do with this new Street View Panorama feature in my app, and I look forward to seeing all the other implementations that others develop!

Stonehenge, as seen from a Street View panorama in Sun Surveyor


Posted by Monica Tran, Google Maps API

Sun Surveyor visualizes the sun and moon in a variety of ways for photographers, filmmakers, solar industry professionals, architects, homebuyers, gardeners, and anyone needing to predict or understand the movement of the sun and moon.

Adam Ratana is a Carnegie Mellon University graduate living in, and loving, Pittsburgh, PA. He produces dance music as a member of Pittsburgh Track Authority, enjoys photography, traveling with his wife, and writing fun software in his free time. Adam also enjoys attending the Pittsburgh Cocoaheads chapter meetings.

]]> In this guest blog post, we hear from Adam Ratana, a hobbyist photographer and software engineer by day, and developer of the Android and iOS Sun Surveyor apps by night. In this tutorial, Adam talks about his creative implementation of custom polylines on Street View panoramas in the Google Maps SDK for iOS.

 As a photography enthusiast, I’m always looking to capture images at the magic hour. My goal when creating Sun Surveyor was to give users an immersive way of visualizing the location of the sun and the moon, making it easy for anyone to figure out when the natural lighting is just right for the perfect shot.

When I set out to build Sun Surveyor, I knew I wanted to give users an easy way of visualizing the location of the sun and the moon. Sun Surveyor has an augmented reality (AR) feature, which overlays sun and moon paths on top of the device camera’s view. This is useful for understanding how light will change over time at a particular location. While I also created a Map View to show the paths on a Google Map for remote locations, it was not as intuitive as augmented reality.

Visualizing the sun and moon paths in augmented reality and map views

When Street View launched in the Google Maps SDK for iOS in v1.4.0 (July, 2013), I couldn’t wait to visualize the sun and moon paths within an interactive panorama. Street View panoramas bridge the gap between Sun Surveyor’s Map View and AR experiences by giving users an augmented reality experience, wherever they want to go.

Sun and moon paths with Street View panoramas

Implementing a sun path Overlay on Street View
I took a creative approach to working with the Google Maps SDK for iOs.  While polylines can be implemented in Map View, this isn’t yet possible in a Street View panorama. To display paths and other items that move with the Street View panorama, I needed to:
  1. Create an overlay on top of the panorama upon which to draw the items
  2. Synchronize the positions of the overlay items with the panorama as it moves
  3. Determine which data are visible and where on the screen to draw them
For this tutorial, I have provided a sample project that will get anyone started doing the same. Let’s walk through the steps.

I. Creating an Overlay

In our main UIViewController, we add a subclass of UIView for the overlay, make its background color transparent, and place the GMSPanoramaView below it in the view hierarchy.


Representing Overlay Items
We represent the overlay items with a protocol having two methods: updateWithPanoramaView and draw. The updateWithPanoramaView method updates an item’s screen location geometry, while draw draws it to the current graphics context.

We store all items to be drawn in a collection, update their positions based on the panorama position, and draw the collection in our view’s standard drawRect method.

If we want to make sure these items are drawn in a certain order that might change based on the data, we can add z-indexes to them and then sort the collection by z-index after we update them and before drawing.

II. Syncing the Overlay with the Panorama
To make sure this overlay view stays updated as the panorama moves beneath it, we can update the view’s data in an implementation of GMSPanoramaViewDelegate’s didMoveCamera method. We can use a CADisplayLink to ensure the overlay view is redrawn at regular intervals, and use a flag to make sure it is only redrawn when necessary.


Optimization
CoreGraphics can be a bottleneck. [UIBezierPath strokePath] and [NSString drawAtPoint] are expensive as you can see by profiling with Instruments. For performance intensive applications, an alternative is to use OpenGL. Avoiding overdraw is always a good idea, so the first optimization, if needed, is to carefully examine what is being drawn to the screen, and draw only what is necessary.

III. Mapping data to the panorama view
The GMSProjection class has a pointForCoordinate method that returns the screen pixel location for a coordinate on the Map. This is useful for overlaying elements on top of a GMSMapView, and is used in the Sun Surveyor Map View to draw text related to sun and moon paths on top of the Map.

GMSPanoramaView has a similar method, pointForOrientation. This method allows us to query the panorama for a screen pixel location given a GMSOrientation (bearing and pitch tuple) relative to the panorama location, where the camera is stationed, at ground level. This is useful to make sure an item we overlay onto the view remains in the same location relative to the scene, even as the camera moves and the view shifts.

Because the camera has a Field of View that determines what is visible on the screen, some orientations are not visible (such as behind the camera position). pointForOrientation helpfully returns NAN (not a number) for such orientations, so we know the given orientation is not visible.

With sun path data already expressed in terms of orientation relative to the ground level of the viewer, drawing corresponding paths with screen pixel locations is easy. We map our data with pointForOrientation, and draw what is visible by checking the result for NAN.



The sample project uses a panorama of Sydney, Australia, looking west, with a sun path for 12/20/2013.


Bonus: altering the Field of View
Version 1.4.1 of the SDK added support for changing the GMSPanoramaCamera’s field of view (FOV). The field of view determines how much of the scene is visible on a device screen, as well as how much distortion around the edges of the view is present. Smaller values for FOV are the equivalent of having a telephoto lens on a real camera: it brings distant objects closer.


Left: FOV of 60 degrees. Middle: 90 degrees (default). Right: 130 degrees.


Street View Panoramas are awesome and easy
The Street View panorama viewer in the Google Maps SDK for iOS is an example of a great API. The GMSPanoramaView class is simple to understand and use. In the course of a weekend, I was able to deliver a fun, interactive and highly requested feature to Sun Surveyor’s iOS users. I can’t wait to see what people are able to do with this new Street View Panorama feature in my app, and I look forward to seeing all the other implementations that others develop!

Stonehenge, as seen from a Street View panorama in Sun Surveyor


Posted by Monica Tran, Google Maps API

Sun Surveyor visualizes the sun and moon in a variety of ways for photographers, filmmakers, solar industry professionals, architects, homebuyers, gardeners, and anyone needing to predict or understand the movement of the sun and moon.

Adam Ratana is a Carnegie Mellon University graduate living in, and loving, Pittsburgh, PA. He produces dance music as a member of Pittsburgh Track Authority, enjoys photography, traveling with his wife, and writing fun software in his free time. Adam also enjoys attending the Pittsburgh Cocoaheads chapter meetings.

 ]]> https://googledata.org/google-maps/sun-surveyor-shines-with-street-view/feed/ 0 Map of the Week: Orbitz https://googledata.org/google-maps/map-of-the-week-orbitz/ https://googledata.org/google-maps/map-of-the-week-orbitz/#comments Fri, 23 Aug 2013 18:00:00 +0000 https://googledata.org/?guid=cf608813e1d02d3866b9055c071cfa59 In today’s guest blog post, we hear from Monika Szymanski and Mike Kelley, of Orbitz' Android engineering team, who recently migrated from version 1 to version 2 of the Google Maps Android API. 

About Orbitz
Nearly 30% of Orbitz.com hotel bookings are now made via mobile devices, fueled in part by the growth of the Android platform. The recently released 3rd-generation update of the Orbitz - Flights, Hotels, Cars app for Android brings major speed and ease of use improvements along with the latest Android UI design patterns to the app. The Google Maps Android API v2 is also integrated into the hotel search experience. Read on to find out how we did it, with tips and sample code along the way.

Migrating from v1 to v2 of the Google Maps Android API 
While users of the Orbitz.com Android app will notice some changes to the app’s user interface for maps, the changes to our code are more than skin deep. New classes offered in v2 of the Google Maps Android API like MapFragment and SupportMapFragment, the transition from ItemizedOverlays to Markers, and the addition of a well-supported info window pattern have made including a Google Map in an Android app much easier.

Say hello to the 3rd generation of Orbitz - Flights, Hotels, Cars app, using the Google Maps Android API v2

 Featuring Fragments 
Prior to the introduction of MapFragment (and SupportMapFragment)  in v2, we had to write a lot of code to manually show/hide the map view in our app. Only one instance of MapView could be created per activity, so we had to be overly clever about persisting that instance in our Activity. Lack of proper Fragment support was a common pain point for developers integrating v1 of the Google Maps Android API in their application.

When Fragment support was added in v2, we essentially rewrote our map code to take advantage of the new features of MapFragment. Let’s start by taking a look at our hotel results Activity layout:

You’ll notice that we’re not including the actual fragment in the layout - we add the Fragment at runtime, because we don’t want to pay the cost of the fragment transaction and add all the markers on the map, unless the user requests it.

You’ll also notice a bit of a hack at the bottom of the layout. In testing, we found that the MapFragment would leave a black box artifact on the screen on certain devices when the user opened our sliding menu navigation. Adding a simple FrameLayout “above” the map seems to fix the problem.

Extending SupportMapFragment makes it much easier to separate the map display logic from our Activity and list fragment. Our SupportMapFragment (and its inner classes) is responsible for:
  • Adding markers representing each available hotel 
  • Customizing the GoogleMap UI options 
  • Centering and animating the map to show the added markers 
  • Showing an info window when a marker is clicked 
  • Launching an Intent to display more details when an info window is clicked 
Next up, we’ll talk about how we add markers to the map and keep memory usage down.

Managing Markers 
One of the challenges in migrating from v1 to v2 of the Google Maps Android API was figuring out the best way to know which hotel’s info to display when a marker is tapped. To solve this, we place each <Marker, Hotel> pair in a HashMap when adding the markers to the Google Map. Later, we can use this HashMap to look up a marker's corresponding hotel info.

The code snippets below illustrate how we do it.


This HashMap allows us to look up the selected hotel in our InfoWindowAdapter, enabling us to display more information about it.


We place quite a few markers on the map for hotel results and each marker can have a different custom image. It's really easy to run out of memory and we were getting quite a few OutOfMemoryExceptions early in development. To manage memory more effectively, we made sure we didn't create a new new Bitmap and BitmapDescriptor for every marker placed on the map. We also ensured that the resources were recycled after we were done with them.


When the user taps a marker, we want to show more information; that’s where info windows come in handy. 

Introducing Info Windows 
Aside from simply viewing the location of all available hotels on a map, users are typically interested in the name and price of the hotel. The architecture for implementing this information window changed considerably from version 1 to version 2 of the Google Maps Android API. 

Before: Info windows in the Google Maps Android API v1
When using v1 of the Google Maps Android API, our app displayed more detailed hotel information in a custom info view when the user tapped on a hotel marker. That custom view displayed the hotel name and price, and triggered a custom animation when the view was added to the screen. This animation made it appear that the view was growing from inside the pin on the map.

We achieved this effect by setting the LayoutParams to MapView.LayoutParams.BOTTOM_CENTER and MapView.LayoutParams.MODE_MAP, which centered the bottom of the custom view on top of the tapped hotel marker.

With the introduction of the Google Maps Android API v2, MapView.LayoutParams.MODE_MAP was removed, so we explored alternative treatments to show the hotel information when the user clicks on a result. For our purposes, the best alternative was to use the new info window interface. 

After: Info windows in the Google Maps Android API v2
Creating an InfoWindowAdapter is pretty straightforward. The API provides two ways to populate the info window; either by supplying the contents of the info window (shown in the default window stylec) or creating a full View. Because we wanted to have a custom window background, loaded from a 9-patch, we opted to build a complete View for the info window by overriding the getInfoContents() method to return null, and by returning a custom View from getInfoWindow().

Here’s a sample of our code:


We could further simplify this code by having our HotelView take a Hotel model as a parameter in the constructor. 

A caveat with info windows is that even though they are populated by the returned View, the info window is not treated like a *live* View object. The system will call the view’s draw() method only once, then use that cached rendering as the user continues to interact with the map. Our existing animation didn’t work in the Google Maps Android API v2, but we decided to be consistent with the platform and remove the animation rather than try to hack around this limitation.

We <3 Google Maps Android API v2
Upgrading from version 1 to version 2 of the Google Maps Android API was virtually painless and fun to do! The introduction of MapFragment helped us separate the map display logic from the rest of the code and made code reuse much easier. Using custom info views was very straightforward with the new info window interface. We look forward to adding even more Google Map features to our app.

Posted by Monica Tran, Maps Developer Marketing

Monika Szymanski is a Lead Engineer on the Android team at Orbitz, where she works on apps that are friendly, fast, and easy to use. In her free time, she enjoys outdoors, running, red wine, and anything chocolate.

Mike Kelley is a Software Engineer at Orbitz, where he works on Android travel tools to help people travel smarter. He's a Michigan grad, transportation and technology enthusiast and craft beer buff. Some of Mike's ideas and projects live online at theelfismike.com.

 Orbitz Worldwide (NYSE: OWW) is a leading global online travel company that uses innovative technology to enable leisure and business travelers to search for, plan and book a broad range of travel products and services including airline tickets, hotels, car rentals, cruises, and vacation packages. Orbitz Worldwide owns a portfolio of consumer brands that includes Orbitz, CheapTickets, ebookers, and HotelClub. Also within the Orbitz Worldwide family, Orbitz Partner Network delivers private label travel solutions to a broad range of partners including many of the world's largest airlines, and Orbitz for Business delivers managed corporate travel solutions for corporations.
]]> In today’s guest blog post, we hear from Monika Szymanski and Mike Kelley, of Orbitz' Android engineering team, who recently migrated from version 1 to version 2 of the Google Maps Android API. 

About Orbitz
Nearly 30% of Orbitz.com hotel bookings are now made via mobile devices, fueled in part by the growth of the Android platform. The recently released 3rd-generation update of the Orbitz - Flights, Hotels, Cars app for Android brings major speed and ease of use improvements along with the latest Android UI design patterns to the app. The Google Maps Android API v2 is also integrated into the hotel search experience. Read on to find out how we did it, with tips and sample code along the way.

Migrating from v1 to v2 of the Google Maps Android API 
While users of the Orbitz.com Android app will notice some changes to the app’s user interface for maps, the changes to our code are more than skin deep. New classes offered in v2 of the Google Maps Android API like MapFragment and SupportMapFragment, the transition from ItemizedOverlays to Markers, and the addition of a well-supported info window pattern have made including a Google Map in an Android app much easier.

Say hello to the 3rd generation of Orbitz - Flights, Hotels, Cars app, using the Google Maps Android API v2

 Featuring Fragments 
Prior to the introduction of MapFragment (and SupportMapFragment)  in v2, we had to write a lot of code to manually show/hide the map view in our app. Only one instance of MapView could be created per activity, so we had to be overly clever about persisting that instance in our Activity. Lack of proper Fragment support was a common pain point for developers integrating v1 of the Google Maps Android API in their application.

When Fragment support was added in v2, we essentially rewrote our map code to take advantage of the new features of MapFragment. Let’s start by taking a look at our hotel results Activity layout:

You’ll notice that we’re not including the actual fragment in the layout - we add the Fragment at runtime, because we don’t want to pay the cost of the fragment transaction and add all the markers on the map, unless the user requests it.

You’ll also notice a bit of a hack at the bottom of the layout. In testing, we found that the MapFragment would leave a black box artifact on the screen on certain devices when the user opened our sliding menu navigation. Adding a simple FrameLayout “above” the map seems to fix the problem.

Extending SupportMapFragment makes it much easier to separate the map display logic from our Activity and list fragment. Our SupportMapFragment (and its inner classes) is responsible for:
  • Adding markers representing each available hotel 
  • Customizing the GoogleMap UI options 
  • Centering and animating the map to show the added markers 
  • Showing an info window when a marker is clicked 
  • Launching an Intent to display more details when an info window is clicked 
Next up, we’ll talk about how we add markers to the map and keep memory usage down.

Managing Markers 
One of the challenges in migrating from v1 to v2 of the Google Maps Android API was figuring out the best way to know which hotel’s info to display when a marker is tapped. To solve this, we place each <Marker, Hotel> pair in a HashMap when adding the markers to the Google Map. Later, we can use this HashMap to look up a marker's corresponding hotel info.

The code snippets below illustrate how we do it.


This HashMap allows us to look up the selected hotel in our InfoWindowAdapter, enabling us to display more information about it.


We place quite a few markers on the map for hotel results and each marker can have a different custom image. It's really easy to run out of memory and we were getting quite a few OutOfMemoryExceptions early in development. To manage memory more effectively, we made sure we didn't create a new new Bitmap and BitmapDescriptor for every marker placed on the map. We also ensured that the resources were recycled after we were done with them.


When the user taps a marker, we want to show more information; that’s where info windows come in handy. 

Introducing Info Windows 
Aside from simply viewing the location of all available hotels on a map, users are typically interested in the name and price of the hotel. The architecture for implementing this information window changed considerably from version 1 to version 2 of the Google Maps Android API. 

Before: Info windows in the Google Maps Android API v1
When using v1 of the Google Maps Android API, our app displayed more detailed hotel information in a custom info view when the user tapped on a hotel marker. That custom view displayed the hotel name and price, and triggered a custom animation when the view was added to the screen. This animation made it appear that the view was growing from inside the pin on the map.

We achieved this effect by setting the LayoutParams to MapView.LayoutParams.BOTTOM_CENTER and MapView.LayoutParams.MODE_MAP, which centered the bottom of the custom view on top of the tapped hotel marker.

With the introduction of the Google Maps Android API v2, MapView.LayoutParams.MODE_MAP was removed, so we explored alternative treatments to show the hotel information when the user clicks on a result. For our purposes, the best alternative was to use the new info window interface. 

After: Info windows in the Google Maps Android API v2
Creating an InfoWindowAdapter is pretty straightforward. The API provides two ways to populate the info window; either by supplying the contents of the info window (shown in the default window stylec) or creating a full View. Because we wanted to have a custom window background, loaded from a 9-patch, we opted to build a complete View for the info window by overriding the getInfoContents() method to return null, and by returning a custom View from getInfoWindow().

Here’s a sample of our code:


We could further simplify this code by having our HotelView take a Hotel model as a parameter in the constructor. 

A caveat with info windows is that even though they are populated by the returned View, the info window is not treated like a *live* View object. The system will call the view’s draw() method only once, then use that cached rendering as the user continues to interact with the map. Our existing animation didn’t work in the Google Maps Android API v2, but we decided to be consistent with the platform and remove the animation rather than try to hack around this limitation.

We <3 Google Maps Android API v2
Upgrading from version 1 to version 2 of the Google Maps Android API was virtually painless and fun to do! The introduction of MapFragment helped us separate the map display logic from the rest of the code and made code reuse much easier. Using custom info views was very straightforward with the new info window interface. We look forward to adding even more Google Map features to our app.

Posted by Monica Tran, Maps Developer Marketing

Monika Szymanski is a Lead Engineer on the Android team at Orbitz, where she works on apps that are friendly, fast, and easy to use. In her free time, she enjoys outdoors, running, red wine, and anything chocolate.

Mike Kelley is a Software Engineer at Orbitz, where he works on Android travel tools to help people travel smarter. He's a Michigan grad, transportation and technology enthusiast and craft beer buff. Some of Mike's ideas and projects live online at theelfismike.com.

 Orbitz Worldwide (NYSE: OWW) is a leading global online travel company that uses innovative technology to enable leisure and business travelers to search for, plan and book a broad range of travel products and services including airline tickets, hotels, car rentals, cruises, and vacation packages. Orbitz Worldwide owns a portfolio of consumer brands that includes Orbitz, CheapTickets, ebookers, and HotelClub. Also within the Orbitz Worldwide family, Orbitz Partner Network delivers private label travel solutions to a broad range of partners including many of the world's largest airlines, and Orbitz for Business delivers managed corporate travel solutions for corporations.
]]> https://googledata.org/google-maps/map-of-the-week-orbitz/feed/ 0 Street View, indoor maps, and an updated map design in the Google Maps SDK for iOS https://googledata.org/uncategorized/street-view-indoor-maps-and-an-updated-map-design-in-the-google-maps-sdk-for-ios/ https://googledata.org/uncategorized/street-view-indoor-maps-and-an-updated-map-design-in-the-google-maps-sdk-for-ios/#comments Wed, 17 Jul 2013 05:01:00 +0000 https://googledata.org/?guid=be31a665e1119b007d64230084d6557c Google Maps SDK for iOS last December, we’ve brought over a dozen of the most requested features to the platform and today, alongside the update to the Google Maps for iOS app, we’re announcing v1.4 of the SDK. Download the SDK to add an immersive mapping experience to your app, powered by accurate data from Google Maps.

With this update, developers can write a few lines of code to access popular features of Google Maps including: Street View in 50 countries, more than one billion square feet of indoor floor plans, and an updated design of our map tiles. For an overview of the new features in this release, watch this introduction from Google Maps Developer Relations team, Mano Marks and Luke Mahe:



Street View
Why drive 5 million miles of roads when you can use a few lines of code to bring Street View to your app? Use Street View panoramas to give users additional visual cues about a location. Try embedding Street View alongside a map or business photos to give your app real-world context. Or find inspiration in some our creative Javascript Street View implementations: GeoGuessr, Driveway Decision Maker, and Converse Street Ready.


Indoor Floor Plans
Indoor floor plans let you bring your users one level deeper by giving them access to floor plans inside shopping malls, airports, train stations and more. In a store finder, imagine showing users the inside of the building where your store is located, rather than just street level.


Updated Map Design
One point of feedback that we’ve heard consistently is that you want a map that blends seamlessly with your app UI. This version of the Google Maps SDK for iOS includes an update to the map tiles, that draws design inspiration from the new Google Maps. We’ve removed the yellow roads, which gives the map a more neutral palette, so that your app’s colors, styles, and map markers can stand out.

The updated map design (right) is inspired by the new Google Maps and has a more neutral palette, so that your app UI can shine.

We’re continuing to iterate rapidly to add features that you want. Let us know what you’d like to see in the next release of the Google Maps SDK for iOS using the issue tracker, and if you have questions, post them to the Google Maps API Developer Community.

Posted by Daniel Schramm, Associate Product Manager, Google Maps.]]> Google Maps SDK for iOS last December, we’ve brought over a dozen of the most requested features to the platform and today, alongside the update to the Google Maps for iOS app, we’re announcing v1.4 of the SDK. Download the SDK to add an immersive mapping experience to your app, powered by accurate data from Google Maps.

With this update, developers can write a few lines of code to access popular features of Google Maps including: Street View in 50 countries, more than one billion square feet of indoor floor plans, and an updated design of our map tiles. For an overview of the new features in this release, watch this introduction from Google Maps Developer Relations team, Mano Marks and Luke Mahe:



Street View
Why drive 5 million miles of roads when you can use a few lines of code to bring Street View to your app? Use Street View panoramas to give users additional visual cues about a location. Try embedding Street View alongside a map or business photos to give your app real-world context. Or find inspiration in some our creative Javascript Street View implementations: GeoGuessr, Driveway Decision Maker, and Converse Street Ready.


Indoor Floor Plans
Indoor floor plans let you bring your users one level deeper by giving them access to floor plans inside shopping malls, airports, train stations and more. In a store finder, imagine showing users the inside of the building where your store is located, rather than just street level.


Updated Map Design
One point of feedback that we’ve heard consistently is that you want a map that blends seamlessly with your app UI. This version of the Google Maps SDK for iOS includes an update to the map tiles, that draws design inspiration from the new Google Maps. We’ve removed the yellow roads, which gives the map a more neutral palette, so that your app’s colors, styles, and map markers can stand out.

The updated map design (right) is inspired by the new Google Maps and has a more neutral palette, so that your app UI can shine.

We’re continuing to iterate rapidly to add features that you want. Let us know what you’d like to see in the next release of the Google Maps SDK for iOS using the issue tracker, and if you have questions, post them to the Google Maps API Developer Community.

Posted by Daniel Schramm, Associate Product Manager, Google Maps.]]> https://googledata.org/uncategorized/street-view-indoor-maps-and-an-updated-map-design-in-the-google-maps-sdk-for-ios/feed/ 0 Behind the Map at Google I/O https://googledata.org/uncategorized/behind-the-map-at-google-io/ https://googledata.org/uncategorized/behind-the-map-at-google-io/#comments Wed, 08 May 2013 19:30:00 +0000 https://googledata.org/?guid=945c61087a843abbdcae9a10429a5a5a
It’s hard to believe that it’s been seven years since our first Geo Developer Day, which has since grown into a little event we now know as Google I/O. This year, we plan on bringing the best of Google Maps to every screen, including demos from the dashboard of a Mercedes-Benz to all seven screens of our latest Liquid Galaxy installation. Read on for a behind-the-map preview of the sessions, sandbox partners and events you won’t want to miss at Google I/O 2013.

Sessions
Join us for Google Maps: Into the Future, where our Product Managers and Developer Advocates will take at look at the present and future of Google Maps on our three platforms, the JavaScript Maps API, Android API, and the iOS SDK. Don’t forget to check out the Maps session schedule for more live I/O Live sessions and mark your favorites. And remember, all sessions will be available on YouTube after Google I/O.

Developer Sandbox
The Developer Sandbox at Google I/O gives you a chance to check out demos from developers who have built applications based on Google technologies and products--here are our favorites from Google Maps.

The developers behind Mercedes-Benz’s Digital DriveStyle will be on hand to walk you through their latest integration of the Places API, using the Google Maps SDK for iOS. Did we mention that the demo takes place from behind the wheel of a 2013 Mercedes-Benz SL550?

You can also take a look behind the lens of the Street View Trekker and SVII cameras, which have made their way from the peaks of Everest and the coral reefs of the Great Barrier Reef, to join us at Google I/O--you can even take the Trekker backpack on a hike through the Grand Canyon. Navigate different areas using the Wii Street U™ powered by Google available on Nintendo’s Wii U™ console.


Our other two partners will let you get hands-on, quite literally, with our Geo APIs. Try flying through Google Earth with a Leap Motion controller. And get an early demo of Map Diving on Google Developers Live this Thursday, where Instrument’s developers will walk you through how they built it using multiple instances of Chrome mashed up with the Google Maps Javascript API v3, Web GL, 3D CSS, web sockets and node.js.

Office Hours
As always, the Google Maps engineering and developer relations teams will be on hand to meet with you for office hours at our Developer Sandbox on the second floor of Moscone West.  Stop by on any one of the three days and chat with one of the members of the team on a variety of topics, including new APIs and features, questions about our APIs in your apps, or simply to learn more about how our technology works.

GeoMeetup
On Thursday, May 16, our friends at GeoMeetup and O'Reilly are hosting an event in San Francisco. While the GeoMeetup is fully booked, we're stil taking applications for speakers at the Ignite sesssions.

I/O Live
For those of you joining us online, we’ll be bringing you highlights from the event on I/O Live. Look for the camera icon on the session schedule and follow us at +Google Maps API, where we’ll let you know when to tune in for a tour of the Maps Sandbox. In the meantime, we’ll look forward to seeing you on Google Developers Live this Thursday for a demo of Map Diving!


Posted by Mano Marks, Maps Developer Relations Team]]>
It’s hard to believe that it’s been seven years since our first Geo Developer Day, which has since grown into a little event we now know as Google I/O. This year, we plan on bringing the best of Google Maps to every screen, including demos from the dashboard of a Mercedes-Benz to all seven screens of our latest Liquid Galaxy installation. Read on for a behind-the-map preview of the sessions, sandbox partners and events you won’t want to miss at Google I/O 2013.

Sessions
Join us for Google Maps: Into the Future, where our Product Managers and Developer Advocates will take at look at the present and future of Google Maps on our three platforms, the JavaScript Maps API, Android API, and the iOS SDK. Don’t forget to check out the Maps session schedule for more live I/O Live sessions and mark your favorites. And remember, all sessions will be available on YouTube after Google I/O.

Developer Sandbox
The Developer Sandbox at Google I/O gives you a chance to check out demos from developers who have built applications based on Google technologies and products--here are our favorites from Google Maps.

The developers behind Mercedes-Benz’s Digital DriveStyle will be on hand to walk you through their latest integration of the Places API, using the Google Maps SDK for iOS. Did we mention that the demo takes place from behind the wheel of a 2013 Mercedes-Benz SL550?

You can also take a look behind the lens of the Street View Trekker and SVII cameras, which have made their way from the peaks of Everest and the coral reefs of the Great Barrier Reef, to join us at Google I/O--you can even take the Trekker backpack on a hike through the Grand Canyon. Navigate different areas using the Wii Street U™ powered by Google available on Nintendo’s Wii U™ console.


Our other two partners will let you get hands-on, quite literally, with our Geo APIs. Try flying through Google Earth with a Leap Motion controller. And get an early demo of Map Diving on Google Developers Live this Thursday, where Instrument’s developers will walk you through how they built it using multiple instances of Chrome mashed up with the Google Maps Javascript API v3, Web GL, 3D CSS, web sockets and node.js.

Office Hours
As always, the Google Maps engineering and developer relations teams will be on hand to meet with you for office hours at our Developer Sandbox on the second floor of Moscone West.  Stop by on any one of the three days and chat with one of the members of the team on a variety of topics, including new APIs and features, questions about our APIs in your apps, or simply to learn more about how our technology works.

GeoMeetup
On Thursday, May 16, our friends at GeoMeetup and O'Reilly are hosting an event in San Francisco. While the GeoMeetup is fully booked, we're stil taking applications for speakers at the Ignite sesssions.

I/O Live
For those of you joining us online, we’ll be bringing you highlights from the event on I/O Live. Look for the camera icon on the session schedule and follow us at +Google Maps API, where we’ll let you know when to tune in for a tour of the Maps Sandbox. In the meantime, we’ll look forward to seeing you on Google Developers Live this Thursday for a demo of Map Diving!


Posted by Mano Marks, Maps Developer Relations Team ]]> https://googledata.org/uncategorized/behind-the-map-at-google-io/feed/ 0 An update to the Google Maps SDK for iOS https://googledata.org/google-maps/an-update-to-the-google-maps-sdk-for-ios/ https://googledata.org/google-maps/an-update-to-the-google-maps-sdk-for-ios/#comments Thu, 21 Feb 2013 20:00:00 +0000 https://googledata.org/?guid=dff9f8f615b27459e3284a00194d1eea Today we’re happy to announce of an updated version of the Google Maps SDK for iOS.

This version of the SDK includes support for ground overlays, gesture control and geodesic polylines.  To get started, enable the Google Maps SDK for iOS service in the Google APIs Console alongside other Google APIs.

We’ve also included a new sample app to make it even easier to learn how to use Google maps in your app.  Here’s a video with Mano Marks and Paul Saxman demonstrating the capabilities of the Google Maps SDK for iOS 1.1 release.



We hope these updates will enable you to enhance your app with Google maps (or create some new ones!).  As always, keep sending us your feedback and ideas, as we continue to make improvements to the SDK based on ideas that you’ve suggested and starred. For additional support, head over to Stack Overflow with your technical questions or watch our Google Maps Developers Live shows for tips, tricks and news about using the Google Maps APIs.  

Posted by Andrew Foster, Senior Product Manager, Google Maps
]]> Today we’re happy to announce of an updated version of the Google Maps SDK for iOS.

This version of the SDK includes support for ground overlays, gesture control and geodesic polylines.  To get started, enable the Google Maps SDK for iOS service in the Google APIs Console alongside other Google APIs.

We’ve also included a new sample app to make it even easier to learn how to use Google maps in your app.  Here’s a video with Mano Marks and Paul Saxman demonstrating the capabilities of the Google Maps SDK for iOS 1.1 release.



We hope these updates will enable you to enhance your app with Google maps (or create some new ones!).  As always, keep sending us your feedback and ideas, as we continue to make improvements to the SDK based on ideas that you’ve suggested and starred. For additional support, head over to Stack Overflow with your technical questions or watch our Google Maps Developers Live shows for tips, tricks and news about using the Google Maps APIs.  

Posted by Andrew Foster, Senior Product Manager, Google Maps
]]> https://googledata.org/google-maps/an-update-to-the-google-maps-sdk-for-ios/feed/ 0