内容来自:第一范文网 http://lanxicy.com
更多"FRAGSTATS 翻译"相关资料请点击这里
FRAGSTATS accepts raster images in a variety of formats, including
ArcGrid, ASCII, BINARY, ERDAS, and IDRISI image files. FRAGSTATS does
not accept Arc/Info vector coverages like the earlier version 2. All
input data formats have the following common requirements: ? All
input grids should be signed integer grids, ideally containing all
non-zero class values (i.e., each cell should be assigned an integer
value corresponding to its class membership or patch type). Note,
FRAGSTATS assumes that the grids are ‘signed’ integer grids;
inputting an ‘unsigned’ integer grid may cause problems. In
addition, note that assigning the zero value to a class is allowable,
but FRAGSTATS will reclassify all zero cell values to a new class
value equal to 1 plus the largest class value in the input landscape.
This procedure is necessary because a zero background class value may
cause problems in the moving window analysis because a background
value of zero in the output grid cannot be distinguished from a
computed metric value of zero. In addition, a zero class value may
cause problems when the landscape contains a border because zero
cannot be negative, yet all cells in the border must be negative
integers). Thus, all zero cells are assumed to be interior (i.e.,
inside the landscape of interest). For these reasons, it is simpler
to avoid the use of zero class values altogether.
FRAGSTATS 可以接受多种格式的遥感 影像,包括 ArcGrid , 二进, ERDAS 和
IDRISI 图像文件。 FRAGSTATS 不接受 阿 ARC/ INFO 矢量信息象早期的
version.2 版本的信息。 所有的输入数 据格式有下列的通常需求:
所有的输入单元格应该是带符号 的正方形栅格, 理论上包含所有的非 零类变
量。 (也就是,每个单元格应该 被分配完整的意义并符合到它的成员 身份或类
型) 注意,FRAGSTATS 假定单 元格是被分配的‘'完整的事物单元; 输 入‘没
标志'完整的事物单元可能引起问 题。 除此之外, 注意分配零值到一个 类是
可允许的,但是在输入地形图时, FRAGSTATS 将会所有的零单元格再分 类到
一个新的等于 1 的大类里面。 这一 个程序是必需的,因为零值的单元格在 输
出时不能和零值的背景单元格相区 别,还有在地形图中零单元格往往会引 起
一个问题就是地形图包括一个边界, 当零单元处在边界时不能被忽略。因
此,所有的零单元被假定是内部的。 (也就是,在重要风景里) 因为这些理 由,
避免零单元类的使用是比较简单 的。
? All input grids should consist of square cells with cell size
specified in meters. For certain input formats (ASCII and BINARY),
this is not an issue because cells are assumed to be square and you
are required to enter the cell size (in meters) in the graphical user
interface. However, FRAGSTATS assumes that all other image formats
(ArcGrid, ERDAS, and IDRISI) include header information that defines
cell size. Consequently these images must have a metric projection
(e.g., UTM) to ensure that cell size is given in metric units.
所有的输入单元格应该以米单位 表示的正方形的格子。 因为单元格是 被假定
是正方形的,在地形图中所有单 元都假定是方形的。(美国信息交换标 准代码
和二进) 。 然而, FRAGSTATS 假定所有的其他图像格式 (ArcGrid , ERDAS
和 IDRISI) 包括定义单元大小 的头文件数据。 结果这些图像一定是 以米为
单位的投影 (举例来说,UTM) 单元都是以米为单位的单元格。
There are some additional special 这里对输入数据格式还有一个额外的
considerations for each input data 空间标准为: format, as follows:
(1) Arc Grid created with Arc/Info. Note, to use Arc Grids you must
have ArcView Spatial Analyst or ArcGIS installed on your computer and
FRAGSTATS must have access to a certain .dll file found either in the
ArcView Bin32 directory (for ArcView Spatial Analyst users) or the
ArcGIS Bin directory (for ArcGIS users). Specifically, a path to the
corresponding dll library file should be specified in the
environmental settings under NT or Windows 2000 operating systems, or
a path statement included in the autoexec.bat file, e.g., under
Windows 98, as follows:
(1) 弧段单元格以弧/信息产生。 注 意, 使用弧段单元格你一定在你的计 算
机上安装 ArcView 空间的分析软件 或 ArcGIS ,而且 FRAGSTATS 有接口去
确定 ArcView Bin32 目录里的 *.Dll 文 件。 ( 为 ArcView 空间的分析使用
者) 或 ArcGIS 字典里.(对于 ArcGIS 使用者), 明确地, 在新 IT 或窗口
2000 操作系统中一条路径对应一个 dll 目 录文件或一份路径包含在
autoexec.bat 文件中,举例来说,在 98 系统下, 则:
Windows NT: You can add the necessary Path variable or edit the
existing one via the Control panel - System Properties - Environment
tab. Add a new variable or edit the existing Path variable in the
system variables, not the user variables (this will require
administrative privileges). Add the full path to the appropriate .dll
file. If you are using ArcView Spatial Analyst, the required file is
the avgridio.dll file and it is typically installed in the following
path: \esri\av_gis30\arcview\bin32. If you are using ArcGIS, the
required file is the aigridio.dll file and it is typically installed
in the following path: \esri\arcinfo\arcexe81\bin. Note, your
software version number and path may be different so be sure to
locate the .dll file on your computer and enter the correct path. If
you are using both Spatial Analyst and ArcGIS, then you can enter
either or both paths to the Path system variable.
Windows NT: 你能增加必需的路径变量 或者经编辑一个控制现有的嵌板环境
定位键。 在系统变量还不是使用者变 量中增加一个新的变量或编辑系统路 径
变量。 (这将会需要管理的特权) 增 加完整的路径到相应的*,dll 中。如果
你正在使用 ArcView 空间的分析软 件,必需的文件是 avgridio.dll 文 件,
而且它特别地安装在下面的路径 中: \esri\av_gis30\arcview\ bin32。 如果
你使用 ArcGIS,必需的文件是 aigridio.dll 文件,而且它安装在下 面路径中:
\esri\arcinfo\arcexe81\ bin。 注意, 你的软件版本数字和路径 可能是不同
的,以至于确定。在你的计 算机上的 dll 文件位于哪,而进入正 确的路径。
如果你正在使用空间的分 析系统和 ArcGIS, 然后你也能进入一 个或两个路径
到系统变量。
Windows 2000/XP: You can add the necessary Path variable or edit the
existing one via the Control panel - System Properties - Advanced tab
- Environment Variables button. Add a new variable or edit the
existing Path variable in the system variables, not the user
variables (this will require administrative privileges). Then,
following the instructions above for.
窗口 2000/XP:你能增加必需的路径变 量或者经编辑一个控制相应的系统嵌 板
环境定位键。 在系统变量中增加一 个新的变量或编辑一个退出的路径变 量而
不是用户变量。然后, 跟随依照上 面的 Windows NT 系统使用说明做。
Windows 95/98: You must add the necessary Path statement to the
autoexec.bat file. First, search your computer for the autoexec.bat
file and open it using any text editor. Then, either add a Path
statement or edit the existing one. Add the full path to the
appropriate .dll file. If you are using ArcView Spatial Analyst, the
required file is the avgridio.dll file and it is typically installed
in the following path: \esri\av_gis30\arcview\bin32. If you are using
ArcGIS, the required file is the aigridio.dll file and it is
typically installed in the following path: \esri\arcinfo\arcexe81\bin.
Thus, the path statement should look something like: PATH
c:\esri\av_gis30\arcview\bin32. Note, your software version number
and path may be different so be sure to locate the .dll file on your
computer and enter the correct path. If you are using both Spatial
Analyst and ArcGIS, then you can enter either or both paths to the
Path system variable. If you are adding the path to an existing path,
simple use a semicolon to separate the unique paths in the Path
statement. After saving the file you will need to reboot your machine
for the change to take effect.
窗口 95/98: 你必须增加这必要的路 径说明到 autoexec.bat 文件中。 首 先,
你的计算机上搜寻 autoexec.bat 文件和然后使用文本编辑器打开它。 然后,
或增加一份路径声明或编辑一 个现有的。 增加一个完整的路径到相 应的
*.dll 文件中。 如果你正在使用 ArcView 空间的分析软件,必需的文件 是
avgridio.dll 文件,而且它特别地 被安装在下列的路径中:
\esri\av_gis30\arcview\ bin32。 如 果你正在使用 ArcGIS,必需的文件是
aigridio.dll 文件,而且它特别地被 安装在下列的路径中:
\esri\arcinfo\arcexe81\ bin。 因此, 路径声明像: 路径 c:\
esri\av_gis30\arcview\bin32。 注 意, 你的软件版本数字和路径可能是 不
同的,确定位于那。在你的计算机上 必须确定 dll 文件而正确的路径和进 入
正确的路径。 如果你正在使用空间 的分析软件和 ArcGIS, 然后你也能进 入
一个或两个路径到系统路径变量。 如果你正在编辑这路径加入一条现有 的路
径, 简单的使用一个分号分开路 径说明中不一致的路径。 在保存文件 你将会
需要重新启动你的机器让变化 的文件有效。
(2) r. Each record should contain 1 image row. Cell values should be
separated by a comma or a space(s). Note, it will be necessary to
strip
(2) ASCII file, 不是头文件。每个记 录应当包含一个影像的一列或行。每个
单元变量应该头号或空格隔开。注意, 如果它存在, 有必要在影像的头文件
中删除它,但是后面涉及到背景单元变 (delete) the header information
from the image file if it exists, but 量应该为后面的这保存它,#排, 和
# 列。 be sure to keep it for later reference regarding background
cell value, # rows, and # columns.
(3) 32-bit binary file, no header; (3) 32 位二进制文件,没有头文件; 没
有其他的限制。 no other limitations.
(4) 16-bit binary file, no header. Patch ID output file, if selected,
will be output in signed 32-bit integer format to accommodate a
greater number of patches. In addition, because moving window
analysis requires floating points, if moving window analysis is
selected, the output grids produced will be 32-bit floating point
grids.
(4) 16-位二进位的文件, 没有头文件。 斑块地址输出文件,如果选择,将用 32
位二进制整型格式记录唯适应后面的 更大的斑块。除此之外,因为移动窗口
分析需要浮点类型的点,如果移动窗口 分析被选择,这些输出的输出单元格将
产生 32 位浮点格式的单元格。
(5) 8-bit binary file, no header. Patch ID output file, if selected,
will be output in signed 32-bit integer format to accommodate a
greater number of patches. In addition, because moving window
analysis requires floating points, if moving window analysis is
selected, the output grids produced will be 32-bit floating point
grids.
(5) 8-位二进位的文件, 没有头文件。 斑块地址输出文件,如果选择,将用 32
位二进制整型格式记录唯适应后面的 更大的斑块。除此之外,因为移动窗口
分析需要浮点类型的点,如果移动窗口 分析被选择,这些输出的输出单元格将
产生 32 位浮点格式的单元格。。
(5) ERDAS image files (.gis, .lan, and .img). FRAGSTATS accepts
images from both ERDAS 7 (.gis and .lan) and ERDAS 8 (.gis, .lan,
and .img), but the limitations are somewhat
(5) ERDAS 图像文件 (.gis,.lan, 和。 img). FRAGSTATS 接受来自两者的
ERDAS 7 的图像 (.gis 和。lan) 和 ERDAS 8(.gis,.lan, 和。img), 但是 限
制略微不同的, 依下列各项:
different, as follows:
ERDAS 8 Files.–FRAGSTATS accepts .gis, .lan, and .img files used by
current versions of ERDAS IMAGINE, including signed 8-, 16-, and 32-
bit integer grids. While .gis and .lan file formats are supported,
their limitations make them less practical than .img (see discussion
of ERDAS 7 files below). Care should be taken when preparing the data
to be used with FRAGSTATS, especially when importing data from other
formats (for instance from Arc Grid). Be sure to set the import
options to ‘signed integer’. Regardless of the input integer format
(8-, 16-, or 32-bit), the patch ID output file created by FRAGSTATS
will be a signed 32-bit integer, and if moving window analysis is
selected, all output grids will be 32-bit floating point. Multi-
layered files are not rejected, but only layer one is processed and
the outputs are all single layered. As noted above, cells must be
square, not rectangular, and the measurement unit should be meters.
If the measurement unit is not specified, then it is assumed to be
meters. The cell size and measurement unit specification can be
changed within ERDAS Imagine using the ImageInfo tool -> Change Map
Model from the Edit menu. The projection information existing in the
input file is passed unchanged to the output files. FRAGSTATS does
not use this information internally.
ERDAS 8 文件。FRAGSTATS 接受来自目 前 ERDAS 平台使用的.gis、.lan
和.img 文件。包括 8、16 和 32 进制格式的整 型单元格。 然而.gis 和.lan
文件 比.img 格式文件常用.(在下面见到 ERDAS 7 文件的讨论) 在使用
FRAGSTATS 软件时细心的准备数据是 必要的, 尤其当输入数据来自其他的 格
式数据的时候.( 举例来说 ARC 大院 格)。 确定将熟入的选项为“带符号整 型
数据“. 不管输入整型是 (8,16, 或 32 位)的数据 ,都将被 FRAGSTATS 软
件赋以地址和以 32 位二进制格式记录, 如果活动窗口被选中,所有输出数据
单 元格将以 32 位浮点型记录。多层数据不 被限制,但只有一层起作用,输出
的作 为一单层。如上方的说明,单元格必须 是正方形,不是矩形,而且量度单
位应 该是米。 如果度量单位未被指定,它被 假定是米。 单元格大小和度量单
位规 范可能被改变,其工具为 ERDAS 里面 的:ImageInfo 工具 ->改变来自
编辑 菜单的地图模型。 在输入输出文件中 存在的投影信息将不被改变,
FRAGSTATS 内部不使用这数据。
ERDAS 7 files.-- FRAGSTATS accepts .gis and .lan files used by ERDAS
7, which are limited to unsigned 8- or 16-bit integer grids.
FRAGSTATS will accept both 8-bit and 16-bit integer files and it will
reject multi-layered files. While .gis and .lan file formats are
supported, their limitations make them less practical than .img. In
particular, ERDAS 7.x files are limited to unsigned integers (i.e.,
only positive integers), therefore landscape borders (which require
negative class values) cannot be represented. Another consequence of
this particular limitation is that FRAGSTATS-generated patch ID files
will not fill the non-landscape cells (i.e., no data cells) with the
usual value (minus the background class value), but with zero values.
The restriction to 8- or 16-bit integers imposes some limitations
when using the FRAGSTATS on large grids. Specifically, unsigned 16-
bit integers can only take on values up to 65,534. Thus, class ID
values are limited to integers within this range (note, this should
not be a problem, since it is unlikely that anyone would have more
than 65,534 patch types). Similarly, patch ID values in the patch ID
output grid optionally produced by FRAGSTATS are limited to the same
range, effectively limiting the number of patches in this output grid
to 65,534. If the grid contains more than this number of patches,
FRAGSTATS will not be
ERDAS 7 文件。FRAGSTATS 接受来自目 前 ERDAS 平台使用的.gis、.lan 文
件。 它限制只使用 8、16 位二进制格式的整 型单元格。FRAGSTATS 将会接受
8、16 位整型文件数据,它不能应用于多层文 件。然而.gis 和.lan 文件是被
支持 的, 他们的限制使他们比.img 不经常 用。 尤其, ERDAS 7. x 文件被
限制 在无符号数据文件 (也就是, 只支持 正的整型数据), 因此地形图边缘
( 它要求有负类) 不能够被表示。这个 特别限制产生另一个结果是 FRAGSTATS
产生的地址文件将不将不 记录非地形数据 (也就是,没有数据单 元) ( 减少了
背景类的值), 但是由于 零值。 在 Fragstats 中使用大单元格时 严格的 8、
16 位整型的限制也增强了这 些限制。特别地, 负的 16 位整型数据 只能使用
最多到 65534。因此,类地址 也被限制在整型,(注意,这不应该是一 个问题,
因为它不太可能超过 65,534 类) 同样地,同样的斑块地址在被 Fragstats 输
出也受到选择性地限制, 有效的地址被限制在 65534 内,如果斑 块数超过这
个数,Fragstats 将不能输 出和斑块一致的地址,这样使用者不得 不去处分
使用同一地址的斑块。最后因 为活动窗口分析需要 32 位二进制文件 (为输出
浮点型点值),活动窗口不支 持 ERDAS 7 文件。
able to output a unique ID for each patch and the user will have to
somehow distinguish among patches with the same ID. Finally, because
the moving window analysis requires 32-bit output files (in order to
output floating point values), moving window analysis is not
supported with ERDAS 7 files.
(6) IDRISI image files (.rdc). IDRISI currently supports signed 8or
16-bit integers and 32-bit floating point grids. This imposes some
limitations when using the FRAGSTATS on large grids. Specifically,
signed 16-bit integers can only take on values between -32,768 and
32,767. Thus, class ID values are limited to integers within this
range (note, this should not be a problem, since it is unlikely that
anyone would have more than 32,767 patch types). Similarly, patch ID
values in the patch ID output grid optionally produced by FRAGSTATS
are limited to the same range, effectively limiting the number of
patches in this output grid to 37,767. If the grid contains more than
this number of patches, FRAGSTATS will not be able to output a unique
ID for each patch and the user will have to somehow distinguish among
patches with the same ID. Fortunately, IDRISI supports 32-bit
floating point grids, which are produced in a moving window analysis.
(6) IDRISI 图像文件 (.rdc). IDRISI 目前支援 8 或 16 位整型和 32 位浮点
型 单元格。 当产生限制 Fragstats 使用大 单元格数据。特别是带符号的 16
位整型 数据仅仅只能表示-32768 到 32767 之间 的值。这样斑块的地址可能被
限制在这 个整数范围内,(注意,这不应该是一个 问题,因为它不太可能超过
32,767 个 类)。 同样地,同样的斑块地址在被 Fragstats 输出也受到选择性
地限制, 有效的地址被限制在 32767 内,如果斑 块数超过这个数,Fragstats
将不能输 出和斑块一致的地址,这样使用者不得 不去处分使用同一地址的斑
块。最后因 为 IDRISI 支持 32 位浮点型网格数据,它 将产生一个活动窗口分
析。
Computer Requirements
FRAGSTATS version 3 is a stand-alone program written in Microsoft
Visual C++ for use in the Windows operating environment. FRAGSTATS
was developed and tested on the Windows NT and 2000 operating systems,
although it should run under all Windows operating systems. Note,
FRAGSTATS is highly platform dependent, as it was developed in the
Microscroft environment, so portability to other platforms is not
easily accomplished. FRAGSTATS is a compute-intensive program; its
performance is dependent on both processor speed and computer memory
(RAM). Ultimately, the ability to process an image is dependent on
the availability of sufficient memory, the speed of processing that
image is dependent on processor speed. Of particular note is the
memory constraint. FRAGSTATS loads the input grid into memory and
then computes all requested calculations. Thus, you must have
sufficient memory to load the grid and then enough leftover for
processing and other operating system needs. To determine whether you
have sufficient memory to load a particular grid, you can use the
following formula: #cells*4bytes. Thus, if you have a 256 rows by 256
columns grid, the memory requirement to simply load the grid is 256
kb (256*256*4/1024 bytes/kb). Plus you need sufficient memory to
process the grid, and this requirement depends on the number of
patches and classes. These memory requirement are not particularly
constraining in a standard analysis, unless you are working with huge
images on an older computer. The solution to this problem if it
arises–unfortunately–is to
计算机需求 FRAGSTATS 3 版本软件是一个在 Windows 平台下用 Microsoft
Visual C++ 编写的独立程序。 FRAGSTATS 的测试 是在 Windows NT 和 2000
操作系统下 进行的,虽然它在 Windows 操作系统下 运行。 注意,FRAGSTATS 需
要高平台支 持, 象它在 Microscroft 环境下发展一样, 以致于其他的平台很
难使用, FRAGSTATS 是内部计算程序,它的计算 效率。最后,处理一个图像
的能力依赖 充份记忆的限制,图像处理的速度依赖 处理器速度。特别注意的
是内存限制。 Fragstats 导入栅格数据岛内存时计算 机要求所有的都被计
算,这样,你必须 有足够的内存去导入栅格数据然后留 足够空间去处理分
析。决定拟是否有足 够的内存是导入什么栅格数据,你可以 通过下面公式计
算需要的空间,这样如 果你是输入 256 行乘 256 列的数据则导 入要求
256*256*4 个字节的内存加上必 要的过程运算容量,这要求应当根据所 分的
类多少而定。这些分析中的标准要 求不是很严格,你在旧的电脑上运行大 的
影像。这些问题的解决方法是买台新 的配置高的电脑。在运行窗口时对内存
的限制是非常严格的,因为 FRAGSTATS 要求足够的内存去输入输出影像,加上
运行需要的空闲内存。如果活动窗口被 选上则,FRAGSTATS 将核对是否有足够
的内存进行影像(也就是运算、输入输 出)在上面分析可知你将需要最低 768
千兆的内存,在分析小的地形图时对大 多计算机没有太多的限制,然而在运行
10000*10000 的影像时,一般需要 1.14Gb 的内存
get a new machine with as much memory as possible. The memory
requirement, however, is very constraining in the moving window
analysis because FRAGSTATS requires enough memory for the input grid
plus one output grid, plus enough leftover for other processing needs
and system needs. If the moving window analysis is selected,
FRAGSTATS checks to see if it can allocate enough memory for three
grids (i.e., 1 input grid + 1 output grid + enough leftover to insure
performance). In the above example, you would need at least 768 kb of