root/MGET/Branches/Jason/PythonPackage/dist/TracOnlineDocumentation/Documentation/ArcGISReference/RExploratoryPlots.DensityHistogramForArcGISPointsCoordinates.html @ 376

Revision 376, 12.2 KB (checked in by jjr8, 4 years ago)

Fixed/implemented:

* #332: SIR file conversion tools should use WGS-72 datum for Lambert projections, and NSIDC's datum for polar stereographic projections
* Bugs in the previous revision related to pre-install scripts.

If this passes additional testing, it will be merged with the Trunk and released as MGET 0.7a12.
Line 
1<?xml version="1.0" encoding="utf-8"?>
2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml"><head><link rel="stylesheet" type="text/css" href="81help.css?format=raw" /><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Density Histogram for Point Coordinate</title></head><body><table style="margin-top:-1em; margin-bottom:0; padding:0; margin-left:-1em"><tr><td style="background:white"><img width="875" height="70" alt="ArcToolbox banner" src="AHBanner_ArcToolbox.gif?format=raw" /></td></tr></table><h1>Density Histogram for Point Coordinate</h1><p></p><p>Creates a density histogram for one of the coordinates of an ArcGIS point feature class or layer.</p><br /><p><h2><img width="11" height="11" border="0" src="sm_arrow_down.gif?format=raw" /> Command line syntax</h2></p><div Class="expand" id="id103150">RExploratoryPlotsDensityHistogramForArcGISPointsCoordinates_GeoEco &lt;pointFeatures&gt; &lt;x | y | z | m&gt; {coordinateName} {transform} {categoryField} {where} {bottom | bottomleft | bottomright | center | left | right | top | topleft | topright} {outputFile} {width} {height} {pointSize} {bg} <br /><br /><b>Parameters</b><br /><table width="100%" border="0" cellpadding="5"><tbody><tr><th width="40%"><b>Expression</b></th><th width="60%"><b>Explanation</b></th></tr><tr><td class="info">&lt;pointFeatures&gt;</td><td class="info" align="left"><p>ArcGIS point feature class or layer for which the plot should be
4generated.</p></td></tr><tr><td class="info">&lt;x | y | z | m&gt;</td><td class="info" align="left"><p>Point coordinate for which a density histogram should be plotted:</p><ul><li><p>x - the x coordinate</p></li></ul><ul><li><p>y - the y coordinate</p></li></ul><ul><li><p>z - the z coordinate</p></li></ul><ul><li><p>m - the measure value</p></li></ul><p>An error will be reported if you specify z or m and the point features
5do not have z coordinates or measure values.</p></td></tr><tr><td class="info">{coordinateName}</td><td class="info" align="left"><p>Name to display for the coordinate (e.g. "Longitude"). If you do
6not specify a name, "x", "y", "z", or "m" will be used.</p></td></tr><tr><td class="info">{transform}</td><td class="info" align="left"><p>Transformation to perform before plotting the density histogram.</p><p>Use this parameter when the distribution of the original data is too
7skewed to yield an informative plot. This parameter must be an R
8expression that operates on the vector d that represents the original
9values. For example, the following expressions perform natural
10logarithm, base 10 logarithm, square root, and cube root transforms,
11respectively:</p><dl><dt></dt><dd><pre>log(d)
12log10(d)
13d^(1/2)
14d^(1/3)</pre></dd></dl><p>The expression may be as complicated as you want, so long as it
15conforms to R syntax, operates only on the variable d, and yields a
16vector of the same length as the input data. For example, if the input
17data represent water depth expressed as a negative number (e.g. -100
18is 100 meters below the surface), and you want to transform the data
19using a base 10 logarithm, you must first take the absolute value of
20depth:</p><dl><dt></dt><dd><pre>log10(abs(d))</pre></dd></dl></td></tr><tr><td class="info">{categoryField}</td><td class="info" align="left"><p>Field specifying categories for the data.</p><p>A separate histogram line will be plotted for each category, allowing
21you to compare the distribution of data between categories. For
22example, in an ecology study, if you wanted to compare the
23distribution at locations where a species was present to locations
24where it was absent, you could specify the "IsPresent" field as the
25category field (1 = species present, 0 = species absent).</p><p>The field must have the data type SHORT, LONG, FLOAT, DOUBLE, TEXT, or
26DATE. Rows with NULL values for this field will not be included in the
27histogram.</p><p>A maximum of six categories is allowed. If this field contains more
28than six unique values, an error will be reported. You can reduce the
29number of categories by specifying a Where Clause that restricts the
30rows that are processed to those having the six or fewer category
31values you are most interested in.</p></td></tr><tr><td class="info">{where}</td><td class="info" align="left"><p>SQL WHERE clause expression that specifies the subset of rows to
32process. If this parameter is not provided, all of the rows will be
33processed. If this parameter is provided but the underlying database
34does not support WHERE clauses, an error will be raised.</p><p>The exact syntax of this expression depends on the underlying
35database. ESRI recommends you reference fields using the following
36syntax:</p><ul><li><p>If you're querying ArcInfo coverages, shapefiles, INFO tables or
37dBASE tables (.dbf files), enclose field names in double quotes in
38the SQL expression: "MY_FIELD".</p></li></ul><ul><li><p>If you're querying Microsoft Access tables or personal
39geodatabase tables, enclose field names in square brackets:
40[MY_FIELD].</p></li></ul><ul><li><p>If you're querying ArcSDE geodatabase tables, an ArcIMS feature
41class, or an ArcIMS image service sublayer, don't enclose field
42names: MY_FIELD.</p></li></ul></td></tr><tr><td class="info">{bottom | bottomleft | bottomright | center | left | right | top | topleft | topright}</td><td class="info" align="left"><p>Position of the plot's legend. If this parameter is omitted, no
43legend will be drawn.</p></td></tr><tr><td class="info">{outputFile}</td><td class="info" align="left"><p>Portable Network Graphics (PNG) file to create for the plot. It is
44suggested that you name your output file with a .png extension, so it
45can be displayed properly by other programs.</p><p>If you specify an output file, it will be written using R's png
46graphics device. An interactive window will not be displayed on the
47screen.</p></td></tr><tr><td class="info">{width}</td><td class="info" align="left"><p>Width of the output PNG file, in pixels.</p></td></tr><tr><td class="info">{height}</td><td class="info" align="left"><p>Height of the output PNG file, in pixels.</p></td></tr><tr><td class="info">{pointSize}</td><td class="info" align="left"><p>The default pointsize of text in the output PNG file, interpreted
48at 72 dpi, so one point is approximately one pixel.</p></td></tr><tr><td class="info">{bg}</td><td class="info" align="left"><p>Background color for the output PNG file. The color must be a
49valid name in R's color palette, or "transparent" if there is no
50background color.</p></td></tr></tbody></table></div><p><h2><img width="11" height="11" border="0" src="sm_arrow_down.gif?format=raw" /> Scripting syntax</h2></p><div Class="expand" id="TEST">RExploratoryPlotsDensityHistogramForArcGISPointsCoordinates_GeoEco (pointFeatures, coordinate, coordinateName, transform, categoryField, where, legend, outputFile, width, height, pointSize, bg) <br /><br /><b>Parameters</b><br /><table width="100%" border="0" cellpadding="5"><tbody><tr><th width="40%"><b>Expression</b></th><th width="60%"><b>Explanation</b></th></tr><tr><td class="info">Point features (Required) </td><td class="info" align="left"><p>ArcGIS point feature class or layer for which the plot should be
51generated.</p></td></tr><tr><td class="info">Coordinate to plot (Required) </td><td class="info" align="left"><p>Point coordinate for which a density histogram should be plotted:</p><ul><li><p>x - the x coordinate</p></li></ul><ul><li><p>y - the y coordinate</p></li></ul><ul><li><p>z - the z coordinate</p></li></ul><ul><li><p>m - the measure value</p></li></ul><p>An error will be reported if you specify z or m and the point features
52do not have z coordinates or measure values.</p></td></tr><tr><td class="info">Name to display for the coordinate (Optional) </td><td class="info" align="left"><p>Name to display for the coordinate (e.g. "Longitude"). If you do
53not specify a name, "x", "y", "z", or "m" will be used.</p></td></tr><tr><td class="info">Transform (Optional) </td><td class="info" align="left"><p>Transformation to perform before plotting the density histogram.</p><p>Use this parameter when the distribution of the original data is too
54skewed to yield an informative plot. This parameter must be an R
55expression that operates on the vector d that represents the original
56values. For example, the following expressions perform natural
57logarithm, base 10 logarithm, square root, and cube root transforms,
58respectively:</p><dl><dt></dt><dd><pre>log(d)
59log10(d)
60d^(1/2)
61d^(1/3)</pre></dd></dl><p>The expression may be as complicated as you want, so long as it
62conforms to R syntax, operates only on the variable d, and yields a
63vector of the same length as the input data. For example, if the input
64data represent water depth expressed as a negative number (e.g. -100
65is 100 meters below the surface), and you want to transform the data
66using a base 10 logarithm, you must first take the absolute value of
67depth:</p><dl><dt></dt><dd><pre>log10(abs(d))</pre></dd></dl></td></tr><tr><td class="info">Category field (Optional) </td><td class="info" align="left"><p>Field specifying categories for the data.</p><p>A separate histogram line will be plotted for each category, allowing
68you to compare the distribution of data between categories. For
69example, in an ecology study, if you wanted to compare the
70distribution at locations where a species was present to locations
71where it was absent, you could specify the "IsPresent" field as the
72category field (1 = species present, 0 = species absent).</p><p>The field must have the data type SHORT, LONG, FLOAT, DOUBLE, TEXT, or
73DATE. Rows with NULL values for this field will not be included in the
74histogram.</p><p>A maximum of six categories is allowed. If this field contains more
75than six unique values, an error will be reported. You can reduce the
76number of categories by specifying a Where Clause that restricts the
77rows that are processed to those having the six or fewer category
78values you are most interested in.</p></td></tr><tr><td class="info">Where clause (Optional) </td><td class="info" align="left"><p>SQL WHERE clause expression that specifies the subset of rows to
79process. If this parameter is not provided, all of the rows will be
80processed. If this parameter is provided but the underlying database
81does not support WHERE clauses, an error will be raised.</p><p>The exact syntax of this expression depends on the underlying
82database. ESRI recommends you reference fields using the following
83syntax:</p><ul><li><p>If you're querying ArcInfo coverages, shapefiles, INFO tables or
84dBASE tables (.dbf files), enclose field names in double quotes in
85the SQL expression: "MY_FIELD".</p></li></ul><ul><li><p>If you're querying Microsoft Access tables or personal
86geodatabase tables, enclose field names in square brackets:
87[MY_FIELD].</p></li></ul><ul><li><p>If you're querying ArcSDE geodatabase tables, an ArcIMS feature
88class, or an ArcIMS image service sublayer, don't enclose field
89names: MY_FIELD.</p></li></ul></td></tr><tr><td class="info">Legend (Optional) </td><td class="info" align="left"><p>Position of the plot's legend. If this parameter is omitted, no
90legend will be drawn.</p></td></tr><tr><td class="info">Output PNG file (Optional) </td><td class="info" align="left"><p>Portable Network Graphics (PNG) file to create for the plot. It is
91suggested that you name your output file with a .png extension, so it
92can be displayed properly by other programs.</p><p>If you specify an output file, it will be written using R's png
93graphics device. An interactive window will not be displayed on the
94screen.</p></td></tr><tr><td class="info">Plot width (Optional) </td><td class="info" align="left"><p>Width of the output PNG file, in pixels.</p></td></tr><tr><td class="info">Plot height (Optional) </td><td class="info" align="left"><p>Height of the output PNG file, in pixels.</p></td></tr><tr><td class="info">Default pointsize of plotted text (Optional) </td><td class="info" align="left"><p>The default pointsize of text in the output PNG file, interpreted
95at 72 dpi, so one point is approximately one pixel.</p></td></tr><tr><td class="info">Plot background color (Optional) </td><td class="info" align="left"><p>Background color for the output PNG file. The color must be a
96valid name in R's color palette, or "transparent" if there is no
97background color.</p></td></tr></tbody></table></div></body></html>
Note: See TracBrowser for help on using the browser.