Google Maps API 3

Recommendations

Info

Introduction This book started out as an idea in spring 2009. I had written quite a few articles and tutorials about the Google Maps API v2 and thought that I could reuse them to write a book. That shouldn’t take too long, I thought. Shortly after, during Google I/O 2009, Google announced that it was releasing version 3 of the API. This release was a total remake of the old one, and I soon realized that I now had to write a book about this version instead. This rendered my intital plan to reuse my old articles completely useless. I also had to learn the new API; it was, after all, a complete remake. In retrospect, I’m glad that I did. The new API has a much cleanear programming interface and is more well structured than the old one. It just feels better to program with. And now that the book is being published, version 2 is deprecated, and version 3 is the recommended alternative for new map applications. Writing this book became a bigger undertaking than I first anticipated, but it has also been a lot more fun and interesting journey than I expected (even if I’ve despaired at times). Writing this, my first book, has been a learning experience. When I started the project, I had no clue how to go about it. I didn’t now how to get it published or how to structure it. But it all somehow unfolded as the work progressed, and here I am now, with a finished book. My journey with Google Maps started in 2007, when I created my very first map. It was a map showing the location of a restaurant. It not only let you see the location of the restaurant but also allowed you to enter an address in a text field to get driving directions. Very cool stuff. Since then, I’ve created a lot of maps using the API, not the least as part of my job as a web developer and interaction designer at Saab Security Solutions. My hope for this book is that you as a reader will be able to quickly grasp the concepts of the Google Maps API so that you can create your own map solutions. In fact, after reading this book, I hope that you’re not only able to create your own maps but that you’re also able to deal with many of the common pitfalls most developers encounter when building Google Maps solutions. Who This Book Is For This book is primarily for web designers/developers who want to learn how to use the Google Maps API on their own web sites. But even if you’re not in the field, you should be able to learn the concepts since they’re thoroughly described. It certainly helps if you have a basic understanding of how to create a web page and how the Web works, but other than that, you should be able to learn how to use the API from just this book. This book is also for those of you who have been using version 2 of the API. I’ve dedicated a whole chapter for you, Chapter 2, where I explain the differences between the two versions so that you can easily transfer your old maps to the new API. Downloading the Code You can download all the code for the examples from the book’s web site at http://www.svennerberg.com/bgma3. It’s also available on the Apress website at http://apress.com/book/view/1430228024 xvi
C H A P T E R 1 ■ ■ ■ Introducing the Google Maps API On today’s Web, mapping solutions are a natural ingredient. We use them to see the location of things, to search for the position of an address, to get driving directions, and to do numerous other things. Most information has a location, and if something has a location, it can be displayed on a map. There are several mapping solutions including Yahoo! Maps and Bing Maps, but the most popular one is Google Maps. In fact, according to Programmableweb.com, it’s the most popular API on the Internet. According to the site’s May 2010 statistics, 43 percent of all mashups use the Google Maps API (www.programmableweb.com/apis). In comparison, the second most popular API was Flickr with 11 percent, and the second most popular mapping API was VirtualEarth (Bing Maps) with 3 percent. Applications and web sites that are combining data or functionality from two or more sources are commonly referred to as mashups. Mashups are becoming increasingly popular and have revolutionized the way information is being used and visualized. Mapping solutions are one important ingredient in a lot of these mashups. The Google Maps API lets you harness the power of Google Maps to use in your own applications to display your own (or others’) data in an efficient and usable manner. An example of a mashup using the Google Maps API is the coverage of the Deepwater Horizon oil spill in the Gulf of Mexico. It combines data of the extent of the oil spill with Google Maps to visualize its massive impact (Figure 1-1); see http://mw1.google.com/mw-earth-vectordb/disaster/gulf_oil_spill/ gulf_oil_map.html. 1
Page 1: THE EXPERT’S VOICE ® IN WEB DEVE
Page 4 and 5: Beginning Google Maps API 3 Copyrig
Page 6 and 7: Contents at a Glance Contents......
Page 8 and 9: ■ CONTENTS Creating a Map .......
Page 10 and 11: ■ CONTENTS Automatically Adjustin
Page 12 and 13: ■ CONTENTS ■ Chapter 8: Creatin
Page 14 and 15: ■ CONTENTS MapCanvasProjection Ob
Page 16 and 17: About the Technical Reviewer ■ Ro
Page 20 and 21: CHAPTER 1 ■ INTRODUCING THE GOOGL
Page 26 and 27: CHAPTER 2 ■ TRANSFERRING FROM VER
Page 41 and 42: C H A P T E R 3 ■ ■ ■ Creatin
Page 43 and 44: CHAPTER 3 ■ CREATING YOUR FIRST M
Page 61: CHAPTER 3 ■ CREATING YOUR FIRST M
Page 64 and 65: CHAPTER 4 ■ TAKING THE MAP FURTHE
Page 66 and 67: CHAPTER 4 ■ TAKING THE MAP FURTHE
Page 68 and 69:
CHAPTER 4 ■ TAKING THE MAP FURTHE
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
CHAPTER 5 ■ X MARKS THE SPOT Figu
Page 94 and 95:
CHAPTER 5 ■ X MARKS THE SPOT Figu
Page 96 and 97:
CHAPTER 5 ■ X MARKS THE SPOT List
Page 98 and 99:
CHAPTER 5 ■ X MARKS THE SPOT A Si
Page 100 and 101:
CHAPTER 5 ■ X MARKS THE SPOT coul
Page 102 and 103:
CHAPTER 5 ■ X MARKS THE SPOT The
Page 104 and 105:
CHAPTER 5 ■ X MARKS THE SPOT }; }
Page 106 and 107:
CHAPTER 5 ■ X MARKS THE SPOT Addi
Page 108 and 109:
CHAPTER 5 ■ X MARKS THE SPOT Nest
Page 110 and 111:
CHAPTER 5 ■ X MARKS THE SPOT for
Page 112 and 113:
CHAPTER 5 ■ X MARKS THE SPOT What
Page 114 and 115:
CHAPTER 5 ■ X MARKS THE SPOT Auto
Page 116 and 117:
CHAPTER 5 ■ X MARKS THE SPOT List
Page 118 and 119:
CHAPTER 5 ■ X MARKS THE SPOT }; }
Page 120 and 121:
CHAPTER 6 ■ MARKER ICONS Changing
Page 122 and 123:
CHAPTER 6 ■ MARKER ICONS Figure 6
Page 124 and 125:
CHAPTER 6 ■ MARKER ICONS ■ Note
Page 126 and 127:
Page 128 and 129:
CHAPTER 6 ■ MARKER ICONS Using Sp
Page 130 and 131:
CHAPTER 6 ■ MARKER ICONS Origin t
Page 132 and 133:
Page 134 and 135:
CHAPTER 6 ■ MARKER ICONS Google M
Page 136 and 137:
CHAPTER 6 ■ MARKER ICONS Defining
Page 138 and 139:
Page 140 and 141:
CHAPTER 6 ■ MARKER ICONS A Clever
Page 142 and 143:
CHAPTER 6 ■ MARKER ICONS Adding D
Page 144 and 145:
Page 146 and 147:
CHAPTER 6 ■ MARKER ICONS Benefits
Page 149 and 150:
C H A P T E R 7 ■ ■ ■ InfoWin
Page 151 and 152:
CHAPTER 7 ■ INFOWINDOW TIPS AND T
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173:
Page 176 and 177:
CHAPTER 8 ■ CREATING POLYLINES AN
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
CHAPTER 9 ■ DEALING WITH MASSIVE
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
CHAPTER 10 ■ LOCATION, LOCATION,
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
APPENDIX ■ API REFERENCE The Name
Page 264 and 265:
APPENDIX ■ API REFERENCE Method R
Page 266 and 267:
APPENDIX ■ API REFERENCE MapOptio
Page 268 and 269:
APPENDIX ■ API REFERENCE Constant
Page 270 and 271:
APPENDIX ■ API REFERENCE ScaleCon
Page 272 and 273:
APPENDIX ■ API REFERENCE MapPanes
Page 274 and 275:
APPENDIX ■ API REFERENCE Table A-
Page 276 and 277:
APPENDIX ■ API REFERENCE Event Ar
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
APPENDIX ■ API REFERENCE Property
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
APPENDIX ■ API REFERENCE Geocoder
Page 292 and 293:
APPENDIX ■ API REFERENCE LatLng C
Page 294 and 295:
APPENDIX ■ API REFERENCE Method R
Page 296 and 297:
APPENDIX ■ API REFERENCE MVCObjec
Page 299 and 300:
• • • Index •A addDomListen
Page 301 and 302:
•INDEX latency, 111 limits on dow
Page 303 and 304:
•INDEX prime meridian, 4 x proper
Page 305 and 306:
•INDEX addListener() see addListe
Page 307 and 308:
•INDEX building address lookup we
Page 309 and 310:
•INDEX handleError function build
Page 311 and 312:
•INDEX size of, 137 v2/v3 compare
Page 313 and 314:
•INDEX creating zoom-in link in I
Page 315 and 316:
•INDEX adding rich content to Inf
Page 317 and 318:
•INDEX maxZoom property, 209 mini
Page 319 and 320:
•INDEX Map object, 247 Marker cla
Page 321 and 322:
•INDEX creating donuts, 170 fillC
Page 323 and 324:
•INDEX MapTypeId class, 51, 52, 2
Page 325 and 326:
•INDEX src attribute, video eleme
Page 327 and 328:
•INDEX streetViewControl, 59—61
show all

Google Maps API 3

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?