Property talk:P2923
Jump to navigation
Jump to search
Documentation
focal height
height of the lamp of a lighthouse from water level
height of the lamp of a lighthouse from water level
[create Create a translatable help page (preferably in English) for this property to be included here]
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
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 reportType “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
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
List of violations of this constraint: Database reports/Constraint violations/P2923#Item P17, SPARQL
Item “located in the administrative territorial entity (P131)”: Items with this property should also have “located in the administrative territorial entity (P131)”. (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 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
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
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
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Subproperty
[edit]Shouldn't this property be a subproperty of elevation above sea level (P2044)? Lymantria (talk) 06:37, 23 June 2016 (UTC)
Double constraint
[edit]Hi,
Right now, there is two time more-or-less the same constraint :
⟨ P2923 ⟩ property constraint (P2302) ⟨ item-requires-statement constraint (Q21503247) ⟩
property (P2306) ⟨ P31 ⟩
item of property constraint (P2305) ⟨ lighthouse (Q39715) ⟩
property (P2306) ⟨ P31 ⟩
item of property constraint (P2305) ⟨ lighthouse (Q39715) ⟩
which is very narrow and limitative to lighthouses using instance of (P31) = lighthouse (Q39715)
and
⟨ P2923 ⟩ property constraint (P2302) ⟨ subject type constraint (Q21503250) ⟩
class (P2308) ⟨ lighthouse (Q39715) ⟩
relation (P2309) ⟨ instance of (Q21503252) ⟩
class (P2308) ⟨ lighthouse (Q39715) ⟩
relation (P2309) ⟨ instance of (Q21503252) ⟩
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)
- 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)