PRJ — WGS 84 in WKT 2 (2019)
The same CRS in WKT 2, which renames almost every keyword (GEOGCRS, ELLIPSOID, LENGTHUNIT) and — crucially — declares axis order explicitly with AXIS and ORDER. WKT 1 left that implicit, which is the root of most latitude/longitude swaps.
GEOGCRS["WGS 84",
DATUM["World Geodetic System 1984",
ELLIPSOID["WGS 84",6378137,298.257223563,LENGTHUNIT["metre",1]]],
PRIMEM["Greenwich",0,ANGLEUNIT["degree",0.0174532925199433]],
CS[ellipsoidal,2],
AXIS["geodetic latitude (Lat)",north,ORDER[1],ANGLEUNIT["degree",0.0174532925199433]],
AXIS["geodetic longitude (Lon)",east,ORDER[2],ANGLEUNIT["degree",0.0174532925199433]],
ID["EPSG",4326]]
Specifications
- Format
- OGC WKT 2 (2019)
- Crs
- WGS 84 geographic
- Epsg
- 4326
- Axis Order
- latitude, longitude (declared explicitly by ORDER)
- Has Authority Id
- true
- Multi Line
- true
- Line Endings
- LF
Testing contract
Expected to pass- Scenario
- Parse both WKT 1 and WKT 2 definitions of EPSG:4326 and compare what each says about axis order.
- Expected result
- Both resolve to EPSG:4326, but only the WKT 2 file states that latitude comes first — the WKT 1 file says nothing about order at all.
What is a .prj file?
A .prj file is the coordinate-reference-system sidecar of an Esri shapefile. It contains a single line of Well-Known Text describing the CRS: for a projected system, the projection method, its parameters, the linear unit, and the geographic system it is based on; for a geographic system, the datum, spheroid, prime meridian, and angular unit. Without it a shapefile's coordinates are just numbers.
How to use this file
Use an example .prj file to test CRS parsers and reprojection pipelines, checking that a WKT definition is matched to the right EPSG code and that the axis order and units are honoured rather than assumed.
How to use this file for testing
“PRJ — WGS 84 in WKT 2 (2019)” is a deterministic Novus Examples fixture for Geospatial, Conversion testing, Metadata testing. GeoJSON, GPX, and KML files with points, lines, polygons, and tracks — for testing map tools, route parsers, and geo importers.
Documented properties for this file: LF · OGC WKT 2 (2019). Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Geospatial fixtures publish one invented territory across formats, with the coordinate reference system and feature counts documented in specs. Convert or reproject and diff against the twin in the same group; edge-case geometries state exactly which assumption they are built to break.
Related files
- geojsonGeoJSON — Legacy 2008 `crs` Member (removed in RFC 7946)A FeatureCollection carrying the `crs` member from the 2008 GeoJSON specification. RFC 7946 removed it and fixed the CRS as WGS 84, so a modern reader should treat this as an ignorable foreign member — but plenty of exporters still write it and some readers still obey it.
- gpkgGeoPackage — Features Stored in Web Mercator (EPSG:3857)The same five towns stored as projected metres rather than degrees, with EPSG:3857 registered in gpkg_spatial_ref_sys and stamped into every geometry blob's header. Unlike GeoJSON, GeoPackage genuinely supports this — so it is the clean way to test that your reader honours the declared SRS instead of assuming 4326.
- kmlKestrel Bay Territory — KML TwinThe same 14 features as KML Placemarks, with the multi-point buoys expressed as a MultiGeometry and the two holed polygons using innerBoundaryIs. KML orders coordinates longitude-first like GeoJSON, which makes it the least surprising twin in this group.
- kmlKML — ExtendedData Untyped Data ElementsAttributes carried in `ExtendedData/Data` elements, which have names and display names but no declared types — every value is a string. Importers must infer that population is a number, and this is where a silently wrong inference starts.
- kmlKML — extrude With Three Different altitudeMode ValuesFour extruded points whose third coordinate means three different things depending on the `altitudeMode` beside it: ignored when clamped, height above terrain when relative, height above the ellipsoid when absolute. Copying the number without the mode changes what the data says.
- kmlKML — Nested Folders (three levels)Eight Placemarks arranged in three levels of Folder, the hierarchy KML uses for layer trees. GeoJSON has nothing equivalent, so a converter must either flatten and record the path or lose the structure entirely — and this file makes which one it did obvious.
Generated by generation/geospatial.py. Free for any use, no attribution required — license.