Aec Geometry¶
Deprecated
This module is deprecated and receives no further changes. It is replaced by adiro_geometry, which continues its version numbering. Every release of it stays published at its own IRI.
Foundational, domain-neutral module for geometry. It records where something sits on a drawing page as a bounding box, read against an explicit coordinate frame. Each box carries its own provenance and confidence. It reuses GeoSPARQL, is imported by the drawing modules, and is shared across use cases.
- IRI:
https://w3id.org/adiro/aec_geometry - Versioned IRI:
https://w3id.org/adiro/aec_geometry/2.0.0 - Imports:
aec_provenance
Interactive view¶
Dependencies¶
Arrows point from an ontology to the ontologies it imports; the current ontology is highlighted.
%%{init: {"themeCSS": ".base .nodeLabel,.base .nodeLabel p,.base text,.base tspan{fill:#9ecbff !important;color:#9ecbff !important}.current .nodeLabel,.current .nodeLabel p,.current text,.current tspan{fill:#16305f !important;color:#16305f !important}"} }%%
graph BT
aec_provenance["Aec Provenance"]
aec_geometry["Aec Geometry"]
aec_drawing_metadata["Aec Drawing Metadata"]
aec_common_symbols["Aec Common Symbols"]
aec_domain_common["Aec Domain Common"]
aec_facade_domain["Aec Facade Domain"]
aec_geometry --> aec_provenance
aec_drawing_metadata --> aec_geometry
aec_drawing_metadata --> aec_provenance
aec_common_symbols --> aec_drawing_metadata
aec_domain_common --> aec_drawing_metadata
aec_facade_domain --> aec_domain_common
aec_facade_domain --> aec_drawing_metadata
click aec_provenance "../aec_provenance/" "Aec Provenance reference page"
click aec_geometry "../aec_geometry/" "Aec Geometry reference page"
click aec_drawing_metadata "../aec_drawing_metadata/" "Aec Drawing Metadata reference page"
click aec_common_symbols "../aec_common_symbols/" "Aec Common Symbols reference page"
click aec_domain_common "../aec_domain_common/" "Aec Domain Common reference page"
click aec_facade_domain "../aec_facade_domain/" "Aec Facade Domain reference page"
classDef base fill:#16305f,stroke:#0e2247,stroke-width:2px,color:#9ecbff;
class aec_provenance,aec_drawing_metadata,aec_common_symbols,aec_domain_common,aec_facade_domain base;
classDef current fill:#f58a1f,stroke:#16305f,stroke-width:3px,color:#16305f;
class aec_geometry current;
Classes¶
Bounding Box¶
A rectangular region on a drawing page that locates something there, whether a model detected it or a person marked it - e.g. a title-block field's caption or value. Its coordinates are held as an xyxy string (bboxXYXY) and are meaningless without the CoordinateFrame it points at (inCoordinateFrame), which fixes the unit, coordinate space, origin, axes, page and exact PDF. A BoundingBox is itself an InferredEntity: it carries its own provenance (aprov:hasInferenceMeta - a detector, or a human annotator, told apart by aprov:inferredBy) and its own confidence (aprov:hasConfidence, the detector's score, absent for a hand-drawn box), which is DISTINCT from the confidence in a value read at that box. A subclass of GeoSPARQL geo:Geometry so it is recognised as a spatial shape.
- IRI:
https://w3id.org/adiro/aec_geometry#BoundingBox - Sub class of:
- Geometry
aprov:InferredEntity
Coordinate Frame¶
A page of a file read in one coordinate convention: the named coordinate space, the unit and the profile that defines it (the datatype properties below), for the page it describes (describesPage). A page can have more than one frame (the primary page_display_pt in points, and px for raster evidence), and each states only its convention: what is true of the page itself (its number, file, rotation and size) is on the aec_provenance:FilePage. Not an InferredEntity: a declared coordinate context, not a detection with its own confidence.
- IRI:
https://w3id.org/adiro/aec_geometry#CoordinateFrame
Geometry¶
Local typing stub for GeoSPARQL's Geometry class (authoritative definition at the rdfs:isDefinedBy IRI), declared here so reasoning stays offline. Used as the supertype of BoundingBox so an ADIRO box is recognised as a spatial shape; ADIRO adopts no GeoSPARQL CRS or spatial-query profile (deferred, GitHub issue #36).
- IRI:
http://www.opengis.net/ont/geosparql#Geometry
Object Properties¶
describesPage¶
The page (an aprov:FilePage) that this coordinate frame reads. The frames of a drawing are reached through its page: the path isOnPage / ^describesPage from the drawing, in aec_drawing_metadata.
- IRI:
https://w3id.org/adiro/aec_geometry#describesPage - Domain: Coordinate Frame
- Range:
aprov:FilePage
hasBoundingBox¶
The bounding box that locates a region on a drawing page. In UC-01 this is the title block's own region (a aec_drawing_metadata:Titleblock, like every MetadataContainer, may have a hasBoundingBox): the field values are read from within that single region and are not themselves individually localised. No rdfs:domain is asserted, so the same property serves any locatable region or element - e.g. UC-03 reference symbols, when that work extends this module.
- IRI:
https://w3id.org/adiro/aec_geometry#hasBoundingBox - Range: Bounding Box
inCoordinateFrame¶
The CoordinateFrame that interprets this geometry's coordinates. Required for a geometry to mean anything: the same xyxy numbers denote different regions in different frames, so equal coordinates alone never establish that two geometries are the same region.
- IRI:
https://w3id.org/adiro/aec_geometry#inCoordinateFrame - Domain: Geometry
- Range: Coordinate Frame
Datatype Properties¶
bboxXYXY¶
The rectangle as a string "[xmin, ymin, xmax, ymax]" in the coordinate frame's convention (xmin/ymin the top-left corner, xmax/ymax the bottom-right, under page_display_pt). The xyxy ordering is aligned to the Croissant cr:BoundingBox 'XYXY' format token, so an ADIRO box can be mapped to Croissant/CV formats by an exporter - ADIRO stores a page-point xyxy string, whereas Croissant expects a four-number array with a format declaration (background: GitHub issue #91). Interpret only together with inCoordinateFrame.
- IRI:
https://w3id.org/adiro/aec_geometry#bboxXYXY - Domain: Bounding Box
- Range:
xsd:string
coordinateSpace¶
The named coordinate convention that fixes the origin and axes. Primary: 'page_display_pt' - top-left origin, x rightwards, y downwards, in points. Native PDF user space and rendered-image pixels are different spaces and must be named as such; do not interchange the names.
- IRI:
https://w3id.org/adiro/aec_geometry#coordinateSpace - Domain: Coordinate Frame
- Range:
xsd:string
profileRef¶
Reference to the versioned coordinate profile that defines the named coordinateSpace in full (origin, axes and unit), so the convention is pinned rather than only implied by the space's name.
- IRI:
https://w3id.org/adiro/aec_geometry#profileRef - Domain: Coordinate Frame
- Range:
xsd:string
unit¶
The unit of the coordinate values: 'pt' for the primary page_display_pt space (1 pt = 1/72 inch), 'px' for raster/pixel evidence. Display-page coordinates in pt are independent of rendering DPI.
- IRI:
https://w3id.org/adiro/aec_geometry#unit - Domain: Coordinate Frame
- Range:
xsd:string
Open in OntoCanvas