erdas apollo 2011 release notes · インストール ... weblogic 10.3 データベース n/a...

ERDAS APOLLO® 2011

リリースノート

v11

2011年1月

Bunkyo Green Court, 17F | 2-28-8 Honkomagome | Bunkyo-ku, Tokyo | 113-6591 JAPAN

2

Copyright © 2010 ERDAS, Inc.

All rights reserved.

Printed in the United States of America.

The information contained in this document is the exclusive property of ERDAS, Inc. This work isprotected under United States copyright law and other international copyright treaties and conventions.No part of this work may be reproduced or transmitted in any form or by any means, electronic ormechanical, including photocopying and recording, or by any information storage or retrieval system,except as expressly permitted in writing by ERDAS, Inc. All requests should be sent to the attentionof:

Manager, Technical DocumentationERDAS, Inc.5051 Peachtree Corners CircleSuite 100Norcross, GA 30092-2500 USA.

The information contained in this document is subject to change without notice.

Government Reserved Rights. MrSID technology incorporated in the Software was developed in partthrough a project at the Los Alamos National Laboratory, funded by the U.S. Government, managedunder contract by the University of California (University), and is under exclusive commercial licenseto LizardTech, Inc. It is used under license from LizardTech. MrSID is protected by U.S. Patent No.5,710,835. Foreign patents pending. The U.S. Government and the University have reserved rights inMrSID technology, including without limitation: (a) The U.S. Government has a non- exclusive,nontransferable, irrevocable, paid-up license to practice or have practiced throughout the world, for oron behalf of the United States, inventions covered by U.S. Patent No. 5,710,835 and has other rightsunder 35 U.S.C. § 200-212 and applicable implementing regulations; (b) If LizardTech's rights in theMrSID Technology terminate during the term of this Agreement, you may continue to use the Software.Any provisions of this license which could reasonably be deemed to do so would then protect theUniversity and/or the U.S. Government; and (c) The University has no obligation to furnish any know-how, technical assistance, or technical data to users of MrSID software and makes no warranty orrepresentation as to the validity of U.S. Patent 5,710,835 nor that the MrSID Software will not infringeany patent or other proprietary right. For further information about these provisions, contact LizardTech,1008 Western Ave., Suite 200, Seattle, WA 98104.

ERDAS, ERDAS IMAGINE, Stereo Analyst, IMAGINE Essentials, IMAGINE Advantage, IMAGINE,Professional, IMAGINE VirtualGIS, Mapcomposer, Viewfinder, and Imagizer are registeredtrademarks of ERDAS, Inc.

Other companies and products mentioned herein are trademarks or registered trademarks of theirrespective owners.


はじめに 3

はじめに本資料は、ERDAS APOLLO 2011 に関する以下の主要な情報を提供するものです。

インストールに必要な動作環境（ソフトウェアおよび、ハードウェア）

新機能、及び改善点に関するサマリ

主要な機能、回避策、有用なヒント、および以前の資料などでご提供できなかった最

新情報など

インストールおよび、設定方法に関する詳細は、ERDAS APOLLO クイックスタートガ

イドをご参照ください。ERDAS APOLLO ソフトウェアを導入する前に本資料をご確認く

ださい。

※ 付録の章について

以下の章は、英文の原文をそのまま引用し、付録として掲載してあります。

Customer Resolutions （新たに対応した機能、解消した不具合など）

Known Issues （既知の不具合）

ERDAS APOLLO に関する、より詳細な情報は、ERDAS Inc.,社の Web サイト、また

は、ライカジオシステムズ株式会社が提供する日本語サイトをご覧ください。

米国サイト（開発元） http://www.erdas.com

日本語サイト（日本総代理店） http://erdas.lgkk.jp

http://www.erdas.com/

http://erdas.lgkk.jp/


4 目次

目次はじめに ................................................................................................................................................................... 3

動作環境 .................................................................................................................................................................. 5What’s New? ........................................................................................................................................................ 10

ERDAS APOLLO 2011 ...................................................................................................................................... 10ERDAS APOLLO : プロダクト全体 ..................................................................................................................... 10ERDAS APOLLO Essentials - IWS.................................................................................................................... 11ERDAS APOLLO Essentials - SDI..................................................................................................................... 12ERDAS APOLLO Advantage ............................................................................................................................. 13ERDAS APOLLO Professional........................................................................................................................... 15ERDAS APOLLO Solution Toolkit...................................................................................................................... 15ERDAS APOLLO Feature Interoperability ......................................................................................................... 15

付録：Customer Resolutions（英文）..................................................................................................................... 16APOLLO............................................................................................................................................................. 16

付録：Known Issues（英文）................................................................................................................................... 21APOLLO............................................................................................................................................................. 21


動作環境 5

動作環境

ERDASAPOLLOEssentials –Image Web

Server1

ERDASAPOLLOEssentials –SDI

ERDASAPOLLO

Advantage2,Professional

ERDASAPOLLOAdvantage(CollaborationModule)

CPU Intel®デュアルコアプロセ

ッサ（2.0 GHz）以上

シングルクアッドコア、

または、デュアルコアプロ

セッサ推奨

Intel®デュアルコアプロセ




セッサ推奨





セッサ推奨


ッサ（2.0 GHz）以上3

メモリ 2 GB 以上

(1 コアあたり 2 GB を推

奨)

2 GB 以上 2 GB 以上

(4GB 以上を強く推奨)

2 GB 以上3

サーバの

ディスク容量

フットプリントに

~500 MB 程度


4GMB 程度


4GMB 程度


~2GMB 程度

データストレー

ジ容量

7200 RPM 以上のディス

クストレージ4

（15000RPM 程度の

RAID アレイや、外部

SAN/NAS などの高速デ

ィスクストレージを推奨）


クストレージ






クストレージ





N/A

ネットワーク 100 Mb 以上. 1Gb 推奨 100 Mb 以上. 1Gb 推奨 100 Mb 以上. 1Gb 推奨 100 Mb 以上


6 動作環境


Server1


ERDASAPOLLO



サーバOS5 Windows Server®

2003Standard, EnterpriseEdition(32-bit / 64-bit)

6

Windows Server 2008,2008 R2 Standard,Enterprise Edition(32-bit / 64-bit)

Windows Server®



Windows XPProfessional SP2以上 (32-bit)

Red Hat®

EnterpriseLinux

®5

(32-bit / 64-bit)

CentOS 5.1, 5.2(32-bit / 64-bit)

Windows Server®



Windows Server®

2008Standard Edition(32-bit)

Red Hat®

EnterpriseLinux

®5 (32-bit)

CentOS 5.1, 0-2(32- bit)

VMWare 上での動作を

サポート

テスト、および

開発向け環境

Windows®

XPProfessional SP2 以上(32-bit / 64-bit)

Windows Vista®

(32-bit / 64-bit)

Windows 7(32-bit / 64-bit)

開発目的では、

Windows または Linux

環境での利用が可能。

ただし、実稼動環境は、

上記の対応 OS および、

使用条件を満たすこと。

開発目的では、

Windows または Linux

環境での利用が可能。

ただし、実稼動環境は、

上記の対応 OS および、

使用条件を満たすこと。

上記対応サーバ OS に

同じ

システム環境N/A JDK 1.6.0 （-20 以上）

(32-bit / 64-bit)

Java AdvancedImaging 1.1.3

（いずれもインストーラー

に含まれる）

JDK 1.6.0 （-20 以上）(32-bit / 64-bit)

Java AdvancedImaging 1.1.3


に含まれる）

JRE 1.6 （32-bit）


に含まれる）


動作環境 7


Server1


ERDASAPOLLO



クライアント

環境

Adobe® Reader® 5.0

以上 (for online

documentation)

Firefox® 3.0 以上

Internet Explorer® 6

以上

Google Chrome™ 4

以上


以上 (for online

documentation)



以上

Google Chrome™ 4

以上


以上 (for online

documentation)



以上

Google Chrome™ 4

以上


以上 (for online

documentation)


以上

ライセンス ERDASNet-licensing 2011(11.0)

ERDASNet-licensing 2011(11.0)



アプリケーション

サーバ

Microsoft® IIS 6

以上

JBoss 4.2.(x 以上)

(JBoss 4.2.2.GA はイ

ンストーラに含まれ

る)

WebLogic 10.3

Apache Tomcat 6 以

上 (Tomcat 6 はイン

ストーラに含まれる)




る)

WebLogic 10.3




る)

WebLogic 10.3

データベース N/A Oracle® Database10g Release 2,Standard, EnterpriseEdition

Oracle® Database11g, Standard,Enterprise Edition

Microsoft SQL

Server® 2008,

2008 R2

(10.0.1600 以上)

