Last Updated: January 26, 2012

Pictometry Online Image Portal Topics

About Pictometry International
What Is The Pictometry Online Image Portal?
Product Offerings
Portal Request Types
Transaction Security And Accounting
Status And Error Reporting
Portal Address and Required Parameters
Location Search Using Decimal Degrees
Location Search Using Decimal Minutes
Location Search Using Degrees/Minutes/Seconds
Location Search Using UTM
Location Search Using State Plane
Address Search
Coverage Search
Optional Search Modifiers
Appendix A: HTTP Status Codes Table
Appendix B: Location/Address Search Results In XML
Appendix C: Inventory Search Results In XML
Appendix D: Coverage Search Results In XML
Appendix E: Optional Image URL Modifiers
Glossary
Search Demonstrations

About Pictometry International
Our product offering is comprised of two elements: images and software. Our patented imaging process captures high-resolution oblique (at an angle) and orthogonal (straight down) images of counties and/or states, and combines them with an interactive software solution that lets users see everywhere, measure anything, and plan everything. Our customer base includes a growing list of county, state, and federal government organizations as well as private business users. Applications include law enforcement, 9-1-1, homeland security, fire departments, architectural and engineering firms, assessors, planning agencies, transportation departments, insurance, real estate, and utility companies.

Pictometry offers a significant advantage compared to traditional overhead photography by taking previously complex technologies (such as photogrammetry, geographic projections, and coordinate systems, aerial imaging and mapping systems, and image storage and retrieval), adding a wealth of new features (such as georeferenced oblique images and walk-the-earth measurements), and then making it affordable and easy-to-use. The result is a revolutionary way to use aerial imaging that was unheard of just a few years ago.

Back to top of page


What Is The Pictometry Online Image Portal?
The Pictometry Online Image Portal is a secure, transaction-based web application that provides a simple, URL-based API to our image database. A search is initiated over a Secure Socket Layer (SSL) to the search engine with the request encoded in the URL. The URL request can be made using either the GET or POST method. The result of a search is an XML document that describes the image set.

Back to top of page


Product Offerings
The Portal Image product allows flexibility in requesting the type and orientation of the images.

The Image product returns an XML document that describes the image set. The document provides metadata and includes a set of specially encoded URL's that can be used to retrieve the images. See Appendix B for details. Up to 4 types of images can be requested in any combination:

  1. Thumbnail - A small version of the image that is used to give the viewer an idea of what the full-sized imaged is like. These are typically used to create clickable images on a web page.
  2. Clip - A full resolution image that is clipped from the source image.
  3. Preview - The entire source image reduced by a scaling factor. This is similar to a thumbnail but in greater detail. This can be used to determine if the required features are contained within the image.
  4. Full Image - The entire source image in full resolution.

The returned Clip images are all centered on the requested search location. Each returned image has a default width/height of 400 x 400 pixels. Larger clips can be requested but are ultimately limited to the size of the source image.

Important: The Portal attempts to return a Clip with as much of the image as has been requested. However, in cases where the request goes beyond the bounds of the source image, the Portal resizes the request to return as much as possible while still keeping the search point in the center of the Clip.

The Portal also provides 2 pure data product offerings. These data products return XML data describing the requested images. These data offerings are:

The Inventory product returns an XML document that describes, for the given location, all available years, shot levels and views. This is useful in determining overall availability. There are cases where it may be necessary to load images from multiple years in order to get the desired orientations or shot levels. A full description can be found in Appendix C.

The Coverage product returns an XML document that contains the geographical bounding boxes for every region and area that our database covers. The default is to return all regions and areas. An optional region code can be supplied to return only those areas contained within the specified region. The Portal currently supports the two-letter postal abbreviations for U.S. states as region codes. A full description can be found in Appendix D.

Billable Transactions
Charges are assessed when a Clip or Full Image is rendered via a URL from the XML document. Currently, Thumbnail and Preview image transactions are not charged and are provided as a convenience.

Back to top of page


Portal Request Types
The Portal has 3 request types, Location, Address and Region. The Location type requires a coordinate specified in any one of three different projections:

Coordinates given in Lat/Lon can be specified in three different formats:

In addition, Lat/Lon and UTM coordinates can be given in WGS84 or NAD27 datums.

Address searches can be made to the Portal with the caveat that the resulting returned location may not fall precisely on the requested address. The results may vary depending on the geocoding engine that is used to translate the address to a location.

The Portal supports two geocoders:

To help users determine the quality of the geocode, the Portal returns a precision attribute in the XML document for all address searches.

The precision values are:

NOTE: There is no guarantee that a parcel precision geocode will fall precisely on the house or building at the requested address. These geocodes are bound to the parcel centroid which may or may not be where the structure is situated.

Region searches are limited to the Coverage product.

Back to top of page


Transaction Security And Accounting
Access to the Portal is over a Secure Socket Layer (SSL) connection so that the user's credentials are protected. Requests made on any other port are rejected. Only authorized users with proper credentials can access the service. Each transaction is logged in our database so that accurate usage statistics can be kept.

Back to top of page


Status And Error Reporting
By default, all status and error events are reported to the requestor via an HTTP status code. The status codes and reason phrases supported by the Portal are listed in Appendix A. This behavior can be overridden by the os option to report errors in plain text. See: Optional Search Modifiers

Back to top of page


Portal Address and Required Parameters
The web address used to access the Portal is: https://pol.pictometry.com/ImagePortal/search/. There are 4 parameters that must accompany every request to the Portal. The table below summarizes these parameters:

Parameter Name Description Case Sensitive
product Must be set to either Image, Inventory, or Coverage,. No
type Must be set to either Location, Address or Region. No
uid User login id. Yes
pw User password. Yes

Back to top of page


Location Search Using Decimal Degrees
The table below summarizes the parameters:

Parameter Name Description (R) - Required, (O) - Optional. All values are case insensitive.
proj (R) - Projection of the coordinates. Must be set to LatLong.
format (R) - Format of the coordinates. Must be set to DD.
lat (R) - The latitude in decimal degrees of the location. The coordinate should be in the form (43.003156). Northern hemisphere is positive. Southern hemisphere is negative.
lng (R) - The longitude in decimal degrees of the location. The coordinate should be in the form (-77.615908). Eastern hemisphere is positive. Western hemisphere is negative.
datum (O) - Datum of the coordinates. WGS84 and NAD27 are supported. Default is WGS84.

An example URL for a location search in decimal degrees (DD) would look like this:

Back to top of page


Location Search Using Decimal Minutes
The table below summarizes the parameters:

Parameter Name Description (R) - Required, (O) - Optional. All values are case insensitive.
proj (R) - Projection of the coordinates. Must be set to LatLong.
format (R) - Format of the coordinates. Must be set to DM.
lat (R) - The latitude in decimal minutes of the location. The coordinate should be in the form (43 11.1456) with the degrees separated from the minutes by whitespace. Northern hemisphere is positive. Southern hemisphere is negative.
lng (R) - The longitude in decimal minutes of the location. The coordinate should be in the form (-77 36.9545) with the degrees separated from the minutes by whitespace. Eastern hemisphere is positive. Western hemisphere is negative.
datum (O) - Datum of the coordinates. WGS84 and NAD27 are supported. Default is WGS84.

