Property talk:P177

Documentation

crosses
obstacle (body of water, road, railway...) which this bridge (ferry, ford) crosses over or this tunnel goes under

Description

The item which this bridge or tunnel crosses, such as a river, sea, lake, valley or other obstacle.

Represents

crossing (Q62059481), river crossing (Q4350791)

Data type

Item

Template parameter

crosses in Infobox bridge

Domain

According to this template: architectural structure (Q811979)

According to statements in the property:
fixed construction (Q811430), ferry (Q25653), fictional building (Q15720793), ferry route (Q18984099), ford (Q12743), crossing (Q62059481) or crossing (Q10816681)

When possible, data should only be stored as statements

Allowed values

geographical feature (Q618123) (note: this should be moved to the property statements)

Example

Franco-Brazilian Binational Bridge (Q996255) → Oyapock (Q1541246)
Channel Tunnel (Q10257) → English Channel (Q34640)
Trans-Amazonian highway (Q1569903) → Amazonia (Q2841453)

Tracking: usage

Category:Pages using Wikidata property P177 (Q23909035)

Tracking: local yes, WD no

no label (Q101364626)

Lists

Proposal discussion

Current uses

Total	40,560
Main statement	40,496	99.8% of uses
Qualifier	62	0.2% of uses
Reference	2	<0.1% of uses

Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Type “fixed construction (Q811430), ferry (Q25653), fictional building (Q15720793), ferry route (Q18984099), ford (Q12743), crossing (Q62059481), crossing (Q10816681)”: item must contain property “instance of (P31)” with classes “fixed construction (Q811430), ferry (Q25653), fictional building (Q15720793), ferry route (Q18984099), ford (Q12743), crossing (Q62059481), crossing (Q10816681)” 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: bridge over valley (Q976622)
List of violations of this constraint: Database reports/Constraint violations/P177#Type Q811430, Q25653, Q15720793, Q18984099, Q12743, Q62059481, Q10816681, SPARQL

Value type “geographical feature (Q618123)”: This property should use items as value that contain property “instance of (P31), subclass of (P279)”. On these, the value for instance of (P31), subclass of (P279) should be an item that uses subclass of (P279) with value geographical feature (Q618123) (or a subclass thereof). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Passerelle de Saint-Antoine (Q187100)
List of violations of this constraint: Database reports/Constraint violations/P177#Value type Q618123, SPARQL

Item “instance of (P31)”: Items with this property should also have “instance of (P31)”. (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/P177#Item P31, search, SPARQL

Scope is as qualifier (Q54828449), as main value (Q54828448): the property must be used by specified way only (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/P177#Scope, SPARQL

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (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/P177#Entity types

Same value in P177 and in P2505
Exception for spiral bridge (Q7577756) items (Help)
Violations query:

SELECT ?item {     ?item wdt:P2505 ?value.     ?item wdt:P177 ?value.     FILTER NOT EXISTS {       ?item wdt:P31 wd:Q7577756     } }

List of this constraint violations: Database reports/Complex constraint violations/P177#Same value in P177 and in P2505

This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Clarification[edit]

Maybe I've been amiss in adding "body of water" and "obstacle" does cover everything; it's just that, as an English speaker, it temporarily threw me for a loop. But yes, if you're trying to travel by land from point a to point b and you must traverse a river, it is indeed an "obstacle." So please revert my edit if desired. Shawn in Montreal (talk) 22:33, 2 March 2013 (UTC)[reply]

Generally, I am just pulling text from wikipedia, the word obstacle is used here Bridge. Danrok (talk) 22:57, 2 March 2013 (UTC)[reply]

Indeed and that's fine. After I added "body of water" I believe Eric added it en francais. It's the only reason I'm not yanking it from my text: does no harm for now, I suppose. Shawn in Montreal (talk) 23:10, 2 March 2013 (UTC)[reply]

Tunnel?[edit]

We could extend this property for use on tunnel items, or should that be a different property? E.g. for Western Scheldt Tunnel -> Western Scheldt. SPQRobin (talk) 00:36, 9 September 2013 (UTC)[reply]

I think it can be safely extended to tunnels and to various other things (for instance roads that pass above another). --Zolo (talk) 16:10, 23 September 2013 (UTC)[reply]

Since nobody voiced opposition, I'm extending it to tunnels. SPQRobin (talk) 11:52, 26 October 2013 (UTC)[reply]

So, a road passes over a bridge over another road can use this property? And the road passning under the frist as well I assume? How about level road crossings? /Esquilo (talk) 20:39, 25 December 2013 (UTC)[reply]

Expending scope to allow statements about anatomy[edit]

anterior interosseous nerve (Q4771357) crosses Interosseous membrane of forearm (Q1692993) in a literal way. Currently this property is limited to architectural structures. I would want to expend it to all structures and allow structures as values as well.

Notified participants of WikiProject Medicine ChristianKl (talk) 21:46, 21 September 2016 (UTC)[reply]

@ChristianKl: Right, so the property was created to describe how bridges "cross" water, and in this example, a nerve "crosses" a membrane. Why do you think it is useful to use the same sort of property for both? Can you say something about why these uses are the same and how you think they might be different. Blue Rasberry (talk) 21:54, 21 September 2016 (UTC)[reply]

Okay, it seems I need another property for this purpose. ChristianKl (talk) 09:28, 22 September 2016 (UTC)[reply]

Mountains?[edit]

I have an item Mourne Wall (Q1543119) which crosses a mountain range (Q46831). Is that a valid statement? Also, the detail on which particular mountain tops it crosses is available. Can I represent this?

I have more problems with the fact that this is used on an item about a wall! Unlike a bridge, a tunnel or possibly a road, that wall was not designed first and foremost to cross an obstacle.Thierry Caro (talk) 21:58, 16 April 2017 (UTC)[reply]

crosses (P177) versus carries (P2505)[edit]

The item-requires-statement constraint (Q21503247) in this case is a simple tautology which for all type of bridge (Q12280) generate some thousand of constrain violation. It should be or wholly deleted or refined for non bridge (Q12280) items.Texaner (talk) 07:46, 22 July 2019 (UTC)[reply]

It seems to work fine on the sample bridge (Q996255). Do you have another one in mind? --- Jura 09:34, 22 July 2019 (UTC)[reply]

I agree, the item-requires-statement constraint (Q21503247) is counterproductive here because in many cases (especially all footbridges) there is no value (a specific highway or railway line) for carries (P2505). I will remove the constraint.--Leit (talk) 22:37, 16 February 2020 (UTC)[reply]

Name change suggestion: 'crosses or runs through'[edit]

It is a bit awkward to suggest a tunnel 'crosses' a unit of bedrock, but I don't think a separate property is necessary here --Middle river exports (talk) 23:13, 1 July 2022 (UTC)[reply]