PostgreSQL version8.4

（PostGIS 拡張）

Oracle® Database10g Release 2,Standard, EnterpriseEdition

Oracle® Database11g, Standard,Enterprise Edition

Microsoft SQL

Server® 2008,

2008 R2

(10.0.1600 以上)

PostgreSQL version8.4

（PostGIS 拡張）

MySQL 5.0


8 動作環境


Server1


ERDASAPOLLO



タイル配信

(OTD配信)のため

のディスク環境

ローカル環境にシリアル

接続した

SCSI RAIDドライブを推

奨7

N/A N/A N/A

管理ツール ERDAS APOLLO IWSAdmin Console

ERDAS APOLLO DataManager

ERDAS APOLLO StyleEditor

ERDAS APOLLO DataManager

ERDAS APOLLO StyleEditor

ERDAS APOLLOCollaboration RegistryAdmin Tool

ERDAS APOLLOCollaboration AdminTool

クライアント


ERDAS TITAN 3D

クライアント

ERDAS APOLLO Web

クライアント

ECWP


OGC互換の

WMS client


ERDAS TITAN 3D

クライアント

ERDAS APOLLO Web

クライアント

ECWP


OGC互換の

WMS client


ERDAS TITAN 3D

クライアント

ERDAS APOLLO Web

クライアント

ECWP


OGC互換の

WMS client


ERDAS TITAN 3D

クライアント

管理ツールOS Windows® XPProfessional SP2

以上 (32-bit)


Windows Server®

2003 Standard,Enterprise Edition (32-bit / 64-bit)

Windows Server 2008,2008 R2 Standard,Enterprise Edition (32-bit / 64-bit)

Windows® XPProfessional SP2

以上 (32-bit)


Windows Server®




以上 (32-bit)


Windows Server®




以上 (32-bit)

Windows 7 (32-bit)


動作環境 9

1. 必要とするハードウェアの動作環境は、利用用途により異なります。

ECWP による、画像配信が主な目的の場合、多数のアクセスを受けるものであっても、高機能でないサーバでも

十分利用可能です。一方で、ImageX / WMS / ArcXML / JPIP プロトコルによる画像配信を行う場合は、高パフォ

ーマンスなサーバ環境をご用意されることを推奨します。

多くの場合、ECWP を利用するにあたってボトルネックとなるのは、ネットワークの回線容量です。処理に必要とす

る CPU 処理能力およびメモリ容量は比較的低い状態で、数千単位の同時アクセスを処理可能ですが、この場合、

100 メガビットのネットワークはすぐに飽和してしまします。

一方、Image Web Server が対応する ImageX/WMS/ArcXML などのプロトコルは、高性能の CPU、大容量のメ

モリを必要とするので、高機能な機器をご用意ください。Windows Serer 2003/2008 をご利用の場合、 Web

Garden により、IIS でアプリケーションプールを利用することで、複数コアの CPU による処理能力を高められます。

利用用途が限定的であったり、ECWP を主要用途として利用する場合は、低性能のハードウェアや、ハードウェア

を共有した環境で利用することも可能です。 Image Web Server は非常にリソース効率の高いサーバです。

2. コラボレーションモジュールのシステム要件は横のカラムをご参照ください。

3. 実際の動作要件は、トランザクション量、リクエストの内容、接続ユーザ数により変化します。

4. データはローカル環境や、NAS/SAN などのストレージデバイスから利用可能ですが、サーバからデータストレージへ

は、十分なアクセス速度が確保できるようにしてください。

5. ERDAS APOLLO Feature Interoperability モジュールは、ERDAS APOLLO Essentials-SDI、Advantage、および

Professional プロダクトで利用できます。しかし、32-bti の Windows 環境にのみ対応しています。ハードウェア環境

が 64-bit である場合、Feature Interoperability モジュールを利用するためには、32-bit 版 JDK（64-bit 版でない）で

システムをインストールする必要があります。

6. Windows 環境では、64-bit 版のご利用をお勧めします。利用用途により変動しますが、5-20%のパフォーマンスの

向上が期待されます。

7. ディスクアクセスの高速化は、パフォーマンスに大きな違いをもたらします。これは、OTD（Optimized Tile Delivery）

配信において顕著です。データはローカル環境や、NAS/SAN などのストレージデバイスから利用可能ですが、サー

バからデータストレージへは、十分なアクセス速度が確保できるようにしてください。

これらの動作環境条件は、変更されることがあります。

最新の仕様条件をご確認するには、

米国 ERDAS Inc.,サイトをご覧ください。http://www.erdas.com

http://www.erdas.com/


10 What’s New

What’s New?

ERDAS APOLLO 2011ERDAS APOLLO はエンタープライズクラスのデータマネージメント･システムです。組

織内にある、ジオスペーシャルデータおよびほとんど全てのデジタル･オブジェクトを記

述、カタログ化、検索、ディスカバー、およびセキュリティを考慮して配布することができ

ます。

ERDAS APOLLO は、３つの階層から成る、相互利用可能（interoperable）な

OGC/ISO ベースのソリューションであり、既存の GIS システムを統合することで、業務

システムを活用し、様々な種類のデータに対応することができます。

ローコストで早い画像転送を実現するシステムから、ダイナミックなデータの編集、分析、

情報抽出まで実現する総合システムまで、ERDAS APOLLO は組織の様々なニーズ

に対応できるように拡張性があり、非常に大きなデータアーカイブを扱う場合でも、比類

ない性能を発揮します。

※上層の製品は下層の製品の機能をすべて含みます。

ERDAS APOLLO : プロダクト全体

オパシティ（透かし設定）オパシティチャネルや、NULL 値に対応したデータフォーマットに対応し、不透明領域を

表示できるようになりました。

ImageX/WMS/ArcXML/ECWP から、オパシティ形式を持つ PNG タイル

（Essentials SDI は WMS のみサポート）

ECW, JP2K, OTDF, ERS, ALG を含むソースデータ


What’s New 11

ERDAS APOLLO Essentials - IWSWeb Map Tiling Service

(WMTS)の対応

OGC 準拠の Web Map Tiling Service(WMTS) インターフェースを利用し、Optimized

Tile Delivery Format(OTDF)テクノロジーを利用できるようになりました。

サードパーティーのアプリケーションから WMTS 経由で、OTDF、ECW およびその

他のフォーマットの画像データを利用可能

クライアント側にプラグインは不要

OpenLayers や、Google Maps とのマッシュアップが容易

新しい再投影エンジン Essential IWS サーバ、ツール、およびユーティリティの座標系参照ライブラリが新しく

なりました。

ERDAS IMAGINE projection toolkit 再投影の品質、速度の設定の選択機能

パフォーマンスの向上スピードが向上し、パフォーマンスの最適化を行いました。

GeoTIFF および、その他 GDAL フォーマットのデコーディング速度の向上

（最大 15%高速化）

WMS Capabilities 文書の生成速度の向上

ECW JPEG200 SDK のバグ修正と拡張

その他の改善 WMS、ImageX のセキュリティオプション、および、discovery サービスの拡張

ファイルネームで取り扱える拡張キャラクターセットの拡張


12 What’s New

ERDAS APOLLO Essentials - SDI

クラスタリングクラスタリングに対応し、複数のサーバを利用することで拡張性が向上しました。クラス

ター環境により、より多くの同時アクセスに対応できるようになります。

Bing Maps インターネットから、Microsoft の Bing Map にアクセス

ERDAS APOLLO Web クライアント、および、TITAN Client の両方で利用可能

ユーザインターフェース上で利用可能な高品質な地図

Bing Maps の三種類のマップソース

Bing Map Roads - ラベルと道路

Bing Map Aerial - 航空写真

Bing Map Hybrid - 航空写真にラベルと道路

ジオメトリ選択ツール ERDAS APOLLO Web クライアントによる、データセットの検索、選択、および、ダウ

ンロードのワークフローが向上しました。

検索、フィルタリング、クリッピングのための新しいジオメトリ選択ツール。

ジオメトリは以下の方法で指定

マップ上の描画

マップ上のジオメトリの選択

Shape ファイルのアップロード、またはオンラインで WFS へアクセス

値によるジオメトリの選択（例：州地図を州の名前により指定）

選択したジオメトリにバッファを適用可能

Web クライアントによるSRS(Spatial Reference

System)の管理

ERDAS APOLLO Web クライアントの SRS 管理機能が向上しました。

SRS 対応：non-EPSG Projection の対応

クライアントサイドで Reprojection(再投影)：ソースデータ以外の座標系へ、クライア

ントサイドから座標変換（Proj4js を利用）

国際化の対応 ERDAS APOLLO Data Manager および、TITAN Client の国際化、ローカライゼー