An example URL for a location search in decimal minutes (DM) would look like this:

Back to top of page


Location Search Using Degrees/Minutes/Seconds
The table below summarizes the parameters:

Parameter Name Description (R) - Required, (O) - Optional. All values are case insensitive.
proj (R) - Projection of the coordinates. Must be set to LatLong.
format (R) - Format of the coordinates. Must be set to DMS.
lat (R) - The latitude in degrees/minutes/seconds of the location. The coordinate should be in the form (43 11 8.74) with the degrees, minutes and seconds separated by whitespace. Northern hemisphere is positive. Southern hemisphere is negative.
lng (R) - The longitude in degrees/minutes/seconds of the location. The coordinate should be in the form (-77 36 57.27) with the degrees, minutes and seconds separated by whitespace. Eastern hemisphere is positive. Western hemisphere is negative.
datum (O) - Datum of the coordinates. WGS84 and NAD27 are supported. Default is WGS84.

An example URL for a location search in degrees/minutes/seconds (DMS) would look like this:

Back to top of page


Location Search Using UTM
The table below summarizes the parameters:

Parameter Name Description (R) - Required, (O) - Optional. All values are case insensitive.
proj (R) - Projection of the coordinates. Must be set to UTM.
zone (R) - The UTM zone of the location.
easting (R) - The UTM easting of the location.
northing (R) - The UTM northing of the location.
hemi (O) - Hemisphere of the coordinates. N = Northern Hemisphere, S = Southern Hemisphere. Default is N.
datum (O) - Datum of the coordinates. WGS84 and NAD27 are supported. Default is WGS84.

An example URL for a location search in UTM would look like this:

Back to top of page


Location Search Using State Plane
The table below summarizes the parameters:

Parameter Name Description (R) - Required, (O) - Optional. All values are case insensitive.
proj (R) - Projection of the coordinates. Must be set to SPCS.
zone (R) - The State Plane zone of the location.
units (R) - The State Plane units of the location.
easting (R) - The State Plane easting of the location.
northing (R) - The State Plane northing of the location.
datum (O) - Datum of the coordinates. WGS84 and NAD27 are supported. Default is WGS84.

An example URL for a location search in State Plane would look like this:

Back to top of page


Address Search
The table below summarizes the parameters:

Parameter Name Description (R) - Required, (O) - Optional. All values are case insensitive.
address (R) - The street address of the location.
city (R) - The city of the location.
sc (R) - The state code. Two-letter postal abbreviation of the state.
zip (O) - The zip code (if known). A 9-digit zip may help increase accuracy.

An example URL for an address search product would look like this:

Back to top of page


Coverage Search
The table below summarizes the parameters:

Parameter Name Description (R) - Required, (O) - Optional. All values are case insensitive. Values
rc (O) - The region code. The Portal currently supports the two-letter postal abbreviation for U.S. states. Default is ALL.

An example URL for a coverage search in New York (NY) would look like this:

If no rc parameter is given, the default behavior is to generate coverage for all regions and areas. An example of the coverage XML output can be found in Appendix D.

Back to top of page


Optional Search Modifiers
The following modifiers can be used in Location and Address searches to override default behavior.

The optional search modifiers provide flexibility in tailoring searches. This section discusses theses options. The table below summarizes the options:

Parameter Description - All values are case insensitive Values
sl Shot Level. Neighborhood Priority, Community Priority, Neighborhood, or Community. Default is Neighborhood Priority. Np, Cp, N, C
st Shot Type. Oblique, Orthogonal or Combined. Default is Oblique. Ob, Or or Cb.
sh Shot Heading. Orientation of Oblique images. Default is North, East, South, and West. Any combination of: N, E, S, W.
sy Shot Year. Limits search to the most recent images available (M) or the least recent images (L) or limit the search to a specific 4-digit year. Default is Most Recent Images (M) M - Most Recent Images. L - Least Recent Images. A year between 2000 - 2012
yl Shot Year Limit. When the sy option is set to (M), this option limits returned images to those where the capture year is greater than or equal to the limit year. When the sy option is set to (L), this option limits returned images to those where the capture year is less than or equal to the limit year. This option has no effect if a year is specified in the sy option. Default is No Limit A year between 2000 - 2012
sb See Score Bias for details. Default is Oblique. 0 - Oblique, 1 - Center
it Image Type. This option determines the URL's that are returned in the XML document. See Appendix B for details. T - Thumbnail
C - Clip
P - Preview
F - Full Image

Any combination of these values.
wh Individual Clip image width in specified units. Default is 400 pixels. Minimum computed pixels: 200
Maximum computed pixels:
No larger than source image width
ht Individual Clip image height in specified units. Default is 400 pixels. Minimum computed pixels: 200
Maximum computed pixels:
No larger than source image height
un Units of the width and height parameters. Default is pixels. px - Pixels ft - Feet m - Meters
fc Fill Color. Color used to fill a clip image. Default is black (000000). Any valid HTML color code.
tc Text Color. Color used to render text. Default is yellow (ffff00). Any valid HTML color code.
qs JPEG Quality Setting. Default is 80. 0 - 100
ch Draw a crosshair on the search point. Default is 0. 0 - No Draw, 1 - Draw
np Draw the north pointer. Default is 0. 0 - No Draw, 1 - Draw
ds Add the datestamp to the image in DD/MM/YYYY format. This is the date the image was captured. Default is 0. 0 - No Draw, 1 - Draw
fs Fixed size for clips . By default, the Portal attempts to return a clip sized to the wh and ht fields. However, in cases where the request goes beyond the bounds of the source image, the Portal resizes the request to return as much as possible while still keeping the search point in the center of the clip.

Setting the fs field to 1 causes the portal to honor the wh and ht fields explicitly, even if this produces empty space at the edges of the image. This ensures that all generated clips are the same size.

0 - Clip is scaled to fit.
1 - Clip size fixed by wh and ht parameters
of Output Format. This option determines the type of image format that the URL's generate. Default is 0 0 - JPEG
1 - GIF
2 - PNG
os Output Status. By default, error results are returned as HTTP status codes. Errors can be returned as plain text by setting this option to 1 or as XML by setting this option to 2. 0 - HTTP Status, 1 - Plain Text Status, 2 - XML
fe See Features below for details. Default (not set or empty) is no request. Empty for no request, JSON encoded string to request. See Features below.
sm Shot Month: Restricts result set to only those images taken during the month(s) specified. Months are represented as 1 (January) to 12 (December). Enter one number to return only that month, enter range for all months specified, inclusive. 3-10 for March through October Inclusive. Leave empty for no restriction. Empty for no restriction

One month number for one month
(ex: sm=3 for March)

