That said, I've recently felt pressure to continue regular upkeep of the list, and as a result, I've entrusted Marc Prioleau to help keep it in good standing going forward. Before passing the baton however, I wanted to publish one last piece of good will. The below infographic was created by Infographic World. They did a fantastic job creating this beautiful image from the list. I can't thank Justin enough for all his effort to produce it. If you ever need an infographic, please give him a call.  

When I was enrolled as a student, the Internet and tools & tricks of the Web made it possible for me to learn. Today, those tools are even more powerful, helping anyone with the will, a computer, and broadband to pursue a world class education from the comfort of their home or office with flexible study hours. It's a wonderful thing.  

A few weeks ago, Google posted an invitation to Geo educators on their Lat/Long blog.

This July, Google is hosting the first Google Geo Teachers Institute. This event is a FREE professional development experience designed to help educators get the most from Google's Geo products and technologies. The Geo Teachers Institute is an intensive, two-day event where participants get hands-on experience with Google's Geo products: Google Earth, Google Maps, and SketchUp, including a focus on features like Mars, Moon and Sky in Google Earth. Attendees will learn about innovative instructional strategies and receive resources to share with colleagues. The Google Geo Education team hopes this event will empower educators to bring the world's geographic information to students in a
compelling, fresh, and fun way.

I applied as soon as I saw the above. Today I received an acceptance email from Google to join them and 200 other educators from all over the world for two days at the Googleplex. I can't wait to get my hands on more Geo tools and learn more tricks to help others learn the same way I did. Thanks Google. My hope is to take away new skills and ideas to inspire other students to continue outstanding location-based services research work such as this. 

Last week, I was excited to hear about the beta release of ArcGIS.com - esri's new "maps-and-apps-for-everyone" offering. I was also itching to get my hands on their basemap options, which from what I saw from Jack & Jeremy's demo at Where 2.0, would allow me to overlay my 'UGC' content atop a vast variety of esri basemap options, including supported nautical charts which aren't available on other common Web mapping portals. Here's a snapshot of esri's world nautical chart, plus a view of what other tiled basemap options are available from esri and ArcGIS.com:

I liked the above map more than what Google offered, so I proceeded to the next step in ArcGIS.com to create a map - my hope was I could export out the KML or GPX file from my trusty service and simply upload personal data into ArcGIS.com to create a more relevant nautical chart map to post, share, and archive in a travel diary. When I tried to upload the KML file, here's what happened:

ArcGIS Online supports ArcGIS map files (mxd, nmf, 3dd, sxd, ncfg, mpk, wmpk, and pmf), ArcGIS layer files (lyr, lpk, and nmc), and ArcGIS tools (eaz, and esriaddin).

So it seems in order to make a simple nautical chart map, I must now find a data conversion tool in order to convert my KML data (which I might add is an OGC standard) to something more esri friendly. I thought we were beyond this formatting nonsense consuming endless hours of time... In his talk at Where 2.0, Jack emphasized the freedom and freeness of ArcGIS.com. If I have to spend time finding a shareware converter or buy ArcGIS, FME, Arc2Earth, or some other data converter to publish a Web map, it's not free nor is it open from my perspective. I was really looking forward to making a different map for this now not-so-different experience. Come on esri... ArcGIS.com has tremendous potential. You can do better than this. Please open up a bit more. It won't hurt business, just make special maps more special & useful.  

The iPhone is not the first mobile phone or smartphone to support background location atop a multitasking OS. While I appreciate the Weborati excitement, and empathize with it to a common degree, before getting too excited about the possibilities, it might be helpful to revisit some mobile location history and lessons learned from other multitasking background capabilities that arose, won brief time to shine, and later became red herring examples of what not to do. For those of you rolling your eyes, thinking "oh geez Spinney, not another history lesson", please bear with me. This one is abbreviated. I promise :-)