ションの対応

ERDAS APOLLO Web クライアントの言語対応：

フランス語 / ポーランド語 / ドイツ語 / オランダ語 / 日本語

i18n 対応

新たに対応した OS, Web

ブラウザ

OS(オペレーティングシステム)

Windows Server 2008 R2 64 bit Windows 7 32/63 bit （データマネージャのみ）

Google Chrome 4 （APOLLO Web クライアントおよび ECWP Plug-in）

バグの回収および、性能

の改善

３５０以上のバグ修正と、性能改善


What’s New 13

ERDAS APOLLO Advantage

Data Manager（サーバ管

理ツール）のユーザインタ

ーフェース改善

Data Manger のユーザインターフェースが改善され、より視覚的に管理できるようにな

りました。

集約された設定機能

CZS パラメータ、RDS チューニングおよびその他多くの設定値など、サーバで頻

繁に利用するユーザインターフェースの改善

クラスター環境では、すべてのノードに対してりプリケートしてアップデート

ユーザロール管理機能の向上

セキュリティユーザ / ロールの追加・削除・更新を行う、新しいユーザインターフェ

ース

クラスター環境における、ノード間でのセキュリティ設定の自動更新。

メタデータの一括処理機

能（バッチ処理機能）

Data Manager により、複数のデータセットに対しメタデータを一括で更新できるように

なりました。

メタデータの更新は下位階層に対し自動的に一括設定が可能

データセット毎にメタデータの編集を個別に設定可能

シンプルかつ効率的な編集用テーブルセルは、属性のコピー＆ペーストに対応。カラ

ムビューにおいて、表示するメタデータフィールドを指定可能

LiDAR データのクロール ERDAS APOLLO Web クライアントの SRS 管理機能が向上しました。

LAS ファイルの妥当なメタデータを抽出し、LAS ファイルごとに自動的に（GeoTIFF

または IMG 形式の）サーフェスファイルを生成

サーフェスは視覚化のために、ヒルシェイド（hillshade）にスタイル化され、WMS

により描画

ERDAS APOLLO Web クライアント、TITAN Client から、WCS 経由で、"Clip, Zip,

Ship（クリップ、圧縮、配信）"機能により、LAS ファイルを入手

カタログが対応する

Raster フォーマットの追

加

対応するデータフォーマットが追加されました。以下のデータフォーマットのクロール、分

類（カタログ）、および配信ができます。

OTDF： WMTS、WMS、および、ImageX で配信可能

ERS / ALG： WMTS、WCS、および、ImageX で配信可能

IWS との統合 ERDAS APOLLO-IWS サーバが統合され、ERDAS APOLLO Advantage システム

内に導入できるようになりました。前バージョンでは個別にインストールし、”IWS モジュ

ール”として、一部の機能しか利用できませんでした。IWS と同等のパフォーマンスで、

すべての対応プロトコル、および ECWP の検索サービスができるようになりました。

数千レベルの同時アクセスに対応可能な ECW、JPIP の対応

ImageX、WMTS プロトコル、および、OTDF の対応

ECWP、ImageX の SSL 対応

IWS の高度なセキュリティモデルによる、スペーシャル、スケールに対するセキュリテ

ィ対応

ECW-JP2 デコーディング

のパフォーマンス向上

ECW-JP2 のデコーディングパフォーマンスが向上しました。


14 What’s New

検索、選択、ダウンロード

オプション

複数選択による、一括ダウンロード

マルチプルダウンロードオプション

Clip, Zip, Ship（クリップ、圧縮、配信）機能

オリジナルファイルのダウンロード

KML 形式でダウンロード（Google Earth 用）

Shoebox 形式でダウンロード（ERDAS IMAGINE 用）

以下のパラメータを指定して、複数データセットを一括でダウンロード可能

一般的な SRS

ユーザがあらかじめ設定したジオメトリ

新たに定義するジオメトリ


What’s New 15

ERDAS APOLLO Professional

European HMA プロジェ

クトの対応

レガシー資産である、RedSpider カタログが、ERDAS APOLLO Professional に

「HMA コンポーネント」という名称で追加されました。このコンポーネントは、European

HMA プロジェクト要件を満たすものです。

規格標準なメタデータによる分類（Catalog）と検索

（ISO 19115/19139、OGC Earth Observation GML、OGC SensorML）

European HMA プロジェクト要件に準拠した、OGC 準拠の CS-W ebRIM インターフ

ェースによるメタデータの提供

レガシー資産のカタログの上位にプロキシ（代理）機能を作成し、European HMA プ

ロジェクト要件を満たす OGC 準拠のカタログサービスを構築

カスタマイズされたメタデータ形式のカタログ化、カタログサービスのインターフェース

（CS-W ebRIM）の形式、および、あらかじめ設定された検索クエリ（ad-hoc なクエリ）

の構築

ERDAS APOLLO Solution Toolkit

IIF/EAST の統合 ERDAS Image Integration Framework（IIF）が ERDAS APOLLO Solution Toolkit

（EAST）に統合されました。IIF を使って、単一のアプリケーション上から、多くの Web

GIS、および、イメージサービスへ同時アクセスして閲覧することができます。それ以外

にも次のような改良点があります。

レイヤグループ・ネストレイヤ：１つの階層レイヤグループとして、WMS サービスに追

加

ImageX タイル API による OTDF/ECW 対応

ERDAS APOLLO Feature Interoperability

ベクターデータのアップロ

ードと配信

ERDAS Feature Interoperability アドオンモジュールは Safe Software FME 2010 に

アップグレードされました。

FME Workbench に、対応フォーマットを追加


16 付録：Customer Relations（英文）

付録：Customer Resolutions（英文）

APOLLOCatalog It is now possible to provide the Database instance name for the SQL Server

during installation so that the schema can be created or updated in theappropriate instance. [EAP-4647]

ERDAS APOLLO Catalog and Vector services now support MicrosoftSQLServer 2008 R2. [EAP-4854]

It is now possible to force the APOLLO Catalog to respond on a specificURL/Port.a set of configuration properties are defined for that goal:

apollo.webapp.hostAndPort=server-alias:80apollo.webapp.name=webapp-alias [EAP-4921]

Data Manager Metadata Editing is correctly disabled when Aggregates and datasets haveread-only permissions. [EAP-1507]

Previously, if two servers had recurring jobs with the same name and you triedto view the status of one job, the Jobs View occasionally reported the status ofthe other job. Jobs View now displays job statuses accurately. [EAP-3191]

Users are able to view and edit the Temporal Extent field in the Properties Viewof the Data Manager again. [EAP-3403]

ERDAS APOLLO Data Manager now performs server-side browsing andvalidation for files and folders during the crawl and add image actions. [EAP-3455]

