landmark · official boundary
Fenway Park
A property designated a landmark by the Boston Landmarks Commission.
Place
official layer
An official boundary, promulgated by an authority with the power to draw it. It is not amended by anything on the vernacular layer.
- Filed by this archive as
- landmark
- Authority
- Boston Landmarks Commission
- Within
- Boston
- Area
- 3.04 hectares
- Boundary
- held as GeoJSON at
/asset/43f4759c264311b6b238690b550bf7e2/fenway-park.geojson— 779 bytes, exactly as accessioned
Map
image/svg+xml at /asset/c8d2e2a6dd372ef127d8100c9a474383/fenway-park.svg — 1379 bytes, SHA-256 c8d2e2a6dd372ef1… · Open Data Commons Public Domain Dedication and Licence (PDDL) 1.0The exact coordinates are held separately as
/asset/43f4759c264311b6b238690b550bf7e2/fenway-park.geojson (application/geo+json, 779 bytes, SHA-256 43f4759c264311b6…). The map is simplified for drawing; the boundary is not.Questions this record answers
Each answer is composed only from fields this record carries, and names the attestation for what it says. A question the record cannot answer from its own attested content is not asked here. Where a boundary is described as official it was promulgated by an authority with the power to draw it and is not amended by anything on the vernacular layer; where it is described as vernacular it is held by attestation alone and amends no official boundary.
Where is Fenway Park, and what kind of boundary does the archive hold?
Fenway Park is recorded as a landmark, within Boston. The archive holds its boundary on the official layer: promulgated by an authority with the power to draw it.
Attested by: City of Boston Open Data Portal (Analyze Boston), retrieved 2 September 2026, under Open Data Commons Public Domain Dedication and Licence (PDDL) 1.0.
Who drew the boundary of Fenway Park?
Boston Landmarks Commission promulgated it. A boundary with no promulgating authority is an assertion rather than a fact, and this archive files those separately, as claims.
Attested by: City of Boston Open Data Portal (Analyze Boston), retrieved 2 September 2026, under Open Data Commons Public Domain Dedication and Licence (PDDL) 1.0.
How large is Fenway Park?
3.04 hectares, computed from the boundary the archive holds and not quoted from elsewhere.
Attested by: City of Boston Open Data Portal (Analyze Boston), retrieved 2 September 2026, under Open Data Commons Public Domain Dedication and Licence (PDDL) 1.0.
What does the archive's map of Fenway Park show?
A static map of the boundary, rendered by the archive on a server and never in a reader's browser, served as image/svg+xml at /asset/c8d2e2a6dd372ef127d8100c9a474383/fenway-park.svg. The exact coordinates it was drawn from are served separately as application/geo+json at /asset/43f4759c264311b6b238690b550bf7e2/fenway-park.geojson.
Attested by: Rendered by archive-ingest 0.1.0 from the boundary this archive holds; digest c8d2e2a6dd372ef127d8100c9a474383b7c6d40d129760468d62d04dc1fe1ce8.
What does the wider world call Fenway Park?
It asserts none, deliberately. 1 candidate was considered and not asserted: Q49136 (declined) — name agrees but type does not: this record is filed in this archive's `landmark` class, and Q49136 is classed on Wikidata as stadium, baseball venue. A wrong sameAs is worse than none: under OWL semantics it instructs a consumer to merge two things into one, so the archive asserts an identity only where it can defend it and publishes the refusal where it cannot. Every verdict is in the reconciliation ledger at /reconciliation.
Attested by: Q49136 — rdfs:label / skos:altLabel = Fenway Park, decided 3 September 2026 by archive-ingest 0.1.0
What does the archive hold for Fenway Park, and under what license?
The Boston Archive holds this record of Fenway Park from City of Boston Open Data Portal (Analyze Boston), retrieved 2 September 2026, under Open Data Commons Public Domain Dedication and Licence (PDDL) 1.0 (public domain). 4 recorded transforms stand between the retrieved bytes and this record. Attribution is due to City of Boston.
Attested by: City of Boston Open Data Portal (Analyze Boston), retrieved 2 September 2026, under Open Data Commons Public Domain Dedication and Licence (PDDL) 1.0.
Candidates the archive declined
Identities that were considered and not asserted. They are published here rather than merely filed, because a decision nobody can see is indistinguishable from never having looked. A candidate is DECLINED where the archive weighed it and refused it, and HELD where the archive asserts it nowhere on this record — most often because it is asserted on the archive's principal record for the same place, and asserting it twice would instruct a consumer to merge two records the archive deliberately keeps apart. Each row states which, in its own words. A wrong sameAs is worse than none. Every verdict is in the reconciliation ledger.
- Wikidata —
Q49136· declinedMatched against: rdfs:label / skos:altLabel = Fenway ParkWhy: name agrees but type does not: this record is filed in this archive's `landmark` class, and Q49136 is classed on Wikidata as stadium, baseball venueMethod: label-type-geography within the P131=Q100 candidate pool · Decided 3 September 2026
Related records
- located in — Boston
Identity
- Identifier
- urn:lemay:boston:entity:fenway-park
- Canonical URL
- https://boston.fyi/place/fenway-park
- As JSON
- https://boston.fyi/place/fenway-park.json
- Version
- 1 · last changed 2 September 2026
Provenance
- Source
- City of Boston Open Data Portal (Analyze Boston) — source of record
- License
- Open Data Commons Public Domain Dedication and Licence (PDDL) 1.0 (public_domain)
- Retrieved
- 2 September 2026
- Source identifier
- 5
- Attribution
- City of Boston
- Rights as stated
- Open Data Commons Public Domain Dedication and License (PDDL)
Transform ladder
| # | Operation | Description | Tool |
|---|---|---|---|
| 1 | fetch | retrieved the dataset's GeoJSON from the City of Boston open-data portal | archive-ingest 0.1.0 |
| 2 | normalize | the source's own name field became the record title; no name was supplied by the archive | archive-ingest 0.1.0 |
| 3 | reproject | the source is WGS 84 (EPSG:4326); geometry was set to that SRID without alteration of coordinates | archive-ingest 0.1.0 |
| 4 | externalize-boundary | The boundary left the inline page graph and became two preserved holdings: the exact coordinates at /asset/43f4759c264311b6b238690b550bf7e2/fenway-park.geojson and a static map rendered server-side at /asset/c8d2e2a6dd372ef127d8100c9a474383/fenway-park.svg. The stored geometry is unchanged; the record graph now addresses it instead of carrying it. | archive-ingest 0.1.0 |