File Geodatabase API – To support both Windows/Linux and 32/64 bit

File Geodatabase API – 4 platform final release set for mid-May

… we’ve received a lot of feedback from everyone wanting 64-bit Linux and we’ve made faster progress than we’d expected on the 64-bit Linux port, so we’ve decided to delay the initial release a few weeks and have a single release that supports all 4 platforms. Bazaam!

Cool, now all I have to do is find a customer that actually wants data delivered in the File Geodatabase format.  Kablooey!

ArcGIS Server 10.1 is 64-bit only, MSDs over MXDs, and what about ArcInfo Workstation 10.1

In the ArcGIS 10 depreciation document this little tidbit catches my eye.

ArcGIS Server 10.1 will no longer support 32-bit operating systems. ArcGIS 10.1 will exclusively support 64-bit operating systems. Support for 64-bit native execution across all the tiers of ArcGIS Server has been a long awaited feature by many of our customers. 64-bit hardware is the norm in today’s market and most modern ArcGIS Server deployments do in fact run on 64- bit hardware. ArcGIS Server 10.1 will run as a native 64-bit application exclusively requiring 64- bit capable hardware.

Now we are talking about Server here, not Desktop, but a total 64-bit server suite is very nice.  One more thing that for some reason seems to get people a bit riled up:

ArcGIS Server 10.1 will no longer support publishing non-optimized map documents (MXD files). ArcGIS 10.1 will only support publishing optimized maps (MSDs) as that is the best practice for map publishing. At ArcGIS Server 10.1, optimized map services (MSDs) will be enhanced to support many of the capabilities that are currently only available through MXD-based map services.

This is a total performance change now that MSDs will support just about everything you need from a cartographic standpoint.  Oh and one last little tip of the hat to the workhorse:

There are no plans to release a new version of ArcInfo Workstation at ArcGIS 10.1.

Frozen in time will ArcInfo Workstation be (hmm did I just channel Yoda there?).

I suspect there will be no fighting over any of the above…

5 predictions Geo for 2010 and 5 things that won’t happen

Here are 5 predictions for Twenty Ten.

  1. The shapefile dies: SpatiaLite + ESRI’s File Geodatabase API finally put a dagger in the shapefile.
  2. GIS on iPhone/iSlate (Apple Tablet) and Android/Chrome OS: With Apple and Google owning the mobile space, we’ll see more proprietary and open source projects being ported to these platforms.  Microsoft Tablet PCs and Windows Mobile/CE begin to die off.
  3. 64-bit: There will be some holdouts (*cough* ESRI), but most of us will be running native 64-bit code on our desktops and servers.  Now to just get more RAM in this laptop.
  4. Mobile: If you aren’t running on the iPhone/Android/Blackberry you aren’t relevant.  Web mapping apps become mobile browser aware.   Those that aren’t were probably irrelevant anyway.
  5. Google: Google’s APIs continue to push the envelope and they continue to be the standard for everyone mapping on the interweb.  Google is able to throw so much money and manpower at “problems” and their solutions are coming faster than anyone else can match.

Here are 5 things that won’t happen:

  1. Augmented Reality: Much like the Nintendo Virtual Boy, it sounds great until you try and use it.
  2. OpenStreetMap Dominates: Between Google’s quick improving of their database and continued licensing issues OSM plateaus.  Companies will continue to try and figure out how to monetize OSM, but fail.
  3. ESRI + Microsoft: This was on the top 10 lists for many people in 2009, but I don’t think we’ll be seeing deeper integration.  ESRI will continue to support multiple platforms (Google, OSM, Microsoft, “other”) and not become a Microsoft shop.  As Google continues to erode away at SharePoint and Bing Maps, ESRI will make sure that they don’t get caught in Microsoft’s blind spot.
  4. Geolocation other than Twitter, Apple and Google (TAG): Foursquare, Brightkite, and others will fade as TAG rolls out new APIs and ensure their mobile devices are tagging everything you do.
  5. MySQL falls apart:  Despite the dire predictions of Oracle or Monty destroying the project, too many people have too much invested in the project to let it fail.  MySQL will be fine and LAMP will continue to power Badgers.

Hey, don’t worry…  It’s gonna be a bright, sun-shiny day!