I asked a couple weeks ago if anyone remembered the Motorola i58sr and its background GPS capabilities. No one responded (even though I offered a prize incentive) so I can only assume my tweets are not worth responding to or no one recalled. Released in 2002, it was the US' first Java-programmble GPS-enabled mobile phone. A brick-ishly ugly, feature-dumb phone, it sported a postage stamp-sized monochrome screen, an ARM 7 processor, a SiRF (now CSR) chipset with a mediocre ceramic GPS antenna, a multitasking JVM with support for a JSR-179 layer atop it, and included a battery juiced for 2.75 hrs of continuous talk time with 71 hrs of standby time. Location data (via autonomous GPS) was easily accessible (Motorola had a freely available SDK) and developers built apps by the thousands despite its swine-like appearance.  Initially, developers used the i58sr to build check-in apps focused on workforce payroll automation and job order auditing.  Others, such as David Cohen's venture iContact built mobile social networking services atop and around the device, which admittedly failed.

Early check-in apps for workforce payroll automation and job order auditing worked fine. When workers weren't chirping back and forth with each other and the office over push-to-talk, they were using their i58sr's as digital time cards. They opened their app, selected 'start job' and then put the device away while they got to work. The 'start job' action captured a time-stamped location. When they finished their job, they hit 'end job' which captured another time-stamped location. The check-in and check-out interpolated times were used to supply back-end payroll systems with data needed to automate hourly payroll and audit jobs - essentially knowing where and when a worker was throughout the day in comparison to a daily job manifest.  Here's an example:

Things then got crazy. A few developers discovered the multitasking JVM could support both background GPS queries while running other "apps" like PTT, voice, and simultaneous data, so they designed apps to continually poll the GPS locally on the phone thinking they could track users all day. Ignoring physics is sometimes liberating for right-sided creativity, but it's certainly not practical in most cases, and certainly not with a device sporting a cheap GPS antenna and weak battery. The dung eventually hit the fan. A deluge of complaints flooded customer support lines - "I think I need a new battery", "Your battery sucks!", "There's something wrong with my phone.", "This thing only works for three hours at a time!", "I constantly have to recharge this piece of crap" were all commonly overheard customer sentiments shared with first lines of support at SMBs.     

Accessible background location in iPhone will either use wifi or GPS. iPhone's wifi implementation will continually query reference points to update itself. The GPS implementation will search the sky find a 3D fix and continue fixing itself over and over. Either option will drain battery power - fast! Apple can either throw hardware at the problem (a reason why I believe Sarantel is undervalued), or they can try to figure it out with a combination of mobile software, cellular networks, and mobile hardware. Steve Cheney summarized the later nicely in a recent post. Either way, there's no getting around the science of this problem with a cool app. I have a sneaking suspicion check-in start-ups and others betting on background iPhone location plays will learn all over again what others painfully learned six years ago with the i58sr, despite the current state of the lithium-ion art.

Social Location Aggregators

Facebook and Twitter. These players are leveraging dozens of smartphone publishing-contributors that push location data up to their larger platforms where it's made Web-available to other developers and applications. A healthy ecosystem of client-publisher-contributors and developer-consumers, Twitter and Facebook have middleman control over access. Beware... they have the keys and can lock the back or front doors at anytime. 

Network Location Aggregators

Alcatel-Lucent, LOC-AID, Neustar, Technocom, ULocate, Useful-Networks, Wavemarket.  ...Call these players the new gatekeepers of yesterdays wireless carrier gatekeepers. Using the wireless network to pull down mobile location data (by phone number), they then run their own privacy protection authorization and authentication management on web services exposed to developers. Years ago, similar aggregation approaches released SMS from individual network stovepipes, subsequently fueling explosive growth for messaging. Network-location aggregators hope the same happens for cross-carrier location data; it helps that all the Tier I's are finally aboard, but beware... they have the keys and can lock the door at anytime. 

Others who have their own hardware/software/services/content stack

Apple, Google, Microsoft, Nokia. They each have their own location-ready devices, positioning databases, mobile OSs, applications, services, and content (including the geo variety). Its their party; we're all just guests. Threatening their core focus could get one expelled (or acquired). Beware... they too have the keys and can lock the door at anytime.

This little exercise is long overdue. We now have heaps of historical data for location technology acquisitions, and since I know understanding the past is critical to manage the present and plan for the future, I'll use this historical M&A data to claim the following top 10 location technology acquisition candidates.