Month range for a range
(ex: sm=3-10 for March through October)

Search Results
The search results are returned as an XML document that, in addition to metadata, contains a set of URL's that are used to retrieve the images. See Appendix B for details on the format of this document. The type of URL's returned are determined by the values in the it (Image Type) option. These URL's have the following characteristics and limitations:

IMPORTANT: The image URL is meant only to retrieve the image. It is not meant to be used as a permanent link in other webpages. Every image URL fetch is counted as a transaction. We strongly discourage Hot-linking.

Shot Level
The sl option allows the user to request Community (C) or Neighborhood (N) level set of images. The community images cover more area with less detail. The neighborhood images cover less area with greater detail.

The priority versions of this option allow requests to be fulfilled based on first and seconds choices. This option is useful if the desire is to see as many views available even if the first choice shot level cannot provide them. The option behavior is as follows:

Caveat: Requests made with units other than pixels cause the images to be sized according to the priority shot level.

Shot Type
The st option allows the user to specify the type of images that are to be returned. By default, the Portal returns only oblique images. The type can be set to return an orthogonal only (Or), obliques only (Ob), or a combination of obliques and an orthogonal (Cb).

Shot Heading
The sh option allows the user to specify the orientation of the returned oblique images. By default, the Portal attempts to return images in all four cardinal directions (North, East, South, West) See Note #1. This means that the top of each image is looking toward the indicated direction See Note #2. By using the shot heading option the user can filter request any available subset of orientations. The shot heading option is a simple string consisting of the 4 letters NESW. For example, to request images for East and West only the string would be: EW. The letters can be specified in any order and are not case sensitive. Orthogonal images are always "North Up" and therefore this option has no effect for these images.

Note #1: Not all areas have 4-way coverage therefore the Portal returns as many directions as are available.

Note #2: Each image has a indicator drawn in the upper left corner that displays the direction of True North.

Shot Year
The sy option limits the search to the Most Recent Images, Least Recent Images, or a designated 4-digit year. The default is to search the Most Recent Images.

Score Bias
The sb option selects the type of bias in the image search scoring algorithm used to determine the "best" image for each direction. Oblique bias attempts to return images that have the search point in the lower 1/3 (greatest detail) of the image. Center bias attempts to return images that have the search point as close as possible to the physical center of the image. This option has no effect on Orthogonal images which are always scored Center bias. The default is Oblique bias.

Image Type
The it option selects the type(s) of image url(s) to be returned in the results. The values for this option are any combination of the following:

Width & Height (Units)
By default, Clip images are 400 x 400 pixels. This can be modified with the width wh and/or height ht options. The default units for width and height are in pixels (px), but this can be modified with the un option to be (ft) for feet or (m) for meters.

Fill Color
Color used for Clip images that don't fill the entire frame. The default color for this border is black (000000). The fc option is used to change this color using any valid HTML color code.

Text Color
Each image is stamped with a copyright notice. The default text color is yellow (ffff00). The tc option is used to change this color using any valid HTML color code.

Quality Setting
The quality setting qs option is used to adjust the amount of compression the returned JPEG image has. The default value is 80.

Crosshair
The ch option is used to draw a crosshair on the search point. The crosshair color is the sames as the text color and is controlled by the tc option. The default setting is NOT to draw.

North Pointer
The np option is used to draw a north pointer icon on the image to indicate True North. The default setting is NOT to draw.

Datestamp
The ds option is used to add the image capture date. The datestamp is written after the copyright and is output in DD/MM/YYYY format. The default setting is NOT to draw.

Output Format
The of option is used to change the default image format. The portal supports JPEG (Default), GIF and PNG.

Output Status
The os option is used to change the default error reporting. Errors are reported via HTTP status codes unless this option is set to 1. This forces the Portal to emit errors in plain text.

Feature
The fe option is used to request a feature(s) be drawn on the requested Image Portal images.

More about Features:
Availble Features and associated name:
DescriptionFeature NameFeature TypeExclusive Feature?
Nationwide (United States) Parcel LayerparcelsPolygonYes

The above table shows the available features you can request to be drawn on an Image Portal image. You request this by appending a parameter (fe) to the search request.

Exclusive Features vs Non-Exclusive Features:
If the feature is marked as Exclusive, we must have a hit on that feature in order to return a result set. If, for example, you request parcels, and there is no parcel where you searched, we will return no data and return an HTTP 433 error: "Exclusive Feature Not Found" as well. If you still wish to have the image returned, request the image without requesting the feature.

How to request a feature:
The request is formatted using a JSON formatted object. In order to request that a feature be drawn on the image with default formatting settings, one would set the key of the first member of the JSON object to be the name of the feature (see above table for feature names), and the value to be an empty object. For example, to request a parcel be drawn on the image, one would append this string to the end of the query:
	fe={"parcels":{}}
The value of the "parcels" key is set to an empty object in the above example. By leaving the object empty, the feature is drawn with the default styling for that feature.

Feature Styles:
The changeable attributes of a drawn figure in the image are as follows:
  • For Polygon layers (ie: parcels):
    • strokecolor : The stroke (border) color of the shape. Accepts six digit hex color values. Note: Do not include the # sign.
    • strokeopacity : The stroke (border) opacity of the shape. Accepts values 0.0 - 1.0
    • strokewidth : The width of the stroke (border). Accepts values 0 - 10.
    • fillcolor : The fill color of the shape. Accepts six digit hex color values. Note: Do not include the # sign.
    • fillopacity : The fill opacity of the shape. Accepts values 0.0 - 1.0
    • featurebuffer : The distance in pixels between the shape and the edge of the image. Accepts values 0 - 200.
The default styles for each of the available layers:
  • Parcels:
    • Stroke Color: ffff00 (yellow)
    • Stroke Opacity: 1.0 (opaque)
    • Stroke Width: 2 (2 pixels)
    • Fill Color: ffffff (white)
    • Fill Opacity: 0.0 (transparent)
    • Feature Buffer: 100 (100 pixels)
To override the defaults, construct a JSON object as the value of the "parcels" key, setting the keys of the object to the names of the style attributes above, and the value as your requested value for that parameter.

Specifying Specific Orientations: To explicitly specify a set of orientations which the feature requested should be drawn on, set the "orientations" feature attribute key on the feature JSON object to the first letter of the orientation you wish the feature to be drawn on. The orientations are N - North, S - South, W - West, E - East, O - Orthogonal. For example, to request a feature be drawn on the Orthogonal Images and the East-Facing Oblique Images, set "orientations" to "OE". To request the feature be drawn on all the orientations, do not specify the "orientations" key, as it will default to "NESWO". See the second example below.

Overriding Orientations Specified with "orientations": Once an image orientation has been selected to draw or not draw a feature using the "orientations" key (detailed above), use the "draw" feature attribute key on the render url to turn the feature drawing on or off. One would set the "draw" key to either true or false depending on what the default specified by "orientations" was. For example, if NESW was specified in "orientations", the orthogonal image would not have the feature drawn on it. However, adding the following will override the setting and instead draw the feature: "draw":true. See the second example below.

