Talk:Q83620

From Wikidata
Jump to navigation Jump to search

Autodescription — thoroughfare (Q83620)

description: transportation route connecting one location to another
Useful links:
Classification of the class thoroughfare (Q83620)  View with Reasonator View with SQID
For help about classification, see Wikidata:Classification.
Parent classes (classes of items which contain this one item)
Subclasses (classes which contain special kinds of items of this class)
thoroughfare⟩ on wikidata tree visualisation (external tool)(depth=1)
Generic queries for classes
Data to provide for this type of item
Property Data type description required
instance of (P31) Item that class of which this subject is a particular example and member; different from P279 (subclass of); for example: K2 is an instance of mountain; volcano is a subclass of mountain (and an instance of volcanic landform) . Possible values: TBD yes
located in the administrative territorial entity (P131) Item the item is located on the territory of the following administrative entity. Use P276 for specifying locations that are non-administrative places and for items about events. Use P1382 if the item falls only partially into the administrative entity. yes
named after (P138) Item entity or event that inspired the subject's name, or namesake (in at least one language). Qualifier "applies to name" (P5168) can be used to indicate which one no
coordinate location (P625) Geographic coordinates should usually contain at least two values, one with qualifier applies to part (P518) set to beginning (Q15053706) and one with applies to part (P518) set to end (Q15053716) yes
See also


I am wondering what subclasses of thoroughfare (Q83620) should be considered acceptable as value of instance of (P31). I think that for urban areas, we should avoid specialized items like "street" or "boulevard" and use thoroughfare (Q83620) directly instead. The reason for that is that they seem to be often arbitrary and hard to translate. For instance, thouroughfares in Beijing are usually called "streets" and those in Shanghai usually called "roads" for no apparent reason. – The preceding unsigned comment was added by Zolo (talk • contribs) at 14:19, 3 December 2013 (UTC).[reply]

@Zolo: could you please elaborate ? I'm doing the exact opposite and I put the most precise value ; in my scenario, if you want all the thoroughfares, you could easily join the subclasses but in your scenario, if you want a specific subclasses, it would be nearly impossible to split. I understand that the classes are sometimes arbitrary and inconsistent, but that just how messy reality is (shikata ga nai (Q1717210)…). Cdlt, VIGNERON (talk) 10:57, 30 August 2016 (UTC)[reply]
@VIGNERON: The distinction between "street", "avenue", "boulevard" etc. seems very fuzzy with . In practice, I suppose we would choose one of them just based "avenue" we use Ateliers Germain (Q754093) even if it does not have any observable difference with a street (Q79007) nearby. For French or German, etc. that might work all right, as there are fairly conventional translations "rue" = "street" = "Strasse". For other languages, that can be more wonky. At least zh <-> en translations are very inconsistnt.
But I guess that does not matter that much, as long as every thing is thoroughfare (Q83620) all right. --Zolo (talk) 12:47, 30 August 2016 (UTC)[reply]

The type thoroughfare (Q83620) can be given a property located in the administrative territorial entity (P131).

However there are frequent cases where the same thoroughfare (Q83620) is part of several distinct administrative units (different cities, different suburbs of the same city).

As we can use located in the administrative territorial entity (P131) only once, we have to fallback to use a larger administrative unit, which is insufficient to locate the instance of thoroughfare (Q83620).

For this reason, I used part of (P361) to enumerate a list of more precise administrative units. But here again this is not precise enough.

What I did was to qualify each listed part of (P361) with a qualifier to indicate the relevant house numbers, using a (partial) address with street address (P6375) (reduced to just the house number, giving the highway name is not needed, but giving the city name, ans possibly the applicable postal code or zip code may still be needed if the highway is shared between two cities).

  • For a case inside the same municipality see La Canebière (Q2554649): we need to specify the administrative quarter (which is sufficient to also specify the administrative municipal arrondissement that each quarter belongs to).
  • For the case where a highway is shared by two municipalities, the highway could be separated into separate items, one per municipality (in France, these highways have separate highway codes) and groupe them in a "super" highway item that would have NO municipality indicated in located in the administrative territorial entity (P131), but only a larger region (sometimes a full country, or even no country at all when the highway separates two countries (e.g. along the border between France and Belgium: even if this is the same physical highway, the country border may separate some addresses along the highway in two parts, and they may have different coexisting names depending on the country).

But using street address (P6375) for indicating a range of addresses may be seen as a hack here, because I used only a partial addresse (indicating the full address would pollute with redundant repeeated data inside each listed adminsitrative unit listed for the highway.

I'd like to be able to specify a "applies to" property, applies to jurisdiction (P1001), but this propery requires selecting a single item, so it is not applicable to a range or a set of addresses. The only propery that allows a "free-form" input that I dound was street address (P6375), and it has an extra problem: we need to specify the language and even if I selected French in La Canebière (Q2554649), what I want to represent is independant of the language.

So this raises two questions:

Thanks. Verdy p (talk) 11:10, 4 June 2020 (UTC)[reply]