1. Intermap. Tops in the top content category, 3D LIDAR long-timer Intermap is in the midst of major transitions from a contract services company to a product company. They need help. Anyone smart enough to snatch them up will have a complete North American and Western Europe 3D data set equal to Microsoft and Google.     
2. Xora/Gearworks. After merging in August 2009, these two together now command the US enterprise mobility space built around carrier partnerships and broad handset portfolio support. They're almost large enough to start annoying Trimble.  
3. UMapper. There aren't many smaller players left in the GIS/mapping category. Most are now too large for acquisition or have an acquisition incompatible mismatch between investments, revenues, and exit multipliers. UMapper is still small and on the cusp. They need someone else larger to help propel them across the chasm. 
4. Skyhook. Ted Morgan brought Skyhook from a NAVTEQ Challenge semi-finalist to one of the most prominent players in the positioning space. iPhone will award that status. Cupertino should just get on with it and branch out a location technology office in Boston. 
5. Loopt. Not because they are a social location player in a red-hot emerging social location category, but because they do it differently (and better) from others with the help of wireless carriers, and because they have broad reach beyond smartphones. Another mainstream social net with a diverse global subscriber base could benefit from Loopt's know-how to reach the masses publishing through a variety of mobile modes.   
6. U-blox. Probably one of the only remaining independent GPS semi providers, it just follows the historical pattern of semi acquisitions for a larger provider to take over U-Blox.  
7. TechnoCom. A Fast-50 in SoCal and like most other silent infrastructure players, most folks haven't heard of TechnoCom. They touch nearly every US wireless location transaction and manage nearly all carrier 911 QA systems. Intrado or TCS would make good parents.  
8. Appello. Like the GIS category, players in the Navigation category are either too large for acquisition or have an exit-incompatible mismatch between existing investments and revenues. That doesn't help in a market where free is becoming the new consumer expectation. Appello is still small enough for another handset provider or carrier to get in on the action and offer a solid feature to boot.  
9. Sarantel. The best GPS Antenna in the market, hands down. If Apple gets serious about owning the entire location tech hardware stack and strives for superior performance, they (or someone else in the hardware category) should consider adding Sarantel.  
10. Layar. Augmented Reality still needs to prove itself as a money-making mode to browse the world, but maybe it won't have to. It's likely most smartphone providers will offer AR features themselves. Those that need a head start and an existing content publisher community should consider Layar.   

Cellular Privacy

Six years ago, mobile location privacy issue discussions de jour focused predominantly on passive extractions common to cellular network capabilities. Two broad issues were: 

1. Corporate-liable location privacy: Companies, businesses, or corporations had legal rights to locate and track mobile devices or vehicles considered corporate property, similar to an insured asset. Locke might have agreed with this notion of property ownership, but some individuals representing labor unions did not!   
2. Individual-liable location privacy: Individuals, consumers, citizens must provide opt-in consent to a software or platform as a service locating or tracking them. The software or platform must authenticate and authorize individual opt-in provisions with requested server-initiated location queries. 