Examples:
To request a parcel with fill opacity of 20%, stroke opacity of 80%, fill color as green (hex: 00cc00), stroke color as black (hex: 000000), and with a buffer of 150 pixels around the image, one would construct a JSON object like the following. (shown with formatting):
	fe={
		"parcels":
			{
				"fillopacity":0.2,
				"strokeopacity":0.8,
				"fillcolor":"00cc00",
				"strokecolor":"000000",
				"featurebuffer":150
			}
	}
This object should be actually requested without carriage-return formatting, such as the following:
	fe={"parcels":{"fillopacity":0.2,"strokeopacity":0.8,"fillcolor":"00cc00","strokecolor":"000000","featurebuffer":150}}
The values in the JSON object that are strings (fill color and stroke color) should be quoted using double quotations, and all key names ("fillopacity", "featurebuffer", etc...) should be quoted using double quotations as well.


To request the same parcel formatting as above, but request that the feature only be drawn on the Orthogonal image (if requested) and the West-facing Oblique (if requested), the request will add the "orientations" key:
	fe={
		"parcels":
			{
				"fillopacity":0.2,
				"strokeopacity":0.8,
				"fillcolor":"00cc00",
				"strokecolor":"000000",
				"featurebuffer":150,
				"orientations":"OW"
			}
	}


Once the images have been returned from the search call, if you change your mind, and you also want to draw the parcel on the East-facing Oblique, add the following to the end of its render url:
	fe={
		"parcels":
			{
				"draw":true
			}
	}


Overriding style values once an image has been generated:
Once an image has been generated, it is possible to override some style parameters with new values, however there is no way to remove a feature completely or add a new feature by modifying the render URL. You may only request features be turned completely on or off by doing a new search. In order to override a feature's style, append the same type of JSON object to the image generation url and any values that are specified will override the currently visible style attributes on the image. The only attribute that cannot be overridden is the Feature Buffer attribute, as this would change the size of the image, which would differ from the width and height values that were originally returned in the xml.

Requesting more than one feature:
Currently the Image Portal only provides one feature that you may request (parcels). However should the Image Portal offer more features than parcels, requesting multiple features is as simple as adding a second member to the top-level JSON object that you pass as the fe parameter. For example, if you were going to request a feature called 'streets' in addition to 'parcels,' you would form such a request as follows:
	fe={"parcels":{},"streets":{}}

	NOTE: "streets" is not currently an available layer, this is only an example

Sizing of the returned image:
When requesting features, the image returned will be, for most cases, the same image that would be returned if a feature were not requested. The ht and wh values requested are respected, and the requested feature will be drawn in the proper location on the image (see Example 2 below). However, there are a some notable exceptions to this generalization.
  • If the feature that is to be drawn on the image continues off the normally returned image the returned image size will be expanded to fit the feature inside the image including any feature buffer requested in the fe json parameter. For example, if a 200x200 image is requested, and an exclusive feature takes up 406x405 pixels in each direction, the image returned will be 406x405 (see Example 3 below).
  • If the feature that is to be drawn on the image continues off the source image, the feature will be truncated and there is no image left to return.
If a uniformly fixed size image is required, set the fs parameter to 1 in order to force a fixed size based on the ht and wh parameters (see Example 4 below). If fs is set to 1, the Image Portal will conduct the request normally, then expand or contract the returned image to fit inside the requested width and height. The aspect ratio of the image will not change, but if the aspect ratio of the generated image does not match the aspect ratio of the requested image size, fill color will be used to fill the rest of the image. The fill color is black (000000) by default and can be overridden by setting the fc parameter to some other hex value (see Example 6 below).

Overall, the ht and wh parameters when requesting a parcel are considered minimum values which can be expanded to fit the size of the parcel. When fs is set, they are exact values and the returned image will be the size requested unless the size requested is larger than the maximum clip size for that request. A clip may not be any larger than the source image requested and will be resized to the size of the source image.

Examples (click image to see full-resolution):

ImageDescriptionOptions
Example 1:

Requested: A normal image search is done with width and height requested at 600 pixels each.

Returned: A north-facing image is returned which has a full 600 pixels in height and width.
wh=600
ht=600
Example 2:

Requested: An image search is done with parcels requested using the minimum parameters required to do a parcel search, therefore defaults for style are utilized. Width and height of 600 pixels are requested.

Returned:: A north-facing image is returned with a full 600 pixels for height and width. Since 600x600 was enough to fit the drawn parcel in the image, the image itself is the same as in Example 1 but with a parcel drawn on it.
wh=600
ht=600
fe={"parcels":{}}
Example 3:

Requested: An image search is done with parcels requested using the minimum parameters required to do a parcel search, therefore defaults for style are utilized. Width and height of 200 pixels are requested.

Returned: A north-facing image is returned and is sized to 406x405 because the parcel was larger than the requested size of 200x200. This illustrates the wh and ht paramaters as being considered as minimums.
wh=200
ht=200
fe={"parcels":{}}
Example 4:

Requested: An image search is done with parcels requested using the minimum parameters required to do a parcel search, therefore defaults for style are utilized. Width and height of 200 pixels are requested. Fixed Size is also set (fs) to 1, forcing the Image Portal to resize the returned image, if necessary, into the size requested.

Returned: Because the parcel was larger than the 200x200 pixels, the image was expanded to fit the image to 406x405 pixels (exactly as shown in Example 3). However, since Fixed Size (fs) was set to 1, the Image Portal resized the 406x405 image to the smaller requested image of 200x200 pixels. The image was deresolved to accomplish this and has less resolution than the source image.
wh=200
ht=200
fe={"parcels":{}}
fs=1
Example 5:

Requested: An image search is done with parcels requested using the minimum parameters required to do a parcel search, therefore defaults for style are utilized. A very large height and width of 2000 pixels is requested.

Returned: Because the requested image size of 2000x2000 extends off the available image, an image of 2000x1878 was returned as there was no more image to create a 2000 pixel tall image.
wh=2000
ht=2000
fe={"parcels":{}}
Example 6:

Requested: An image search is done with parcels requested using the minimum parameters required to do a parcel search, therefore defaults for style are utilized. A very large height and width of 2000 pixels is requested. Fixed Size is also set (fs) to force the Image Portal to return an image exactly 2000x2000 pixels.

Returned: Because the requested image size of 2000x2000 extends off the available image, an image of 2000x1878 was returned as there was no more image to create a 2000 pixel tall image. Since fs was set to 1, the returned image was fit into an image 2000x2000 pixels. There is some black fill added at the bottom to make up for the lack of image available.
wh=2000
ht=2000
fe={"parcels":{}}
fs=1
Example 7:

Requested: An image search is done with parcels requested using the minimum parameters required to do a parcel search, therefore defaults for style are utilized. The width and height are set to 200 by 1000, which requests a very tall image.

