Wikidata:Property proposal/lighthouse range
Jump to navigation
Jump to search
lighthouse range
[edit]| Description | the distance at which the light can be seen. If the light has colors, there will be several ranges, one for each color. It's usually given in nautical miles (USCG, NGA, and Admiralty light lists, at least). [1] |
|---|---|
| Data type | Quantity |
| Template parameter | range in https://en.wikipedia.org/wiki/Template:Infobox_lighthouse |
| Domain | lighthouses |
| Allowed values | distance usually in nautical miles |
| Allowed units | usually in nautical miles |
| Example | w:Baltimore Harbor Light > 7 nautical miles (applies to part: white light) |
| Source | infobox |
Comment needed for w:Template:Infobox_lighthouse.
--- Jura 13:17, 13 June 2016 (UTC)- Note discussion at Property talk:P2073. @Thryduulf, Thierry Caro, TomT0m. --Izno (talk) 13:56, 13 June 2016 (UTC)
- Might be desirable to back this off to "light range/range of light" as this may be valuable outside the lighthouse domain? Is this maximum range without weather effects? --Izno (talk) 13:57, 13 June 2016 (UTC)
- I would definitely back units off to any units of distance. --Izno (talk) 13:58, 13 June 2016 (UTC)
Support. We would probably benefit from the proposal being slightly widened to include any signal that may be emitted by an object. But even without that move, I support this. Thierry Caro (talk) 14:14, 13 June 2016 (UTC)- Support I would have proposed this myself :) I do think that broadening the scope will serve this and other purposes well. Susannaanas (talk) 15:37, 13 June 2016 (UTC)
- Support, although I would prefer the widening of the property per Izno. On the other hand, I would also prefer to just allow one (SI) unit, possibly metre (Q11573) (as base unit) or kilometre (Q828224) as "practical" unit. This allows easier unit conversions and the ability to do comparisons and math in SPARQL. (This is a general comment that applies to most properties.) --Srittau (talk) 16:09, 13 June 2016 (UTC)
- I'd rather avoid conversion being done before adding values to a statement. -- Jura 16:21, 13 June 2016 (UTC)
- Do you care to state your reasons for that opinion? --Srittau (talk) 16:29, 13 June 2016 (UTC)
- It can introduce inaccuracy and not easily detectable discrepancies to a source.
--- Jura 16:31, 13 June 2016 (UTC)- Fair points. Maybe at some point in the future, Wikibase can support certain types of units natively and convert them internally to a common representation, so we could get the best of both worlds. --Srittau (talk) 17:30, 13 June 2016 (UTC)
- It can introduce inaccuracy and not easily detectable discrepancies to a source.
- Do you care to state your reasons for that opinion? --Srittau (talk) 16:29, 13 June 2016 (UTC)
- I'd rather avoid conversion being done before adding values to a statement. -- Jura 16:21, 13 June 2016 (UTC)
- "electromagnetic radiation range"? Would apply to models of radios then. --Izno (talk) 16:17, 13 June 2016 (UTC)
- From a user perspective I would prefer to be able to input both km and nautical miles. /Susannaanas (talk) 18:00, 13 June 2016 (UTC)
Oppose a property this specific, but I would Support "range of light", "range of signal" or similar broad properties per my comments at Property talk:P2073. Thryduulf (talk) 22:25, 13 June 2016 (UTC)
@Jura1, Thierry Caro, Susannaanas, Srittau, Izno, Thryduulf: 
Done Now lighthouse range (P2929). Make good use of it. --Lymantria (talk) 20:27, 22 June 2016 (UTC)
- @Lymantria: I think there is support for a wider property. --Izno (talk) 11:24, 23 June 2016 (UTC)
- @Izno: The property was widened, although only slightly. More discussion and precision on how to widen might take place at the property talk page. I did not see an example of how a more wide "range of light" should be used. Lymantria (talk) 12:27, 23 June 2016 (UTC)