-
Notifications
You must be signed in to change notification settings - Fork 4
JSON
lgrammel edited this page Jul 21, 2012
·
3 revisions
Expected structure of the JSON files rentals.json
and uvic_transit.json
. The files can easily be renamed or retrieved from a dynamic service.
Contains an array of buildings with all available units per building.
[
{
"id": int,
"url": string (url),
"image_url": string (url),
"source": string (e.g. rental agency name),
"lat": float (latitude),
"lon": float (longitude),
"availabilities": [ // all units for rent in a building
{
"bedrooms": int,
"price": float (dollar)
},
...
],
"updated_at": int (timestamp)
},
...
]
Contains routes and stops separately, because different routes use the same stops.
{
"routes": [
{
"route": string (descriptive name),
"stops": [
{
"point_id": int (reference to point, see below),
"sequence": string (? might not actually be used)
},
...
]
},
...
],
"stops": [
{
"lat": float (latitude),
"lon": float (longitude),
"routes": [
string (descriptive routes name, see above), ...
],
"id": int (stop id, used in routes)
},
...
]
}