A Data Manager Translation Toolkit is available for translating all the APOLLOspecific plugins and the Eclipse RCP (3.0.0) framework that the Data Manageris built on top of and has language bundles available for download from theEclipse download site:(http://download.eclipse.org/technology/babel/babel_language_packs/europa.php). [EAP-3483]

ERDAS APOLLO can handle coverage files whose names use Chinesecharacters when the server locale is Chinese. [EAP-3731]

Indexing image in ERDAS APOLLO SDI may fail sometimes due to DataManager inactivity. The workaround is to dismiss the error message, right clickon the provider for edit and reindex the provider in the Data Source tab in theData Manager. [EAP-5698]

It is now possible to install and run ERDAS APOLLO 2010 Data Manager andERDAS APOLLO 2011 Data Manager side-by-side on the same machine.[EAP-6122]

In the Data Manager, port numbers can now be between 0 and 65535(inclusive) where previously port numbers were limited to 32767. [EAP-6172]

The aggregate icon in the Explorer View of the Data Manager now uses color toindicate WMS/WCS interface. A yellow folder means it has both WMS and WCS,a grey folder means it has neither, and a half yellow/half grey folder means ithas either WMS or WCS. [EAP-817]


付録：Customer Relations（英文） 17

General ERDAS APOLLO now supports the pseudo Web Mercator SRS with EPSGcode - EPSG:3857 [EAP-2498]

A new service configuration parameter lets you choose the rendering logicwhen datasets and aggregates have styles and/or pyramids. It is calledPORTRAYALMODE. It can take the following values:

standard: to get the old behaviour (default)style: to render an aggregate as a whole if it has a style defined ora pyramid associated, otherwise each child is rendered separatelydeep: each child is rendered separatelydefault: same meaning as standard (for now)Sample<PARAM NAME="PORTRAYALMODE" VALUE="standard" />

[EAP-3026] The result of a search in the Web Client can be saved as an IMAGINE Shoebox

file. [EAP-3395] In ERDAS APOLLO, the radiometric quality of the GIF output is improved with a

new algorithm implementation. [EAP-3448] The ISO Metadata generation templates have been externalized to allow easy

overriding. [EAP-3498] Fixed an RDS timeout issue/extremely slow pyramid generation for large

datasets without pyramids when using the Processing and Web Options of theCrawler Schedule Wizard. [EAP-3517]

Out-of-memory issues with Crawling large datasets is addressed by tuning theJVM parameters on a 32-bit JVM. [EAP-3544]

The Greek HEPOS SRS is now supported. The EPSG code is 40032 for theprojected system and 40031 for the geographic one. Note that the referencedatum EPSG code is 6760 for HTRS07. [EAP-4186]

Start/Stop of JBoss as Service used to frequently fail. It will now occurs muchless often.But that is also depending on the performances of the machine. Don't try to stopit before it is completely started. The stop process is done by launching a newprocess which will connect to the running server and send it a stop message. Ifthat connection fails, the server process will not be stopped and you have to goto the Task Manager to kill it. [EAP-4368]

EPSG:3785 has been added for enhancing interaction with popular third-partyviewers. [EAP-4424]

ERDAS APOLLO Web Client can now be localized in Greek. [EAP-4434] The ERDAS APOLLO Web Toolkit/Client switching SRS has been improved. It

now does the following:Try to reproject the current box to that SRS:

* if it succeeds, then we set that box* if it fails, then it looks for an "area of use" for the new SRS* if it finds one, then it fits to that area, in the new SRS* if it doesn't, then a human-friendly message is displayed to the user:

{{The current map extents could not be transformed into the selectedSRS, and no area of use is known for that SRS}}. [EAP-4447]

After activating cots-srs-ntv2.jar for transforming ETRS89 to ED50, the result isnow properly located in all regions of Spain. [EAP-4523]

ECW-JP2 access in ERDAS APOLLO has been improved and now anyproblems with the ERDAS ECW-JP2 SDK are logged properly into a separatelog for diagnosis purposes instead of showing a dialog box in a headless serverenvironment. [EAP-5253]

Tiled TIFF performance for raster IO and decoding metadata in ERDASAPOLLO 2011 has been improved compared to ERDAS APOLLO 2010. [EAP-5351]

Service Tester applet now has a nicer look. [EAP-5734] When the license is invalid or not found, the service startup error message now

mentions it explicitly. [EAP-5996]



Imagery & WMS/WCS APOLLO WMS/WCS now supports more than Integer data stored in OracleGeoRaster: float and double are now supported. Moreover, the endianness(big-endian or little-endian) of the data can now be configured through the"endian" parameter. [EAP-4939]

According to the OGC WCS 1.0.0 specification, a GetCoverage is valid undercertain conditions even when the BBOX parameter is absent. The APOLLOCoverage service now accepts that situation. [EAP-4958]

The EPSG 29873 RSO Timbalai projection is now correct. A slight error wasfound in the Oblique Mercator. [EAP-5610]

The "TRANSPARENT=true" parameter of an OGC request received by theserver is now accepted even though the "true" or "false" value should be upper-case.Moreover, that behaviour can be configured if a user wants strict OGCcompliance: the OGCSTRICT property can be set to TRUE to turn off lenience.The overall effects of that setting are:

* turn off the lenient behaviour* turn the VERSIONCHECK parameter to "required" (applies to WFS only)* if not defined, the OGCStrictConformance is set* if not defined, the SRSOutputFormat is set to URN* if not defined, the UseUTCDateFormatDefault is set [EAP-5825]

Installation & Licensing Solution Toolkit installer now has a JVM embedded, making it useless to have apre-installed Java SDK. [EAP-4502]

Portrayal WGS84 reprojection from NZTM no longer fails when map bounds extendbeyond projection envelope. [EAP-4632]

Vector & WFS WFS GetFeature with GeoRSS as output format now works even when legendis enabled for portrayal. [EAP-3591]

Corrected issue when selecting a feature from a Multi-Polygon vector layer, thatseveral feature results were displayed for a single selected feature. [EAP-3592]

The use of required quoting is now automatically detected in the fid="generated"mapping. This solves the problem of tables created with quoted fields. [EAP-3594]

If you try to edit layers on a WFS-T using the Edit tab of the ERDAS APOLLOWeb Client, the layers are seen as editable in all cases. [EAP-4475]

JSON output of the ERDAS WFS now outputs dates and array property typesproperly. [EAP-4503]

Creation of a Shapefile vector service using the Multipath option displayedobscure error messages during the creation sequence. The field validation andthe error messages have been improved. [EAP-4556]

DGN v8 files now render correctly in ERDAS APOLLO. Updated the DGNConnector to use master units by default. To manually set this up, make surethe configuration contains a directive setting UNITS to IGDS_MASTER_UNITSin the providers.fac file.

<PARAMBLOCK NAME="directives" ><PARAM NAME="UNITS" VALUE="IGDS_MASTER_UNITS" /></PARAMBLOCK> [EAP-4588]

There can now be more than one instance of the FIO (Feature InteroperabilityOption) installed on a single machine. [EAP-4662]

JSON output of date properties and of complex WFS properties (array type)now give a valid output. [EAP-4793]

When the font chosen to portray an Arabic field value is not Arabic, we now usealternate ways of detecting if it has to be written from right to left: check if it is anArabic string, and check the Arabics unicode plan and Hebrew plan.This might fail if the string starts with a blank character or if it mixes Arabic andnon-Arabic characters. [EAP-5524]


付録：Customer Relations（英文） 19

When ESRI ArcSDE table name cases are mixed, the association of the SRSwith the table could fail with the message "the handle to Arcsde Srs CoordinateSystem is invalid".Now when such association fails, the server checks the various cases (upper,lower, camel). [EAP-5693]

Web Client/Toolkit The APOLLO 10.1 Client was managing projections based on SRS EPSGcodes. This limitation has been lifted by using the Proj4JS library. The WebClient now truly manages the spatial reference systems, supporting non-EPSGSRS definitions and allowing to reproject data client-side. [EAP-1083]

The Web Client Search Panel and Result list now allows you to download thesearch results as a batch file. [EAP-2212]

The mouse wheel will now always zoom in and out the map, no matter whatnavigation icon is selected in the Client navigation toolbar. [EAP-2865]

In APOLLO 10.1 Web Client, it was not possible to select styles on publicimagery datasets when not logged in, this is now fixed [EAP-3385]

Zoom to extent for WMS & ECWP layers in Web Map Context file now workscorrectly when the layer is visible. [EAP-3441]

Updated the Scale box above the map panel in the Web Client so that whenyou manually update the scale, it accepts the input and zooms to theappropriate scale. [EAP-3445]

Some erroneous data was sometimes being displayed when zooming andpanning in the APOLLO 10.1 client. This is now fixed [EAP-3476]

In the APOLLO 10.1 Web Client, the 'Fit to Layer' command was sometimesfailing due to reprojection issues (dependant upon the respective data and theview SRS). This is now fixed. [EAP-3646]

The APOLLO 10.1 Web Client was quite slow to add very big WCS and WFSservices because of unnecessary GetCapabilities requests, this is now fixed.[EAP-3661]

The Search Panel results now uses the dataset and aggregate Titles(descriptive) instead of Names. [EAP-3685]

When adding secured layers, the Web Client was sometimes asking for username and password twice before displaying the image, this is now fixed [EAP-3691]

The Web Client now proposes a default navigation mode at startup:Zoom-in/out with the mouse wheel and Pan as the start-up tool. [EAP-4028]

In the APOLLO 10.1 Web Client, turning a layer to tiled mode disabled the scalehints, enabling other layers that should be disabled at that scale. This is nowfixed. [EAP-4037]

When the transformation in the current map's SRS is not possible, "Unavailable"will be displayed, together with a tooltip explaining how the transformation failed.[EAP-4152]

It was possible in 10.1 to have the web client displaying mixed translations, thisis now fixed. [EAP-4264]

Compatibility with third-party WMS servers has been improved by making theWeb Client more lenient [EAP-4299]

When adding APOLLO Essentials - IWS layers, the APOLLO Web Client willnow automatically fall back to WMS when the ECWP plug-in is not available inthe browser. [EAP-4327]

The Web Client now fully runs on Google Chrome and is able to consumeECWP streams using the ECWP plug-in. [EAP-4361]

The Web Client is now able to add layers with Chinese names (Add to Mapbutton in a catalog search result) [EAP-4365]

The APOLLO Web Client now falls back to the WMS interface whenever theECWP plug-in fails to reproject some data (with custom SRS definition). [EAP-4369]

The APOLLO Web Client now loads context files much faster [EAP-4372] The APOLLO Web Client is now able to correctly export vector data with

Chinese attributes [EAP-4386]



The OTDF data consumption (through ImageX) has been improved in theAPOLLO Web Client. [EAP-4441]

The GetInfo tool is now lazy loading the vector data information. The tool onlyretrieves the one needed by the user. This reduces the bandwidth usage andimproves the performance. [EAP-4485]

The vector data filtering tool now works with vector data layers (WFS) withChinese names. [EAP-4495]

The list of styles in the layer configuration panel was sometimes disappearingwhen adding a new style, this is now fixed [EAP-4499]

It is now possible to add external WMS services that report scale ranges asNaN to the Web Client. WMS Client handling is made more lenient. [EAP-4546]

With APOLLO 10.1, the Web Client did not actually delete the search footprintwhen requested. This is now fixed [EAP-4769]

Google Maps and other layers in the Web Client are handled correctly inregards to reprojecton and drawing features at the correct locations. [EAP-4810]

The measurement tool is now reset when switching from one context/projectionto another. [EAP-5300]

When viewing dataset ISO metadata, a new link (View ISO xml) is available todownload the raw XML document. [EAP-5389]

It is now possible to configure the output format that will be used as defaultformat for WMS requests in the apollo-client.properties configuration file.Current default is image/gif [EAP-5420]


付録：Known Issues（英文） 21

付録：Known Issues（英文）

APOLLOCatalog The GeoRSS output of the ERDAS APOLLO Catalog is currently not fully

compliant with the GeoRSS specification, so it may not be properly handled bysome GeoRSS clients. [EAP-3614]

When searching by keyword in the ERDAS APOLLO Web Client, the searcheswill not return anything if any of the keywords contain an underscore character( _ ). For example, a search for the keyword "place_names" will return nothing,even if there is data in your catalog with that exact keyword. Searching for"place", "names", or "place names" will work, however. [EAP-3627]

While harvesting resources through the CSW endpoint of the ERDAS APOLLOCatalog, it may indicate that it did not harvest any items, even though it actuallydid harvest them. [EAP-3629]

In the Publish tab of the ERDAS APOLLO Catalog Web Interface, to harvestsecured services you will need to put the security credentials in the URL of theservice to harvest. For example, http://login:[email protected] . [EAP-3633]

KML view of services cannot be read by Google when there are too manylayers. [EAP-3637]

If you are using the custom resources crawler in the Data Manager to addresources on a remote machine to your catalog, you need to make sure that theuser running the Data Manager has write access on the associated *.gim files,because the custom resources crawler needs to modify these files. [EAP-3638]

Attempting to display overlays of WMS layers in Google Earth is likely to fail forcertain WMSs, as Google Earth does not completely support the WMS interface.[EAP-3639]

The ERDAS APOLLO Catalog Web interface will allow you to attempt to publishOGC services to your catalog, even when your session has timed out and youare no longer logged in. After a while, it will notify you that your attempt hasfailed and that you should log in again. If you log in again, you should be able topublish a valid OGC service. [EAP-3866]

Harvesting the same dataset simultaneously several times may cause an errorby the ERDAS APOLLO server. [EAP-3886]

APOLLO 2011 does not work out of the box with Posgres 9. It is stronglyrecommended to use Postgres 8.3 version. A possible work-around is toupgrade the Postgres drivers in APOLLO. Download the drivers for Postgres 9,back up the driver for Postgres 8.3 from [ERDAS-APOLLO]\webapps\erdasapollo\profiles\eaim\lib\postgresql-8.3-603.jdbc3.jarand copy/paste there the one you downloaded. Rebuild/redeploy and restart thewebapp and it should work. [EAP-6417]

Users may experience problems when browsing catalog records using theCatalog Web Interface hosted on a WebLogic server. Namely, HTML pagesmay not be properly interpreted by browsers, and are instead displayed as rawHTML code. This has been observed only on catalog content displayed inHTML, e.g. on URLs of the form ./erdas-apollo/content/catalog/... displayed in abrowser. This does not affect other output types, such as KML,JSON, and soforth. Technically, this is caused by missing HTTP headers in responses fromWeblogic-based servers. Consequently, the browser is unable to determineactual content type, and mistakenly interprets it as plain text. [EAP-6424]


22 付録：Known Issues（英文）

Data Manager After installing a new version of the ERDAS APOLLO Data Manager, youshould locate the file named .apollo-xx.x and delete it. This file is generallyfound in the folder C:\Documents and Settings\<username> on computers thatuse MS Windows, and the folder //HOME/<username> on Linux computers.[EAP-1001]

The IAS Viewer from ITT Visual Information Solutions does not displaystreaming data from some JP2 images. It appears to be related to the metadatain the JP2 file. To work around the issue, you can re-export these images usingIMAGINE 9.3 or higher or use another viewer, such as Kakadu kdu_show or theERDAS IWS plug-in. [EAP-1461]

In ERDAS APOLLO Data Manager versions 9.3.2 and higher, the crawlers arecase sensitive, so that if someone changes the case of a directory or file namethat has already been cataloged, the crawler will view it as a new directory orfile and will re-catalog it. [EAP-2999]

When configuring an APOLLO Essentials-SDI server using the Data Manager,the refresh button will not update changes to the server made outside of thatData Manager instance. The workaround is to disconnect and reconnect. [EAP-3067]

If the Data Manager is kept running over night, it is possible that alreadycompleted system jobs stay visible in the Jobs view. A refresh of the Jobs viewor a restart of the Data Manager will take care of this display issue. [EAP-3133]

The Properties View may not display date queryables after migration fromERDAS APOLLO Image Manager 9.3.2 to ERDAS APOLLO 2010. The simplestsolution is to regenerate any date queryables with the following steps:

1. Shut down your server and remove or comment out any date queryablesin the queryables.xml file.

2. Restart the server and log in to it with the Data Manager.3. Right-click on the server connection in the Explorer view and select

'Update Queryables' on the menu.4. Wait until the queryable update job finishes. All date queryables should

be removed now.5. Shut down your server and add or uncomment your date queryables in

the queryables.xml file.6. Restart the server and log in to it with the Data Manager.7. Right-click on the server connection in the Explorer view and select

'Update Queryables' on the menu.8. Wait until the queryable update job finishes. All date queryables should

be back now. [EAP-3171] When using Chinese keywords for aggregates and datasets in the Data

Manager, your ERDAS APOLLO database must be using the Chinese versionof Oracle in order for the keywords to be stored and displayed properly. It mayalso be true for other languages that require UTF-8 character encoding. [EAP-3519]

The ERDAS APOLLO Data Manager cannot add service providers to thecatalog if the security has been configured for them. [EAP-3581]

If you attempt to add a raster scale service provider to the map in the DataManager, the layer will not appear in the Layers View or the Maps View. [EAP-3717]

In the Data Manager, if you right-click a dataset for a Map & Proxies serviceprovider and select Show Metadata in the menu that appears, it will not usuallyshow you any metadata. The workaround is to manually add the ISO metadatafiles for the data in the following location:<APOLLO_HOME>\config\erdasapollo\ metadata\map\<SERVICE_NAME>\<LAYER_NAME>.xml. [EAP-3726]

The ERDAS APOLLO Data Manager doesn't allow you to apply a style to araster service provider of type "List" and have it automatically apply to all of thedatasets of the service provider. You must manually edit the default SLD stylesdefined per format and located in<APOLLO_HOME>\config\erdasapollo\rendering\collection\FORMAT_NAME\default\SVG.sld [EAP-3733]



The services created in the ERDAS APOLLO SDI cannot be registered in theERDAS APOLLO Catalog if their security has been configured. [EAP-3744]

The ERDAS Apollo server doesn't allow to overide the metadata for proxiedserivces. [EAP-3745]

When you use the ERDAS Apollo Data Manager to add a dataset to a OracleGeoRaster service, you must know the table and column names for thedatabase that contains the data, because the current version of ERDAS ApolloData Manager cannot detect them. [EAP-3777]

In WMS Capabilities documents, layer <Abstract> and <KeywordList> elementsare not generated by default. For vector providers, they can be added via themapping file as follows:

<!-Info for type wfs:admin98-><Info name="wfs:admin98"><Operations>Query</Operations><Abstract>My abstract</Abstract><Keywords>My, Keywords, List</Keywords><SRS>EPSG:4326</SRS><BoundingBox SRS="EPSG:4326" minx="-180.0" miny="-90.0"maxx="180.0" maxy="83.62359619140625"/></Info>

For MultiSimpleProvider and IndexedProvider, this info can be set in theERDAS APOLLO Data Manager (Coverage Info field in the Service Info tab ofthe Service Provider Editor View) For a Hierarchichal provider, this info is in thecatalog. [EAP-3782]

StyleEditor sometimes may output invalid context file when styles are applied toWCS layer(s) in which case layers does not show in the map which are part ofthe web map context. The workaround is to remove the SLD style from theWCS layer to display it on the map as part of the map context. [EAP-3785]

In the ERDAS APOLLO Style Editor, the Save menu item is disabled when onlythe Scale is modified. The user should pan the coverage slightly to enable theSave menu item and save the workspace. [EAP-3792]

When creating a vector service provider for data with a Chinese name, youmust generate the types and mapping files using the command line toolrunfromsqlshp with the -CHARSET parameter instead of generating them withthe ERDAS APOLLO Data Manager. (see the ERDAS APOLLO Admin Guide -Essentials-SDI Edition for more details) You can also set the property "Typesschema" to "defaultsql3:4326" in the Data Source tab of the service providereditor in the ERDAS APOLLO Data Manager. [EAP-4148]

When creating a Vector Data/File/Shape Service, the tool does not parse thesub-directories to find data. [EAP-5974]

While setting up any type of "Maps&Proxies" service, the wizard does notpropose all the necessary panels for the services to be properly configured. Youhave to apply additional settings by clicking Edit Provider. [EAP-6201]

ERDAS APOLLO Data Manager does not show the WMS hierarchy for proxyservices. In order to see the WMS hierarchy use the Web Client to view layers.[EAP-6213]

When you logout of Data Manager and log back in, refreshing the Property Viewwill update the User name property. [EAP-6229]

Occasionally, when creating a new service, the Data Manager Services treefails to display properly. Clicking the refresh button fixes this issue. [EAP-6320]



General The Clip, Zip, and Ship feature of the ERDAS APOLLO Web Client may fail ifthe SMTP server is not configured or is not accessible. You must configure themail server and make sure it is available so that the server can send the user anemail to download data from the server via HTTP or FTP. [EAP-1379]

When multiple NODATA values are input for the aggregate, only the "last"number in the comma delimited list is being honored. [EAP-1650]

Sometimes, if JP2 imagery cannot be reprojected using the ECWP plugin in theERDAS APOLLO Web Client, you may need to export them as ECWs andcatalog them so that they can be viewed in the Web Client without anyreprojection issues. [EAP-1733]

When you Download datasets that are NTFs, the output format is NTF, and anirregular polygon is specified as the Clip geometry, its bounding box is usedinstead of the irregular polygon. [EAP-2024]

If you generate pyramids for an aggregate, delete them within a few minutes,and then attempt to generate them again, the pyramid regeneration may fail andyou may receive the error message "The requested operation cannot beperformed on a file with a usermapped section open".As a temporary workaround, you can stop and restart the application server. Inmost cases, you should then be able to regenerate the pyramids.If it still fails, or if you don't want to stop the application server, do the following:

1. Launch Microsoft Process Explorer. (Available for free from Microsoft)2. Press Ctrl + F on the keyboard. The Process Explorer Search dialog will

open.3. Type the name of the aggregate in the Handle or DLL Substring box and

click the Search button.4. The search will indicate the files that are associated with the pyramid you

just generated, and the process that is using these files. Each process isidentified by a Process ID number, shown in the second column from theleft. You need to kill those processes by right-clicking them in the mainProcess Explorer window and selecting **Kill Process** in the menu thatappears.Hint: You can find the process in the main window by matching theprocess number from the search dialog to the PID in the main window.Also, if you click a row in the Process Search Explorer dialog, it willhighlight that process in the main window for you.)

