icecondor:api
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
icecondor:api [2008/09/07 18:18] – 192.168.0.3 | icecondor:api [2008/09/30 23:27] – 64.122.198.69 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | === web/SVG version === | ||
+ | http:// | ||
+ | http:// | ||
+ | |||
=== Introduction === | === Introduction === | ||
input format: HTTP get/post variables \\ | input format: HTTP get/post variables \\ | ||
Line 4: | Line 8: | ||
success/ | success/ | ||
- | id = Any unique string identifier (usually | + | === IDs/URIs === |
- | lat = signed float (in degrees) \\ | + | |
- | long = signed float (in degrees) \\ | + | the id field in icecondor is a URI, with some standard URNs defined. |
- | alt = signed float (in meters) \\ | + | |
- | time = 2008-09-05T22:00Z (ISO8601) \\ | + | A person is generally defined by their OpenID |
- | hdop = float (Dilution | + | < |
- | vdop = float \\ | + | http:// |
- | pdop = float \\ | + | </ |
+ | |||
+ | If there is no identified URL for the user, a regular uuid can be generated. | ||
+ | < | ||
+ | urn: | ||
+ | </ | ||
+ | |||
+ | |||
+ | The follow URNs are used to build an icecondor id when the MAC address | ||
+ | |||
+ | < | ||
+ | urn: | ||
+ | urn: | ||
+ | </ | ||
=== Update location === | === Update location === | ||
< | < | ||
- | POST location | + | POST /locations |
input: | input: | ||
- | id=< | + | id=< |
+ | or | ||
+ | id=<id> next_to=< | ||
output: | output: | ||
+ | </ | ||
- | GET location | + | === Search === |
+ | < | ||
+ | GET / | ||
input: | input: | ||
search filters: | search filters: | ||
- | id=< | + | radius=< |
+ | | ||
+ | | ||
+ | | ||
+ | or | ||
+ | id=< | ||
output: | output: | ||
returns the most recent post. | returns the most recent post. | ||
- | id, | + | |
</ | </ | ||
+ | |||
+ | |||
+ |
icecondor/api.txt · Last modified: 2024/01/31 04:08 by 127.0.0.1