EastingNorthing
Projected coordinates: an easting and a northing, by name, in their reference system's units.
Geospatial; not ordered; since Jadpo 0.1.0.
Make one
Build one from its fields, EastingNorthing { easting: ... northing: ... crs: ... }.
Fields
| Field | Type |
|---|---|
easting |
Decimal |
northing |
Decimal |
crs |
Crs |
Text, JSON and storage
It has no single text form, so text.from and text.parse don't take it. JSON sends an object of its parts.
| JSON |
|---|
{"easting":"530000","northing":"180000","crs":"EPSG:27700"} |
{"easting":"448251.795","northing":"5411932.678","crs":"EPSG:32630"} |
It is stored in 3 columns, each named for the field, _ and its suffix. This is {"easting":"448251.795","northing":"5411932.678","crs":"EPSG:32630"}:
| Column | Type | Holds |
|---|---|---|
<field>_easting |
numeric |
448251.795 |
<field>_northing |
numeric |
5411932.678 |
<field>_crs |
text |
'EPSG:32630' |
Shown to people
text.format(value, locale:) shows it to people in their locale.
With locale: Locale.en_gb:
| Value | Shown |
|---|---|
{"easting":"530000","northing":"180000","crs":"EPSG:27700"} |
easting 530,000, northing 180,000 (EPSG:27700) |
{"easting":"448251.795","northing":"5411932.678","crs":"EPSG:32630"} |
easting 448,251.795, northing 5,411,932.678 (EPSG:32630) |
Operations
It has the contract's own operations: text.format, json.read, json.write and ==. It isn't ordered, so < and sorting don't take it. Every standard type meets one contract says how they work.
Markdown for agents: /docs/types/type-easting-northing.md.Built from Jadpo main at e00e61f.