PolyField
- Engine: MongoDB (mongoengine document)
- App: reference
- Table/Collection: ``
Landing position measured by the PolyField client, in metres. The client sends rotated coordinates for the landing point. We store them exactly as supplied; the rendering side owns the geometric interpretation, so no assumptions about origin or rotation are baked into the schema.
| Field | Type | Column/Key | Null/Default | PK | Choices | Notes |
|---|---|---|---|---|---|---|
| rx | DecimalField | rx | null | — | Landing position, x: distance across the sector from its cen… | |
| ry | DecimalField | ry | null | — | Landing position, y: distance out along the sector, in metre… |
Field names link to their fuller explanation below.
Field details
Click a field name in the table above to jump to its explanation. Fields with no help text yet show a prompt, and are the ones to improve by adding a help_text on the model field, then regenerating.
rx
- Engine: MongoDB
- Type:
DecimalField - Column/Key:
rx - nullable
Landing position, x: distance across the sector from its centre line, in metres, in the rotation the PolyField client uses — negative to one side, positive to the other, so a landing on the centre line has rx = 0. Stored as a 2dp string exactly as supplied. Empty when there is no measurement: hand-recorded attempts and fouls have no landing point.
ry
- Engine: MongoDB
- Type:
DecimalField - Column/Key:
ry - nullable
Landing position, y: distance out along the sector, in metres, in the same rotation as rx. This is the axis the throw travelled down, measured from the origin the client uses, so it need not equal the recorded distance. Stored as a 2dp string exactly as supplied. Together with rx it places the marker on the throws map.
Generated by docs_models management command for MongoDB.