Travel Mapping
Highway Data Discussion => Updates to Highway Data => Topic started by: neroute2 on November 14, 2019, 09:08:17 am
-
On 29 January 2016, it ceased to be the Federal District (Spanish: Distrito Federal or D.F.) and is now officially known as Ciudad de México (or CDMX), with a greater degree of autonomy. (https://en.wikipedia.org/wiki/Mexico_City)
This would mean renaming the MEX-DF (https://github.com/TravelMapping/HighwayData/tree/master/hwy_data/MEX-DF) folder and the files within from mexdf* to mexcdmx*, as well as changing any references to the city limits.
Edit: "MEX-DF:" added to subject
-
I don't remember where but we discussed the Mexican region names anywhere. We usually go with ISO 3166: https://en.wikipedia.org/wiki/ISO_3166-2:MX
Please don't jump the gun with changing, we should discussed first. I'm in favor of changing it to ISO names when the whole revision of active Mexican systems is done - on activation of the new systems.
-
I'm in favor of changing it to ISO names when the whole revision of active Mexican systems is done - on activation of the new systems.
Which would require a whole bunch of changes after I make the new files - changes to file names, prefixes for state routes, labels for state lines :(
-
Yes, but the region name change is much less effort for users than the effort to map their travels to the new routes. When we wanna change the name of one region, we should do it for all regions.
-
Are you volunteering to go through all the files I haven't made yet and change the state abbreviations in the future? Otherwise I see no reason I shouldn't start using the new abbreviations now in waypoint labels.
-
Are you volunteering to go through all the files I haven't made yet and change the state abbreviations in the future? Otherwise I see no reason I shouldn't start using the new abbreviations now in waypoint labels.
Sure, it's just 155 files in 69 folders. A quicky when doing offline. It would be awful doing it directly on Github.
Maybe yakra could do it even quicker with some smart code? Maybe an automated renaming of the files (and folders).
The file content is no issue at all (~10 minutes job for me)
-
It's also worth thinking about whether we should use the abbreviations the states themselves use on shields. Every state has a standard abbreviation for the normal state shield.
-
I don't remember where but we discussed the Mexican region names anywhere. We usually go with ISO 3166: https://en.wikipedia.org/wiki/ISO_3166-2:MX
Please don't jump the gun with changing, we should discussed first. I'm in favor of changing it to ISO names when the whole revision of active Mexican systems is done - on activation of the new systems.
15 out of 32 codes had to be changed (marked with '-->'). In addition one region name:
MEX;Mexico;MEX;NA;Country
MEX-AGS --> MEX-AGU;Aguascalientes;MEX;NA;State
MEX-BC --> MEX-BCN;Baja California;MEX;NA;State
MEX-BCS;Baja California Sur;MEX;NA;State
MEX-CAM;Campeche;MEX;NA;State
MEX-CHIH --> MEX-CHH;Chihuahua;MEX;NA;State
MEX-CHIS --> MEX-CHP;Chiapas;MEX;NA;State
MEX-COAH --> MEX-COA;Coahuila;MEX;NA;State
MEX-COL;Colima;MEX;NA;State
MEX-DF --> MEX-MEX;Distrito Federal;MEX;NA;Federal District
MEX-DGO --> MEX-DUR;Durango;MEX;NA;State
MEX-EMEX --> MEX-CMX;Estado de Mexico --> Ciudad de Mexico;MEX;NA;State
MEX-GRO;Guerrero;MEX;NA;State
MEX-GTO --> MEX-GUA;Guanajuato;MEX;NA;State
MEX-HGO --> MEX-HID;Hidalgo;MEX;NA;State
MEX-JAL;Jalisco;MEX;NA;State
MEX-MICH --> MEX-MIC;Michoacán;MEX;NA;State
MEX-MOR;Morelos;MEX;NA;State
MEX-NAY;Nayarit;MEX;NA;State
MEX-NL --> MEX-NLE;Nuevo León;MEX;NA;State
MEX-OAX;Oaxaca;MEX;NA;State
MEX-PUE;Puebla;MEX;NA;State
MEX-QRO --> MEX-QUE;Queretaro;MEX;NA;State
MEX-QROO --> MEX-ROO;Quintana Roo;MEX;NA;State
MEX-SIN;Sinaloa;MEX;NA;State
MEX-SLP;San Luis Potosí;MEX;NA;State
MEX-SON;Sonora;MEX;NA;State
MEX-TAB;Tabasco;MEX;NA;State
MEX-TAM;Tamaulipas;MEX;NA;State
MEX-TLAX --> MEX-TLA;Tlaxcala;MEX;NA;State
MEX-VER;Veracruz;MEX;NA;State
MEX-YUC;Yucatán;MEX;NA;State
MEX-ZAC;Zacatecas;MEX;NA;State
-
After thinking about it, I would oppose changing away from the abbreviations used on state shields (I'll make a full list of these when I'm not on my phone). The only two states or equivalents that can't use this abbreviation are EMEX/MEX (ambiguous since we also use that for federal highways) and DF/CDMX (no state routes).
-
Here are the abbreviations used on signs:
AGS (no current files)
BC (no change)
BCS (no change)
CAM (no change)
CHIH (no change)
CHIS (no change)
COAH (no change)
COL (no change)
DGO (no change)
GRO (no change)
GTO (no change)
HGO (no change)
JAL (no change)
MEX (needs to stay EMEX to avoid ambiguity; a few signs (https://www.google.com/maps/@19.2959798,-98.8726332,3a,20.7y,260.98h,101.44t/data=!3m6!1e1!3m4!1sCoZPneEiYIr-3vr7IByC9w!2e0!7i13312!8i6656) not posted by the state use EDO MEX)
MICH (no change)
MOR (no change)
NAY (no change)
NL (no change)
OAX (no change)
PUE (no change)
QRO (no change)
Q. ROO (no change from QROO)
SIN (no change)
SLP (no change)
SON (no change)
TAB (no change)
TAM or TAMPS (no change from TAM)
TLAX (no change)
VER (no change)
YUC (no change)
ZAC (no change)
So the only change I support is DF to CDMX.
-
I'm not aware of any exception to ISO codes - except of Mexico of course.
-
I'm not aware of any exception to ISO codes - except of Mexico of course.
Are you aware of any other countries that prominently use abbreviations on their subnational routes?
-
I'm not aware of any exception to ISO codes - except of Mexico of course.
Are you aware of any other countries that prominently use abbreviations on their subnational routes?
I don't know about Australia, Canada, China, India and USA but Germany, France, Spain and UK don't. However, all European countries - which are often TM regions - do. And it's mostly different to ISO.
What does the master of regions.csv think about it, Si?
-
Are you aware of any other countries that prominently use abbreviations on their subnational routes?
Spain for their autonomous community routes (as michih should know!)
And there's discrepancies between what's on the roads, and ISO has as codes.
Andalusia: ESP-AN, abbrev A
Aragon: ESP-AR, abbrev ARA-, A
Asturias: ESP-AS, abbrev AS
Cantabria: ESP-CB, abbrev CA
Castille and Leon: ESP-CL, abbrev CL
Castilla-La Mancha: ESP-CM, abbrev CM
Canary Islands: ESP-CN, abbrevs FV, GC, GM, HI, LP, LZ, TF (done at lower level, islands)
Catalonia: ESP-CT, abbrev C
Galacia: ESP-GA, abbrevs AG (community-wide motorways), AC, LU, OU, PO (done at lower level)
Balearic Islands: ESP-IB, abbrevs EI, Ma (done at lower level, islands)
Region of Murcia: ESP-MC, abbrev RM
Community of Madrid: ESP-MD, abbrev M
Navarre: ESP-NC, abbrev NA
Basque Country: ESP-PV, abbrevs A, BI, GI (done at lower level)
La Rioja: ESP-RI, abbrev LR
Valencian Community: ESP-VC, abbrev CV
Also, for something you might be familiar with: Michigan's state routes are M-xx, not MIxx.
-
Of course I know. I thought that I read "subnational borders" instead of "subnational routes". Sorry......
Edit: German states use L, S or St but never BB, BE, BW, BY,... All German districts use K except of Bavarian districts which use district abbreviations like A, AB,..
-
Are you aware of any other countries that prominently use abbreviations on their subnational routes?
Spain for their autonomous community routes (as michih should know!)
That's pretty horrible. In what universe is this (https://www.google.com/maps/@43.2896317,-3.9595372,3a,15y,167.48h,83.2t/data=!3m6!1e1!3m4!1su9JZ4Vp26cFUhaY6Fg16IA!2e0!7i13312!8i6656) CB-170?
Edit: I see, the route name is still CA170 (http://travelmapping.net/hb/index.php?units=miles&u=neroute2&r=espcb.ca170). Changing still seems like additional confusion with no benefit. Someone traveling these roads is likely not going to know the ISO abbreviation, unless they've looked it up.
-
Changing still seems like additional confusion with no benefit.
Likewise with the DF -> CDMX change, surely?
My point is that we don't necessarily match subdivision abbrevations with subdivision-derived prefixes.
-
Changing still seems like additional confusion with no benefit.
Likewise with the DF -> CDMX change, surely?
That's an actual change of name of the subdivision. There no longer is a DF.
-
I still think that we should change it. I still volunteer to update the files in the HB repo.
I don't remember where but we discussed the Mexican region names anywhere. We usually go with ISO 3166: https://en.wikipedia.org/wiki/ISO_3166-2:MX
Please don't jump the gun with changing, we should discussed first. I'm in favor of changing it to ISO names when the whole revision of active Mexican systems is done - on activation of the new systems.
15 out of 32 codes had to be changed (marked with '-->'). In addition one region name:
MEX;Mexico;MEX;NA;Country
MEX-AGS --> MEX-AGU;Aguascalientes;MEX;NA;State
MEX-BC --> MEX-BCN;Baja California;MEX;NA;State
MEX-BCS;Baja California Sur;MEX;NA;State
MEX-CAM;Campeche;MEX;NA;State
MEX-CHIH --> MEX-CHH;Chihuahua;MEX;NA;State
MEX-CHIS --> MEX-CHP;Chiapas;MEX;NA;State
MEX-COAH --> MEX-COA;Coahuila;MEX;NA;State
MEX-COL;Colima;MEX;NA;State
MEX-DF --> MEX-MEX;Distrito Federal;MEX;NA;Federal District
MEX-DGO --> MEX-DUR;Durango;MEX;NA;State
MEX-EMEX --> MEX-CMX;Estado de Mexico --> Ciudad de Mexico;MEX;NA;State
MEX-GRO;Guerrero;MEX;NA;State
MEX-GTO --> MEX-GUA;Guanajuato;MEX;NA;State
MEX-HGO --> MEX-HID;Hidalgo;MEX;NA;State
MEX-JAL;Jalisco;MEX;NA;State
MEX-MICH --> MEX-MIC;Michoacán;MEX;NA;State
MEX-MOR;Morelos;MEX;NA;State
MEX-NAY;Nayarit;MEX;NA;State
MEX-NL --> MEX-NLE;Nuevo León;MEX;NA;State
MEX-OAX;Oaxaca;MEX;NA;State
MEX-PUE;Puebla;MEX;NA;State
MEX-QRO --> MEX-QUE;Queretaro;MEX;NA;State
MEX-QROO --> MEX-ROO;Quintana Roo;MEX;NA;State
MEX-SIN;Sinaloa;MEX;NA;State
MEX-SLP;San Luis Potosí;MEX;NA;State
MEX-SON;Sonora;MEX;NA;State
MEX-TAB;Tabasco;MEX;NA;State
MEX-TAM;Tamaulipas;MEX;NA;State
MEX-TLAX --> MEX-TLA;Tlaxcala;MEX;NA;State
MEX-VER;Veracruz;MEX;NA;State
MEX-YUC;Yucatán;MEX;NA;State
MEX-ZAC;Zacatecas;MEX;NA;State