Esri announced late today that Service Pack 2 for ArcGIS 10 is available. It looks like a fairly sizable list of issues was addressed with this service pack.
Who knows, we could be witnessing history as this could potentially be the last service pack to address ArcIMS. (Well, I can dream, can’t I?)
Anyway, if you’re among those who like to wait until the second service pack before doing an Esri upgrade, you can now start putting 9.3 out to pasture. Live it up!
A few weeks ago, my company announced the availability of the first beta version of WeoGeo Tools for ArcGIS. Unlike the previous version, which opened a separate browser window, this new release allows a user to order a data set from WeoGeo Market or a library from inside ArcMap.
One of the challenges was enabling data set previews. If you browse data sets using the WeoGeo online tool, you can get an idea of what the data set contains by using the data set preview images supplied by the data set provider.
When we developed the first version of WeoGeo Tools for WeoGeo, they used kamap to create preview tiles for data sets. This was accomplished by used either one of two desktop tools: the weoapp (command line) or gWeoApp (GUI). The first version of WeoGeo Tools used the weoapp in the background to create tiles when uploading data. Continue reading “Using BruTile and MapsUI to Enable WeoGeo Previews”
I generally try to keep my blog separate from my daily work life in that I usually don’t directly blog about the projects on which I am working. I’m going to deviate from that today to make a couple of announcements.
It’s been a while now, but you may recall that, about a year ago, WeoGeo announced the availability of WeoGeo Tools for ArcGIS. It was an ArcGIS Desktop extension that integrated the ability browse data sets on WeoGeo Market or hosted libraries as well as providing the ability to upload your data directly from ArcMap.
My first bit of news is that my company, Zekiah Technologies, produced that extension for WeoGeo. We did not announce it at the time because the original plan was for WeoGeo to support it after it was released. That arrangement has continued to the present. Continue reading “Announcing WeoGeo Tools for ArcGIS”
If you’ve been to the Obtuse Software site recently, you may or may not have noticed a change to the “Who We Are” page. It now lists only Abe Gillespie and Paolo Corti. Prior to my trip to Colorado to talk about zigGIS at GIS in the Rockies, I informed Abe and Paolo that I would be stepping back from any “official” involvement in Obtuse.
This does not mean that I am stepping back from involvement in zigGIS. I plan to continue to support zigGIS as it returns to open-source but, in truth, I haven’t done much with zigGIS day-to-day in a long time. As part of the return of zigGIS to open-source at version 3.0, Abe has been working on a plan to give the community multiple paths to support the project, including sponsorship and technical support plans. I’m sure he’ll have the details out soon so I’ll leave it at that (since it’s not my story to tell). So, as Obtuse transitions to more of a supporting role for the zigGIS 3.0 open-source project, I felt that this was a good time to step away and become part of the community. Continue reading “Me and zigGIS”
I finally got around to finishing my travel plans for GIS in the Rockies (personal obligations prevent me from making it out for Ingite Spatial NoCo). I booked my flight a while ago but I had been procrastinating on the hotel and rental car. This will be my first time in that part of Colorado so I am looking forward to seeing the area and meeting people out there. NoCo is second only to the DC area in clustering of folks in my Twitter crowd. Continue reading “Gearing up for GIS in the Rockies”
Mike Hogan tweeted that the Esri deprecation plan for ArcGIS 10.0 and 10.1 is now available. It can be found here. Much of what it contains is not new as Esri has been pretty good about getting information related to 10.x out. Some of the more interesting things (to me) include (comments in parens are mine):
ArcGIS Server 10.0 is the last release with support for 32-bit operating systems. The next release of ArcGIS Server (10.1) will run natively as a 64-bit application, requiring 64-bit operating systems. (I heard about the native 64-bit move at the Esri UC but I didn’t know that included dropping 32-bit. It’s not a big deal for me but I can imagine it’ll be an impact for many.)
ArcGIS Server 10.0 is the last release supporting publishing non-optimized map documents (MXD files). The next major release will only support publishing optimized maps (MSDs) as that is the best practice for map publishing. (There you have it, no more serving from MXDs after 10.0.)
ArcGIS Server 10.1 will be the last planned release for the ArcGIS Server Web ADFs (Application Developer Framework) for both Microsoft .NET and Java. (We had a small “wake” in San Diego for the ADFs. I won’t shed a tear when it’s “official.”)
ArcGIS Server 10.1 will no longer support local connections (DCOM connections) from Web ADF applications. ArcGIS Server 10.1 will be a web services (REST and SOAP) server only. (This is actually pretty major and the document details the impacts. If you have any ADF code doing editing and such, read this!)
There’s a lot of good information in the document, especially pertaining to ArcGIS Server so it’s definitely worth a read.
I just got an e-mail announcement from Arc2Earth (disclaimer: my company is a reseller) regarding some updates to version 3 that have come out since the ESRI UC. One of the updates that catches my attention is:
ArcGIS Server Tile Cache Format – You can now create or manage tile caches that can be used with ArcGIS Server. use Arc2Earth tile management tools (like the Change Detection Level) to dramatically reduce the time it takes to update tile caches
Continue reading “Arc2Earth Supports ArcGIS Server Tile Caches”