Skip to main content

Place:Point

 Place:Point  node definition.

Description

Nodes with both the "Place" and "Point" labels, representing a variety of geospatial point locations, including points with an elevation level, often used in the recording of archaeological surveys and excavations. Represented in visualizations by HTML hex color #22223B:  Place:Point  with white (#FFFFFF) label text.

Analogy

A row in a "Points" spreadsheet or relational database table.

Example

Elevation points, general GPS points, etc.

CIDOC-CRM Mapping

MAYBE include a short summmary here, but leave the details for the designated CIDOC-CRM section.

Node Properties

Basic Properties

propertytypereq?uniq?descriptionexample(s)
------
uidstringYYUnique identifier as alphanumeric slug, prepended with “point-”"point-uj-0034"
namestringYYUnique name by which this Point is known in the database."UJ.Point.0034"
descriptionstringYnShort description of the Point recorded by this node. Will almost certainly be unique, but this is not enforced."UJAP benchmark at West Church."
locationWKTstring (WKT)nnREQUIRED FOR ALL NEW PLACES. The place's spatial geometry as a point, line, or (multi)polygon, expressed as a WKT string (the Open Geospatial Consortium standard for spatial geometry interchange)."POINT ((36.379595 32.319053))"
locationSRIDstringnnREQUIRED FOR ALL PLACES WITH A locationWKT. Spatial Reference Identifier (SRID, often identical to EPSG code) for the coordinate reference system in which the location is defined."4326" for WGS 84
locationConfidencestringnnREQUIRED FOR ALL PLACES WITH A locationWKT. The confidence level in the recorded location's accuracy and precision, selected from the Vocab:Confidence controlled vocabulary."moderate"

TENTATIVE Properties

(these may be changed to edge/relationships with Vocab terms or XX nodes, rather than directly stored as node properties)

propertytypereq?uniq?descriptionexample(s)
------
typestringnnThe type of Point recorded by this node entity, selected from the Vocab:PointType controlled vocabulary."benchmark"

System/Audit Properties

(these are not required/enforced by Neo4j but are populated via the UJAP Database web application; these could also be handled—perhaps more simply—by edge/relationship to AuditEvent nodes)

propertytypereq?uniq?descriptionexample(s)
proposedAtdatetimennTimestamp of entity proposal (initial database record creation)"2026-01-30T02:39:15.638Z"
proposedBystringnnEmail or userID of the person who created this entity's initial/proposed record"person@email.com"
approvedAtdatetimennTimestamp of entity proposal (initial database record creation)"2026-01-30T12:47:15.638Z"
approvedBystringnnEmail or userID of the person who created this entity's initial/proposed record"person@email.com"
committedAtdatetimennof node entity COMMIT (i.e., formal approval/ publishing to database by an admin)."2026-01-31T02:41:56.043Z"
committedBystringnnEmail or userID of the person who COMMITTED this node entity."person@email.com"
THE FOLLOWING RELATIONSHIPS REQUIRE ATTENTION/EDITING!

Relationships (outgoing)

 :Place:Point  ) ——[:FALLS_WITHIN_PLACE]——> (  :Place:Area  )

 :Place:Point  ) ——[:FALLS_WITHIN_PLACE]——> (  :Place:Context  )

 :Place:Point  ) ——[:FALLS_WITHIN_PLACE]——> (  :Place:Grid  )

 :Place:Point  ) ——[:FALLS_WITHIN_PLACE]——> (  :Place:Region  )

 :Place:Point  ) ——[:FALLS_WITHIN_PLACE]——> (  :Place:Site  )

 :Place:Point  ) ——[:FALLS_WITHIN_PLACE]——> (  :Place:StorageLocation  )

 :Place:Point  ) ——[:FALLS_WITHIN_PLACE]——> (  :Place:Trench  )

Relationships (incoming)

 :Activity:FieldSeason  ) ——[:TOOK_PLACE_AT]——> (  :Place:Point  )

 :Activity:FieldworkProcess  ) ——[:TOOK_PLACE_AT]——> (  :Place:Point  )

 :Activity:LabProcess  ) ——[:TOOK_PLACE_AT]——> (  :Place:Point  )

 :Activity:Sampling  ) ——[:TOOK_PLACE_AT]——> (  :Place:Point  )