Returned: An image sized 406x1000 pixels was returned. A width of 200 was requested but because the parcel is wider than 200 pixels, the image was resized to 406 pixels wide to fit the entire width of the parcel in the image. The height of 1000 was not modified and was returned because the parcel fit inside that requested height.

Optional Modifier: The requested image size of 200x1000 was not possible because the parcel was larger than that size in some way. As in the previous Example 6, by setting fs to 1, the Image Portal will take the normally returned image, resize if necessary and return an image exactly the same size as the one requested, even if that requires adding blank space, filled with the color specified in fc.
wh=200
ht=1000
fe={"parcels":{}}

Optional: fs=1
Example 8:

Requested: An image search is done with parcels requested using the minimum parameters required to do a parcel search, therefore defaults for style are utilized. The width and height are set to 1000 by 200, which requests a very wide image.

Returned: An image sized 1000x405 pixels was returned. A height of 200 was requested but because the parcel is taller than 200 pixels, the image was resized to 405 pixels tall to fit the entire height of the parcel in the image. The width of 1000 was not modified and was returned because the parcel fit inside that requested width.

Optional Modifier: The requested image size of 1000x200 was not possible because the parcel was larger than that size in some way. As in the previous Example 6, by setting fs to 1, the Image Portal will take the normally returned image, resize if necessary and return an image exactly the same size as the one requested, even if that requires adding blank space, filled with the color specified in fc.
wh=1000
ht=200
fe={"parcels":{}}

Optional: fs=1
Example 9:

Requested: An image search is done with parcels requested using additional style parameters to give the parcel outline and fill a different look and feel. The stroke color is set to purple-blue (330099), is semi-transparent at 80% (0.8) opacity, and is 5 pixels wide. The fill color is set to yellow (ffff00) and is semi-transparent at 30% (0.3) opacity. The height and width parameters are set to 600 by 600 pixels.

Returned: An image 600x600 pixels is returned with the parcel drawn as requested on it.
wh=600
ht=600
fe={"parcels":
        {"strokecolor":"330099",
         "strokeopacity":0.8,
         "strokewidth":5,
         "fillcolor":"ffff00",
         "fillopacity":0.3}
      }
Example 10:

Requested: An image search is done with parcels requested using additional style parameters to give the parcel outline and fill a different look and feel. The stroke color is set to black (000000), is semi-transparent at 50% (0.5) opacity, and is 2 pixels wide. The fill color is set to purple-blue (330099) and is semi-transparent at 40% (0.4) opacity. The height and width parameters are set to 600 by 600 pixels.

Returned: An image 600x600 pixels is returned with the parcel drawn as requested on it.
wh=600
ht=600
fe={"parcels":
        {"strokecolor":"000000",
         "strokeopacity":0.5,
         "strokewidth":2,
         "fillcolor":"330099",
         "fillopacity":0.4}
      }
Example 11:

Requested: An image search is done with parcels requested using additional style parameters to give the parcel outline and fill a different look and feel. The stroke color is set to black (000000) but is transparent at 0% (0.0) opacity. The fill color is set to red (ff0000) and is semi-transparent at 30% opacity. The height and width parameters are set to 600 by 600 pixels.

Returned: An image 600x600 pixels is returned with the parcel drawn as requested on it.
wh=600
ht=600
fe={"parcels":
        {"strokecolor":"000000",
         "strokeopacity":0.0,
         "fillcolor":"ff0000",
         "fillopacity":0.3}
      }

Back to top of page



Appendix A: HTTP Status Codes and Reason Phrases

Status Code Reason Phrase Description
401 Authorization Failed User credentials did not authenticate.
403 Access Forbidden Request did not originate on SSL Port 443.
404 No Images Found No images were found based on the request parameters.
420 Credentials Missing The user id and password parameters were not in the request.
421 Request Type Undefined The required request type parameter was not in the request.
422 Unknown Request Type Request type was not set to Location or Address.
423 Unknown Projection Projection was not set to LatLong, UTM or SPCS.
424 Bad Lat/Lon Request Lat/Lon parameters are missing or malformed.
425 Bad UTM Request UTM parameters are missing or malformed.
426 Bad SPCS Request State Plane parameters are missing or malformed.
427 Address Incomplete Required parameters for Address search are incomplete or missing.
428 Unable to Geocode Translation of address to coordinates failed.
429 Image Generation Error Image generation failed due to server error.
430 Database Error Image database is unreachable.
431 Product Type Undefined The required product type parameter was not in the request.
432 Unknown Product Type Product type was not set to Image,
Inventory, or Coverage.
433 Exclusive Feature Not Found An Exclusive Feature was requested but upon querying was not found.
Since it is an Exclusive Feature, no data is returned
unless there is a hit when this Feature is being requested.
434 Feature Decode Failed The feature definition in the fe field could not be decoded.
435 Invalid Query String The query string provided to the renderer was invalid. Check any additional parameters that were added.
503 Service Unavailable The Portal service is temporarily unavailable.

Back to top of page



Appendix B: Location/Address Search Results In XML

The XML document displayed in the table below was generated as a result of a location search. The search element encloses all search results and contains 3 attributes. The type attribute indicates whether the search was based on location or address. The latitude and longitude attributes are the search coordinates. For location searches these simply echo the original coordinates. For address searches these represent the geocoded coordinates. The coordinates are given in the WGS-84 datum.

In addition, an address search will return a precision attribute along with the coordinates. This attribute indicates the quality of the geocode. The precision values are:

NOTE: There is no guarantee that a parcel precision geocode will fall precisely on the house or building at the requested address. These geocodes are bound to the parcel centroid which may or may not be where the structure is situated.

The images element encloses all image information and contains 3 attributes. The count attribute indicates that there are 5 images available. The views attribute indicates the general orientation of the image: N - North, E - East, S - South, W - West, O - Orthogonal. The format attribute indicates the image format. Currently, the Portal only supports JPEG format.

Information about each image is enclosed within an image element. Contained within each image element are elements that describe the image. The view element describes the general orientation of the image. The heading element gives the actual orientation of the image in degrees from True North. The level element describes the shot level of the image and is either C for Community or N for Neighborhood. The day, month, and year elements give the numerical date on which the image was captured.

The imagepolygon element with the image element describes the coordinates for each corner of the source image. The ul, ur, lr, ll elements provide these coordinates. They are referenced starting in the upper-lefthand corner of the image and proceed clockwise. The ul element geolocates the upper-lefthand, the ur element geolocates the upper-righthand, the lr element geolocates the lower-righthand and the ll element geolocates the lower-lefthand. Each element contains a latitude and longitude attribute given in decimal degrees in the WGS84 datum.

URL Elements

There are up to 4 URL elements returned depending on what image types were requested. These elements are:

Each of these elements contains a url element that is used to retrieve the image.The clip, preview and fullimage elements also contain width and height elements. These values are in pixels. The clip element contains an imagepolygon element that provides the coordinates for the corners of the clip and follow the same format as described above for the source image.

