Google Plugin for Eclipse 2.5

Since Google added SQL support to App Engine in the form of Google Cloud SQL, the Google Plugin for Eclipse (GPE) team has been working hard on improving the developer experience for developing App Engine apps that can use a Cloud SQL instance as the backing database.

They are pleased to announce the availability of Google Plugin for Eclipse 2.5. GPE 2.5 simplifies app development by eliminating the need for manual tasks like copying Cloud JDBC drivers, setting classpaths, typing in JDBC URLs or filling in JVM arguments for connecting to local/remote database instances.

GPE 2.5 provides support for:

  • Configuring Cloud SQL/MySQL instances
  • Auto-completion for JDBC URLs
  • Creating database connections in Eclipse database development perspective
  • OAuth 2.0 for authentication.

Configuring Cloud SQL/MySQL instances
App Engine provides a local development environment in which you can develop and test your application before deploying to App Engine. With GPE 2.5, you now have the ability to configure your local development server to use a local MySQL instance or a Cloud SQL instance for testing. When you choose to deploy your app, it will use the configured Cloud SQL instance for App Engine.

Auto-completion for JDBC URLs
GPE 2.5 supports auto-completion for JDBC URLs, and quick-fix suggestions for incorrect JDBC URLs.

Creating database connections in Eclipse database development perspective
The Eclipse database development perspective can be used to configure database connections, browse the schema and execute SQL statements on your database.

Using GPE 2.5, database connections are automatically configured in the Eclipse database development perspective for the Development SQL instance and the App Engine SQL instance.

You can also choose to manually create a new database connection for a Cloud SQL instance. In GPE 2.5, we have added a new connection profile for Cloud SQL.

GPE 2.5 now uses OAuth 2.0 (earlier versions were using OAuth 1.0)  to securely access Google services (including Cloud SQL) from GPE. OAuth 2.0 is the latest version of the OAuth protocol focussing on simplicity of client development.

Can’t wait to get started?
Download GPE here and write your first App Engine and Cloud SQL application using GPE by following the instructions here.

Google hope GPE 2.5 will make cloud application development using App Engine and Cloud SQL a breeze. We always love to hear your feedback and the GPE group is a great place to share your thoughts.

Find your perfect home with Google Fusion Tables

My husband and I were recently in the market for a new home. We worked with a realtor for a few months, looking at several houses every weekend. As we checked out each house, we tracked our thoughts about it in a Google spreadsheet, which included columns for the address, our pros and cons, individual ratings and the combined rating of the house.

One day, while my husband and I were rating a recently viewed home, he came up with a brilliant idea to put all of our home data on a map. We realized that adding geographic information to our personal opinions would help us find trends, such as which neighborhoods we preferred. A light bulb went on over my head: Google Fusion Tables!

Fusion Tables is a data management web application that makes it easy to view tabular data on a Google Map. Columns with location data, such as addresses, points, lines, or polygons, are automatically interpreted and mapped. The map features can be styled according to the data in your table. It’s also simple to share the map visualization with others.

In just a few steps, we were able to convert our spreadsheet into a fusion table:


This was a great start, but what we really wanted was to quickly get a glimpse of this data on a map. All we had to do was select ‘Visualize > Map’ from the table menu and the data in the ‘Address’ column was geocoded (i.e. converted into latitude and longitude coordinates) and the markers were displayed on the map. Clicking on the markers showed additional information about the house pulled from our spreadsheet, including the pros, cons and ratings we inputted for each location.

Our house ratings viewed in Google Maps (after being converted into a Fusion Table).
Fusion Tables also allow you to style the features on the map according to data in a numerical column in the table. We had the perfect column to use for this purpose: the ‘Total Rating’ column!

 

In order to color code the map markers by their ‘Total Rating’ score, we customized the icons based on a range of scores, with red representing the lowest scores, yellow show mid-range scores and green showing the houses with the highest combined rating. After saving these new settings, the map markers were immediately styled:


Our new map made it much easier to see what locations we were most interested in (the house just south of Redwood City) and the neighborhoods of low interest (those that were closer to the bay or hills).

We shared the map with our realtor and she loved it. It helped her refine the selection of homes she showed us and in just a matter of weeks, I’m happy to say that my husband and I found the perfect house!

Posted by Kathryn Hurley, Developer Programs Engineer, Geo DevRel

via: GoogleLatlong

Keller on Letting It Go

 

“When one door of happiness closes, another opens; but often we look so long at the closed door that we do not see the one which has been opened for us.”

– Helen Keller (1880–1968)
American humanitarian
Advocate for the deaf and blind

 

What are the most common “drag you down, get in the way of success” thoughts?

  • Defeatist (accepting, expecting, or being resigned to defeat)
  • Cynical (contemptuously distrustful of human nature and motives)
  • Vindictive (seeking revenge)
  • Blame/ Fault (who cares? what are we going to do now?)
  • Wishful (do what you can to influence the deal and keep moving)

The new Places page and Google’s intentions

Much has been written about what Google left out in the Places upgrade and much speculation has been offered as to the reasons for the change. The specualtion have often made the assumption that the new design was a reactive response on the part of Google.

After looking at a large number of pages, I would suggest that the changes were primarily proactive in a nature and design driven (did I just say design and Google in the same sentence?). To get a sense of Google’s intentions I looked at a number Places pages in a range of industries and states and captured a screen shot of the information above the fold on a typical size screen 1280 x 1024 screen to see exactly which objects and activities had been prioritized. I captured the same Places page on my iPhone for comparison.

We all know of the call to action for additional reviews and uploaded photos those were very obvious. However Google made a number of other decisions in terms of how to prioritize the information. Here is the slide show and I think you will find the choices made interesting and design driven. Click to start the slide show:


While Google may have left some things off in response to complaints about their use of 3rd party reviews, for the most part the changes are a conscious design effort to make Places more interactive, more current and more social and more transactional.

They include a strong call to action (review, upload photos) and clear sense of priorities as to what is important going forward – even coupons now have a higher visibility – more user generated content, more understanding of your social circles intent and a greater desire, at least in the hotel industry, to use Places to “close” the sale.

UNITAR/UNOSAT team & Google Map Maker

In times of disaster and humanitarian needs, relief activities are sometimes carried out in chaotic and dynamic conditions in which multiple groups need to interact. First responders need to quickly build an on-the-ground picture of where people are, what condition they are in, what their needs are, what services are still available, and what resources have survived. This helps relief and humanitarian responders as well as local planners to plot and obtain a big picture of the impact of the disaster. They are then able to target their efforts and mobilize their resources of equipment, personnel, and supplies. Unfortunately, despite many technical and institutional advances, basic data is often not readily available on the onset of a disaster.

As Einar Bjorgo, UNITAR/UNOSAT’s head of Rapid Mapping, Applications and User Relations, has noted, Google Map Maker addresses a significant part of this data gap by capturing community knowledge — verified through community moderation — and making it available in near real-time. UNITAR/UNOSAT is the only operational UN program fully focused on providing satellite imagery and mapping products to the humanitarian community, including its United Nations’ sister agencies and governments — and it now does so largely with Google’s Map Maker data.

Today, after years of successful collaboration, UNITAR/UNOSAT (the operational satellite applications program of UNITAR) and Google have strengthened their joint efforts by signing an agreement that will give the crisis response and humanitarian community increased access to Google Map Maker source data for use in their disaster response and humanitarian activities, in more than 150 countries around the world.*

Under this agreement UNITAR/UNOSAT will act as a conduit within the United Nations family and its Member States to make Google Map Maker data more widely and easily available to aid organizations in the event of major disasters and for humanitarian efforts. In addition, government and United Nations agencies will be able to contact UNOSAT/UNITAR (email unosat@unitar.org) for consideration as potential licensees of the Google Map Maker data, for their disaster response, humanitarian and development projects. This agreement builds on dozens of previous joint mapping efforts between UNITAR/UNOSAT and Google, such as the ones that were coordinated for Pakistan, Sudan, and West Africa.

UNOSAT Manager Francesco Pisano shared his thoughts, noting that “Google Map Maker gives us access to baseline data over areas where detailed information is usually unavailable. Now roads, bridges, buildings, and other services, with local and official names, can be mapped and damages tracked in near real-time. This new ability to integrate Google Map Maker data more widely into our satellite analysis will have a monumental impact on UNOSAT’s ongoing efforts to make geographic information a key part of providing information for modern humanitarian relief. This agreement will also bring key benefits to the broader disaster and humanitarian community by making Google Map Maker data more widely and easily available.”

UNOSAT map of the flood-affected areas in Pakistan. It uses Map Maker data as its primary source of Road and Place names data.
With this new agreement with UNITAR/UNOSAT, we are expanding our ability to share useful map data that the Map Maker community contributes with the world, for increased benefit to people all over in preventing and recovering from man-made and natural hardships. We’re thrilled to deepen our relationship with the United Nations, and their partners. We welcome you to join the Map Your World Community, and start mapping to contribute to this effort and increase the quality of maps data. If you are one of our long-term mappers, thank you for your efforts that inspire us to keep finding ways to together make a positive difference to the world. Keep mapping!

 

Posted by France Lamy, Program Manager, Google.org

*Countries for which UNITAR/UNOSAT will have access to Google Map Maker data: Afghanistan, Albania, Algeria, American Samoa, Angola, Anguilla, Antigua and Barbuda, Argentina, Armenia, Aruba, Bahamas, Bahrain, Bangladesh, Barbados, Belarus, Belize, Benin, Bermuda, Bolivia, Botswana, Bouvet Island, British Indian Ocean Territory, British Virgin Islands, Brunei,Burkina Faso, Burundi,Cambodia, Cameroon, Cape Verde,Cayman Islands, Central African Republic, Chad, Chile, Christmas Island, Cocos (Keeling) Islands, Colombia, Comoros, Congo, Cook Islands, Costa Rica, Cote d’Ivoire, Cuba, Democratic Republic of the Congo, Djibouti, Dominica, Dominican Republic, Ecuador, El Salvador, Equatorial, Guinea, Eritrea, Ethiopia, Faroe Islands, Fiji, French Polynesia, French Southern and Antarctic Lands, Gabon, Gambia, Ghana, Greenland, Grenada, Guadeloupe, Guatemala, Guinea, Guinea-Bissau, Haiti, Honduras, Iceland, Iraq, Jamaica, Jordan, Kazakhstan, Kiribati, Kuwait, Kyrgyzstan, Laos, Liberia, Libya, Madagascar, Malawi, Malaysia, Maldives, Mali, Malta, Marshall Islands, Mauritania, Mauritius, Micronesia, Mongolia, Montenegro, Montserrat, Morocco, Mozambique, Myanmar (Burma), Namibia, Nauru, Nepal, Netherlands Antilles, New Caledonia, Nicaragua, Niger, Nigeria, Niue, Norfolk Island, North Korea, Northern Mariana Islands, Oman, Pakistan, Palau, Panama, Papua New Guinea, Paraguay, Peru, Philippines, Pitcairn Islands, Qatar, Romania, Rwanda, Saint Helena, Saint Kitts and Nevis, Saint Lucia, Saint Pierre and Miquelon, Saint Vincent and the Grenadines, Samoa, Sao Tome and Principe, Senegal, Seychelles, Sierra Leone, Solomon Islands, Somalia, Sri Lanka, Sudan, Suriname, Svalbard and Jan Mayen, Swaziland, Tajikistan, Tanzania, Timor-Leste, Togo, Tokelau, Tonga, Trinidad and Tobago, Tunisia, Turkmenistan, Turks and Caicos Islands, Tuvalu, Uganda, Uruguay, Uzbekistan, Vanuatu, Venezuela, Vietnam, Wallis and Futuna, Western Sahara, Yemen, Zambia, Zimbabwe