Skip to content

fix(example-sets): public-space locations are objects with format geo:point - #4895

Merged
rubenvdlinde merged 1 commit into
developmentfrom
fix/public-space-geo-format
Oct 26, 2026
Merged

rubenvdlinde merged 1 commit into
developmentfrom
fix/public-space-geo-format

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

What

REFRESH-7 refused the whole Zuiddrecht set: public_space_register.json (#4891) declared its locations as "type": "geo", which is not a JSON Schema type. The Opis validator threw "type contains invalid json type: geo" for every public-space object (11 refusals).

The location property of tree, street-light, play-equipment and road-section is now {"type": "object", "format": "geo:point"}. That is the spelling GeoJsonGeometryValidator documents as the one a JSON Schema validator accepts, and it still runs the GeoJSON point check. Nothing else in the descriptor changed.

Test

ZuiddrechtPublicSpaceTest::testEveryObjectPassesTheValidator runs ValidateObject::validateObject() and GeoJsonGeometryValidator::validateObject() over all 13 public-space objects of the cast file.

  • Control: on the old descriptor it fails with InvalidKeywordException: type contains invalid json type: geo.
  • With this fix it passes.

The schema-shape test now detects the location by format: geo:point.

Verified

The dossiq catalogue read only type: geo for its Kaart view. The companion head fix/object-views-read-geo-format (5b6c07972) reads a geo type or format, so Boom, Lantaarnpaal, Speeltoestel and Wegen en paden keep "Kaart, Tabel".

Assisted-by: ClaudeCode:claude-opus-5-5

…:point

"type": "geo" is not a JSON Schema type, so the validator refused every
public-space object ("type contains invalid json type: geo") and with them
the Zuiddrecht set. A location is now {"type": "object", "format":
"geo:point"}, the spelling GeoJsonGeometryValidator reads. A test runs
ValidateObject and the GeoJSON check over all 13 objects.

Assisted-by: ClaudeCode:claude-opus-5-5
@rubenvdlinde
rubenvdlinde merged commit 8b85a70 into development Oct 26, 2026
9 of 10 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/openregister @ 51f4efa

Check PHP Vue Security License Tests
lint ✅
phpcs ✅
phpmd ❌
psalm ✅
phpstan ✅
phpmetrics ✅
eslint ✅
stylelint ✅
build ✅
check-specs ✅
test-l10n ✅
test-l10n-parity ✅
format ❌
check-schema-l10n ❌
composer ✅ ✅ 173/173
npm ❌ ✅ 648/648
app:check-code ⏭️
info.xml ✅
REUSE ✅
lockfile sync ✅
PHPUnit ❌
Newman ❌
Playwright ⏭️ deferred: E2E runs locally and on the promotion path only. This pull request targets development, so the suite is asked once per promotion into beta and main rather than once per push per open pull request. Run it locally with npx playwright test, or from the Actions tab on a branch with no open pull request into development.
Hydra gates ❌

Quality workflow — 2026-10-26 10:58 UTC

Download the full PDF report from the workflow artifacts.

rubenvdlinde added a commit that referenced this pull request Oct 26, 2026
…ted again (#4897)

An example set skipped every required register already on the instance,
so a schema fixed in the descriptor (public-space location type geo to
object + format geo:point, #4895) never reached an instance that had
installed the set. The set now re-imports a required register when its
descriptor ships a newer version than the instance holds
(RegisterDescriptorService::isBehind), and the public-space register and
its four changed schemas move to 1.0.1.

Assisted-by: ClaudeCode:claude-opus-5-5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant