Blog

TileCache 2.0 has been released with support for ArcIMS AXL requests. This should be of great interest to users of ArcIMS who want to create a tile cache. If you have a server that can run Python CGI and has write access to the hard drive and an ArcIMS Web Service, you can create tiles. Now your ArcIMS site will have the performance of the tile cache and you can even use the cache with the OpenLayers client. I’m really anxious to give this a try when I get back from vacation on some of our older ArcIMS sites.

In addition Christopher Schmidt says there is also limited support for KML Super-Overlays in Google Earth. We’ve had great luck with Arc2Earth and using super-overlays created directly from ArcMap and using TileCache in Google Earth just as interesting to me. Definitely have to look more into that (just think, ArcIMS in Google Earth using super-overlay). Christopher also mentions that Amazon S3 is available. I’ve really taken to leveraging Amazon S3 with sharing our datasets. The costs are just so inexpensive that I cannot think of hosting data any other way. TileCache just became much more valuable to our workflows with S3 support.

So as Agent J might say from MIB II; you can take your old “old and busted” ArcIMS web service and turn it into new hotness with TileCache.

The ArcGIS Explorer Blog just announced that AGX build 440 is available:

The ArcGIS Explorer Team is pleased to announce that today, at approximately 1:58 p.m. PST, the newest version of ArcGIS Explorer – Explorer 440 – was released.

If the ESRI servers are your home servers, you’ll be notified that there is a new version available the next time you start the application. Just follow the instructions to download and install this new release.

The “What’s New in ArcGIS Explorer 440” page has a list of all the enhancements (I think many will appreciate the ArcIMS improvements since that is the biggest complain I always hear).

MapGameDay.com has a new section called the Travel Map. The section contains conference and team road game data collected for regular season games from the 1998 through the 2007 NCAA Football schedule. As you might guess, any conference with a team in Hawaii would probably lead the rankings in miles traveled and the WAC does not disappoint. What amazed me though was that Georgia has traveled a total of 358 miles for non-conference road games (only traveling out of conference to Georgia Tech and Clemson) since 1998 but Hawaii has traveled 72,918 total miles (coupled with the fact that they still have to travel 4,037.56 miles to play LaTech in conference). The Travel Map is very interesting to see how little large schools travel out of conference (Arizona State is no exception). The conference rankings are below:

Conference Travel Miles
WAC 327,521
Conference USA 278,991
MWC 188,308
Sun Belt 154,512
PAC 10 150,990
MAC 127,212
Big East 127,076
Big Ten 107,881
ACC 101,545
Big 12 73,183
SEC 42,141

PostgreSQL is about to get really integrated into ArcGIS workflows in 2008. First off we have ArcGIS Server Enterprise (ArcSDE) which will support PostgreSQL (ESRI and PostGIS data types) and now we have zigGIS 2.0 which will support PostGIS/PostgreSQL without the need for the traditional “ArcSDE” connection.

First and foremost, the zigGIS codebase will remain open. Secondly, personal and educational use of zigGIS will remain free…

As for our corporate users – you will need to purchase licenses per seat. Licenses will fall somewhere below $300 each. We hope this keeps zigGIS affordable to those organizations that require heavy-duty GIS capabilities. (don’t forget that the use of PostGIS + zigGIS saves you from all ArcSDE licensing costs)

If you are in an enterprise environment, ArcGIS Server Enterprise probably makes a ton of sense (especially in the ESRI server stack), but in smaller offices and workgroups why pay for all that overhead you are not using?

OK, so here is what is happening at 9.3 with ArcSDE.

1. ArcSDE finally rides into the sunset. Even though technically ArcSDE has been replaced at 9.2, it was still a separate product. Now at 9.3 it will become fully integrated into ArcGIS Server. ArcGIS Server Enterprise will be the “traditional” ArcSDE level where ArcGIS Server supports an unlimited number of users via either direct connect or connection to an application server. It offers DBMS support for IBM DB2, IBM Informix, all editions of Microsoft SQL Server, Oracle and PostgreSQL. It has no data or memory limits. The Workgroup level of ArcGIS Server supports a maximum of 10 direct connect users. It includes an embedded DBMS (Microsoft SQL Server Express Spatial). It has a data limit of 4 GB and a memory limit of 1 GB.
2. ArcGIS will connect to Microsoft SQL Server via direct connect. Out of the box ArcGIS application will be able to connect to Microsoft SQL Server Express Spatial, but if you want unlimited users, you’ll need to purchase ArcGIS Server Enterprise. This is probably less than what folks wanted, but you’ll have to sort that our yourselves.
3. ArcGIS supports older versions of the Geodatabase. At 9.3, ArcGIS can connect and create geodatabases (personal, file) back to 9.0. This means you won’t need to keep older versions of the geodatabase around to share with others. You also won’t have to upgrade your geodatabases just because ArcGIS went to a new release. If you wish, you can keep your older geodatabases running at whatever release you wish (back to 9.0).
4. SQL Server 2008 Spatial will be fully supported when Microsoft releases final version of SQL Server 2008. This might mean that SQL Server 2008 support might not show up until SP1 or SP2 for 9.3. It all depends on Microsoft’s release schedule.
5. PostgreSQL support will be available at 9.3 as has been reported. There will be support for both the PostGIS and ESRI data types.
6. ArcGIS Engine will allow developing with Microsoft SQL Server 2008 Express so you can scale down your enterprise applications to the workgroup level. You’ll no longer be limited to working with personal for file geodatabases.
7. ArcGIS Server Enterprise will support 64bit processors. This is only the spatial database application server and not the AGS Basic, Standard and Advanced product.

So does that answer your questions about ESRI spatial database support at 9.3?

Amazon SimpleDB is on its way and it may just change how you use databases with your web applications (or even desktop apps). SimpleDB is a web service that leverages Amazon S3 and Amazon EC2 to store, process and query datasets. Currently most if not all of us use a RDBMS such as SQL Server, Oracle, MySQL or PostgreSQL to store our data, but that requires hardware and most of the time a DBA to administer database.

Can you imagine a spatial component to Amazon SimpleDB and how you’d integrate it with your workflows? My spine is tingling just thinking about the possibilities.

You can learn more about the details of SimpleDB here.

Update: The more I think about this, the more I realize how disruptive SimpleDB will be. It was designed to be used with web applications and will be able to scale with them easily. You just can’t do that on your own. I was writing about AWS back in June and how its ability to scale could help users provide services that only the largest companies can afford.

Announced earlier this month and talked about for at least a year (I think they mentioned this at the 2007 Dev Summit), ESRI is moving away from socket licensing to using the number of cores on the server.

Through November 30, 2007, ESRI licensed server software based primarily on the number of physical sockets on the server which are being utilized by CPU chips. These CPU chips can have 1 or more processing “cores,” each core providing additional computing power for the CPU chip. Licensing requirements and fees for ESRI server software are based on the combination of the number of utilized sockets on the server and the number of cores on each CPU chip.

To address recent changes in the server hardware markets, ESRI has adjusted the licensing and pricing model for ESRI server software to be based only on the number of cores on the server. This adjustment simplifies the process of determining the appropriate license requirements and license fees, especially for new hardware configurations that are continuously being introduced.

Now before you get all worked up that this will cost you more money…. DON’T. Your maintenance will not change because ESRI is adjusting the pricing model as well. It will mean you’ll have a much easier time determining your license and fees using the new chart provided by ESRI.

The news this morning out of the UK is that Microsoft has agreed to buy Multimap for approximately 50 million $50M (updated from earlier number).

Multimap owns a maps website aimed at consumers that attracted more than 4 million unique users in the UK last month, according to Nielsen NetRatings, the market researchers.

The figures place the site second in the field in the UK ‘ sandwiched between the market leading Google Maps, which attracted about 11 million users, and the third-placed Google Earth. Microsoft’s current mapping effort, Live Search Maps, languished in a distant fifth place, with about 868,000 users.

I’m not sure what this will mean for developers, but it is probably a really great move for Microsoft competing against the Google.

Multimap will operate as a wholly owned subsidiary of Microsoft as part of the Online Services Groups and the Microsoft Virtual Earth and Search teams.

Sanchez offers up big money to buy out Multimap

I’m traveling this week so its seems like a great time to have another open thread. Enjoy…..

The Editor is out this week

Good news for those who want to take advantage of SQL Server 2008 Spatial and ArcGIS.

ESRI’s ArcGIS 9.3 software, the next scheduled release of ESRI’s ArcGIS suite, will take full advantage of the new spatial technology in the upcoming release of SQL Server 2008. With the November SQL Server 2008 community technology preview (CTP), Microsoft Corporation is extending the use and value of spatial technology by integrating it directly within SQL Server at no additional cost.

Bring It!