Create a Zone Endpoint

[lovehandle]

Create a zone information endpoint that takes a bounding box and returns a JSON array of zone data within that bounding box.

Request:

curl http://local:3000/zones/search?bounding_box=-122.5155,37.7038,-122.5155, 37.7038

Response:

[{"id": "DCP-0", "title": "Downtown Centennial Plan", "description": "Lorem Ipsum", "geom": ""}]

[louh]

What is the primary difference between this one and #9?

I was thinking of a parcel endpoint that is the primary retrieval endpoint for http://lv-dof-staging.herokuapp.com/#/section/50

Which means sending a request like:

curl http://local:3000/parcels/search?id=123456789

And the response would be all the data that we have to populate the parcel information.

Would it be better to use other means of retrieving the data (e.g. having the front-end perform separate lookups by parcel number on separate data sets, rather than have the back-end assemble this parcel data for the front-end)

[louh]

re: "having the front-end perform separate lookups by parcel number on separate data sets"

Is this the best way to do this:

• Set up a factory on the application itself so it loads all the zone data from the endpoint into memory upon load. This is a JSON of zone IDs, names, and perhaps other metadata related to it.

• Any time something refers to a zone, it just provides the zone_id. Since zone data is already in memory, the front end can read from it without loading an endpoint each time. The response would look something like

  [{"parcel_id": 1234, "zone_id": "1"}]

• re: zone_id do we want to use our own unique integers or go with the city designation, e.g. "DCP-0"

See public/data/zone-types.json for an example of the data it reads.

[lovehandle]

@louh updated to reflect discussion in #9