Skip to content
Testaroo
geojson1.5 KB

GeoJSON: Non-ASCII Property Values

Four features whose labels are written in Latin with diacritics, katakana, right-to-left Arabic, and a decomposed combining sequence: all stored as raw UTF-8 rather than \u escapes. Shapefile DBF export is where these usually turn into question marks.

GeospatialEncoding detectionJSON parsing
Preview, first 50 linesgeojson
{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "id": "u-1",
      "properties": {
        "name": "Kestrel Bay",
        "localName": "Baie du Cresserelle",
        "script": "Latin with diacritics",
        "note": "café, naïve, Ångström"
      },
      "geometry": {
        "type": "Point",
        "coordinates": [
          -12.482,
          47.064
        ]
      }
    },
    {
      "type": "Feature",
      "id": "u-2",
      "properties": {
        "name": "Marram",
        "localName": "マラム",
        "script": "Japanese katakana",
        "note": "地図テスト"
      },
      "geometry": {
        "type": "Point",
        "coordinates": [
          -12.3915,
          47.112
        ]
      }
    },
    {
      "type": "Feature",
      "id": "u-3",
      "properties": {
        "name": "Holloway",
        "localName": "هولواي",
        "script": "Arabic (right-to-left)",
        "note": "اختبار الخريطة"
      },
      "geometry": {
        "type": "Point",
        "coordinates": [
          -12.551,
… 74 lines total: download for the full file.

Specifications

Format
GeoJSON (RFC 7946)
Crs
WGS 84 (EPSG:4326)
Coordinate Order
longitude, latitude
Encoding
UTF-8
Line Endings
LF
Features
4
Bom
false
Scripts
Latin, Japanese katakana, Arabic, combining marks
Escaped
false
Valid
true

Testing contract

Expected to pass
Scenario
Round-trip the collection through a format with its own encoding declaration, such as shapefile with a .cpg sidecar.
Expected result
All four labels survive byte-for-byte; the decomposed sequence stays decomposed rather than being silently normalised.

What is a .geojson file?

GeoJSON is a JSON-based format for encoding geographic data structures such as points, lines, and polygons, along with their properties. It uses WGS84 longitude-latitude coordinates and standard feature and feature-collection objects. It is a common interchange format for web mapping and GIS.

How to use this file

Use an example GeoJSON file to test geometry parsing, coordinate handling, and mapping libraries or GIS pipelines that render or analyze spatial features.

How to use this file for testing

“GeoJSON: Non-ASCII Property Values” is a deterministic Testaroo fixture for Geospatial, Encoding detection, JSON parsing. 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: UTF-8 · LF · GeoJSON (RFC 7946). 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.

Code examples

import geopandas as gpd

gdf = gpd.read_file("properties-unicode.geojson")
print(gdf.head())
print(gdf.crs)

Generated by generation/geospatial.py. Free for any use, no attribution required, license.

Related files