Today, Google announced Google Exacycle for Visiting Faculty, a new academic grant program that will provide 1 billion hours of computational core capacity to a small group of qualified researchers. These researchers are tackling a variety of problems that require massive amounts of computational power to advance their disciplines.
In the future, we think that Google Exacycle could also help companies create new business opportunities in a variety of industries, including human genome sequencing in biotech, Monte Carlo simulations in financial services, and complex rendering and CGI in entertainment, as well as address other challenging issues in energy, agriculture, and manufacturing.
If your business can benefit from access to large amounts of computing power (hundreds of millions of autonomous core-hours) to solve complex technical challenges, and you want to discuss potential applications, you can reach us here.
Posted by Jordan Breckenridge, Google Exacycle Team
Showing posts with label enterprise. Show all posts
Showing posts with label enterprise. Show all posts
Thursday, April 7, 2011
Thursday, August 19, 2010
Chains to trains: BART provides bike-friendly directions with Google Maps API Premier
Editor’s note: Today’s guest writer is Timothy Moore, Website Manager for Bay Area Rapid Transit (BART). Here he discusses how they use Google Maps API Premier v3 to power searches and biking directions on BART.gov. BART serves the San Francisco Bay Area covering 4 counties, 43 stations, 104 miles (167 km) of track, and has an average weekday ridership of 335,000 passengers. It is the 5th busiest heavy rail rapid transit system in the U.S.
Recently the BART website (www.bart.gov) launched some cool new trip planning services, including bicycle directions and station area points of interest, using the Google Maps API. The BART QuickPlanner is one of the most popular features on our website. If you live in the Bay Area, chances are you’ve used it. The QuickPlanner has traditionally offered a mix of BART trip plans, directions for walking and driving to the station, connecting transit information, carbon savings and more.
We're always looking for ways to improve the QuickPlanner, so when Google Maps started offering bicycle directions we were green with envy. Our latest research shows that only 4% of BART customers ride a bicycle from their home to a station. With ongoing cuts to connecting transit services and many BART station parking lots filled to the brim, adding bicycling directions to the QuickPlanner will help us promote the option to more than a million website visitors every month.

Frankly we've struggled with the integration of other mapping products into our custom-built BART scheduling application; weak documentation, limited real-world examples, and cumbersome programming requirements. Developing with the Google Maps API was a whole different world. As our lead programmer, Robert Falconer, noted, "It was easy to learn and quick to implement. And the ability to use free-form input terms for addresses, locations and points of interest was a major plus.”
If you've ever had to trap address or landmark input errors you know what he’s talking about. For example, if a user enters in “Frrey Blding” to the QuickPlanner, Google's geocoding service can recognize the user's intent and return the proper term "Ferry Building" with the correct corresponding address. All of this is done seamlessly behind the scenes so that all user sees is the address they are looking for when their trip is mapped out.

Again, using the Google Maps API, we’re able to provide more information about points of interest near BART stations, including directions. If you visit the neighborhood map section you can now use freeform search for station area destinations, and we’re no longer limiting you to searches based on standard address formats or a preset pull down menu. We also use the Google Maps API for services like “Find Closest Station” and for the map images presented on our station landing pages.
Overall this was a really fun project for us. I hope our use of the Google Maps API on bart.gov will encourage more bicycling to BART and I also hope people will use it to discover all of the awesome things that BART station area neighborhoods have to offer.
Posted by Carlos Cuesta, Google Earth and Maps Team
Recently the BART website (www.bart.gov) launched some cool new trip planning services, including bicycle directions and station area points of interest, using the Google Maps API. The BART QuickPlanner is one of the most popular features on our website. If you live in the Bay Area, chances are you’ve used it. The QuickPlanner has traditionally offered a mix of BART trip plans, directions for walking and driving to the station, connecting transit information, carbon savings and more.
We're always looking for ways to improve the QuickPlanner, so when Google Maps started offering bicycle directions we were green with envy. Our latest research shows that only 4% of BART customers ride a bicycle from their home to a station. With ongoing cuts to connecting transit services and many BART station parking lots filled to the brim, adding bicycling directions to the QuickPlanner will help us promote the option to more than a million website visitors every month.

