Official Google Maps API Blog

Official Google Maps API Blog

Neo Geo Blog

Wednesday, May 28, 2008 at Five:20:00 PM

Posted by Michael Weiss-Malik, KML Product Manager

I have good news and bad news. Let’s commence with the bad.

The bad: After Two years, 6 months, and 14 days of dedicated developer community service, the Official Google Maps API Blog is being retired. That’s right. the blog you’re reading right now, right here, is no more, beginning today. No more news will be posted here.

The good: All is not lost! A fresh blog is taking this blog’s place: The Google Geo Developers Blog. Hop on overheen there to see the very first postbode and get the utter story on the switch.

So if you’re reading this postbode ter an RSS reader, be sure to subscribe to the fresh blog’s feed. And if you’re reading this postbode right on blogger itself, be sure to update your bookmark. Because there will still be slew of continued Maps API news. you just won’t be able to catch it here.

See you all overheen at the fresh blog!

App Engine, Restringido Search, & Maps: Making Static Maps. Interactive?

at Ten:50:00 AM

Posted by Ben Lisbakken, AJAX APIs Team

JavaScript and Flash are fine for putting Google Maps on your webstek, but sometimes they just won’t do. For mobile browsers or users with dial-up connections, simpler is better. So I wrote an open source non-JavaScript version of Google Maps which is designed to demonstrate how effortless it is to write an application on App Engine that makes use of two fresh APIs from Google: The Static Maps API and the Locorregional Search API’s Surplus interface. It doesn’t have advanced features like street view and public transportation, but it gives you a searchable opbergmap that you can teleobjetivo te/out on spil well spil save locations. It also automatically saves your last ordner view so that every time you go back to the webpagina it will showcase you what you were last looking at. Check out the source code.

It uses App Engine to store saved points, the AJAX LocalSearch Surplus API for search functionality, and the Static Maps API to display maps. App Engine is effortless to learn and the gegevens store is useful for this kleintje of application. The Surplus API for LocalSearch is also very plain. For more information on it, go here.

To use the Static Maps API, you just need to create a URL with the zindelijk parameters for your desired opbergmap view. Keep ter mind that you need to set the teleobjetivo level (unless you are specifying numerous points &mdash, then it’s calculated for you). Ter the vast majority of cases, this is totally fine. Te my case, however, I needed to know what the teleobjetivo level wasgoed, so that I could give the user the option to teleobjetivo ter/out. That meant coming up with calculations of the teleobjetivo both for the numerous points and single point case, and that wasgoed the trickiest part of the app.

If you use the AJAX Locorregional Search and it comebacks one result then there will be a viewport object returned with it. This viewport contains the Northeast and Southwest latitude/longitude bounds that are optimal for displaying this point. However, Static Maps only accept teleobjetivo levels and center points. Here’s the Python to generate that information: At this point you will have everything you need to construct the opbergmap: the center point (the Recinto Search point), teleobjetivo level, marker point.

Then there’s the case where you have numerous points returned by the AJAX Circunscrito Search. Since wij will have a collection of latitudes and longitude points that wij want to display wij can just find the minteken/maxes, do some rounding, and voila you get a bounding opbergruimte. With a bounding opbergruimte and a calculated center point, you can repeat the same steps spil before.

From line 121 to about 285 you’ll find all the necessary functions for the situations described above. Attempt using this code to create your own interactive version of Static Maps, and let us know ter the forum if you have questions or just want to voorstelling off your nifty app.

geo search Two.0: Gegevens Ter, Gegevens Out

Thursday, May 22, 2008 at Ten:05:00 AM

Posted by Pamela Fox, Maps API Team

Last week during the geo madness of Where2.0 and WhereCamp, wij announced two enhancements ter geo search to make it both lighter for developers to get their gegevens into our geo search index and lighter for developers to get gegevens back out of the index:

  • Geo Sitemaps: Sitemaps are a protocol that bots use to index content from websites. Last year, wij announced the capability to include KML/GeoRSS files te regular sitemaps just like a natural web resource. This year, wij announce a special extension for sitemaps that adds geo-specific tags and makes it lighter for us to index. To get your geo content indexed spil prompt spil possible, just submit the sitemap to Google Websitebeheerder Central. For more information on creating a KML opstopping to include te a sitemap, read this article te the KML documentation. An example geo sitemap listing a KML and a GeoRSS verkeersopstopping is shown below:
  • Geo search ter the API: The Nave Search API has traditionally bot used to terugwedstrijd business listings and address geocodes. Spil of last week, it can now be used to retrieve any of the content wij have te our geo index. There are a duo different ways to do this, depending on how you use the API. If you’re using the LocalSearchControl, here’s some sample code (and live example) that will come back blended results: If you’re using the Locorregional Search API from Javascript, here’s some sample code to terugwedstrijd only results from indexed geo files: And eventually, if you’re using the Locorregional Search API from somewhere other than Javascript – for example, with our fresh nifty Maps API for Flash – here’s some sample AS3 code (and live example) to terugwedstrijd only results from indexed geo files PLUS add a webpagina restrict technicus to limit it to results from platial.com:

There are (atleast) two truly cool consequences of this news: 1) you’ll be able to enable users of your mashups to instantly find international results where previously none existed, and to be able to find results for non-standard searches (e.g. “dog parks”), and Two) by indexing your content, waiting a few weeks, and then using the circunscrito search with a “webpagina:yourdomain.com” appended to the query, you get to leverage the power of google search on your own content with hardly any code of your own.

So what are you waiting for? Give us your geo sitemap, use our API calls, and let us know what you think te the Maps API, KML, or AJAX API forums.

libkml Marches On!

Monday, May Nineteen, 2008 at Five:04:00 PM

Posted by Mano Marks, Geo APIs Team

Google has released version 0.Two of libkml, an open source library for serializing and deserializing KML files. libkml now uses a memory management scheme based on “brainy pointers”, and has deprecated the use of SCons. On Linux and Mac OS X it now use the traditional automake, and on Windows Microsoft Visual Studio. The “brainy pointer” scheme presently restricts support for some alternate language bindings, so libkml 0.Two can only be called from C++, Java, and Python. Version 0.1 also supported PHP, Perl, and Ruby, and is still available ter the subversion repository if you’re interested. Wij project on restoring the those bindings spil soon spil wij can.

Here’s an example of what the code looks like:

The engineers who worked on it waterput a lotsbestemming of thought into making it swift and light weight. However, it is an alpha release. Wij truly would love to have comments and terugkoppeling on it, both ter the KML Developer Support forum and ter the libkml kwestie tracker.

Love My Maps? Use its Line and Form Editing ter your API Apps!

Friday, May 16, 2008 at Four:30:00 PM

Posted by Keith Golden, My Maps team

When wij launched the opbergmap editing contraptions ter Google Maps, the reaction of developers wasgoed “This is cool, but how can I use it on my own webpagina?” Spil someone who wasgoed originally drawn to Google te part because of the Maps API and the good developer community around it, I committed to making the My Maps implements useful for developers on their own sites.

Today, I’m pleased to announce that our user interface functionality for editable polylines and polygons is now part of the Maps API.

Say, for example, that you have a GPolygon you want users to be able to edit. Simply call GPolygon.enableEditing() and the poly will have draggable edit control vertices when the user mouses overheen it. To zometeen make it non-editable, call GPolygon.disableEditing() .

Wij’ve also exposed extra events for GPolygon and GPolyline so that you can lightly mimic the MyMaps behavior (te mashups or Mapplets) by calling enableEditing on “mouseover” and disableEditing on “mouseout”. To find out when the user makes an edit, listen for the “lineupdated” event. And if you want users to be able to draw a fresh GPolyline totally from scrape, just use enableDrawing spil shown below:

Every click on the schrijfmap will add a fresh vertex to the polyline until the user double-clicks or clicks again on the last vertex. You can also call enableDrawing to lets users append vertices to either end of an existing polyline. And just because everyone likes pretty colors, wij exposed methods to let you switch the style of a polyline or polygon: setStrokeStyle and setFillStyle . Have joy, and let us know what you think te the forum.

Introducing the Google Maps API for Flash

Wednesday, May 14, 2008 at Five:40:00 AM

Posted by Mike Jones, Maps API Team

Here at Google, wij receive a loterijlot of feature requests – and it feels excellent every time wij fulfill one of them. The capability to utilize the power of Google Maps from Flash is one of those requests that has bot popping up on blog posts and other forums since the beginning of time (or more accurately, the beginning of the Javascript Maps API). Overheen the past few hours, I’ve had the enjoyment of ultimately witnessing this particular feature request – a Maps API for Flash – come to fruition. Tiredness will grab mij soon, no doubt. If you’re one of the very first readers of this postbode, surplus assured that I’m unlikely to still be awake: long hours have bot worked, pre-launch nerves have jangled. Now it’s time to let our kind liberate into the world and see how the developer community will embrace it.

