Here's the recent geonews in batch mode. My challenge in life is to find out what not to do - too much enthusiasm impacts focus. But don't worry, I'm not dropping Slashgeo just yet ;-)
From the open source and open data front:
From the Google front:
From the Esri front:
From the Microsoft front:
In the miscellaneous category:
In the maps category:
Google is discussing a stiry named How Google Is Remapping Public Transportation. We did mention quite a few times the GTFS (General Transit Feed Specification) in the past.
Their summary: ""Google wants to 'organize the world's information,' but there isn't a marketplace or a category of knowledge it can organize without remaking it in the process. A case in point: public transportation. Largely outside the media spotlight, Google has wrought a quiet revolution over the last five years in the way commuters get schedule information for local buses and trains, and the way public transit agencies communicate with their riders. GTFS and GTFS-realtime, which Google invented, have become the de facto world standards for sharing transit data, and have opened up space for a whole ecosystem of third-party transit app developers. This in-depth article looks at the history of GTFS and Google's efforts to give people information (largely via their smartphones) that can help them plan their commutes on public transportation — and, not incidentally, drive a lot less.""
Specifically on the GTFS-realtime standard from the article: "To enable all that, Google introduced a new standard in 2011 called GTFS-realtime. It builds on GTFS, but is a different animal, since it includes new feed types for trip updates, service alerts, and vehicle positions, as well as provisions for constantly refreshing this data throughout the day. In an advisory to agencies, Google puts it this way: “Because GTFS-realtime allows you to present the actual status of your fleet, the feed needs to be updated regularly—preferably whenever new data comes in from your Automatic Vehicle Location system.”"
Science fiction is coming our way. Slashdot is discussing a story named Google Heads Up Display Coming By the End of the Year.
Their summary: "Google is working to deliver a heads-up display allowing users access to email, maps and other tools through a wearable interface. According to the NY Times' sources, the device will be available later this year, and sell for prices comparable to smartphones. 'The people familiar with the Google glasses said they would be Android-based, and will include a small screen that will sit a few inches from someone’s eye. They will also have a 3G or 4G data connection and a number of sensors including motion and GPS. ... The glasses will have a low-resolution built-in camera that will be able to monitor the world in real time and overlay information about locations, surrounding buildings and friends who might be nearby, according to the Google employees. The glasses are not designed to be worn constantly — although Google expects some of the nerdiest users will wear them a lot — but will be more like smartphones, used when needed.'"
More geo-stuff from the article: "The glasses will send data to the cloud and then use things like Google Latitude to share location, Google Goggles to search images and figure out what is being looked at, and Google Maps to show other things nearby, the Google employee said. “You will be able to check in to locations with your friends through the glasses,” they added."
Here's the recent geonews in batch mode.
From the open source / open data front:
From the Google front:
In the everything-else category:
In the maps category:
Slashdot is running a discussion named How To Pull Location Data From Encrypted Google Maps Sessions.
Their summary: "In the last couple of years, Google and some other Web giants have moved to make many of their services accessible over SSL, and in many cases, made HTTPS connections the default. That's designed to make eavesdropping on those connections more difficult, but as researchers have shown, it certainly doesn't make traffic analysis of those connections impossible. Vincent Berg of IOActive has written a tool that can monitor SSL connections and make some highly educated guesses about the contents of the requests going to Google Maps, specifically looking at what size the PNG files returned by Google Maps are. The tool then attempts to group those images in a specific location, based on the grid and tile system that Google uses to construct its maps."
Bloggage update: Continuing the ongoing (re)discovery of cools maps for the rest of us, here are two I found on Facebook from my friends Christophe Staff in Belgium and Aidos Malybayev in Kazakhstan. They show a map I helped with to post Templar sites on an embedded Google Map, and a localised derivative of same for Russia, Ukraine, Belarus and Kazakhstan. As I said before, this blog is dedicated to the weird and wonderful ways we find to display information from work through current affairs to the personal, quickly and easily on web maps... and not unlikely after hours!
Here's the recent Google-related geonews in batch mode.
From official sources:
From other sources:
Slashdot runs a discussion named French Court Calls Free Google Maps Unfair Competition.
Their summary: "A French court has ruled that Google is unfairly subsidizing its free mapping products, making for unfair competition with paid services. This might seem ridiculous, but keep in mind that Google started charging for use of its mapping API once the free version had come to dominate the market."
We of course mentioned last October that Google decided to enforce usage limits for the Google Maps API.
Bloggage update: Last week I reported Google Maps' released of multimodal transportation mapping in the greater London UK area. Not to be outdone, Transport for London released a brilliant road congestion mapper under Roads Live Travel News, also based on Google Maps! So again I couldn't resist reporting this somewhat peripheral topic to what I normally cover, but hey, "it's my bloggage and I'll write if I want to" (apologies to Lesley Gore).
Yesterday, Google released Google Earth 6.2.
From the announcement: "With Google Earth 6.2, we’re bringing you the most beautiful Google Earth yet, with more seamless imagery and a new search interface. Additionally, we’ve introduced a feature that enables you to share an image from within Google Earth, so you can now simply and easily share your virtual adventures with family and friends on Google+. [...] We’ve also made some updates to the search feature in Google Earth. Aside from streamlining the visual design of the search panel, we’ve enabled the same Autocomplete feature that's available in Google Maps."
On the welcomed seamless globe: "While this change will appear on all versions of Google Earth, the 6.2 release provides the best viewing experience for this new data." Sri Lanka, before and after:
A quick reminder, Slashgeo has its Google+ page too (but it's inactive at the moment, that doesn't mean it's not worth adding it to your circles ;-).
Related, the GEB shares an entry named Google Earth 6 now required for Street View.