Important: The width/height values for a clip may be different from those requested. However, in cases where the request goes beyond the bounds of the source image, the Portal resizes the request to return as much as possible while still keeping the search point in the center of the clip.

World File Elements

For orthogonal images the Clip and Full elements optionally contain a World File element which describes the location, scale and rotation of the image. The world file elements are:

Search Element Data

There is a difference in the data returned between a location and address search element. These differences are shown below:

Search Results
<?xml version="1.0"?>
<search type="location" latitude="43.003158" longitude="-77.615799">
<images count="5" views="NESWO">
<image>
<view>N</view>
<heading>356.27</heading>
<level>N</level>
<day>16</day>
<month>04</month>
<year>2006</year>
<imagepolygon>
<ul latitude="43.008876" longitude="-77.620122"/>
<ur latitude="43.008124" longitude="-77.610785"/>
<lr latitude="43.002728" longitude="-77.611449"/>
<ll latitude="43.002784" longitude="-77.618200"/>
</imagepolygon>
<thumbnail>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</thumbnail>
<clip>
<width>400</width>
<height>400</height>
<imagepolygon>
<ul latitude="43.003601" longitude="-77.616235"/>
<ur latitude="43.003584" longitude="-77.615509"/>
<lr latitude="43.002909" longitude="-77.615421"/>
<ll latitude="43.002921" longitude="-77.616116"/>
</imagepolygon>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</clip>
<preview>
<width>401</width>
<height>267</height>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</preview>
<fullimage>
<width>4008</width>
<height>2672</height>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</fullimage>
</image>
<image>
<view>E</view>
<heading>93.27</heading>
<level>N</level>
<day>16</day>
<month>04</month>
<year>2006</year>
<imagepolygon>
<ul latitude="42.998401" longitude="-77.609740"/>
<ur latitude="42.999927" longitude="-77.619296"/>
<lr latitude="43.005706" longitude="-77.617237"/>
<ll latitude="43.004926" longitude="-77.610317"/>
</imagepolygon>
<thumbnail>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</thumbnail>
<clip>
<width>400</width>
<height>400</height>
<imagepolygon>
<ul latitude="43.002711" longitude="-77.615500"/>
<ur latitude="43.002815" longitude="-77.616295"/>
<lr latitude="43.003693" longitude="-77.616076"/>
<ll latitude="43.003597" longitude="-77.615319"/>
</imagepolygon>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</clip>
<preview>
<width>401</width>
<height>267</height>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</preview>
<fullimage>
<width>4008</width>
<height>2672</height>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</fullimage>
</image>
<image>
<view>S</view>
<heading>185.47</heading>
<level>N</level>
<day>15</day>
<month>04</month>
<year>2006</year>
<imagepolygon>
<ul latitude="42.998401" longitude="-77.609740"/>
<ur latitude="42.999927" longitude="-77.619296"/>
<lr latitude="43.005706" longitude="-77.617237"/>
<ll latitude="43.004926" longitude="-77.610317"/>
</imagepolygon>
<thumbnail>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</thumbnail>
<clip>
<width>400</width>
<height>400</height>
<imagepolygon>
<ul latitude="43.002711" longitude="-77.615500"/>
<ur latitude="43.002815" longitude="-77.616295"/>
<lr latitude="43.003693" longitude="-77.616076"/>
<ll latitude="43.003597" longitude="-77.615319"/>
</imagepolygon>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</clip>
<preview>
<width>401</width>
<height>267</height>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</preview>
<fullimage>
<width>4008</width>
<height>2672</height>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</fullimage>
</image>
<image>
<view>W</view>
<heading>274.39</heading>
<level>N</level>
<day>16</day>
<month>04</month>
<year>2006</year>
<imagepolygon>
<ul latitude="43.000251" longitude="-77.619716"/>
<ur latitude="43.006651" longitude="-77.619298"/>
<lr latitude="43.005402" longitude="-77.612001"/>
<ll latitude="43.000639" longitude="-77.612475"/>
</imagepolygon>
<thumbnail>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</thumbnail>
<clip>
<width>400</width>
<height>400</height>
<imagepolygon>
<ul latitude="43.002947" longitude="-77.616398"/>
<ur latitude="43.003514" longitude="-77.616329"/>
<lr latitude="43.003440" longitude="-77.615217"/>
<ll latitude="43.002898" longitude="-77.615282"/>
</imagepolygon>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</clip>
<preview>
<width>401</width>
<height>267</height>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</preview>
<fullimage>
<width>4008</width>
<height>2672</height>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</fullimage>
</image>
<image>
<view>O</view>
<heading>0.00</heading>
<level>N</level>
<day>16</day>
<month>04</month>
<year>2006</year>
<imagepolygon>
<ul latitude="43.005220" longitude="-77.618465"/>
<ur latitude="43.005220" longitude="-77.613738"/>
<lr latitude="43.000166" longitude="-77.613738"/>
<ll latitude="43.000166" longitude="-77.618465"/>
</imagepolygon>
<thumbnail>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</thumbnail>
<clip>
<width>400</width>
<height>400</height>
<imagepolygon>
<ul latitude="43.003446" longitude="-77.616136"/>
<ur latitude="43.003446" longitude="-77.615465"/>
<lr latitude="43.002953" longitude="-77.615465"/>
<ll latitude="43.002953" longitude="-77.616136"/>
</imagepolygon>
<worldfile>
<a>0.000001678371</a>
<d>0.0</d>
<b>0.0</b>
<e>-0.000001231852</e>
<c>-77.616336244397</c>
<f>43.003453313135</f>
</worldfile>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</clip>
<preview>
<width>401</width>
<height>267</height>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</preview>
<fullimage>
<width>4008</width>
<height>2672</height>
<worldfile>
<a>0.000001678371</a>
<d>0.0</d>
<b>0.0</b>
<e>-0.000001231852</e>
<c>-77.618449310000</c>
<f>43.005246890000</f>
</worldfile>
<url>
http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9
</url>
</fullimage>
</image>
</images>
</search>

Back to top of page



Appendix C: Inventory Search Results In XML

The XML displayed in the table below was generated as a result of a location or address search with the product set to Inventory. There are 3 attributes to the search element. The type attribute indicates that this an inventory search. The latitude and longitude attributes describe the location for which this data is valid.

The libraries element contains all library information and has one attribute. The years attribute contains a comma separated list of all available years for this location.

The library element has one attribute and contains the shot level and view information for a particular year. The year attribute indicates the year the library was captured.

The neighborhood and community elements describe the inventory for each shot level. Each element contains two attributes. The count attribute indicates the number of images available. The views attribute indicates the general orientation of the images: N = North, E = East, S = South, W = West, O = Orthogonal.

Inventory Search Results In XML
<?xml version="1.0"?>
<search type="inventory" latitude="40.764601" longitude="-74.000303">
<libraries years="2004,2003">
<library year="2004">
<neighborhood count="4" views="NESW"/>
<community count="3" views="NWO"/>
</library>
<library year="2003">
<neighborhood count="4" views="NESW"/>
<community count="4" views="NESW"/>
</library>
</libraries>
</search>

