Parcel Service
Introduction
In collaboration with the Department of Planning we have written a restful parcel service. This page describes that service.
Data Concurrency
The parcel data are updated every weeknight. Because these updates rely on lots of moving parts, they will fail a few times a year. We actively monitor this and usually have everything fixed for the next business day.
User Contacts
Contact | Department |
---|---|
Aksel Olsen | Department of Planning |
Example URLs
NOTE: all the links in this section are to an internal server which is not accessible from outside the city (sorry)
The URL is case sensitive.
A parcel that exists: http://10.250.60.189/search/parcel/1234001/
A parcel that does not exist: http://10.250.60.189/search/parcel/1234001X/
A parcel without geometry: http://10.250.60.189/search/parcel/5678007/
A retired parcel: http://10.250.60.189/search/parcel/5708026/
Example Response
{ "returnObj": [ { "geometry": "MULTIPOLYGON (((6000289.6490318738000000 2109189.6356368181000000, 6000303.3496173630000000 2109090.5707322196000000, 6000331.9383771177000000 2109094.5545561356000000, 6000318.0463601183000000 2109193.5863283621000000, 6000289.6490318738000000 2109189.6356368181000000)))", "block_num": "1234", "blk_lot": "1234001", "centroid": "POINT (6000310.7489634585000000 2109142.0785302911000000)", "lot_num": "001", "srid": 2227, "date_map_add": "1998-07-01", "date_rec_drop": null, "map_blk_lot": "1234001" } ], "status_code": 0, "message": "", "errors": {}, "success": true }
Field Definitions
field name | description |
---|---|
date_map_add | create date |
date_rec_drop | retire date |
geometry | geometry of the parcel polygon |
centroid | center point of parcel polygon |
srid | spatial reference id |
lot_num | lot number |
block_num | block number |
blk_lot | concatenation of block |
map_blk_lot | ground level parcel identifier |