To protect themselves, partners, and users from invasive threats, most cellular providers crafted supporting legalese with technology deployments written to safeguard personally identifiable information with included location information. Boiler agreements I recall reviewing protected individuals and application & service providers from intentional abuse and/or accidental misuse of location information coupled to a phone number (wireless' personal identity primary key). Most agreements looked similar to the below click-thru, but were less efficient and typically required legal review and sign-off - particularly for group activations. 

While safeguards introduced then protected carriers, application providers, companies and individual constituents for transactions, little discussion revolved around location information histories and storage of location data for other post-transaction commercial uses. Some early movers had foresight to include protection clauses within terms of service agreements explicitly stating location data history with personally identifiable information shall not be stored for post-processing analytics, but it's commonly known crude cellular-identification positioning techniques accompany every wireless transaction detail record. It's also known some of these historical records were attained from wireless carriers on the receiving end of issued subpeonas covered by the Patriot Act, which raises concerns and questions... Is it acceptable to store and analyze personally identifiable location information histories for government and security uses, while unacceptable for commercial purposes? ...Questions I expect the hearing addresses not just in the context of cellular provider behavior, but in the larger and more general context of the privacy discussion.

Social Web Privacy

Beyond cellular network approaches to location information capture and storage, we're now entering a new era of availability, accessibility, and concern. Today, GPS and other positioning technologies are ubiquitous within mobile devices to a point where Mobility is now synonymous with Location. At the same time, the Web has evolved from a read-only Web to a writable Web where volunteered status updates from location-capable smartphone applications post personally identifiable location information to social nets interconnected across the Web. Boutique check-in, "I am here" location broadcasting services linked to larger social networking services like Twitter are leading the movement, while controversial services such as Google's Buzz have recently emerged. While these new mobile & Web services offer local protection safeguards for users to control and manage how location information is shared and published, it's anything but clear or publicized how back-end services will use location information in post-processed commercial contexts. It's widely speculated bits of private information will be used for local advertising, based on stored, analyzed, and synthesized personal location information histories.

As an example, I use Latitude on my smartphone which offers local privacy controls for publishing and sharing.

While I control privacy provisions for peer sharing, I don't yet know how Google (or any other Web property aggregator) uses my stored location histories. I assume they synthesize my mobility movements into predictability patterns for profit, where in the future businesses in business with them tap derived intelligence and insert ads into my mobile life, and while I might want to share my location with my social network, I might not want the former. At this time, it appears I must do both, without choice. Also, who else could they sell my historical data to? Could they themselves also use my data without my authorization for their own data-product improvements? Will they grant government entities access to my information? These are all unknowns not of my personal concern, but of public concern - additional items I hope the House committee addresses on Wednesday. 

Pseudonymity, Dishonesty, & the New Privacy

Scott McNealy's now infamous utterance "You have zero privacy, get over it" may be true (or become reality soon), but it doesn't have to. In order for location information histories to create value for commercial purposes, the data must be associated with individual, unique identity. In the cellular arena it's impossible to fake individual identity because monthly bills and validated billing information define accountable relationships between individuals and service providers. However, on the Web, where 'free' defines the loose relationship between individuals and services, individual pseudonymity and dishonesty may become the currency for identity privacy on the Web. Lying about identity is wrong, but perhaps it's the only way for individuals to protect themselves while benefiting from the good-side of services on the Web & Social Web. It's troubling to think we might become a society of liars killing trust, but Web & Social Web influences may inadvertently encourage social dishonesty as a means of personal privacy protection. Will the House address these digital dishonesty issues as well? They should.

 Of course, I can always spoof my location as part of a trap. Caution all around. 

Okay Spinney..., but what the hell does this have to do with Apple staying with AT&T to launch the iPad, particularly when users complain about network performance, dropped calls, and 3G coverage? The answer, I think, can be found by examining lowest common denominator effects. 

Everyone knows AT&T is one of two tier-I GSM carriers in the US along with T-Mobile - the smallest in the tier-I camp, and as such not a reasonable choice for Apple. Sprint and Verizon are CDMA carriers. Not everyone knows Qualcomm invented CDMA, owns most patents for it, and licenses these patents along with semiconductor sales for tons of dough to equipment vendors and handset manufacturers who supply Sprint and Verizon with their network gear and devices. If you're a mobile device supplier and want to launch a CDMA handset on a CDMA network, you're paying Qualcomm something - either for IP usage or for their chipsets. I can't imagine this sits well with Apple (it certainly doesn't with others like Nokia), but that's only perhaps one reason Apple launched iPad on AT&T instead of Verizon (Sprint, I suspect, was out of consideration since they too are CDMA plus connect the competitive Kindle e-reader).

The main reasons I suspect Apple continued a relationship of convenience with AT&T at this time was the A4 and Apple's vertical approach to product development, which is directly at competitive odds with Qualcomm's full system-on-a-chip Snapdragon offering currently being adopted by Android, Chrome OS, BREW, WinMo, and Linux. The situation may change when Verizon builds out a new 4G LTE network atop their 700 Mhz spectrum and when Apple will be free from Qualcomm IP licensing, but until then, AT&T looks like the long term winner of all wireless Apple products in the US because AT&T is a GSM network and at this time, that means freedom to control everything for Apple. 

Back to the A4... Remember that little thing his Steveness mentioned last week?

The A4 is Apple's 1Ghz processor (they acquired the technology), similar to Qualcomm's Snapdragon 1Ghz processor. However, unlike Qualcomm's Snapdragon, the A4 doesn't include a 3G modem, GPS, or other full system-on-a-chip capabilities that most wireless semiconductor providers have built into 3G offerings. 3G support inside iPad is a separate module from the A4 processor. I suspect it's Infineon's offering since they rule the iPhone (on a side note, Infineon's GPS also supports the iPhone).  Like Qualcomm did with their own BREW software, Jobs made it clear last week that Apple strives for super tight integration between their software and silicon to reach optimal performance, vertical scalability, and software development flexibility. Using Qualcomm-inside technology might have made it more difficult for Apple to achieve these goals while limiting their control. It's for this reason they chose to continue with AT&T!

Eventually, the same freedom-from-control that comes with vertical product development may be the reason Apple extends the A4 to build their own full system-on-a-chip that includes 3G and 4G modems, A-GPS, plus all the other features competing solutions have. I wouldn't be surprised if they did. Apple has proven controlling the whole stack and experience has competitive advantages while igniting explosive innovation with openness at the SDK and API level.

On a much lighter note, Foursquare must absolutely love user Joseph G of NYC. He has an average of 24 check-ins per evening and he's mayor of 177 NYC spots of interest.

Clearly, he's a cheater; exactly the kind Foursquare must want. After all, the more he fibs, the better Foursquare's POI database gets. I have no interest in helping Foursquare build a POI databases for their benefit, particularly when there's none reciprocated other than bragging rights shared amongst a user community all doing the same. 

I'll keep using Latitude. It's incapable of lying, mostly importantly, to myself :-)

Here's what Elliott had to say... 

"The NIM acquisition is about servicing our operator customers as best as possible, with our infrastructure, services, with applications. We obviously did our due diligence with Verizon and other operator customers, and we feel there's lots of room for growth. While today, the operators offer point solutions, I can definitely envision them having very powerful integrated location-based experiences that include navigation, locators, and search, all with parental controls and social phonebooks built-in. We'll continue to offer them whatever they want, if that's advertising or pay-for apps and experiences."

When asked about challenges faced by free alternatives...

"We don't see Google taking over the world, because operators don't want Google to take over the world. Google may get 20% market share, but not all of it, and we see the total market growing 3X over the next five years. No one is going to let Google dominate because they understand Google is not looking out for their interests. If an app is still making money, operators will continue to market it as a premium service while watching free Android apps and emerging ad revenues carefully. It will also be interesting to see how other handset manufacturers now using Android react to Google's own device launch."

1. More consolidation in the LBS space. Check. Not only did we see Google do everything themselves, simplifying the once-overly complex supply and value chain considerably, but we also saw LBS M&A deals nearly level with the explosive growth of 2007.
2. Carrier Network-As-A-Service irrelevance. I didn't nail this one, but got it partially correct. SDPs are still around and more modern APIs are now available, but when I talk to developers about these, they aren't aware they exist and are instead focused on handset only development where Location is now a measly feature everyone uses. Also, Mobile Browser support for device resource access isn't quite there yet, but W3C's GeoLocation API is prime time, endorsed and supported by all the new webkit entrants. It's coming, soon.  
3. App Store proliferation and carrier billing disintermediation. There are now over 100K Apps in the iTunes App store. Need I say more?
4. Smartphones will receive first-class subsidy care and marketing. When was the last time you saw a carrier ad promoting a feature phone? 'Nuff said. 
5. A resurgence in mobile enterprise applications coverage. I didn't get this one right, but look for it to happen in 2010.    

I give myself a mark of 75% for the above - a pass- and as such, here we go... My 5 predictions for 2010.  

1. Still more consolidation, in three main areas. First, expect one or two vertically-integrated mobile behemoths to buyout other ailing and aging yesteryear map service and mobile hardware behemoths. Second, smaller social location start-ups will get consumed by larger more established social players. We've already seen some initial movement. Third, content-related acquisitions will continue and include buyouts of 3D digital elevation model data providers and place-based POI providers who leverage social feedback loops for ratings and rankings.
2. The tectonic shift from voice to data economics will finally start to gain real momentum and circuit-switched networks will begin to be phased out of existence. With this, location-contextual voice will emerge as a new killer enabler and with it a whole new slew of integrated communications and networking applications. Wireless 911 as we know it will change. 
3. Mobility (connectivity + location) beyond-the-phone trends will continue and become common in M2M infrastructure processes and services managed in the utilities, local government, transportation, healthcare, and energy sectors. GIS has an opportunity to shine again in a new connected mobile era. 
4. Desktop operating systems & software environments will get further pushed into the specialty back-office, as thinner, lighting-fast operating systems with the Browser, and hybrid clouds start to handle repetitive 'desktop' activities; activities increasingly more mobile-accessible, via WAN connected, location-smart tablets & netbooks.  Contextual cloud-sync services will define how users interact with email, calendars, contacts, media files, and map data. More niche social sharing tools will emerge for professional collaboration. 
5. Location will be included in *every* new mobile application that is introduced. I realize this is nearly impossible to track, but I'll try to keep an eye on it and report back next year.   