Frankly we've struggled with the integration of other mapping products into our custom-built BART scheduling application; weak documentation, limited real-world examples, and cumbersome programming requirements. Developing with the Google Maps API was a whole different world. As our lead programmer, Robert Falconer, noted, "It was easy to learn and quick to implement. And the ability to use free-form input terms for addresses, locations and points of interest was a major plus.”
If you've ever had to trap address or landmark input errors you know what he’s talking about. For example, if a user enters in “Frrey Blding” to the QuickPlanner, Google's geocoding service can recognize the user's intent and return the proper term "Ferry Building" with the correct corresponding address. All of this is done seamlessly behind the scenes so that all user sees is the address they are looking for when their trip is mapped out.

Again, using the Google Maps API, we’re able to provide more information about points of interest near BART stations, including directions. If you visit the neighborhood map section you can now use freeform search for station area destinations, and we’re no longer limiting you to searches based on standard address formats or a preset pull down menu. We also use the Google Maps API for services like “Find Closest Station” and for the map images presented on our station landing pages.
Overall this was a really fun project for us. I hope our use of the Google Maps API on bart.gov will encourage more bicycling to BART and I also hope people will use it to discover all of the awesome things that BART station area neighborhoods have to offer.
Posted by Carlos Cuesta, Google Earth and Maps Team
Monday, July 19, 2010
Google Search Appliance now supports OpenSearch, enabling searching directly from browsers or Windows 7 clients

People should have the power to conduct searches from everywhere. This is why we provide users with numerous options beyond Google.com, such as typing in a search query directly in the address bar in Google Chrome, or through Google Toolbar, or Google Desktop.
However, when it comes to searching information on their corporate intranet, most users’ choices are limited. Corporate users typically have to go to a special URL or open up a special portal application to search their intranet. To alleviate this limitation, we have integrated the Google Search Appliance with the OpenSearch protocol. OpenSearch is a collection of simple formats for the sharing of search results. So for instance, integrating with OpenSearch enables accessing the Google Search Appliance directly from the browser:

Or, as shown below, you can search directly from Windows Explorer within Windows 7:

Ultimately, we are trying to provide as many options as possible to the end user. And by supporting OpenSearch, these options will increase as more platforms connect with OpenSearch.
You can immediately download this feature on Enterprise Labs, or learn more about it in our technical documentation.
Posted by Alexander Kerschhofer, Google Search Appliance team
Wednesday, June 23, 2010
Introducing multi-domain support in Google Apps
Thousands of organizations deploy Google Apps every day, and a challenge for some large businesses has been migrating employees on multiple domains. Until now, companies that ran into this issue could either set up other domains as domain aliases or set up different Google Apps accounts for each domain, neither of which was an ideal solution. Now there’s a better way: multi-domain support in Google Apps.
Posted by Will Smit, Software Engineer, Google Apps
Multi-domain support is a new admin control that allows organizations with two or more domains on Google Apps to manage them from a single control panel. Users belonging to different domains within an organization keep their domain-specific email address but can see coworkers from other domains in the organization’s global address book. It’s also easy for users to share across domains in Google Docs, Sites and the rest of Google Apps. Matt Vandenbush, director of IT strategy and architecture at Brady Corporation, says, "Multi-domain support in Google Apps lets us administer our entire organization from one central place. Considering that we have users on 88 different domains, this is a big time-saver for our IT department, and it lets employees from different parts of our organization share information much more seamlessly than before.”
This feature is available now to Premier and Education edition users at no additional charge. To learn more about multi-domain support on Google Apps, please visit our Help Center or join us for a live webinar on Tuesday, July 13th at 9am PST / 12pm EST / 5pm GMT.
Subscribe to:
Posts (Atom)
