The smart choice for parcel data.

Parcel Overlays Documentation

Parcel Boundary Map Tiles

Parcel boundary map tiles, which are 256-by-256 pixel transparent PNG images, can be accessed in one of two ways: through our Javascript API, or directly via REST endpoint.

Javascript API: See our Google or Bing examples pages (and the source thereof) to see how to overlay boundary map tiles onto those map services in a web browser (Javascript) environment. A simple implementation requires including only a single <script ...> tag and a few lines of javascript.

To change the color of boundary lines in map tiles using the Javascript API, add a second parameter to the REP.Layer.Google.Initialize(...) or REP.Layer.Bing.Initialize(...) function call with a Parcels_OutlineColor key and your color as the value. So for instance change the call:

REP.Layer.Google.Initialize(map);

to:

REP.Layer.Google.Initialize(map, {Parcels_OutlineColor: 'rgb(0,128,255)'});

to make parcel lines light blue, or to:

REP.Layer.Google.Initialize(map, {Parcels_OutlineColor: 'green'});

to make parcel lines green.

While this javascript ultimately makes calls to the REST API (below), it abstracts away a number of details.

REST API: boundary map tiles can be accessed directly from our server using a REST endpoint, which has the following format:

https://reportallusa.com/dyn/tile.py?map=siteroot/Base_Layers.map&layer=Parcels&mode=tile&tilemode=gmap&tile=X+Y+Z&client=[client_key]

Where X is the tile's X coordinate, Y is the tile's Y coordinate, and Z is the tile's Z (zoom) coordinate, in the Google Maps coordinate system. Z must be between 15 (at the most zoomed out) and 21 (at the most zoomed in), inclusive. As per the Google Maps coordinate system, X and Y must be between 0 and 2Z - 1. A useful tile coordinates reference tool can be found at: http://www.maptiler.org/google-maps-coordinates-tile-bounds-projection/.

To change the color of boundary lines in map tiles using the REST API, add a &palette_recolor=r%20g%20b parameter ("%20" is a urlencoded space) where r, g, and b are numbers between 0 and 255 (inclusive), indicating the amount of red, green, and blue in the desired color.

Parcel Attributes and Geometry

To retrieve parcel attribute and geometry information, you can use the Javascript API or the REST API.

Javascript API

For information on getting parcel attribute and geometry information using the Javascript API, see the Google Maps example page or the Bing Maps example page.

REST API

To get parcel attribute and boundary information using the REST API, your application makes HTTP requests to our endpoint

https://reportallusa.com/api/parcels.php

and receives JSON responses. The following kinds of requests are supported: Address, Parcel Id, Owner, Point, Nearest parcel, and Polygon.

After receiving a request, our server responds with a response object in JSON format which contains the following attributes:

AttributeMeaning
status'OK' if the request was processed successfully.
'error' the request was not processed successfully, in which case see the 'message' attribute for the specific error message.
countTotal number of records matching the query.
pagePage of results returned.
rppNumber of results per page.
resultsArray of result rows, each a dictionary mapping column names to values. Each result row includes the parcel boundary's coordinates as an OGC Well-Known Text (WKT) polygon string.
queryThe query string issued to retrieve these results.

For details on the composition of each result row, see our Data Dictionary page.

All requests require that you supply your client key as a

client_key=[client_key]

parameter. If you do not have a client key, you can get one by following the link under "Try:" on the main Parcel Overlays page.

You can optionally supply the page and rpp parameters as integer values, to control the number and range of results returned.

Examples of requests are below.

Address queries: There are two address query formats, depending on whether you wish to supply the address and its region (city, county, state, and/or zip) in separate parameters or in the same parameter:

  1. Supply the address and region in separate address=... and region=... parameters:
    (note: "%20" is the urlencoded value for a space character)
    https://reportallusa.com/api/parcels.php?client=[client_key]&v=2&region=Geauga%20County,%20OH&address=100%20Short%20Court

    https://reportallusa.com/api/parcels.php?client=[client_key]&v=2&region=Parma,%20Ohio&address=4603%20Brookpark%20Rd

  2. Supply the address and region in a single q=... parameter:
    https://reportallusa.com/api/parcels.php?client=[client_key]&v=2&q=100%20Short%20Court,%20geauga,%20oh

    https://reportallusa.com/api/parcels.php?client=[client_key]&v=2&q=1950%20Lucy%20Lane,%20Riverside%20County,%20California