So, what do I like about the API for Flash? Smoothness and speed are a big part of it. Wij’ve designed it so that Flash graphics can be used for each tile layer, marker and informatie window – opening up possibilities like dynamic shading, shadowing, animation, and movie. When the user zooms the opbergmap, magnification switches toebijten slickly and place names fade te. After the user hauls a marker, it gently bounces to a halt. Generally, Flash permits for much greater embellishment, and, well. “flashiness.” I get excited just thinking about the creative ways developers might take advantage of having a Flash API for Google Maps.

What wasgoed one of our main vormgeving decisions for this project? Wij knew that version 1 of any software project is not ideal, so wij opted to split the interface and implementation. Spil a result, you can build against the current version of the API, and spil wij add enhancements and tweaks, your webstek benefits automatically from each update. When you wish to take advantage of fresh API functions, only then do you need to download the latest API and rebuild.

What does it look like? Wij’ve played with it, thrown our ideas te, and also worked with outside companies to see how they use the API. It’s bot a pleasure to see some of the demos that have come back. Here’s one from AFComponents that shows some of the possibilities:

When I very first joined Google ter Sydney, I got to hear about the practice of the Maps team when they very first observed the traffic and the whirr build for the launch of Google Maps. Well, now I’m ready to practice that with this fresh API. Do send us terugkoppeling, wij’re looking forward to it.

Upcoming Events

Friday, May 09, 2008 at 1:49:00 PM

Posted by Pamela Fox, Google Geo APIs Team

There’s four big Geo events ter the San Francisco Bay Area this month, and Mano and I will be at all of them. Here’s the details:

Where2.0: May 12-14th

Sharing Your Content on the Google Maps API

Ter this session, you’ll roll up your sleeves and learn about publishing and sharing using the Maps API. Then wij’ll hear from Google fucking partners about what constitutes “great” content and how they expose it.

Searching the Geoweb: Exposing Your Geo Gegevens to Search Engines

Have you bot wondering how to drive traffic to that cool maps mashup you created recently? Wij’ll vertoning you how to get your maps mashup crawled and indexed, and how best to optimize your content for user discovery via search using KML.

WhereCamp: May 17-18th

No sessions planned! This is an unconference – that means the participants do the session programma on the spot. So if there’s a Maps API or KML topic you want to talk about, come on by and propose it! (And stay for the slumber party, there’ll be lots of hacking and coffee). And, it’ll be at the Googleplex! And it’s free!

Web Two.0 Mapping and Social Networks Group: May 20th

Communities + Google Maps: Stiffer, Better, Swifter, Stronger

Pamela Fox will talk about the various ways of using Google Maps & the Maps API to create user-contributed maps, covering the spectrum from no-coding solutions to total custom-built databases and code, and displaying examples of sites successfully using each mechanism.

Google I/O: May 28-29th

There’s lots of Geo sessions at Google I/O, here’s just Three:

Harnessing StreetView, Static Maps, and other Fresh Additions to the Google Maps API:

Ben Appleton will review some of the latest additions to the Maps API including how to use Static Maps for rapid pagina explosions and printable maps, and how to incorporate Street View imagery ter your app.

Hosting Your Geo Gegevens, an Overview of Vormgeving Options:

Mano Marks will discuss the various options for hosting your Geo gegevens, including Google App Engine, and explain how to choose the right gegevens monster for your project.

The World’s Information ter Setting:

Michael T. Jones will discuss fresh product directions and key trends of importance to geo developers.

Be sure to visit the Google I/O webstek to see the accomplish list of sessions and to register. For those coming from out of town, wij’ve arranged discounted slagroom rates at nearby hotels. Read the details on the webstek to take advantage of the discount, but stir prompt because the hotel discount finishes May 13th.

Wij’re looking forward to watching you at some of thesis events soon.

Related movie: How To Create Custom-made Financial Year Quarters – Power Bisexual


You may also like...

3 Responses

  1. AmandaGreene says:

    Your BCH is now ter your Coin Colchoneta account, and if they did it for safety like they say I’m fine with it. Now that the Largest Brokerage is supporting BCH wij will see a big dump ? or a slow Pump ?

  2. KerryB78 says:

    I think this is a excellent case explore moving forward when other coins split, even tho’ I didn’t support Bcash I did want everyone to have to capability to access their rightful tokens. The argument now is everyone should be responsible for their deeds and Coinbase laid out their project of act weeks ahead of the hardfork. However I recall when Poloniex had to zekering serving residents te one state and many of those members never got an email or warning when logging on the webpagina. I’ll keep an eye out on the story even I don’t know who’s right or wrong on this one.

  3. jewel1964 says:

    I think they said by January 1, 2018…so hopefully bitcoin contant’s blockchain strings up around at least long enough for people that have money te coinbase

Leave a Reply

Your email address will not be published. Required fields are marked *