// Set component variables  
  variables.appConfig = 0;  
  variables.modelGlueConfig = 0;  
  variables.rolePermissions = structnew();  
  variables.userIDWithAdminRights = "";  
  

cfset test (XML close)

cfset test (non-XML close)

An example of the select clause functions are the map extent basics like:

• ST_X, ST_Y: Which will return the x and y coordinates (that's Latitude and Longitude) of a point
• ST_minX, ST_minY, ST_maxX, ST_maxY: Which return the extend (or bounding box) for a geographic feature/row
• ST_Area: No prizes for guess this returns the area of a spatial feature.

These are the simple one, the real power of ST_GEOMETRY comes when you look into the where clause functions.

To quote ESRI:

To see what Google is doing with Flex - visit the SearchMash site for yourself - could it be that a Flex-based Google Maps KML parser is on the way ? I'll bet....

Now imagine a world where a Flex client with its native vector capabilities can hook into other services -- even WFS native vector streaming -- and then pull in WMS services from wherever (native transparency) and even ArcGIS server (leveraging your existing ArcObjects code, Models, Data Tansformations via Interop) -- .Net or Java (who cares) and then natively layer all that stuff into one unified system -- that can hook into any web service -- say SAP, Oracle, whatever -- well you get the idea...Oh yeah, and then Apollo will come and all this can run as a desktop app with fine-grained pdf support...

So I went the ArcIMS Tasker to delete some files for me (this is its job). I opened the Tasker.properties file to check out where to add a directory etc. -- C:\Program Files\ArcGIS\ArcIMS\AppServer\Tasker -- It references the config file -- tasker.xml as being in C:\Program Files\ArcGIS\ArcIMS\Middleware\Tasker -- a directory that does not exist.

In fact the tasker.xml property is right next to the Tasker.properties file in C:\Program Files\ArcGIS\ArcIMS\AppServer\Tasker . So I changed the reference to it in the taskfile property in the taskfile.properties. Restarted and checked the stdout stderr logs in the same Tasker directory -- still wrong, because of course this is ArcIMS using Java -- it wants forward slashes. A quick change to taskFile=C:/Program Files/ArcGIS/ArcIMS/AppServer/Tasker/Tasks.xml in the tasker.properties and a restart says the tasker is now happy.

The point - if you (or your clients) have directories that are not getting cleaned up as they should be -- this is probably the issue. Tasker cleans out the files as instructed in tasker.xml.

I believe this is still a Flex 1.5 application. It will get a lot more interesting when they finish their port to Flex 2.

Redlands, California-- At the upcoming 26th ESRI International User Conference in San Diego, California, ESRI will be showcasing its commitment to building an open and interoperable geographic information system (GIS) platform.
“GIS is inherently collaborative, and ESRI users must be able to easily work in heterogeneous computing, GIS, and data environments,” says Jack Dangermond, president of ESRI. “ArcGIS 9.2 and the GIS Portal Toolkit are engineered to be open and to support OGC and ISO standards. I believe our users will be pleased with the enhanced OGC support, whether they are single users or large organizations deploying a service-oriented architecture using ESRI technology.”

Several new interoperability improvements in ArcGIS 9.2 and in the ArcGIS Data Interoperability extension will be shown and discussed at the upcoming User Conference (August 7–11, 2006). These include ArcGIS 9.2 support for OGC WMS, WFS, and GML Simple Features on both the client and server. ArcGIS 9.2 also embraces the ISO 19139 metadata standard. In addition, there is greatly enhanced support for reading, exporting, and working with CAD drawings from AutoCAD and MicroStation.

The ArcGIS Data Interoperability extension is also updated with FME 2006 GB, the latest release of the core Safe Software engine. This release enhances support for many of the existing formats including OGC GML Simple Features and adds support for several new formats including Google Earth Data Exchange (KML), MapInfo TAB (replaces old MapInfo TAB reader), tabular data, ESRI geodatabase (file-based), ESRI ArcGIS 9.x layer, and GML 3.1.1.

ESRI is currently finishing support for the Web Coverage Service (WCS) and is developing an application that supports WFS-T as part of ArcGIS Server. These developments will be included in ArcGIS 9.2 or will be available shortly thereafter.

Some standards organizations that ESRI actively participates in include OGC, ANSI/INCITS L1, ISO/TC 211, and OASIS.

In addition to enhanced standards support, ESRI’s open architecture supporting spatial extraction, transformation, and loading; hundreds of direct read/write data formats; KML; CAD-GIS data sharing; various data models; SQL access to the geodatabase; open APIs (Java, .NET); SOAP/UDDI/WSDL; and openly published data formats of shapefile and geodatabase will be shown at the 26th ESRI International User Conference.

For more information about ESRI's commitment to standards and interoperability, visit www.esri.com/standards.

End Release:

"...a collection oof 2D and 3D web mapping/geopublishing tools, applications and services. Application developers will have access to components (objects, Web controls, and services) for building solutions on both the Java and .Net frameworks."

This not only "streamlines" the product line -- it also diffuses the tension between Oracle Spatial and ArcSDE. Since you now get SDE as part of "Server GIS" when you get ArcGIS Server and ArcIMS, it simply makes SDE a non-issue. I am sure that we will be hearing more and more about this as the UC approaches, and the implications for creating a CFC connector for "Server GIS" has been raised another knotch in my opinion.