Property talk:P1976

Documentation

INEGI locality ID
identifier for a locality of Mexico

Represents

import and export of data (Q6007395)

Data type

External identifier

Template parameter

Wikipedia infobox parameters, if any; ex: "código" in es:Plantilla:Ficha de localidad

Domain

locality of Mexico (Q20202352) (note: this should be moved to the property statements)

Allowed values

[0-9]{9}

Example

Sisal (Q517463) → 310380004
no label (Q61259000) → 180190918
El Chino (Q61300588) → 260030090

Source

According to this template: external reference, Wikipedia list article, etc.

According to statements in the property:
https://www.inegi.org.mx/app/ageeml/

When possible, data should only be stored as statements

Formatter URL

https://www.inegi.org.mx/app/areasgeograficas/?ag=$1

Robot and gadget jobs

Not sure. But data can be imported from Spanish Wikipedia

Related to country

Mexico (Q96) (See 20 others)

See also

INEGI municipality ID (P3801)

Lists

Proposal discussion

Current uses

Total	203,844
Main statement	203,829	>99.9% of uses
Qualifier	3	<0.1% of uses
Reference	12	<0.1% of uses

Search for values

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

Distinct values: this property likely contains a value that is different from all other items. (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/P1976#Unique value, SPARQL (every item), SPARQL (by value)

Single value: this property generally contains a single value. (Help)

List of violations of this constraint: Database reports/Constraint violations/P1976#Single value, hourly updated report, SPARQL

Format “\d{9}”: value must be formatted using this pattern (PCRE syntax). (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/P1976#Format, SPARQL

Item “country (P17): Mexico (Q96)”: Items with this property should also have “country (P17): Mexico (Q96)”. (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/P1976#Item P17, search, 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/P1976#Item P131, search, 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/P1976#Entity types

Scope is as main value (Q54828448), as reference (Q54828450): 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/P1976#Scope, SPARQL

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

This property is being used by:

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

URL edit

Latest comment: 7 years ago1 comment1 person in discussion

(Notifying Tobias1984, with whom I talked about this property last year)

The URL used for this property, currently http://www.microrregiones.gob.mx/catloc/contenido.aspx?refnac=$1 has one big weakness: It only works for villages (localidades), INEGI IDs however also exist for the Mexican municipalities (municipios) and states (estados). For example:

http://www.microrregiones.gob.mx/catloc/contenido.aspx?refnac=270150060
This is the URL for Tapijulapa, a village somewhere in the Mexican state of Tabasco. The URL works fine.
http://www.microrregiones.gob.mx/catloc/contenido.aspx?refnac=27015
INEGI IDs follow a system: Digits number one and two represent the state, digits number three, four and five the municipality, digits number six, seven, eight and nine the village. This is to say that by cutting off the last four digits of a nine-digit ID, you can extract the municipality code of the municipality the given village is located in. This URL, using the INEGI code for the municipality of Tacotalpa, however doesn't offer any useful information, it only tells you that there is no information. The same is true for a URL which only uses the state ID:
http://www.microrregiones.gob.mx/catloc/contenido.aspx?refnac=27

The microrregiones database however does offer a way to point to a municipality. For this purpose, however, the code needs to be split:

http://www.microrregiones.gob.mx/catloc/LocdeMun.aspx?tipo=clave&campo=loc&ent=27&mun=015

And for a state the URL we could use looks like this:

http://www.microrregiones.gob.mx/catloc/LocdeMun.aspx?tipo=clave&campo=loc&ent=27

Consequently, different URLs for different input lenghts (two-digit, five-digit or nine-digit) are necessary.

Yet there is another database, where any INEGI code can be used as is resulting in a useful URL:

This, however, is only a beta URL. Comments? → «« Man77 »» 16:46, 13 January 2017 (UTC)Reply

Add topic