|
|
||
|
|
Valid WHERE clauses for whereClause parameter in SpatialQueryOptions
Example:
City='Murrieta'
Result: Locations in Murrieta
AND
finds records that meet both criteria.
Example: Type='Amusement Parks' AND State='CA'
Result: Amusement parks in California
OR finds records that meet one or both criteria.
Example: Type='Amusement Parks' OR State='CA'
Result: Amusement Parks located
anywhere and all places within California
>
is strictly greater than
Example: Name>'D'
Result: Names beginning D–Z
and characters such as ~ and -
<= is less than or equal to
Example: Zone<='60000'
Result: Zones 60000 and smaller
<> is not equal to
Example: State<>'CA'
Result: All states that are not California
BETWEEN
tests whether a value is between two other values.
Example: City BETWEEN 'E' AND 'L'
Result: Cities such as Fedora that fall between E and L alphabetically
IN tests whether a value is in a list of possible values.
Example: Type IN ('red', 'blue', 'green')
Result: All types are that red, blue, or green
_
tests for exactly one wild card character.
Example: State LIKE 'W_'
Result: States that begin with W such as Washington (WA), West Virginia
(WV), Wisconsin (WI), and Wyoming (WY)
% tests for zero to multiple wild cards.
Example: City LIKE '%ing'
Result: Cities that end in "ing" such as Redding
Use the method findFeaturesByPoint when your input search geometry is a point or circle. Create a circle by applying a spatial buffer to the input search point. When your input is a circle, any features in the data source that intersect the circle are returned. When your input is a point, the nearest features from your data source are returned.
Use the method findFeaturesByGeometry when your input search geometry is a polygon, polyline, or multipoint. With this method, any features in the data source that intersect the input search geometry are returned. Note that you can apply spatial buffers to any type of input search geometry. Use Utility Web Service to convert various shapes to Geometry objects. See Utility Web Service methods for details.
ResultSet does not always return fields in same order
Be aware that fields returned by object ResultSet might be returned in a different order than expected. There is no guarantee that the field order will be consistent with each response.
Data from ArcWeb:InfoUSA.BusinessListings*.US must be presented to end users in specific ways. See Using infoUSA data for details.
Finding detailed business listings
The data source ArcWeb:InfoUSA.BusinessListings.US contains the name, address, city, state, NAICS code, SIC code, and unique ID of registered businesses. It supports up to 20 results from one request and is intended for proximity and area searches.
The data source ArcWeb:InfoUSA.BusinessListingsDetails.US contains the ZIP Code, phone number, and unique ID of registered businesses. It supports one result per request and is intended for querying a specific business listing.
These two data sources work in conjunction with one another. Locate businesses through proximity and area searches using the data source ArcWeb:InfoUSA.BusinessListings.US. Once you have the unique ID of a business, use the data source ArcWeb:InfoUSA.BusinessListingsDetails.US to see detailed listings about this specific business.
You can query for elevations using the methods findFeaturesByPoint or findFeaturesbyGeometry with the data source ArcWeb:USGS.Elevation.US. The method findFeaturesByPoint returns the elevation of a point. The method findFeaturesbyGeometry returns the elevations of the points that make up a geometry. For up to 20 points, if you don't specify the number of points to return, the same number you input is returned. If you want more than 20 points, you need to specify the number in your request (specify the number through the object parameter SearchOptions.resultSetRange). You are charged in groups of 20 points. Note that elevation data does not support spatial buffers or the method findFeaturesByExtent.
For information on spatial query codes, see Spatial Query codes.
Visit the Feedback page to give comments or suggestions about the ArcWeb Developer's Guide.