5. After you kill the associated process, you can close the Process Explorerand go back to the Data Manager to re-generate the pyramids. [EAP-2039]

If some of the datasets from an NITF sub aggregate are deleted, the crawlermay not re-catalog the deleted datasets on a subsequent run. To re-catalog thedeleted datasets, delete the sub aggregate and crawl the folder again. [EAP-2083]

In ERDAS IMAGINE, multi-images are accessed using the subimage file (*.sbi)and when the image pyramids are generated the RRD files are associated withthe sub-image file (*.sbi) instead of the NITF (*.ntf) files. This causes ERDASAPOLLO Image Manager Server to generate external GeoTIFF pyramids whenthe images are indexed into the system. [EAP-2095]

When aggregates are deleted, folders that are created for thumbnails, pyramidsand ISO metadata files may remain and will be empty. It should not create anyfunctional problems. [EAP-2109]

When cataloging imagery that covers a large portion of the earth, please keepin mind a limitation of Oracle Spatial, see Oracle Spatial Developer's Guidechapter 6.2.5 Other Considerations and Requirements with Geodetic Data(http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28400/sdo_cs_concepts.htm#i895077):The following size limits apply with geodetic data:

1. No polygon element can have an area larger than or equal to onehalf thesurface of the Earth.

2. In a line, the distance between two adjacent coordinates cannot begreater than or equal to one-half the perimeter (a great circle) of theEarth.