Back to top of page



Appendix D: Coverage Search Results In XML

The XML displayed in the table below was generated as a result of a coverage search in California (CA). There are 3 attributes to the search element. The type attribute indicates that this a coverage search The regions attribute indicates that there is 1 region contained in the coverage search. The areas attributed indicates there are 6 total areas contained in the coverage search.

The region element describes the state, province or geographical zone in which this bounding box is enclosed. Each region has a name attribute assigned to it. The area element describes the county, parish, city or metro area that this bounding box covers. Each area has a name attribute assigned to it. There is one boundingbox element for each available area.

Contained within each bounding box is a set of attributes that define the area. The minx, miny, maxx, and maxy attributes describe the actual bounding box coordinates in WGS-84 Latitude/Longitude. minx and maxx describe the bounding longitudes. miny and maxy describe the bounding latitudes. Adjacent areas may have bounding boxes that overlap.

Coverage Search Results In XML
<?xml version="1.0"?>
<search type="coverage" regions="1" areas="6">
<region name="CA">
<area name="Alameda">
<boundingbox minx="-122.192626" miny="37.544809" maxx="-121.895584" maxy="37.713715"/>
</area>
<area name="Los Angeles">
<boundingbox minx="-119.186167" miny="32.758056" maxx="-117.375562" maxy="34.847333"/>
</area>
<area name="Orange">
<boundingbox minx="-118.609306" miny="33.150328" maxx="-116.916268" maxy="34.217658"/>
</area>
<area name="San Bernardino">
<boundingbox minx="-118.486442" miny="33.698399" maxx="-113.711536" maxy="36.008712"/>
</area>
<area name="San Francisco">
<boundingbox minx="-122.594684" miny="37.549970" maxx="-122.153080" maxy="37.869490"/>
</area>
<area name="Solano">
<boundingbox minx="-122.526489" miny="37.896185" maxx="-121.472982" maxy="38.674326"/>
</area>
</region>
</search>

Back to top of page



Appendix E: Optional Image URL Modifiers

There are a number of optional fields that can be used with an image URL to modify the output. For example, suppose the original search did not enable the datestamp. The image URL can be modified to add this without issuing a new search to the Image Portal. The optional modifiers are listed below:

Examples:

Any combinations of these values are allowed. See the Optional Search Modifiers section for details on option values.

Re-center A Clip

This feature adds some rudimentary navigation capability to clips requests that allow the user to re-center the clip to a point anywhere within the original clip. This is accomplished by adding x and y fields to the clip URL from the returned XML document. The x and y fields are the image coordinates of where to re-center.

For any given clip, the image upper left corner is always at image coordinate (0,0) and the lower right corner is alway at image coordinate (width - 1, height - 1). The x-coordinate values increase from left to right and the y-coordinate values increase from top to bottom.

Suppose we had an 800x800 pixel clip. The image coordinates would range from (0,0) to (799,799). If we wanted to re-center the image to (200,200) we would modify the URL in the following way:

Example: http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9&x=200&y=200

Limitations

XML Output

Updated center and corner coordinates can be obtained from a re-centered clip by modifying the URL as shown below:

Example: http://pol.pictometry.com/ImagePortal/render/?id=eyJpZCI6IjEiLCJ0Z ... OWNjNjNlMyJ9&x=200&y=200&output=xml

The would return an XML document similar to the one below:

XML Output
<image>
<center latitude="43.003075" longitude="-77.616097"/>
<ul latitude="43.002817" longitude="-77.616683"/>
<ur latitude="43.003393" longitude="-77.616665"/>
<lr latitude="43.003322" longitude="-77.615510"/>
<ll latitude="43.002773" longitude="-77.615546"/>
</image>

Back to top of page


Glossary

Area
Describes the county, parish, city or metro area that a bounding box covers.

Base64
Base64 encoding, as specified in RFC 2045 - MIME uses a 64-character subset (A-Za-z0-9+/) to represent binary data and = for padding. Base64 processes data as 24-bit groups, mapping this data to four encoded characters.

Bearing
The degree of angle of an object in relation to due North.

Bounding Box
Represents a geographical search area using a min x, min y, max x, max y.

Community
An image representing an entire community. Community shots are usually taken at a higher altitude and show less detail than neighborhood shots. Community images are captured with approximately a 2-foot ground sample distance and cover an area of approximately 1-mile by ½-mile.

Coordinate
Any of a set of numbers used in specifying the location of a point on a line, on a surface, or in space.

Coordinate System
A reference system used to measure horizontal and vertical distances on a map.

Coverage Product
Returns XML description of the area coverage for the Portal.

Crab
Crab is a maneuver used to eliminate the drift of an aircraft caused by wind. The pilot will offset the heading of the aircraft from the desired track by a calculated amount, and the aircraft's velocity combined with the wind through vector addition will give a net movement in the desired direction. For orthogonal images, the process of
orthorectification removes the effects of crab. However, this process can sometimes leave black areas around the edges of the images.

Datum
A set of parameters and control points used to accurately define the three-dimensional shape of the Earth.

Decimal Degrees
A method of specifying lat/lon coordinates such that whole degrees are to the left of the decimal point with the fractional degree to the right. Positive whole degrees indicate the Northern hemisphere for latitude and the Eastern hemisphere for longitude. Negative whole degrees indicate the Southern hemisphere for latitude and the Western hemisphere for longitude.

Example: 43.003158 -77.615799 is 43.003158 degrees north latitude and 77.615799 degrees west longitude.

Decimal Minutes
A method of specifying lat/lon coordinates such that there are whole degrees with whole minutes to the left of the decimal point and fractional minutes to the right. Positive whole degrees indicate the Northern hemisphere for latitude and the Eastern hemisphere for longitude. Negative whole degrees indicate the Southern hemisphere for latitude and the Western hemisphere for longitude.

Example: 43 00.186 -77 36.950 is 43 degrees 00.186 minutes north latitude and 77 degrees 36.950 minutes west longitude.

Degrees/Minutes/Seconds
A method of specifying lat/lon coordinates such that there are whole degrees, whole minutes and whole seconds. Seconds are sometimes written in a decimal format so that whole seconds are to the left of the decimal point and fractional seconds are to the right. Positive whole degrees indicate the Northern hemisphere for latitude and the Eastern hemisphere for longitude. Negative whole degrees indicate the Southern hemisphere for latitude and the Western hemisphere for longitude.

Example: 43 00 11.2 -77 36 57.0 is 43 degrees 00 minutes 11.2 seconds north latitude and 77 degrees 36 minutes 57.0 seconds west longitude.

Easting
A rectangular (x,y) coordinate measurement of distance east from a north-south reference line, usually a meridian used as the axis of origin within a map zone or projection.

