Mark Murphy - Beginning Android

For example, here are the lines from the NooYawkactivity’s onCreate()method that accomplish the latter points:

ViewGroup zoom = (ViewGroup) findViewById(R.id.zoom);

zoom. addView(map. getZoomControls());

Then, you can manually get the zoom controls to appear by calling displayZoomControls()on your MapView, or they will automatically appear when the user pans the map as seen in Figure 34-1.

Figure 34-1. Map with zoom indicator and compass rose

Typically, you will need to control what the map is showing, beyond the zoom level, such as the user’s current location, or a location saved with some data in your activity. To change the map’s position, call setCenter()on the MapController.

This takes a GeoPointas a parameter. A GeoPointrepresents a location, via latitude and longitude. The catch is that the GeoPointstores latitude and longitude as integers representing the actual latitude and longitude multiplied by 1E6. This saves a bit of memory versus storing a floator double, and it probably speeds up some internal calculations Android needs to do to convert the GeoPointinto a map position. However, it does mean you have to remember to multiply the “real world” latitude and longitude by 1E6.

Just as the Google Maps you use on your full-size computer can display satellite imagery, so too can Android maps.

MapViewoffers toggleSatellite(), which, as the names suggest, toggles on and off the satellite perspective on the area being viewed. You can have the user trigger these via an options menu or, in the case of NooYawk, via keypresses:

@Override

publicboolean onKeyDown(int keyCode, KeyEvent event) {

if(keyCode == KeyEvent.KEYCODE_S) {

map. setSatellite(!map. isSatellite());

return( true);

} else if(keyCode == KeyEvent.KEYCODE_Z) {

map. displayZoomControls( true);

return( true);

}

return( super. onKeyDown(keyCode, event));

}

If you have ever used the full-size edition of Google Maps, you are probably used to seeing things overlaid atop the map itself, such as “push-pins” indicating businesses near the location being searched. In map parlance — and, for that matter, in many serious graphic editors — the push-pins are on a separate layer than the map itself, and what you are seeing is the composition of the push-pin layer atop the map layer.

Android’s mapping allows you to create layers as well, so you can mark up the maps as you need to based on user input and your application’s purpose. For example, NooYawkuses a layer to show where select buildings are located in the island of Manhattan.

Any overlay you want to add to your map needs to be implemented as a subclass of Overlay. There is an ItemizedOverlaysubclass available if you are looking to add push-pins or the like; ItemizedOverlaysimplifies this process.

To attach an overlay class to your map, just call getOverlays()on your MapViewand add()your Overlayinstance to it:

marker. setBounds(0, 0, marker. getIntrinsicWidth(),

marker. getIntrinsicHeight());

map. getOverlays(). add( new SitesOverlay(marker));

We will explain that marker in just a bit.

As the name suggests, ItemizedOverlayallows you to supply a list of points of interest to be displayed on the map — specifically, instances of OverlayItem. The overlay, then, handles much of the drawing logic for you. Here are the minimum steps to make this work:

• First, override ItemizedOverlayOverlayItemas your own subclass (in this example, SitesOverlay)

• In the constructor, build your roster of OverlayIteminstances, and call populate()when they are ready for use by the overlay

• Implement size()to return the number of items to be handled by the overlay

• Override createItem()to return OverlayIteminstances given an index

• When you instantiate your ItemizedOverlaysubclass, provide it with a Drawablethat represents the default icon (e.g., push-pin) to display for each item

The marker from the NooYawkconstructor is the Drawable used for the last bullet — it shows a push-pin, as illustrated in Figure 34-1 earlier in this chapter.

You may also wish to override draw()to do a better job of handling the shadow for your markers. While the map will handle casting a shadow for you, it appears you need to provide a bit of assistance for it to know where the “bottom” of your icon is, so it can draw the shadow appropriately.

For example, here is SitesOverlay:

private classSitesOverlay extendsItemizedOverlay {

privateList items = newArrayList();

privateDrawable marker = null;

public SitesOverlay(Drawable marker) {

super(marker);

this.marker = marker;

items. add( new OverlayItem( getPoint(40.748963847316034,

-73.96807193756104), "UN", "United Nations"));

items. add( new OverlayItem( getPoint(40.76866299974387,

-73.98268461227417), "Lincoln Center",

"Home of Jazz at Lincoln Center"));

items. add( new OverlayItem( getPoint(40.765136435316755,

-73.97989511489868), "Carnegie Hall",

"Where you go with practice, practice, practice"));

items. add( new OverlayItem( getPoint(40.70686417491799,

-74.01572942733765), "The Downtown Club",

"Original home of the Heisman Trophy"));

populate();

}

@Override

protectedOverlayItem createItem(int i) {

return(items. get(i));

}

@Override

publicvoid draw(Canvas canvas, MapView mapView,

boolean shadow) {

super. draw(canvas, mapView, shadow);