If you need to work with larger elements, first break these elements into multiplesmaller elements and work with them. For example, you cannot create ageometry representing the entire ocean surface of the Earth; however, you cancreate multiple geometries, each representing part of the overall ocean surface.To work with a line string that is greater than or equal to one-half the perimeter ofthe Earth, you can add one or more intermediate points on the line so that alladjacent coordinates are less than one-half the perimeter of the Earth. [EAP-2152] For recurring crawler, if new datasets get added after every crawl the aggregate

thumbnails may not updated. The workaround is manually do the followingsteps:

1. Delete the aggregate pyramids2. Regenerate pyramids for the aggregate either by attaching an existing

pyramid or regenerating the aggregate pyramids using Data Manager3. Regenerate the thumbnails using Data Manager.

It is also recommended to perform the manual operations on weekly basis ifnew datasets are getting added daily. [EAP-2229]

If new datasets are added to the directory that has a recurring crawlerassociated with it, the existing aggregate thumbnail file should be deleted, thenthe recurring crawler will recreate the aggregate thumbnail. [EAP-2357]

If pyramid generation ends up in error, thumbnail generation is skipped. Thereason is that thumbnail generation might clog the server while doingresampling for the large images that have no pyramids associated with them.[EAP-2367]

Adding existing pyramids to aggregate that is not yet done crawling is notsupported yet. Hence it should be done when the crawling is complete for theaggregate. [EAP-2378]

The ERDAS APOLLO server reads its configuration files only once at startup.This means that any update of the queryables.xml file requires a server restartto become active. [EAP-2406]

ERDAS APOLLO Web Client currently does not support streaming ECW fileswith custom CRS. It is recommended before indexing to the catalog to reprojectECW image to standard EPSG CRS using ERDAS IMAGINE to stream the thedata to the Web Client. [EAP-3088]

When upgrading from ERDAS APOLLO Image Manager 9.3.2 to ERDASAPOLLO 2010, the user will need to make note of the recurring crawlers in theold system and recreate them in the new system. [EAP-3172]

Styling does not take into account styles on children aggregates when higherlevel aggregates are consumed by WMS. [EAP-3185]

The crawler performance can degrade if a folder on the file system you arecrawling has more than 1000 datasets under it. For optimal crawlingperformance, it is recommended that you arrange the data on the file system insuch a way that a folder does not contain more than few hundred datasets .[EAP-3231]

Crawling of images that have not been georeferenced will now only succeed iftheir extent is compatible with the SRS of the parent aggregate. [EAP-3296]

Using IndexAdministration API for updates to the catalog outside the servercould cause unanticipated problems due to the Hibernate cache becominginconsistent with manipulations to the database outside the server. Please usethe remote Catalog Service API for any updates to the catalog. [EAP-3394]

When an aggregate with a large number of datasets is viewed in the web-client/Data Manager, you may notice missing blocks in the image, a mosaic ofall the datasets under the aggregate, returned by the server. This may be due toa safeguard setting. The maximum number of images that are combined into amosaic is set in the "im-providers.fac" configuration file which is found under"<APOLLO_HOME>\config\erdas-apollo\providers\coverage\improviders.fac".The parameter "maxStitch" controls the maximum number of images that will beused in a mosaic (defaults to 500 images). Note that increasing this number willdegrade performance since it can take a very long time to create such a mosaic.[EAP-373]



Any ERDAS APOLLO catalog images projected in EPSG:28992 that wereedited with ERDAS IMAGINE 2010 will not work with WMS/WCS. You can nowpermanently fix these images by using ERDAS IMAGINE 2010 version 10.1 toproject the images in EPSG:28992 again. [EAP-4296]

JP already updated the download page for FIO. [EAP-4539] Band re-ordering with styling, will not be applied to ERS, ALG or OTDF files.