Geocoding
The process of converting a street address into a geographical location. Geocoding is not exact and may not return a coordinate precisely at the desired location. The location is determined by a process of interpolation that uses well-known coordinates, such as street intersections, to approximate a location for a given street address. As a general rule, the geocoding process is more accurate in urban areas where lot sizes and blocks tend to be more uniform. Suburban areas are prone to less accuracy with rural areas being the least accurate.

Georeference
To establish the relationship between page coordinates on a planar map and known real-world coordinates.

Global Positioning System (GPS)
A system of satellites and receiving devices used to compute positions on the Earth.

Image Product
Returns up to 5 images. one orthogonal view and up to 4 oblique views. If there is no orthogonal, the request is fulfilled with obliques only. The oblique will be the best view (most centered) unless a particular orientation is selected.

Interpolation
To estimate values between two known values using an algorithm.

Inventory Product
Returns an XML description of the image inventory for the requested location.

Latitude
Angles in a north-south direction measured from the earth’s center to locations on the earth’s surface.

Longitude
Angles in an east-west direction measured from the earth’s center to locations on the earth’s surface.

Magnetic North
The north direction shown on a compass. The compass needle is attracted by the earth's internal magnetic field. The true north pole and the magnetic north pole are about 1500km apart.

Metadata Search
Returns an XML description of the image metadata for the requested location.

NAD27
North American Datum 1927, CONUS - Also called NAS-C (or sometimes just NAS), this datum is being superceded by NAD83 and WGS84, but is still very commonly found used for USGS 1:24000 DRGs and DEMs.

NAD83
North American Datum 1983, CONUS - Also called NAR-C.

Neighborhood
An image representing a given neighborhood in a community. Neighborhood shots are usually taken at a lower altitude than community shots and show greater detail. Neighborhood images are captured with approximately a 6-inch ground sample distance and cover an area of approximately 750-feet by 1,500-feet.

Northing
A rectangular (x,y) coordinate measurement of the northward distance from the origin within a map zone or projection.

Oblique Image
An image taken on an angle from the target image. Oblique shots enable you to see greater detail in the image than an orthogonal image.

Orthogonal Image
An image taken directly above the target; a straight-down view. Contrast to an oblique image.

Orthorectification
The process of removing image distortions from an aerial photograph caused by lens distortion, camera tilt, varying distance to camera, terrain, etc.

Photogrammetry
The science of making reliable measurements by the use of photographs and especially aerial photographs.

Point
A single x, y coordinate on a map.

Polygon
A simple closed figure that consists of only line segments.

Projection
A mathematical calculation transforming the three dimensional surface of the earth to a two-dimension plane.

Radius
A straight line measuring from the center to the outside of a circle.

Region
Describes where the bounding box in question is found. It includes states, provinces, territories or any large geographical zone.

Score Bias
A bias added to the image search algorithm used to determine the "best" image for each direction. Oblique bias attempts to return images that have the search point in the lower 1/3 (greatest detail) of the image. Center bias attempts to return images that have the search point as close as possible to the physical center of the image. This option has no effect on Orthogonal images which are always scored Center bias.

State Plane Coordinate System (SPCS)
A system of plane-rectangular coordinates established by the federal government. The system is used for defining positions of points on, above, or below the earth's surface in terms of x,y values based on the distance from an origin point defined for each SPCS zone. One or more zones exists for each state in the US.

True North
The geographic north pole of the Earth located at 90° North latitude. True north is equal to 0 degrees and the rest of the angles go clockwise in a 360 degree circle: east = 90 degrees, south = 180 degrees, west = 270 degrees.

USGS
United States Geological Survey. www.usgs.gov

Universal Transverse Mercator (UTM)
A standardized grid system used to identify points on maps. Units are measured in eastings and northings.

WGS84
World Geodetic System 1984 - A worldwide datum. Originally a military standard (MIL-STD-2401 Military Standard) produced to address the need for a global positioning coordinate system (for GPS). WGS84 is an earth fixed global reference frame used for defining coordinates when surveying and by GPS systems.

World File
A World File is plain text data used by geographic information systems to coordinate raster map images. The file specification was introduced by ESRI.

XML
eXtensible Mark-up Language, a specification developed by the W3C. XML is a pared-down version of Standard Generalised Mark-Up Language, designed especially for Web documents. It allows designers to create their own customised tags, enabling the definition, transmission, validation, and interpretation of data between applications and between organizations. See here for details.

Back to top of page


Search Demonstrations
The following section contains forms that can be used to demonstrate the functionality of the Pictometry Online Image Portal. The 5 location searches (3 formats of Lat/Lon, UTM and State Plane), the address search, and the coverage search can be initiated from these forms.

IMPORTANT: Please disable pop-up blocking software before initiating a search.



Location Search Using Latitude/Longitude
 
Uid: Password: Product: Status:
Shot Level: Shot Type:
URL: T:  C:  P:  F: 
Format:
Lat: Lon: Datum: Format:
Units: Width: Height:
Fill Color: Text Color: Quality: Year:
Crosshair:  Datestamp:  North Pointer:  N:  E:  S:  W: 
Year Limit: Score Bias: Fixed Size: Month Filter: to
Parcel Search: Stroke Color: Stroke Opacity: Stroke Width:
Fill Color: Fill Opacity: Buffer Outside Parcel:
 
  

Back to top of page





Location Search Using UTM
 
Uid: Password: Product: Status:
Shot Level: Shot Type:
URL:  T:  C:  P:  F: 
Format:
Zone: Hemisphere: Easting: Northing:
Datum: Units: Width: Height:
Fill Color: Text Color: Quality: Year:
Crosshair:  Datestamp:  North Pointer:  N:  E:  S:  W: 
Year Limit: Score Bias: Fixed Size: Month Filter: to
Parcel Search: Stroke Color: Stroke Opacity: Stroke Width:
Fill Color: Fill Opacity: Buffer Outside Parcel:
 
  

Back to top of page





Location Search Using State Plane
 
Uid: Password: Product: Status:
Shot Level: Shot Type:
URL:  T:  C:  P:  F: 
Format:
Zone:

Units: Easting: Northing:
Datum: Units: Width: Height:
Fill Color: Text Color: Quality: Year:
Crosshair:  Datestamp:  North Pointer:  N:  E:  S:  W: 
Year Limit: Score Bias: Fixed Size: Month Filter: to
Parcel Search: Stroke Color: Stroke Opacity: Stroke Width:
Fill Color: Fill Opacity: Buffer Outside Parcel:
 
  

Back to top of page





Address Search
 
Uid: Password: Product: Status:
Shot Level: Shot Type:
URL:  T:  C:  P:  F: 
Format:
Address: City: State: Zip:
Width: Height: Units:
Fill Color: Text Color: Quality: Year:
Crosshair:  Datestamp:  North Pointer:  N:  E:  S:  W: 
Year Limit: Score Bias: Fixed Size: Month Filter: to
Parcel Search: Stroke Color: Stroke Opacity: Stroke Width:
Fill Color: Fill Opacity: Buffer Outside Parcel:
 
  

Back to top of page





Coverage Search
 
Uid: Password: State:
 
  

Back to top of page