Property talk:P2923

From Wikidata
Jump to navigation Jump to search

Documentation

focal height
height of the lamp of a lighthouse from water level
Descriptionheight of the lamp of a lighthouse from sea level
Representsfocal height of lighthouse (Q1409551)
Data typeQuantity
Template parameter|focalheight= in en:Template:Infobox_lighthouse
Domain
According to this template: lighthouse (Q39715)
According to statements in the property:
lighthouse (Q39715), lighthouse light (Q106975467) or beacon (Q7321258)
When possible, data should only be stored as statements
Allowed values1 ≤ 𝓧 ≤ 530
Allowed unitsmetre (Q11573) or foot (Q3710)
ExampleBengtskär lighthouse (Q3737012) → 51 metre
Cape Canaveral Light (Q5034639) → 137 foot
Tracking: usageCategory:Pages using Wikidata property P2923 (Q28648934)
See alsolighthouse range (P2929), height (P2048), light characteristic (P1030), luminous intensity (P3041)
Lists
Proposal discussionProposal discussion
Current uses
Total7,273
Main statement7,19899% of uses
Qualifier751% of uses
[create Create a translatable help page (preferably in English) for this property to be included here]
Units: “metre (Q11573), foot (Q3710): value unit must be one of listed. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2923#Units
Range from “1” to “530”: values should be in the range from “1” to “530”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P2923#Range, hourly updated report
Type “lighthouse (Q39715), lighthouse light (Q106975467), beacon (Q7321258): item must contain property “instance of (P31)” with classes “lighthouse (Q39715), lighthouse light (Q106975467), beacon (Q7321258)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: no label (Q42308845)
List of violations of this constraint: Database reports/Constraint violations/P2923#Type Q39715, Q106975467, Q7321258, SPARQL
Item “country (P17): Items with this property should also have “country (P17)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2923#Item P17, SPARQL
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2923#Item P131, SPARQL
Item “light characteristic (P1030): Items with this property should also have “light characteristic (P1030)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2923#Item P1030, SPARQL
Item “coordinate location (P625): Items with this property should also have “coordinate location (P625)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2923#Item P625, SPARQL
Item “inception (P571): Items with this property should also have “inception (P571)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2923#Item P571, SPARQL
Item “located in or next to body of water (P206): Items with this property should also have “located in or next to body of water (P206)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2923#Item P206, SPARQL

Subproperty

[edit]

Shouldn't this property be a subproperty of elevation above sea level (P2044)? Lymantria (talk) 06:37, 23 June 2016 (UTC)[reply]

✓ Done Lymantria (talk) 08:36, 2 July 2016 (UTC)[reply]

Double constraint

[edit]

Hi,

Right now, there is two time more-or-less the same constraint :

⟨ P2923 ⟩ property constraint (P2302) View with SQID ⟨ item-requires-statement constraint (Q21503247)  View with Reasonator View with SQID ⟩
property (P2306) View with SQID ⟨ P31 ⟩
item of property constraint (P2305) View with SQID ⟨ lighthouse (Q39715)  View with Reasonator View with SQID ⟩

which is very narrow and limitative to lighthouses using instance of (P31) = lighthouse (Q39715)

and

⟨ P2923 ⟩ property constraint (P2302) View with SQID ⟨ subject type constraint (Q21503250)  View with Reasonator View with SQID ⟩
class (P2308) View with SQID ⟨ lighthouse (Q39715)  View with Reasonator View with SQID ⟩
relation (P2309) View with SQID ⟨ instance of (Q21503252)  View with Reasonator View with SQID ⟩

which is the same idea but more flexible and allow to check the lighthouses not using instance of (P31) = lighthouse (Q39715).

I removed the first but Esquilo reverted me and asked for explanations here. Here they are, I can give more if needed.

Cdlt, VIGNERON (talk) 15:02, 20 December 2017 (UTC)[reply]

  • It's different. The problem with the type constraint is that some applications use just that and others don't support it fully. Is there a lighthouse where you were unhappy with the result?
    --- Jura 15:16, 20 December 2017 (UTC)[reply]