Posts Tagged ‘Google’

  • Are ski slopes streets? Google says YES, they are.

    0

    We know Google mounts car with 360 degrees cameras and GPS to show us streets. We know Google also mounts bicycles with 360 degrees cameras and GPS to show us streets where cars are not allowed to drive. But now Google also mounts snowmobiles with 360 degrees cameras and GPS to show us ski slopes in the mountains.

    This video was embedded using the YouTuber plugin by Roy Tanck. Adobe Flash Player is required to view the video.

    Rign on time, only several days before the official start of the winter olympics Google publishes street view images from Whistler Mountain and several other ski resorts around Vancouver.

    View Larger Map

    Quote from the Google Blog:

    The Street View team’s constant experimenting yielded a snowmobile decked out with cameras to capture slope-level imagery of several runs on Whistler Blackcomb Mountains. The view from the top of 7th Heaven chairlift on Blackcomb and from the peak of Whistler are among my favourites, as are the top of the Dave Murray downhill, where the men’s alpine skiing events will start, and the Peak 2 Peak gondola. (That’s Whistler’s new feat of engineering which takes skiers and riders from Whistler to Blackcomb.) With the Street View trike, we’ve also covered Whistler Village and Whistler Creekside at the mountains’ bases.

    The Google Maps team also launched a new site, including all street view areas of ski slopes, for the Olympic Winter Games: www.google.com/games10

    The only question left: Where else will be StreetView and do we need all this imagery?

    Critical Statement: The next thing announced are indoor StreetViews in stores and shopping centers. Again a playground for marketing. I hope at least some places on planet earth will left blank on the StreetView Map.

    [http://google-latlong.blogspot.com/2010/02/street-view-hits-slopes-at-whistler.html]

  • Google I/O: What would you say if you get a free Android Phone?

    0

    Attendees of the this years Google I/O Conference get an HTC Magic smartphone for free. If I had known this before maybe I had planned a trip to San Francisco to be there.

    io2009

    Even though the smartphone was the highlight of the first day in the Moscone Center also interesting things were discussed. Main topics were HTML 5, Android, AppEngine, etc. Google made a clear statement to be in favour with HTML 5. They do not want to wait another 10 years before using new technology as it was with AJAX. One slide contains:

    5>2

    Google thinks HTML 5 will be the next evolution after Web 2.0. The examples shown in the keynote gave an shot impression what will be possible with HTML 5. For example Youtube can be coded completely with HTML 5 without the need of further plugins. Also 3D Grahpic application will become possible with HTML 5. According to Google also the browser support is already good. All in all work for developers will become easier interacting on pixel level. The remaining question is: Who will need flash anymore?

    Another part was about Geolocation inside modern browsers. Browser applications will use Cellular and Wireless networks to determine the current location of the user. This could be very need when working with mapping application. The security issue was also mentioned, because of course it could also happend that your location is used by malware (e.g. advertisments, etc.)

    The next version of Android (post 1.5) will include open source speech recognition. It was also announced that today (2nd day) we will hear about an amazing new product launch from Google. I hope we will not be dissapointed after the 2nd keynote.

    You can follow Google I/O on Youtube.

  • Streetview is covering Europe

    0

    More and more parts of Europe are covered with Streetlevel imagery in Google Maps. The last update effected several cities in Great Britain. In following countries is Google’s StreetView available.

    • Great Britain
    • Spain
    • France
    • Italy
    • The Netherlands

    europe_sv[via Google Maps]

  • StreetView available for Vienna, Austria

    2

    StreetView is now available for the Austrian capital Vienna. But it is not the original StreetView service by Google Maps. The Service is provided by eXtreme Soft Group S.R.L. a private company seated in Bucharest. Their main task is to provide “street-level-imagery”.

    norc

    The web service allowing its visitors to do virtual walks through cities in Central and Eastern Europe. The images provided to the visitors are taken based on a proprietary technology of generating views that are geo-referenced in the street. The technology consists in using cars equipped with a proprietary panoramic photographing device based on 10 cameras, correlated with a Differential Global Positioning System (DGPS).

    The current coverage:

    • Romania – www.norc.ro – Bucharest, Ploiesti and Prahova Valley, Constanta and the Seaside, Brasov and Poiana Brasov, Cluj-Napoca, Timisoara, Iasi, Sibiu, Pitesti, Targoviste
    • Austria – www.norc.at – Vienna
    • The Czech Republic – www.norc.cz – Prague, Brno
    • Slovakia – www.norc.sk – Bratislava, Trnava, Kosice, Banska-Bystrica, Zilina, Nitra
    • Poland – www.norc.pl – Warsaw, Krakow, Poznan, Wroclaw
    • Russia – www.mappi.ru – Moscow

    Link for Austria: www.norc.at

  • Nearly area-wide streetview – but only in the USA

    0

    Google has updated StreetView data for the USA. According to Google the update doubles the coverage of StreetView information in the United States. As you can see in the image the coverage for the USA is quite impressive. Also the coverage for Australia and New Zealand is very good.

    The current coverage of the European StreetView information by contrast is still very poor. Beside the Tour de France track of 2008, some cities in France, Spain and Italy you will not find any places where StreetView is available. StreetView cars were seen all over Europe, therefore it can be assumed that there will be a massive update of StreetView data in Europe as well.

    [via Googlewatchblog]

  • Google Earth for iPhone

    0

    It was only a question of time since Google Earth will be available on the iPhone. Now it is available as free download form the iTunes App Store.
    Even if Google is promoting their own handset platform (Android) the is a strong relation to Apples and the iPhone. Now they have developed a own customized application of Google Earth. The functionality is quite similar to the desktop version. Of course the interface is optimized for the touch screen and the sensors. The following videos shows how to interact with Google Earth on an iPhone.

    You need to a flashplayer enabled browser to view this YouTube video

    The software can also be used for the iPod touch.

    [via derStandard.at]

  • Google switched completely to TeleAtlas

    2

    Google switched their underlying map data to TeleAtlas for their whole branch of products. Now Google Earth, Google Maps, Local Search and Google’s mobile solution using Teleatlas for their underlying data. Many see this as logical step after the acquisition of Navtech by Nokia. Recently there where some differences in locations when you ask for them in two different products (e.g. Google Maps and Google Maps API). This should now be unified.

    Map Errors can be reported:

    With the “Edit” functionality the users have the possibility to correct mapping errors (http://maps.google.com/support/bin/answer.py?answer=68474#modify). but Google also encourage people to report errors directly to Teleatlas using following link: http://www.teleatlas.com/ForConsumers/MapFeedback/index.htm

    Information to Teleatlas:

    TeleAtlas was founded in 1984 and is a wholly-owned subsidiary of TomTom. The headquarter is in Ghent, Belgium and by 2007 about 1900 employees are working at TeleAtlas. The total revenue is more than 300 mio. Euros. Official Homepage: www.teleatlas.com

    [via spatiallyadjusted]

  • “Google Satellite” Successfully Launched Into Space

    0

    I’ve already posted that Google together with GeoEye will launch a new Satellite for Google Earth and Google Maps images. The so called “GeoEye-1” satellite will take photos with a resolution of 0.41 cm / pixel. In the following pictures you can see the difference between a image with 100cm/px reolution and a picutre with 41cm/px.

    100cm/px

    41cm/px

    On the GeoEye Website you can watch the lauch of the satellity on video.

  • Picasa 3.0 – New Version available

    0

    Today Google has not only released a new Browser (Google Chrome), they also introduced a new version of Picasa Web Albums and their Picasa software. Picasa Web Albums looks a little bit fresher. Some news includes different tabs to explore and manage photos. Additionally it is possible to upload new photos via email. The change of the image size can be done smoothly and the album map has  been extended. But the biggest feature is definitively face recognition. It takes a little while until all photos are scanned and faces have to be tagged.

    Also the Picasa software itself has a new interface with additional features.

    One thing still hasn’t changed: Picasa Web Albums offers only 1 GB storage for free. That’s unacceptable nowadays.

  • Android in a pre 1.0 version available

    0

    Google recently released a pre 1.0 beta version of the Android SDK.

    “This is the first release of the Android SDK that is formally on the path to Android 1.0.”

    This let assume at first handset devices are comming soon.
    As Google clarifies this is the first serious version of on the way to Android 1.0. Previous releases were considered very early looks at the SDK. This release should be fully compatible with Android 1.0 and all applications build with this release should run on final Android 1.0 devices.
    The differences between this release an the final release are expected to be small and no major API changes are planned.

    This beta SDK contains a large number of bug fixes and improvements form the early SDKs.

    Some important changes include:

    * new standard applications like arlam, calculator, camera, music, photo and messages where added.
    * inprovements of the developer tools, e.g., preview of the XML layout.
    * changes and impreovements withing the API
    * new “Home” screen.

    The relase notes, change overview and API Delta Report give a complete overview about all changes and extenstion of the SDK.

    Now some issues from these documents related to “GEO”:

    Location (Geo)

    * The android.hardware.Sensors class has been replaced by android.hardware.SensorManager and android.hardware.SensorListener.
    * The SensorManager class now notifies SensorListener objects of sensor changes, rather than firing Intents. The registerListener and unregisterListener methods are used to add and remove listeners.
    * There is a new constant SensorManager.STANDARD_GRAVITY that may be useful to interpret accelerometer values.
    * A method LocationManager.getProviderNames() has been added that
    * returns the names of all providers, including ones for which the caller lacks permissions.
    * The LocationManager class now notifies LocationListener objects of location and status changes, rather than firing Intents.
    * The requestUpdates method has been renamed to requestLocationUpdates and now takes a LocationListener object rather than an Intent.
    * A new requestStatusUpdates method has been added, also taking a LocationListener object.
    * The removeUpdates method now takes a LocationListener object.
    * The LocationManager.request*Updates methods must be called from a Looper thread, such as the main thread of an Activity. Additional method variants have been added that take an explicit Looper argument to allow for use outside of a main thread.
    * A number of constants have been added to the LocationManager class.
    * The LocationProviderImpl class has been removed.
    * The Address class has several addtional fields and accessors in or order to better describe real locations.  Several incorrectly named methods have been renamed.
    * The Geocoder class contructor now requires a Context parameter.
    * The Location class now includes information on the estimated accuracy of a fix. It has new reset() and set() methods.

    MapView

    * New required MapView attribute: android:apiKey. Just like the traditional Google Maps API, you will be required to provide an authentic API key for your Android application. For now, the value of this can be an arbitrary string, like “myapikey,” but will need to be changed in order to work on actual devices. A process for acquiring a key is coming soon.
    * MapView.toggle* replaced with set*. DeviceType removed from all Overlay methods.
    * OverlayController removed, replaced with direct access to the Overlay List, with MapView.getOverlays(). The recommended practice is to use the new ItemizedOverlay class to manage map Overlays.
    * Adds support for “map pin” child view that marks a given geo-location on the map. Such a view would stay in the correct place as the map is scrolled and zoomed:
    * MapView child views can now be positioned relative to the Map or to the View.
    * MapView child views can now be aligned relative to their position point.
    * MapView no longer has a showMyLocation attribute; all methods referring to location are removed from MapActivity, MapView, and MapController. The new way to display location on the map is by creating a new MyLocationOverlay, enabling it, and adding it through the OverlayController.OverlayController.doZoom() is removed.
    * MapController.setFollowMyLocation() no longer accepts a zoom.
    * MapView.PixelCalculator was moved out into its own class PixelConverter, and its methods were renamed and changed to
    * use android.graphics.Point objects instead of int arrays.
    * Point renamed to GeoPoint

    Google Maps

    * New Maps menu alphabetic shortcuts This adds four invisible menu items:
    menu+I – zoom in
    menu+O – zoom out
    menu+J – previous result
    menu+K – next result
    * Add a new style attribute to enable/disable MapView’s My Location feature. By default it’s disable meaning no extra location based permissions are required for developers wanting to write a Maps based app.
    * Move Overlay.PixelCalculator -> MapView.PixelCalculator and added a MapView.getPixelCalculator.
    * A new GestureDetector to help detect common gestures.
    * The OverlayController, MyLocationOverlay and MapController classes are changed to final

    Release Notes
    http://code.google.com/android/RELEASENOTES.html

    Overview of Changes, m5 to Android 0.9 SDK
    http://code.google.com/android/migrating/m5-0.9/changes-overview.html

Page 1 of 41234»