Parcel Id queries: Parcel Id queries return the parcel record whose assessor-assigned Parcel Id (also known as Parcel Identification Number (PIN) or Assessor's Parcel Number (APN)) matches a given parameter:

  1. Supply the Parcel Id in a parcel_id=... parameter and the region in a region=... parameter:
    https://reportallusa.com/api/parcels.php?client=[client_key]&v=2&region=Cuyahoga%20County,%20Ohio&parcel_id=44327012

    Multiple parcels can be specified by separating them with a semicolon:
    https://reportallusa.com/api/parcels.php?client=[client_key]&v=2&region=Cuyahoga%20County,%20Ohio&parcel_id=44327012;44327010;44327013

Owner Name queries: Owner Name queries return the parcel record(s) whose owner name matches a given parameter. The owner name format is "Lastname Firstname". If a single word in given (e.g. "Smith"), an exact match search on last name (surname) is performed. If more than one word is given (e.g. "Smith J"), a prefix match is performed. To perform a prefix match on a single word, add a star to the end of the word (e.g. "Smit*").

  1. Supply the Owner Name in a owner=... parameter and the region in a region=... parameter:
    https://reportallusa.com/api/parcels.php?client=[client_key]&v=2&region=Cuyahoga%20County,%20Ohio&owner=Smith

    Multiple owners can be specified by separating them with a semicolon:
    https://reportallusa.com/api/parcels.php?client=[client_key]&v=2&region=Cuyahoga%20County,%20Ohio&owner=Smith;Jones

Point queries: Point queries return the parcel record whose polygon contains the given query point. (In rare cases such as some condominium parcels, more than one record can be returned.) There are two point query formats, depending on whether you wish to supply a point in the web mercator coordinate system or the WGS84 Lon/Lat coordinate system:

  1. In web mercator coordinates using a "spatial_intersect=POINT(x y)" parameter:
    https://reportallusa.com/api/parcels.php?client=[client_key]&v=2&spatial_intersect=POINT(-7804647.3396951%205055285.6724133)

  2. In WGS84 Lon/Lat coordinates using a "spatial_intersect=POINT(lon lat)&si_srid=4326" parameter:
    https://reportallusa.com/api/parcels.php?client=[client_key]&v=2&spatial_intersect=POINT(-70.110502%2041.2905919)&si_srid=4326

Nearest parcel queries: Near parcel queries return the parcel records closest to the given query point, in increasing order of distance. There are two nearest parcel query formats, depending on whether you wish to supply a geometry in the web mercator coordinate system or the WGS84 Lon/Lat coordinate system:

  1. In web mercator coordinates using a "spatial_nearest=POINT(x y)" or "spatial_nearest=POLYGON((...))" parameter:
    https://reportallusa.com/api/parcels.php?client=[client_key]&v=2&spatial_nearest=POINT(-7804647.3396951%205055285.6724133)

  2. In WGS84 Lon/Lat coordinates using a "
    spatial_nearest=POINT(x y)&sn_srid=4326
    " or "
    spatial_nearest=POLYGON((...))&sn_srid=4326
    " parameter:
    https://reportallusa.com/api/parcels.php?client=[client_key]&v=2&spatial_nearest=POINT(-70.110502%2041.2905919)&sn_srid=4326

Polygon queries: Please contact support@reportallusa.com if you wish to issue polygon queries. They may return multiple result records, and thus decrease your quota faster than other query methods. For this reason we disable them by default.

There are two polygon query formats, depending on whether you wish to supply a polygon in the web mercator coordinate system or the WGS84 Lon/Lat coordinate system:

  1. In web mercator coordinates using a "spatial_intersect=POLYGON((...))" parameter:
    https://reportallusa.com/api/parcels.php?client=[client_key]&v=2&spatial_intersect=POLYGON((-9663128.4741915%203962254.4093738,-9663128.4741915%203962386.9798447,-9663033.5250705%203962386.9798447,-9663033.5250705%203962254.4093738,-9663128.4741915%203962254.4093738))

  2. In WGS84 Lon/Lat coordinates using a "spatial_intersect=POLYGON((...))&si_srid=4326" parameter:
    https://reportallusa.com/api/parcels.php?client=[client_key]&v=2&spatial_intersect=POLYGON((-86.8053600077677%2033.5029528113281,-86.8053600077677%2033.5039458470498,-86.8045070653017%2033.5039458470498,-86.8045070653017%2033.5029528113281,-86.8053600077677%2033.5029528113281))&si_srid=4326

Errors: If an error occurs in processing your request, the REST API will return a JSON response of the form: {"status": "error", "message": "..."}

All content © 2017 Real Estate Portal, USA. U.S. Patent No. 8,255,418. Terms of Service