Use ECW or JP2 files instead if band re-ordering is necessary. [EAP-4821] When an aggregate is deleted, whatever associated pyramids are deleted as

well. [EAP-5184] Some fine-tuning of the INFO-level messages in the log files is needed. [EAP-

5916] It can happen that imagery operations on top of a Microsoft SQL Server 2008

catalog will produce a deadlock error message:"Transaction (Process ID 57) was deadlocked on lock resources with anotherprocess and has been chosen as the deadlock victim. Rerun the transaction."The work around is to re-add the images if the deadlock fails to add a specificimage. [EAP-6204]

It can happen that imagery operations on top of a Microsoft SQL Server 2008catalog will produce a ConcurrencyFailureException error message:"com.erdas.rsp.babel.dao.ConcurrencyFailureException: could not executequery;"The work around is to re-add the images or to run a DescribeCoverage requestif the issue impacts generation of ISO metadata. [EAP-6207]

The 11-bit/16-bit JP2/ECW images may look washed out when viewed via WMSusing ImageXRasterCoverageDecoder. [EAP-6274]

When creating a recurring crawl job having aggregate pyramids enabled, theaggregate pyramids should be regenerated each time some datasets are addedor deleted between the runs. This is not the case in 11.0, the pyramids getgenerated during the first run but are not recomputed on subsequent runs toreflect the the new data. A patch is scheduled shortly after the 11.0 release thatshould include a fix for this issue. [EAP-6336]

Since 11.0, the configuration parameters are editable in Data Manager forsystem jobs such as Geoprocessing (WPS) Cleanup Job and Provisioning(CZS) Cleanup Job. However, any change in the configuration parameters forthese jobs won't be applied until the application server is restarted. [EAP-6344]

Geoprocessing & WPS Geoprocessing outputs may be slightly different depending on whether youchoose datasets as inputs or choose aggregates that contain the individualdatasets. If you choose the datasets themselves, the software will access thefiles directly in order to optimize speed. If you select an aggregate, the softwarehas to access the dataset pixels via WCS, and some resampling may occur.[EAP-3326]

PostgreSQL server version 9.x is not supported by APOLLO 2011 because itwas released too late for us to be able to validate it properly. But we do notexpect major issues.If are using a PostgreSQL 9.x server, replace the JDBC driver bundled inAPOLLO with the 9.x driver (availablehere:http://jdbc.postgresql.org/download.html. [EAP-6348]



Imagery & WMS/WCS When creating a service, the ERDAS APOLLO Data Manager uploads all filesthat have the same name as the given name but with other extensions. Forexample, if cities.shp is specified, cities.shx, cities.dbf, cities.prj are alsouploaded. If unwanted files are uploaded, they can be deleted in the Resourcetab of the Service Provider Editor View. [EAP-2508]

Logging to a console (i.e,. log4j.appender.CONSOLE.Threshold in<APOLLO_HOME>/tools/native/nci/rds_log4j.properties) at any level belowINFO may cause RDS to hang/slow down severely. Logging to a file (i.e.,log4j.appender.Socket_Logger.Threshold in<APOLLO_HOME>/tools/native/nci/rds_log4j.properties) at any level will workwithout any problems. [EAP-2631]

The hillshading portraying process sometimes displays unwanted black borderson the map. [EAP-3604]

The "Brightness Only" checkbox of the "Hillshade" option of the styling panel inthe ERDAS APOLLO Data Manager has no effect. [EAP-3840]

WMS Proxy Provider fails to update LegendURLs. The URLs returned in thecapabilities document for the proxy provider containURLs to the original service provider, not to the proxy provider. If a non-secureproxy service is set up on a secure service , the legendURL will containreferences to the secure service and so expect credentials. [EAP-4165]

Seams might appear between the tiles of a mosaic, when datasets projectionsare heterogeneous [EAP-4416]

If you catalog or index ALG/ERS files where the underlying source datasets areanything other than ECW and JP2 images, they may fail as theImageXRasterCoverageDecoder may not be able to extract the EPSG codesuccessfully from them. [EAP-4984]

Band re-ordering with styling, will not be applied to ERS, ALG or OTDF files.Use ECW or JP2 files instead if band re-ordering is necessary. [EAP-4991]

The current gdal_tool decoder bundles the ECW SDK 3.3 for ECW and JP2outputs. It has not yet been migrated to the latest release: ECW SDK 4.1. Thisshould have no functional impact. [EAP-6185]

ECW/JP2 imagery opacity (alpha-channel) is not taken in account, through theWMS interface, if styles are explicitly defined on ascendant aggregates. TheImageX and ECWP interface/protocol is correctly applying the Alpha channel.[EAP-6384]

Installation & Licensing The ERDAS APOLLO installer may display a warning message if you do nothave the JAVA_HOME environment variable defined before you run it. TheWARNING message will say "WARNING -Valid VM not found, launcher cannotbe configured to a specific launcher." You can safely disregard this warning, asit has no adverse affect the ERDAS APOLLO installation process. [EAP-3699]

On an Eclipse workspace, the quick start project shows a warning that says thenet-components-1.3.8a.jar is missing when Maven integration is activatedduring installation. This jar is not used by the generated project , so this warningmessage can be safely ignored. [EAP-3765]

To uninstall APOLLO on Windows 7 64-bit systems, delete the installation folderand the shortcuts from the start menu manually. Afterwards, the entry in thecontrol panel "Programs" display can be removed by interacting with it. [EAP-4187]

After installing the APOLLO 10.1 incremental installer on an installation usingTomcat, the rebuild and deployment of the webapps has to be done manuallyafter the installation. [EAP-4481]

The path for 2008.08.Mappings.map is wrong when using a 64bit platform forlicense checks. The message appears in the log file but has no functionalimpact. [EAP-5552]

Uninstalling APOLLO Data Manager on Windows 7 - 64 bits fails. It isnecessary to delete the installation directory manually. [EAP-6309]



When deploying APOLLO on Weblogic, it is necessary to select the 'ProductionMode' in the WebLogic Domain Startup Mode section. Failing to do so mightresult in a very slow APOLLO deployment, and/or inconsistent behavior. [EAP-6388]

Metadata Framework File name patterns that are specified in the decoder.txt and the metadata.txtconfiguration files are currently case sensitive. For this reason, if you want thesoftware to detect and handle the files with that pattern regardless of case, youwill have to provide two lines in your decoder or metadata parser configurationfile, one for upper case and one for lower case.For example (for decoder.txt):alos_1 =,com.lggi.esp.coverage.decoder.raster.gio.GIORasterDecoderProxy,VOL-ALPSM*alos_2 =,com.lggi.esp.coverage.decoder.raster.gio.GIORasterDecoderProxy,vol-alpsm*[EAP-2895]

In some cases, the system cannot use custom metadata parsers that containXSL to read the metadata from images. [EAP-3181]

Vector & WFS When requesting a GeoRSS output, it can happen that the request fails with anerror telling:

com.ionicsoft.api.wms.WMSException:java.lang.NullPointerException

atcom.ionicsoft.wfs.rendererimpl.FeatureRenderer.translate(FeatureRenderer.java:1911)

This is because legend portrayal is currently not supported by the GeoRSSencoder.To avoid this, the legend must be disabled for GeoRSS output. Technically, inthe portrayal post rule, set parameters.legendEnabled to false. [EAP-3591]

WFS PostGIS connector does not build correct queries when Columns creationforces them in upper case. [EAP-3593]

In the absence of a specific GeoRSS rendering rule, the default GeoRSS outputis obtained through a rendering bridge which is only able to extract thegeometry (in this case) as it has no idea which part of the feature the userexpects in the output. So to override this behaviour, the user must install a javarule [EAP-3595]

. The APOLLO Feature Interoperability add-on is not compatible with a 64-bitJVM. It will prevent the vector DGN service from being set up. The onlyworkaround is to reinstall the APOLLO software with a 32-bit JVM. [EAP-4445]

. In APOLLO 10.1, when Tomcat is started as Service, the FME plugin will notinitialize.

One workaround is to define the relevant variables (PATH andIMAGINE_HOME_PATH) as global Windows variables.

Another solution is to edit the tomcat/bin/service.bat script and append to line112 "%EXECUTABLE%"

//US//%SERVICE_NAME% --JvmOptions ... the setting: --Environment "IMAGINE_HOME_PATH=SET;PATH=%PATH%" Then reinstall Tomcat as service and start it. [EAP-4480]



Web Client/Toolkit In CZS, editing parameters such Interpolation and Channel selection, will nothave any effect if the output format is NITF. Those parameters are applied onlyfor IMG and TIFF outputs. [EAP-2077]

In the Web Client, only "like" and "equal" operators return values when queryingon queryables of type String. Other operators such as greater than or less thanoperators may not return results. [EAP-2187]

Because of the technology used for displaying a printable view of the map,loading such a view could take a long time, in the case of Advantage &Professional editions.Printing has thus been disabled for those editions, and is kept only forEssentials edition. [EAP-2475]

In Add Service option in the Web Client, only true IWS Streaming Services canbe added. ERDAS APOLLO 2010 supports streaming via ECWP but it does notexpose the ECW files registered in the ERDAS APOLLO Catalog as IWSstreaming services. Use the Search option to find the ECW and JP2 from thecatalog and display it in the Web Client. [EAP-2816]

The Input/Output Abstract only shows in the Data manager. In the upcomingrelease, we will show the input/output abstracts as tooltips in the web client.[EAP-3002]

ERDAS IMAGINE Model Publisher currently allows certain datasets that are notWCS enabled as input to the IMAGINE spatial models that run on the server. Ifsuch datasets are passed as arguments to the WPS processes, it may not runon the server as the process is expecting a WCS input for raster data. It isrecommended to use Data Manager to enable WCS for the datasets oraggregates if it is desired to use them as inputs to geoprocessing processes onthe server. [EAP-3053]

When uploading WMS data, a service will be created that has a "toplevel" layerwhose name is the same as the service's name, holding a child layer thatactually _is_ the data uploaded by the user.The "duplicate" child is thus an "umbrella" layer. [EAP-3138]

When downloading images, selecting another coordinate reference system tostore the file may result in a file that has some missing projection definitions.WGS84 is a safe coordinate system to transform the download files to but someothers may be at risk to bad encoding. Its seems like images with EPSG SRSwith HARN based Datums have their datum information lost during encodingdue to projection translation.The process of downloading images uses an open-source third party library toencode and transform the files of which we cannot fully guarantee thecorrectness of the outputs. Planned for future a release, is the replacement ofthis third party encoder with the proven ERDAS raster encoders but for the timebeing, outputs that may have missing projection definitions can be corrected byusing ERDAS IMAGINE 2010 by opening and reprojecting the file into the samereference system to fix the missing items. [EAP-3269]

The calendar panels in the search tab are not "physically attached" to a tab.The user needs to close it manually. [EAP-3642]

If the user edits an existing geometry, the cancel button in the geometry editingtoolbar will delete the geometry rather than canceling the editing operation. Inmany cases, the geometry can not be recovered, but if the geometry edit is partof a feature edit, the geometry can be recovered by discarding the feature andreselecting it. [EAP-3653]

The APOLLO Web Client does not support custom Spatial Reference Systemsdefined using a Well Known Text description [EAP-3654]

Internationalization of the list of coordinate system entries is not currentlysupported in the CRS Chooser dialog. This will be implemented in a subsequentrelease. [EAP-3674]

If a map layer in the Web Client contains an SLD with a filter element, theproperty name of the filter may be dropped when the SLD is opened for editing.The user must reselect the property name before submitting a change or thelayer will not display. [EAP-3676]



If a WMS or WFS layer has only a default style (no named styles), it is notpossible to switch back to the default after creating a new style. Theworkaround is to delete the layer and re-add it. [EAP-3677]

SLD for SLD-capable services, other than ERDAS services, will be available ina later release. [EAP-3684]

When digitizing polygon features, outer rings are supposed to be counter-clockwise and inner rings are supposed to be clockwise by convention. The webclient allows you to digitize rings in either order, but if both inner and outer ringsare in the same order, the inner rings will not appear when the geometry isportrayed. To avoid this problem, make sure your inner and outer rings aredigitized in opposite directions. [EAP-3692]

The Feature properties that are edited using the ERDAS Web Toolkit areupdated in the navigation view but not on the Feature Summary. Refreshing thesearch results will display updated information. [EAP-3905]

The extents may never seem to change when a Tile Map Service (TMS) WebMap Context (WMC) is used as overview map. The workaround is to use WMSand WFS layer based WMC as an overview map instead of TMS based WMC.[EAP-3910]

In a French locale environment, saving & loading GoogleMapsbased contextswill not work. [EAP-3940]

The web client cancel map requests that are no longer needed (for exampleuser zooms in before all layer are loaded), this producesstacktraces in the logsadvertising a SocketException. This error message does not prevent thesoftware to run correctly and does not represent a specific software failure. Thismessage will disappear in a future release. [EAP-3950]

When legends are defined for several layers, the web client is likely to overlapthem. A workaround is to aggregate the layers inside a Context and define aContext provider. [EAP-3953]

Secure services are not supported when printing, yet. [EAP-3955] When uploading local imagery into the Web Client, only the GeoTIFF and the

GDAL decoders are likely to be used. The GIO decoders will not be invoked.[EAP-3981]

After creating a secure service (i.e. with user and password) in the DataManager, opening it in the Web Client without mentioning the user/passwordshould not add it at all in the browse tree. [EAP-3988]

Filters associated to WMS/WFS layers are not taken into consideration whenprinting. [EAP-3996]

With Internet Explorer 8, the geometry creation tool might not work as expectedand the digitized vertices might appear slightly off. This can be fixed bydisabling the Internet Explorer compatibility mode. [EAP-3997]

It is possible to configure APOLLO Essentials to run with no catalog service (viaa post-installation rebuild). When done, the Web Client still has a "Search"panel.A workaround is:

1) go to WEB-INF/classes/apollo-essentialscomponents. properties2) comment the line: components.active=Search3) restart the server [EAP-4033]

