The Boston ArchiveBoston, Massachusetts

landmark · official boundary

Austin Block

A property designated a landmark by the Boston Landmarks Commission. At Exterior only (Parcel 3686).

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
180 square meters
Boundary
held as GeoJSON at /asset/48dd0e6bab5abece485ab26a333b84ed/austin-block.geojson — 809 bytes, exactly as accessioned

Map

A map of the boundary of Austin Block, a landmark in the record of Boston, Massachusetts, within Boston. The outline is an official boundary, promulgated by Boston Landmarks Commission. It encloses approximately 180 square meters.
Rendered by the archive, served as image/svg+xml at /asset/e9168eca0f19a345b5d40ae36e71ddc4/austin-block.svg — 1399 bytes, SHA-256 e9168eca0f19a345… · Open Data Commons Public Domain Dedication and Licence (PDDL) 1.0
The exact coordinates are held separately as /asset/48dd0e6bab5abece485ab26a333b84ed/austin-block.geojson (application/geo+json, 809 bytes, SHA-256 48dd0e6bab5abece…). 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 Austin Block, and what kind of boundary does the archive hold?

Austin Block 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 Austin Block?

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 Austin Block?

180 square meters, 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 Austin Block 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/e9168eca0f19a345b5d40ae36e71ddc4/austin-block.svg. The exact coordinates it was drawn from are served separately as application/geo+json at /asset/48dd0e6bab5abece485ab26a333b84ed/austin-block.geojson.

Attested by: Rendered by archive-ingest 0.1.0 from the boundary this archive holds; digest e9168eca0f19a345b5d40ae36e71ddc448054a54ef62480c96dc7b3e71cdf52a.

What does the wider world call Austin Block?

It asserts none, deliberately. 1 candidate was considered and not asserted: Q131685636 (declined) — the name matched an ALIAS of Q131685636, whose own label is "90-92 Main Street" — a different name, not this record's name wearing a qualifier. 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: Q131685636 — rdfs:label / skos:altLabel = 90-92 Main Street, decided 3 September 2026 by archive-ingest 0.1.0

What does the archive hold for Austin Block, and under what license?

The Boston Archive holds this record of Austin Block 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.

Related records

Identity

Identifier
urn:lemay:boston:entity:austin-block
Canonical URL
https://boston.fyi/place/austin-block
As JSON
https://boston.fyi/place/austin-block.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
127
Attribution
City of Boston
Rights as stated
Open Data Commons Public Domain Dedication and License (PDDL)

Transform ladder

#OperationDescriptionTool
1fetchretrieved the dataset's GeoJSON from the City of Boston open-data portalarchive-ingest 0.1.0
2normalizethe source's own name field became the record title; no name was supplied by the archivearchive-ingest 0.1.0
3reprojectthe source is WGS 84 (EPSG:4326); geometry was set to that SRID without alteration of coordinatesarchive-ingest 0.1.0
4externalize-boundaryThe boundary left the inline page graph and became two preserved holdings: the exact coordinates at /asset/48dd0e6bab5abece485ab26a333b84ed/austin-block.geojson and a static map rendered server-side at /asset/e9168eca0f19a345b5d40ae36e71ddc4/austin-block.svg. The stored geometry is unchanged; the record graph now addresses it instead of carrying it.archive-ingest 0.1.0