That's all. I'll keep score again, and a year from now, let you know how I faired. Good luck this year!

Anyway... like last year, a Google topic this year again wins the most visited and popular post on this blog for 2009 - "How The Nexus One Could Destroy Conventional Mobile Industry Supply Chain Economics". However, unlike last year, I won't further speculate about the Nexus One. I'm done speculating about Google (week-after-week innovations speak for themselves). Plus, we should all know more about the Nexus One in a couple weeks upon release.

At this point, I'm thrilled to see mobile industry US-company wins for Qualcomm's Snapdragon offering (they've earned it) and for a cloud-sync mobile era that Google is leading in lieu of other mobile leaders seemingly caring less about either. I'm also expecting exciting things for 2010. This year looks like the breakout year for contextual voice, mobile VoIP, and over-the-top data-driven smart voice offerings. Maybe we'll even see Apple do a connected mobiletop for widgets and connect that iPhone mobile computer to network mobility. Novel! ;-)

Seems far fetched right? Perhaps not. Hear me out on this one... Three years ago, Schmidt made it clear and in no uncertain terms he believes phones should become free as ad impressions per user out-earn two-year carrier contract subsidies plus mobile device hardware costs. Widely considered industry blasphemy back then, I'll admit I didn't fully understand how an ad subsidized free device might be possible. I've come to learn it's feasible through experience... A year after Schmidt made his thoughts public, I started working for a handset manufacturer where I was responsible for inking deals with vendors in the supply chain. 

While building phones, I learned there are many components that go into a production and distribution, and each have costs in a complex array of supply chain economics. Our total bill of materials was about $60. Beyond the core BOM, we also budgeted for ancillary packaging, shipping, distribution, logistics, and GSM patent licensing costs, plus one-off FCC certification, tooling and assembly line costs - the later two of which were charged-for by our Chinese OEM, Nollec. Nearly all of our silicon and component costs were available at discounted prices, primarily because Nollec had previously used our selected piece parts in designs for other manufacturers and preexisting supply chain contracts were in place - we simply inherited what was already available in the market and used two-year old technology that was less expensive.  After all costs, our unlocked street price generated a 45% gross margin for the business, which made it profitable.  

Anyway, the mobile industry supply chain I worked in (the one that still exists today) is complex - as is its money flow. If Google were to pull-off offering a free phone (or an easily obtainable inexpensive one), I suspect they would have to front at least some of the initial supply chain and manufacturing costs themselves - initial up-front costs run too much red for HTC and their technology suppliers to bear in suspended after market return. That said, I do not doubt that ad revenues generated per user over time could indeed cover all embedded and production costs needed to maintain existing profit margins for supply chain vendors and OEMs.

Pretend for a moment that the Nexus One costs $300 to produce. This cost may seem high, but with all the cutting edge tech inside it, this may be a fair estimate. HTC, Qualcomm, and everyone else needs to earn what they earn now from a $300 BOM. Could Google generate the $300 over the life of the device from businesses advertising through them? I think so, but in order for it to be profitable for Google, they would need an additional margin beyond the BOM costs. Is that possible?  Sure. I can see a device like the Nexus One generating a couple thousand dollars per user from businesses seeking third screen reach through highly contextual and personalized mediums.  So, free could be possible. 

Others speculate if a free or even inexpensive Nexus One is launched, it will leave little reason for other handset OEMs to follow or care about Android if hardware profits are eliminated. 

I'm not so sure. Profits aren't eliminated with this model, they just have a different point of origin and the money flows differently. Assuming the existing supply chain earns what they've grown comfortable with, why should anyone care if payment originates from businesses who pay Google to advertise versus payment originating from consumers, through the carrier, onto handset manufacturer's and subsequently onto the technology supply chains. From this perspective, a free Nexus One seems possible, and I wouldn't be a bit surprised if it happens. It's disruptive as hell, and "as long as you're on the side of the consumer, you'll be fine", right? :-)