When reloading saved Filters, sometimes the Filtering buttons (Save, Load,Apply,...) will be greyout out under Internet Explorer 8. Selecting the layer againand rebuilding the filter will workaround the problem. [EAP-4450]

The APOLLO Web Client will fail to add an APOLLO Advantage ECW dataset ifthe spatial reference system information is not available in the ecw file. This canoccur with old ecw file generated with Imagine 9.3 versions where the spatialreference system information was written in a .aux file. A workaround is todelete the .aux file and use ERDAS IMAGINE to set projection again, so that itgets written to the .ecw file. [EAP-4474]

Secured ECWP layers from ERDAS APOLLO Essentials - IWS consumed viaECWP in APOLLO Web Client may not show on the map. The same layers willwork correctly if consumed as OGC WMS layer or ImageX layer. [EAP-4713]

Web Client hover over highlighting does not work as expected in GoogleChrome 6. It is fixed in later versions of Google Chrome. [EAP-5594]



Reprojection of data through the streaming protocols is supported only inECWP and not JPIP. In order to add an image using JPIP protocol, change theWeb Client Map SRS to the same SRS as the image. [EAP-5811]

When using Google Chrome to run the APOLLO Web Client, Adding a securedservice layer to the layer list, and clicking the layer configuration (Wrench)button, opens a broken configuration panel. [EAP-5875]

For ECWP or JPIP, opacity channel needs to be built using IMAGINE orERMapper software to remove null values around images. [EAP-5885]

In certain circumstances, when images from the catalog are downloaded as anERDAS IMAGINE Shoebox file, the server log may report errors during the flushoperation of the output. It is safe to ignore this error and it does not affect theIMAGINE Shoebox file output the client receives. [EAP-5994]

In the APOLLO Web Client, the GetInfo tool on vector data might take quite along time to return the results if one or more vector object has a huge geometry.They will be displayed only when all the vector data geometries is download bythe browser. A patch including a fix for this issue is scheduled shortly after therelease. [EAP-6228]

When you select ALG or ERS files and "Download Original File", the text file isdownloaded, not the image file(s) referenced in the ALG/ERS file. [EAP-6318]

When migrating from APOLLO 10.x to 11.0, the following issue might appear;Under certain circumstances, the Web Client Geoprocessing progress statusmight not get updated. This is a case when some old 10.x WPS jobs are stillregistered. Deleting the old jobs using the Data Manager should fix the problem.[EAP-6329]

In the APOLLO Web Client search panel, selecting the 'WCS layers' searchoption will return registered WCS service layers AND WCS enabled imagerydatasets. Selecting the 'WMS layers' search option will return registered WMSservice layers but not WMS enabled imagery datasets. This is not really anissue as imagery datasets are meant to be found using the 'Datasets' searchoption, but this inhomogeneous behavior will be fixed in a subsequent release.[EAP-6335]

In ERDAS APOLLO Web Client, secured WFS layers may request forcredentials for every layer when multiple layers are added from the service.Once the credentials are provided the WMS layer will display correctly. [EAP-6414]

Loading context files that contain secured WMS layers in certain browsers suchas Firefox and Chrome might show some errors. Please use Internet Explorer7.x or later versions if you encounter errors loading Web Map Context filescontaining secure layers in Firefox or Chrome. [EAP-6422]