Nokia’s Here Auto Tries to Innovate
Interesting article on Engadget:
The latest version of Here Auto, launched at the Paris Auto Show, has very few rough edges. It’s designed to think ahead of you, learn your habits, work with other devices and present information and options in the least distracting way possible. That’s Nokia’s goal, anyway - to see if it succeeded, I took a tour around Paris in the company’s Range Rover demonstrator.
Self aware in car mapping. Sounds interesting but a demonstrator doesn’t mean care companies are going to jump on board. My 2014 Toyota 4Running has a completely out of date navigation system that I’m stuck with. Toyota seems to have signed deals with Yelp, Bing and Facebook to get POIs which I can’t decide is better or worse than just having a whole Nokia system. Apple and Google are getting car integration but they don’t seem to be doing any better than Nokia.
I suspect most of us will continue to use Google or Apple Maps in the car on our smartphone or tablets for naviagation. At least Siri talks through my bluetooth…
The New York Times College Football Fan Map
The New York Times released a new map showing which college football teams the people root for from data it got exclusively from Facebook.
Like the other sets of maps, these were created using estimates of team support based on each team’s share of Facebook “likes” in a ZIP code. We then applied an algorithm to deal with statistical noise and fill in gaps where data was missing. Facebook “likes” are an imperfect measure, but as we’ve noted before, Facebook likes show broadly similar patterns to polls.
The map is highly detailed and the accompanying article goes into different rivalries. Teams such as Oregon, Texas and Notre Dame appear in counties all around the country. A fun map to explore this Saturday! At least Arizona is dominated by the better University.
The New York Times College Football Fan Map
The New York Times released a new map showing which college football teams the people root for from data it got exclusively from Facebook.
Like the other sets of maps, these were created using estimates of team support based on each team’s share of Facebook “likes” in a ZIP code. We then applied an algorithm to deal with statistical noise and fill in gaps where data was missing. Facebook “likes” are an imperfect measure, but as we’ve noted before, Facebook likes show broadly similar patterns to polls.
The map is highly detailed and the accompanying article goes into different rivalries. Teams such as Oregon, Texas and Notre Dame appear in counties all around the country. A fun map to explore this Saturday! At least Arizona is dominated by the better University.
Google Maps Engine API Goes V1
It’s hard to believe that Google Maps is over 9 years old. I think back to how online mapping was done before it came and it was an ugly cruel world. The fact that I used MapObjects IMS to actually create applications tells you everything you need to know how bad things were. But as great as Google Maps was, it wasn’t always easy to get your data into it to create your own maps. That was Esri’s “thing”. Google Maps Engine has been around for a couple years but the API just went V1.
Today we’re launching the Maps Engine API v1.0: you can now do any CRUD operation on Maps Engine data via the API. The API is fully covered by our service level agreement (SLA) and deprecation policy. There is also a great set of new tutorials and documentation to help get you started.
Heck, even Safe FME supports Google Maps Engine for data upload. Putting your data on Google’s cloud. Google Maps Engine is sort of the Google My Maps for 2014 with it’s free tier. I’ve been playing around a bit with Google Maps Data Layer but I have to be honest just putting this data into Google Maps Engine itself sounds pretty good as well. You can expect a lot of playing Google Maps Engine from me this fall.
Google Maps Engine API Goes V1
It’s hard to believe that Google Maps is over 9 years old. I think back to how online mapping was done before it came and it was an ugly cruel world. The fact that I used MapObjects IMS to actually create applications tells you everything you need to know how bad things were. But as great as Google Maps was, it wasn’t always easy to get your data into it to create your own maps. That was Esri’s “thing”. Google Maps Engine has been around for a couple years but the API just went V1.
Today we’re launching the Maps Engine API v1.0: you can now do any CRUD operation on Maps Engine data via the API. The API is fully covered by our service level agreement (SLA) and deprecation policy. There is also a great set of new tutorials and documentation to help get you started.
Heck, even Safe FME supports Google Maps Engine for data upload. Putting your data on Google’s cloud. Google Maps Engine is sort of the Google My Maps for 2014 with it’s free tier. I’ve been playing around a bit with Google Maps Data Layer but I have to be honest just putting this data into Google Maps Engine itself sounds pretty good as well. You can expect a lot of playing Google Maps Engine from me this fall.
Open Data…
This should be the mantra of any open data website:
Open data means being open to the opportunity that it has a derivative and that use is valid
— Michael Byrne (@byrne_tweets) September 16, 2014