Q Why is this such a big deal?
A Strategically, this is about mindshare. Google offers Esri a massive boost in mindshare outside the traditional GIS community – which has to be a good thing for GIS. That mindshare will likely translate into wider understanding of the critical importance of quality spatial information for decision support.
A Operationally, this brings clarity to an ambiguous relationship. Google and Esri should never have been in competition and arguably never really were. But ambiguity breeds misunderstanding and misunderstanding spawns competitive positioning. Most Google Earth Enterprise customers were actually buying content and content viewers rather than analysis or editing capability. With that new clarity we can see how Esri’s analysis and editing capabilities working on Google’s content and viewers creates an immediate win-win and long term powerful synergy.
A More tactically, this isn’t necessarily such a big deal. Many of the bigger Google Earth Enterprise customers were already running hybrid environments with Esri technology on the back end. So I’d anticipate that ‘hybrid’ might be a theme running through the early days of this new relationship with ‘hybrid’ becoming more and more seamless over time.
Q What does this mean in technology terms?
A In many respects, Esri and Google technology has become well aligned over the last decade. Their architectures have become similar, the underlying IT frameworks are compatible and the technology transition from Google Server to ArcGIS Server and/or ArcGIS Online should be relatively smooth, particularly for hybrid users.
A For Google-only and Google-other users, the technology transitions will still benefit from the fact that Google and Esri both tend to follow IT best-practice in terms of their platform architectures.
A Note that the question and first answer referred to ‘technology’… the other elements of processes, people and information all need to be carefully considered since the processes will need to change; the people will need to be trained; and the information type, sources and flows through the organisations will change. In a nutshell, the spatial information supply chains for your organisation will need to change, potentially for the better.
Q What about KML?
A In the short to mid-term, KML must survive. It is an open standard and will retain its place in the standards ecosystem. That’s not a huge challenge for Esri – the ArcGIS platform already serves and consumes KML.
A In the mid- to long-term, expect to see Esri’s ArcGIS REST API edge out KML.
A That does beg some questions about whether that will change OGC’s opinion of adopting the proposed REST standard: we watch with interest.
Q What about content?
A Content is perhaps the biggest unanswered question about this new collaboration. Google Earth and Google Maps are the content kings and have unrivalled content for the whole world, but that content is currently locked into those applications – you can’t consume Google basemap content outside Google applications or APIs. There’s a very good reason for that restriction; Google pays content providers a fortune in licensing fees and those license terms do not allow that content to be used in other applications. I foresee a lot of behind-the-scenes horse trading ahead. That begs some other questions about content:
Q Will Google continue to invest in content at the same level?
A On one hand, local search will continue to demand high quality, recent map content. Imagery is less important in that local search respect and so perhaps we can expect to see a slower refresh of satellite imagery, although arguably the community has become very familiar with the satellite imagery view of their local place, so that could be a driver to maintain some level of information refresh. The fact is that at present, we don’t know. We will watch the content space carefully!
Q Will Esri provide a new monetised channel for that Google Earth content through ArcGIS Online?
A ArcGIS Online has become a mature content platform over the last few years with premium services that match and in some cases beat Google Earth content. So Esri already knows how to monetise premium content.
A I suspect the biggest challenge will be battling the naïve expectation that Google content is free. In the context of consumer applications, it is! In the context of Google Earth Enterprise, it certainly isn’t. If (and we can only surmise at this point), Google Earth content were to become available through ArcGIS Online, it would make ArcGIS Online an unrivalled spatial content platform.
Q What about the ‘private’ content which organisations currently store in Google Earth Enterprise?
A In many cases, there will be huge volumes of data stored in Google Earth Enterprise. That’s going to need to move to a different information store; that’s going to depend whether you want to head down the on premise or cloud road. Either way, it’s a trivial task in terms of technology; Esri for example has a batch data conversion process and tools like Safe Software FME have had this capability for years. It is important to set this work into a strategic framework: do I need to convert everything; do I understand my most precious data; are the data models still valid?
Q How do I set about planning a migration?
A This where it is essential that organisations do their research and make a clear decision about the road ahead. A knee-jerk reaction is rarely going to result in a good outcome and is unlikely to create consensus.
A This is where a spatial strategy is required: what are you currently doing with Google Earth Enterprise; what are your aspirations for spatial technology; how best to achieve those aspirations (recognising that staying with Google Earth Enterprise isn’t an option)? Out of that careful assessment will emerge technology options. Developing this spatial strategy and roadmap is what Spatial.IQ does best!
Q Are there other technology options apart from Esri?
A Part of developing a migration strategy must be an assessment of technology options. This is where the crystal ball becomes a little murky. In my experience of Esri, they don’t take short-term views of partnership; indeed, many of the frustrations that Esri users tend to suffer are ultimately caused by long-term vision trumping short-term fixes. So my guess is that there’s much, much more to the Google / Esri partnership than has been announced so far.
A Clearly, any benefits that might emerge from the Google / Esri partnership in the mid- to long-term will only be available to those who chose the Esri option. Organisations need to start migration strategy work sooner rather than later and so will need to explore those other options.
A Safe Software set out some useful thoughts in their excellent blog post at titled, ‘Esri & Google in a Post Google Earth Enterprise World’.
Q How do I compare the technology options?
A In a word: holistically. The fact that Esri has a free replacement software offer is useful for avoiding that particular aspect of CAPEX. That levels the playing field against open source (for the first year anyway – note that maintenance does kick in after that to cover both tech support and ongoing upgrades); and potentially tips the balance away from other commercial software offerings. The fact that training is free (but check the small print to find out what’s in and out of scope) tips the balance away from open source.
A Software and training are only a part of the real costs of a migration. Applications will need to be rebuilt; integration with other enterprise systems reworked; and a new technology culture established. Those represent potentially big costs and big turmoil.
A Those are the implications when a vendor backs away from a market and those are costs which all Google Earth Enterprise customers are going to need to wear. So best not make the same mistake again! This suggests that this comparison of technology options is a BIG DEAL! There will be very few Google Earth Enterprise customers that will have the expertise in-house to do that holistic assessment. Call us – this is what we do; we can help!
Q How can I plan my implementation?
A Migration is never going to be as simple as adopting ArcGIS licenses and getting up and running the following day. There has to be a full audit of your current state and an assessment of how the organisation will need to change its integration points to other enterprise systems.
A LINQ has developed a powerful methodology for understanding the relationships between information, processes (actions), people and systems in the ‘as built’ environment; helping plan cost effective migration to the desired future state. Please take a look at our white paper to understand how LINQ can help your implementation planning.
Q Where can I find more information?
A To our surprise, we’re still not seeing much blog activity on this important topic. I’m sure that Esri will be pushing more information out on its various blogs. I’m waiting for Google to push information out on the Google Earth blog and the Google for Work blog. I’m also sure that Safe will continue to post great content. LINQ will continue to assess the situation and we aim to post regularly on this topic. In the meantime, if you have any additional questions, feel free to pass them to us and we will do our best to address them through further blog posts or where appropriate, individual engagements with you directly.
We’d welcome your thoughts and / or more questions either in comments below or via e-mail.
Your assessment is very thoughtful and I appreciated it very much, particularly the point about the need for strategic planning.
Moving over to our platform will require data and app migration, however because so many sites already maintain their data in our server the data part may be less than one might imagine. Also our partnership with Safe Software makes it strength forward.
Users biggest issues will be in migrating apps and possible related work flows. For Google Earth users it will be very little problem but for Map engine users it may require more work. Fortunately our new web app builder, app studio technology and ArcGIS runtime technology will help a lot.
Regardless we very much appreciate your
Interest in helping users in their migration efforts and would like to offer our support to you
in any way, please let me know.
Regards,
Jack
We have been covering these developments closely and blogging about them:
http://www.webmapsolutions.com/google-esri-and-the-huge-geospatial-for-business-opportunities
http://www.webmapsolutions.com/esri-google-and-drawing-a-line-in-the-sand
–Matt
Thanks for not one but two excellent items! Here is my take on it:
http://blog.zolnai.ca/2015/02/esri-google-all-may-not-be-as-it-seems.html
[…] Spatial IQ (Feb 4) – Google / Esri – What will this mean for You? SpatialIQ (New Zealand) provides a Q&A that examines some implications for customers. O particularly like this comment… “I suspect the biggest challenge will be battling the naïve expectation that Google content is free” […]
Hi Neil. Excellent summary, really useful, as are the follow on comments. This is without doubt a story to be followed. I hope life is treating you well!
Thanks for taking the time to discuss this important topic. There are a lot of companies with an investment in these technologies and I think as an industry is important we provide a good path towards the future.
We at CartoDB are offering “CartoDB for Google Cloud Platform” (http://cartodb.com/solutions/cartodb-on-google-platform). This will provide a smooth transition for GME users that want to keep using Google Maps and benefit from the power of a dynamic rendering on the cloud and as a SaaS solution. There are some important points to this solution. The future is on Cloud, SaaS and I would say Open Stacks that ensure the viability on the long run. Additionally I think we can clearly see the need for separation between Content Platforms, like Google Maps, and the technology to power geospatial applications.
Most organizations know the most important thing is looking into the future, and ensuring their investments are aligned to the clear technology directions we are seeing: cloud and SaaS. Most platforms, including CartoDB, will provide free resources and training while doing the migrations.
FME has done a great job providing support for migrations for multiple platforms — check out this video on FME-CartoDB (https://www.youtube.com/watch?v=G05dWIPPXfE). Additionally, thanks to the fact that GME and CartoDB both run on the cloud, we have developed a migration tool to help you move your data in 3 steps, and in our experience the code changes on the client side take less than an hour. See the tool here, http://gme2cartodb.com/.
Again, thanks for bringing attention to this important topic.
[…] http://spatialiq.co.nz/index.php/uncategorized/google-and-esri-whod-have-thought/ http://spatialiq.co.nz/index.php/spatial-linq/google-esri-what-will-this-mean-for-you/ […]
Cheers Martin – good discussion!
It seems to assume that GIS = ESRI & does not discuss possible impacts on the non-ESRI (proprietary or open source) part of the global GIS space, whether this alliance will increase ESRI’s market share, and who is likely to face challenges because of it.
One point: my take on the OGC/ESRI REST issue was that as long as ESRI retained the rights to control the standard (as they did in the last proposal), rather than fully vest control in the OGC, it could never become a genuine “OGC standard”, just an OGC ratification of an ESRI standard.
This is a very thoughtful and well written article. Thank you very much for sharing it.