Diferencia entre revisiones de «MapRaid San Luis Potosí 2018 Ver historial

Locking standards
VisualWikitexto
m (Capitalize Return to the Junction Style Guide)
(Página creada con «{{mbox|image=40px |text=El MapRaid será del '''14 al 29 de mayo del 2018'''}} == Misión == Los objetivos principales son: *'''Depurar los {{blue|URs,...»)
Línea 1: Línea 1:
{{construction
{{mbox|image=[[File:clock.png|40px]]
| contact    = http://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7009939
|text=El MapRaid será del '''14 al 29 de mayo del 2018'''}}
| contacttype = user
| draft      = yes
| open        = no
| revision    = yes
| section    = yes
| talk        = yes
}}


{{ReturnTo | Junction_Style_Guide | the Junction Style Guide}}
== Misión ==
Los objetivos principales son:


== Three-way ==
*'''Depurar los {{blue|URs, PURs}}.'''
*'''Asegurar la conectividad y numeración de las carreteras federales y estatales.'''
*'''Dar de alta ciudades y poblados.'''
*'''Aumentar los segmentos con límites de velocidad.'''
*'''Dar de alta y actualizar Gasolineras.'''


=== Right angles ===
 
{| class="Wikitable floatright"
{{mbox
| [[Image:Jct_3_90_ex.png|border]]
| type = notice
| [[Image:Jct_3_90.png|border|x199px]]
| text = '''Cualquier edición para mejorar el mapa es bienvenida, pero si tienes duda en algo, contacta con los líderes de grupo.'''}}<br>
 
== Áreas del MapRaid ==
Serán '''<big>3 Equipos</big>''', con sus respectivos líderes.
 
 
 
[[File:Quintana Roo MR.png|600px]]
 
== Editores Locales ==
 
{{Username|DavidAbarca}} -  Supervisor Región Sureste
 
{{Username|jisaacgmx}} -  Area Manager
 
{{Username|janoteweb}} -  Conoce algunas zonas del estado
 
== {{red|IMPORTANTE}}==
{{mbox
| type = warning
| text = '''{{red|¡¡ PROHIBIDO HACER EDICIONES MASIVAS únicamente con la finalidad de obtener PUNTOS !!}}''' Esto se vigilará durante TODO el MapRaid.}}<br>
 
* De confirmarse este tipo de actividad, '''{{red|se dará de baja del mapraid y se restringirá su actividad para futuros eventos.}}'''
 
== Ediciones del Mapa ==
=== Tipo de Segmentos ===
 
{{Locking Standard Mexico|title=Area Urbana|Fwy=5|Ramp=4|MH=4|mH=3|PS=2|Street=1|title2=Area Rural|Fwy2=5|Ramp2=4|MH2=4|mH2=2|PS2=1|Street2=1|RR=4}}
 
*Al bajar de nivel algún segmento y terminar la edición, '''pide nuevamente SUBIR el nivel del segmento.'''
 
 
=== Límites de Velocidad ===
<big>'''Quintana Roo:'''</big>
{| border="1" class="wikitable"
!colspan="4" bgcolor="#387fb8"|Límites de Velocidad
|- style="text-align: center;"
|'''''Carreteras'''''
|km/hr
|-
| Autopista (FW) || 110
|-
| Rampa || 40
|-
| Carretera Primaria (MH)|| 90
|-
| Carretera Secundaria (mH)|| 90
|}
|}
The simplest junctions often resemble a "T" and are considered diverging or branch roads. The branch road will normally meet the main road at nearly a 90 degree angle. This is the simplest situation to map, as the physical and logical views of the roads match up well.
{{clear}}


=== Odd angles ===
{| border="1" class="wikitable"
{| class="Wikitable floatright"
!colspan="4" bgcolor="#387fb8"|Límites de Velocidad
| [[Image:Jct_3_45_ex1.png|border]]
|- style="text-align: center;"
| [[Image:Jct_3_45.png|border|x200px]]
|'''''Ciudad'''''
|km/hr
|-
| Carretera Primaria (MH) || 60
|-
| Carretera Secundaria (mH) || 60
|-
| Calle Principal (PS)|| 40
|-
| Calle (St)|| 40
|-
|Zonas de Hospital, Escuelas  (St)||20
|}
|}
Some roads meet at odd angles. The initial urge will be to represent the junction as it is in the physical world - two lines running into each other at a sharp angle. But there are issues with this method.
* Depending on the angle, the client may give a "Keep Right" instruction to the driver when a "Turn Right" instruction is more appropriate. If Minor Highways or above are involved, you will actually get an "''Exit'' Right" which can be confusing in many situations.
* In some cases, no instruction will be given at all. In the worst case, the [[routing server]] may determine that it isn't possible to make a very sharp turn angle and not suggest the turn at all (in the example image, heading south, then turning left, to head east).
* Automatic map errors may appear with turns from one direction as the path of the turning traffic is "too far" away from the actual junction (in this example, traveling south, then turning left to head east).
{{clear}}


{| class="Wikitable floatright"
{| border="1" class="wikitable"
| [[Image:Jct_3_45_curve.png|border]]
!colspan="4" bgcolor="#387fb8"|Límites de Velocidad
|- style="text-align: center;"
|'''''Otros - Conducibles'''''
|km/hr
|-
| Sendero 4x4 / Sin mantenimiento (OR)|| 30
|-
| Vía de Estacionamiento (PRL) || 10
|-
| Vía Privada (PR)|| 30
|}
|}
To eliminate ambiguity, map the junction from a logical point of view. Since basic "Turn Left" and "Turn Right" instructions are desired, tweak the intersecting angle so it resembles a basic 90 degree intersection. Add [[Glossary#Geometry node|geometry nodes]] to make the branch road leave the main road at close to 90 degrees, then gradually curve the road to match the true departure angle. This will produce a junction that logically works like a basic 90 degree junction, but it also fits the reality of the physical world.
{{clear}}


{| class="Wikitable floatleft"
 
| [[Image:Jct_3_45_ex.png|border]]
 
<big>'''Municipio Benito Juárez:'''</big>
{| border="1" class="wikitable"
!colspan="4" bgcolor="#387fb8"|Límites de Velocidad
|- style="text-align: center;"
|'''''Ciudad'''''
|km/hr
|-
| Carretera Primaria (MH) || 60
|-
| Carretera Secundaria (mH) || 60
|-
| Calle Principal (PS)|| 60
|-
| Calle (St)|| 60
|-
|Zonas de Hospital, Escuelas  (St)||20
|}
|}
Here is a completed real world example which provides the expected turn instructions and "catches" turns from all directions avoiding automatic problems for [[Map_Problems_in_Waze_Map_Editor#Missing_road|missing road]] when they are "too far apart."
{{clear}}


=== Name changes on straight path ===
=== Alta de Ciudades y Pueblos ===
For conditions where the straight through route changes road names, it is important to identify which segment is drawn as the straight route and which is shown as the right turn from the main road. As the [[How_Waze_determines_turn_/_keep_/_exit_maneuvers|How Waze Determines turn/keep/exit maneuvers]] page explains, segment names and geometry are very important in determining what navigation instructions are given.
 
*En este '''[https://docs.google.com/forms/d/e/1FAIpQLSeXBdcgxUIgOvf07IQ4r3x8E-lpirzCLL6PLZHYMKwb-lVb4Q/viewform <big>Formulario</big>]''' se solicitará el alta. '''{{blue|(Únicamente se darán de alta ciudades mediante EL FORMULARIO).}}'''
 
*Aunque no es prioridad perfeccionar los límites geográficos de cada ciudad''' {{red|es importante revisar si la ciudad o pueblo que editemos se encuentre BIEN DELIMITADA}}''', esto se logra al revisar el campo '''Ciudad/City''' que tienen los segmentos.


[[Image:Jct_Y_ex_aerial.png|right|border]]
*Al crear nuevos segmentos, llena el campo "ciudad" '''<big>solamente si estás 100% seguro de qué ciudad es</big>''', de lo contrario déjalos como '''SIN CIUDAD'''.
In this example to the right, the multi-lane surface street is known as Main Street to the west and Atlantic Ave. to the east. The name change occurs when Main St. branches off as a regular surface street. That is the human description, but a more technical description would be that Main St. travels in a perfectly straight line and Atlantic Ave. branches off of it. But if we map it that way in the editor, we create a major problem.
{{clear}}


[[Image:Jct_Y_ex_map_bad.png|left|border]]
*Los segmentos de '''carreteras''' se deben dejar '''SIN CIUDAD'''.
Since the multi-lane segment of Main St. and the regular street segment of Main St. have the same name, the routing engine automatically considers that to be "straight". If the two sections line up in a straight line the way they appear from the sky, then we are reinforcing the idea that "straight" is Main St. to Main St. But as a typical driver would want, "straight" should be the path that remains on the multi-lane roadway, regardless of what name it uses.
*Aquí puedes [https://wazeopedia.waze.com/wiki/Mexico/M%C3%A9xico/Nombre_de_Ciudad#Campo_.22Ciudad.22_o_.22City.22 repasar dicho tema.]
{{clear}}


[[Image:Jct_Y_ex_map.png|right|border]]
=== Edición de Lugares (Places) ===
To make sure the routing engine understands the proper treatment of the junction, we have to be deliberate with the segment geometry of all three involved segments.  We end up with something like the image on the right. Now the geometric definition of straight is the multi-lane portion of Main St. onto Atlantic Ave., since we have made that transition as close to zero degrees as possible. The regular street portion of Main St. now branches off at an angle close to 90 degrees. The routing engine should recognize that a turn is required. So the result is that Main St. to Atlantic Ave. has no announced turn, and multi-lane Main St. to surface road Main St. has a turn announced. Exactly what most drivers would expect in the real world.


=== Steep angles with exits and keep right or left ===
Es importante [https://www.waze.com/forum/viewtopic.php?f=1797&t=230742 '''<big>leer este tema del Foro</big>'''] e instalar el Script [https://greasyfork.org/en/scripts/26340-wme-place-interface-enhancements '''WME Place Interface Enhancements''']
{|
 
|-
En los lugares que se conozca la página web, colocar el formato adecuado (http://www.elsitiocorrecto.com.mx) y los teléfonos deben incluir la '''Lada''' de la localidad, ejemplo: '''(998) 123-4567.'''
| [[File:Jct ramp no geo.png|border|Jct ramp no geo.png]]
 
| [[File:Jct ramp no geo arrow.png|border|Jct ramp no geo arrow.png]]
{{mbox
|}
| type = notice
| text = Cuando edites lugares, utiliza '''Street View''' para corroborar todos los datos posibles y utiliza '''Google Linked Places''' para unirlos con los de Google.
}}<br>
 
Recuerda que para cadenas comerciales o sucursales, se tienen que usar '''Identificadores:
 
por ejemplo: '''''Starbucks - Plaza Universidad'''''.
              '''''Starbucks - Centro'''''
 
'''{{blue|*Para saber si un lugar debe ser Punto o Área, revisa:}}''' [https://wazeopedia.waze.com/wiki/Mexico/M%C3%A9xico/Lugares#Puntos_de_Inter.C3.A9s_y_Lugares <big>Lugares Puntos/Áreas</big>]
 
=== Gasolineras ===
Deberán editarse de acuerdo a la '''[https://wazeopedia.waze.com/wiki/Mexico/M%C3%A9xico/Lugares#Gasolineras.2C_Estaciones_de_Gas_Automotriz_y_Estaciones_de_Carga_para_Autom.C3.B3viles_El.C3.A9ctricos Regla actual que tenemos en la Wazeopedia México.]'''
 
'''{{red|IMPORTANTE:}}''' Añadir también las '''Vías de Estacionamiento''', dejando los segmentos '''"Sin Nombre"''', colocar la ciudad correspondiente o en su defecto dejar '''"Sin Ciudad"'''. Colocar la '''velocidad límite a 10 Km''' y bloquear los segmentos a '''nivel 4'''.
 
[[File:Pemex.png|500px]]


A ramp from a highway is another good example where additional geometry nodes are helpful. Especially since most ramps diverge at a very small angle from the road. The drawback in this case is it may be hard to see and click on the turn restriction arrows in the editor.


{|
Para más información de la Gasolineras, consultar en [http://guiapemex.pemex.com/SitePages/home.aspx <big>Guía PEMEX</big>]
|-
| [[File:Jct ramp w geo.png|border|Jct ramp w geo.png]]
| [[File:Jct ramp w geo arrow.png|border|Jct ramp w geo arrow.png]]
|}


Therefore add one more geometry node to make the departure angle at the junction closer to 10 or 20 degrees. (dogleg) See the discussion on [[Junction Style Guide#Controlling Turn Instructions|controlling turn instructions]] for details on those angles. Now the arrows are visible and accessible. Note that also pressing '''s''' in the editor will '''s'''pread or '''s'''eparate the arrows at a junction, if a arrow is still difficult to reach. See the [[Keyboard shortcut|keyboard shortcuts]] article for more tips on other keys.
==Recursos de edición:==


With this adjusted angle, this junction now behaves as expected and the turn restrictions can be easily accessed. {{clear}}
==== Capas de Equipos (Layers)====
* [https://greasyfork.org/en/scripts/44553-wme-mapraid-quintana-roo-overlay Capas de EQUIPOS]
'''{{red|** Agradecimiento a}} [https://www.waze.com/es/user/editor/drysoft drysoft]'''


== Four-way ==
==== Poblaciones URBANAS (kml) ====
*  [https://www.dropbox.com/s/tj8cz4vm7vas64v/Equipo%201%20-%20Urbana.kml?dl=0 Equipo 1]
*  [https://www.dropbox.com/s/40jm0ruzlqrppkq/Equipo%202%20-%20Urbana.kml?dl=0 Equipo 2]
*  [https://www.dropbox.com/s/b2jxwzfh98tewmg/Equipo%203%20-%20Urbana.kml?dl=0 Equipo 3]


=== Right angles ===
'''{{red|** Agradecimiento a}} [https://www.waze.com/es/user/editor/VHCB16 VHCB16]'''
{| class="Wikitable floatright"
| [[Image:Jct_4_90_ex.png|border]]
| [[Image:Jct_4_90.png|border|x200px]]
|}
The second simplest junction category is a "+" or "cross" four-way junction that intersects at 90 degrees. These roads are simple to map as the logical and physical views of the roads match up well. These instructions follow the similar guidelines and solve the same problems as [[Junction Style Guide/Diverging roads|diverging roads]].
{{clear}}


=== Odd angles ===
==== Poblaciones RURALES (kml) ====
{| class="Wikitable floatright"
*  [https://www.dropbox.com/s/j5lizdig5b4zvp2/Equipo%201%20-%20Rural.kml?dl=0 Equipo 1]
| [[Image:Jct_4_45_ex1.png|border]]
*  [https://www.dropbox.com/s/0cplrkkpupgalni/Equipo%202%20-%20Rural.kml?dl=0 Equipo 2]
| [[Image:Jct_4_45.png|border|x200px]]
*  [https://www.dropbox.com/s/cr97jbl8fdl3gp8/Equipo%203%20-%20Rural.kml?dl=0 Equipo 3]
|}
Similar to diverging roads that intersect at odd angles, crossing roads can do the same thing. When these intersections are mapped as seen here with these odd angles, complications can occur.
{{clear}}


{| class="Wikitable floatright"
'''{{red|** Agradecimiento a}} [https://www.waze.com/es/user/editor/VHCB16 VHCB16]'''
| [[Image:Jct_4_45_curve.png|border|x200px]]
|}
[[Glossary#Geometry_node|Geometry nodes]] bring the actual junction close to 90 degrees. [[Map_Editor_Interface_and_Controls#Zoom_Control|Zoom]] in to the intersection and add a single geometry node on each side as close to the junction point as possible. This will give the more desirable 90 degree angle, and it will still be virtually invisible to client app users making it look like the physical world. This image is what is seen when zoomed in as close as possible. Zoomed back out, it looks just like the map image showing the junction without any geometry nodes.
{{clear}}


{| class="Wikitable floatleft"
| [[Image:Jct_4_45_ex.png|border]]
|}
Here is a real world example at a close zoom level where you can still see the geometry adjustment. With that adjustment in place, the junction will produce predictable turn left and right navigation instructions while the roads still appear to meet at the real-world angle in the client app.
{{clear}}


== {{anchor|Split road intersections}}Divided road intersections==
==== ALTA de Ciudades y Pueblos====
Many of the principles stated above apply to intersections between divided roads. Usually, divided road intersections should look like the traffic lanes they represent. "Box" shaped intersections are easiest to draw, maintain, and to explain to other editors.  Only use variations when they are needed.
* [https://docs.google.com/forms/d/e/1FAIpQLSeXBdcgxUIgOvf07IQ4r3x8E-lpirzCLL6PLZHYMKwb-lVb4Q/viewform Formulario] '''{{blue|(Únicamente se darán de alta ciudades mediante EL FORMULARIO).}}'''


Read through the pros and cons of the intersection types below and select the best suited.


{{NeedInfo|Insert examples of a divided road intersecting a two-way road, two divided roads intersecting each other, 3-way intersections involving divided roads, intersections where one road changes between  divided/2-way at the intersection...}}
==== INEGI (fuente oficial)====
* [http://gaia.inegi.org.mx/mdm6/ INEGI GAIA]


=== Box and partial box intersections ===
==== Medios de Comunicación====
Discord


This type of intersection is most useful in intersections where the traffic queues in a median segment that is long enough to justify being mapped, especially if the one-way roads would have to deviate greatly from their physical location to meet in a single point for a bow tie. This also allows the map to route correctly while representing the actual geometry of the roads in real life, which is more intuitive to users.
==== PANEL ====
[https://qr.wazemapraid.com Panel de MapRaid]


Do not use this type of junction if the crossbar will be less than {{:Segment length/Minimum}}. Waze has difficulty in capturing average speeds for short segments, especially in wide intersections where traffic travels a fairly curved path rather than sticking close to the segment.  Add in the inaccuracy of many phone GPS units, and you may have a situation where the reported positions of some of the vehicles are never on the segment during the maneuver.


When creating three way and four way intersections, if the cross street changes names at the junction, make sure that the segment(s) have no name. This will cause the segment to inherit the appropriate name depending on the direction of travel.  This center segment will not be included when you choose "Select entire street".
====Carreteras Federales y Estatales====


Three way divided road intersections are easier to edit accurately than four way intersections.


{{NeedInfo|Insert examples: divided road ends at 2-way road (single point if both lefts are allowed and u turns are not); divided road ends at divided road ("triangle" in median if both lefts are allowed and u turns are not); 2-way road ends at divided road (easy).}}
* [http://www.sct.gob.mx/fileadmin/DireccionesGrales/DGST/Datos-Viales-2018/23_QROO_2018.pdf Archivo pdf de la SCT]


[[Image:3wayunsplitsplit.png]]
* [https://docs.google.com/spreadsheets/d/1C6_uS1EHAm_eIz0wh4FX8STkxkw3yaw0PuGJAyolyC0/edit?usp=sharing Spreadsheet Carreteras Quintana Roo]


If possible, lay out the intersection to resemble reality.  When all divided-road U turns are allowed at an intersection, or when disallowed U turns are effectively restricted in Waze by existing restricted left turns already, use the guidance in this section.


When a U turn must be restricted, but both of the left turns that make up that U turn are allowed on their own, follow the guidance in [[#Avoiding U turns|Avoiding U turns]] below.
====Scripts recomendados:====


{{NeedInfo|Insert examples: divided road intersects a 2-way road (≠); two divided roads intersect (#); intersection where one road changes between divided/2-way at the intersection...}}
'''WME Geometries'''
* Permite cargar diversos archivos: '''kml, etc.'''
** [https://greasyfork.org/en/scripts/8129-wme-geometries Script para Greasyfork]


{| class="wikitable"
'''WME Place Interface Enhancements'''
|-
* Modifica la visualización de los Places para añadir mas datos y funciones.  
! Intersection style !! Example
** [https://greasyfork.org/en/scripts/26340-wme-place-interface-enhancements Script para Greasyfork]
|-
| A divided road intersecting a divided road. || [[Image:4waysplitsplit.png|300px]]
|-
| A divided road intersecting a 2-way road. || [[Image:4waysplitunsplit.png|300px]]
|-
| A transitioning (divided-2-way) road intersecting a 2-way road. || [[Image:Split_road_to_sinlge_road.png|300px]]
|-
| A transitioning (divided-2-way) road intersecting a divided road. || (image)
|-
| Be careful with your geometry – following the center of the actual road too closely can lead to rather high turn angles, and therefore possibly unwanted turn instructions. Keep it smooth. || [[Image:Transition.png|300px]]
|}


=== Bow tie ===
'''WME True Segment Length'''
{{Anchor|Bowtie}}
* Indica la longitud exacta de un segmento en tiempo real. Muy útil para retornos y segmentos menores a 16m.
** [https://greasyfork.org/en/scripts/25444-wme-true-segment-length Script para Greasyfork]


[[File:Jct_bowtie.png|300px|thumbnail|right|Gaining control of turns by reducing the intersection to a single point.]]The "bow tie" intersection method makes it easy to take separate control of left turns and u-turns at divided-road intersections. It also allows Waze to correctly draw conclusions about where traffic queuing occurs.
'''WME ClickSaver'''
Use it only
* Mejora la interfaz del editor para ahorrar tiempo y espacio.
* at 4-way divided road intersections (between two divided roads, or between a divided road and a two-way road).
** [https://greasyfork.org/es/scripts/22059-wme-clicksaver Script para Greasyfork]
* only when necessary to prevent u-turns while allowing left-hand turns.
* The angles at the single bow tie intersection can reasonably be made 45 degrees or less. Otherwise, drivers going straight through will get an instruction to turn or stay right in [[right-hand traffic]] countries (turn or stay left in [[left-hand traffic]] countries)
* Because of the awkward appearance of the bowtie, consider using other methods, such as the U-turn prevention mechanism immediately below. It is common for drivers to report map errors due to the appearance.


=== Avoiding U turns in box and partial box intersections===
'''Waze - Google Maps Link'''
{{anchor|Avoiding U turns}}
* Abre el mapa de Google Maps directamente desde el WME.
{{Mbox|type=forum|text=For the latest discussion on this section please visit [http://www.waze.com/forum/viewtopic.php?t=108731 the wiki forum thread].}}
** [https://chrome.google.com/webstore/detail/waze-google-maps-link/jblojdkgpamepmiammlgkkhknojnlmai Extensión de Google Chrome]
{{Mbox|type=important|text=It is possible for this method to fail to prevent U-turns in certain circumstances which are presumed to be unusual. If you observe this method to fail when it is implemented properly, please report it in [http://www.waze.com/forum/viewtopic.php?p=994385#p994385 this forum thread]}}


[[File:MinSegLengthUturn2.png|border|390px|right|Segment too short to allow two left turns]]
'''WME Speedhelper'''
U-turns can be avoided where two divided roads intersect (in a # configuration, aka a Box junction) or a divided road intersects an undivided - ''a single-segment (one-way or two-way)'' - undivided road (in an H configuration junction)
* Mejora la interfaz del editor para colocar los límites de velocidad en los segmentos.
# The U-turn we want to forbid is one incoming one-way segment, one median segment, and one outgoing one-way segment.
** [https://greasyfork.org/es/scripts/13774-wme-speedhelper Script para Greasyfork]
# there is a median segment of length less than {{:Routing penalties/U-turn minimum}}.
# The portion of those two segments closest to the median segment must be within ±5° of exactly parallel.


A convenient way to check for parallel is relative to a reference segment that connects the A and B nodes of the median segment with no geometry nodes. A median segment with no geometry nodes is its own reference segment. The reference segment can be deleted after the check is complete, if appropriate. Check two angles:
'''WME GPS Track View'''
X -- the angle between the incoming one-way segment and the reference segment
* Para delimitar polígonos de pueblos y ciudades a editar.
Y -- the angle between the outgoing one-way segment and the reference segment.
** [https://greasyfork.org/es/scripts/7361-wme-gps-track-view Script para Greasyfork]
If the sum of these two angles is within 5 degrees of 180, then rule 3 is satisfied.


In the example below, angle X is 102 degrees and angle Y is 75 degrees. The sum is 177, which is within 3 degrees of 180. Therefore rule 3 is satisfied.
'''WME Junction Angle info (JAI)'''
[[File:LilyPondU-turn.jpeg]]
* Añade ángulos en las uniones de los segmentos.  
** [https://greasyfork.org/en/scripts/35547-wme-junction-angle-info Script para Greasyfork]


The Waze routing algorithm assesses a [[Routing penalties#Road_configurations|penalty]] for a double-left turn in [[right-hand traffic]] countries and a double-right in [[left-hand traffic]] countries.
'''WME Color Highlights'''
* Añade colores a segmentos de carretera para mostrar su estado. Los lugares/areas son resaltados en función de su tipo.
** [https://chrome.google.com/webstore/detail/wme-color-highlights/ijnldkoicbhinlgnoigchihmegdjobjc Extensión de Google Chrome]
** [https://greasyfork.org/scripts/3206-wme-color-highlights Script para Greasyfork]


{{clear}}
'''WME Chat Addon'''
{{ReturnTo | Junction_Style_Guide | the Junction Style Guide}}
* [http://greasyfork.org/en/scripts/2103-wme-chat-addon WME Chat Addon] es un script que mejora el chat del WME.

Revisión del 18:19 20 ago 2018

 El MapRaid será del 14 al 29 de mayo del 2018

Misión

Los objetivos principales son:

  • Depurar los URs, PURs.
  • Asegurar la conectividad y numeración de las carreteras federales y estatales.
  • Dar de alta ciudades y poblados.
  • Aumentar los segmentos con límites de velocidad.
  • Dar de alta y actualizar Gasolineras.


 Cualquier edición para mejorar el mapa es bienvenida, pero si tienes duda en algo, contacta con los líderes de grupo.


Áreas del MapRaid

Serán 3 Equipos, con sus respectivos líderes.


Editores Locales

DavidAbarca (PM) - Supervisor Región Sureste

jisaacgmx (PM) - Area Manager

janoteweb (PM) - Conoce algunas zonas del estado

IMPORTANTE

 ¡¡ PROHIBIDO HACER EDICIONES MASIVAS únicamente con la finalidad de obtener PUNTOS !! Esto se vigilará durante TODO el MapRaid.


  • De confirmarse este tipo de actividad, se dará de baja del mapraid y se restringirá su actividad para futuros eventos.

Ediciones del Mapa

Tipo de Segmentos

En México tenemos un estándar mínimo establecido para las carreteras según el tipo de segmento de bloqueo. Cualquier camino de un cierto tipo de segmento debe estar bloqueado al menos al rango (nivel) en la tabla de abajo. Las carreteras pueden tener bloqueos superiores para la protección y situaciones especiales (áreas con la construcción, diseño complicado, errores frecuentes, inexactitudes de formación de imágenes, y similares), pero no deben tener bloqueos inferiores.

Estándar de bloqueo mínimo para México
Segment Type Area Urbana  Area Rural
 Autopista  5
 Rampa  4
 Carretera Primaria  4
 Carretera Secundaria  3 2
 Calle Principal  2 1
 Calle  1
 |-|-|-|-|-|-|-|-|-| Vía Ferrea |-|-|-|-|-|-|-|-|-|  4
 • • • • Transbordador • • • •   5
  • Al bajar de nivel algún segmento y terminar la edición, pide nuevamente SUBIR el nivel del segmento.


Límites de Velocidad

Quintana Roo:

Límites de Velocidad
Carreteras km/hr
Autopista (FW) 110
Rampa 40
Carretera Primaria (MH) 90
Carretera Secundaria (mH) 90
Límites de Velocidad
Ciudad km/hr
Carretera Primaria (MH) 60
Carretera Secundaria (mH) 60
Calle Principal (PS) 40
Calle (St) 40
Zonas de Hospital, Escuelas (St) 20
Límites de Velocidad
Otros - Conducibles km/hr
Sendero 4x4 / Sin mantenimiento (OR) 30
Vía de Estacionamiento (PRL) 10
Vía Privada (PR) 30


Municipio Benito Juárez:

Límites de Velocidad
Ciudad km/hr
Carretera Primaria (MH) 60
Carretera Secundaria (mH) 60
Calle Principal (PS) 60
Calle (St) 60
Zonas de Hospital, Escuelas (St) 20

Alta de Ciudades y Pueblos

  • En este Formulario se solicitará el alta. (Únicamente se darán de alta ciudades mediante EL FORMULARIO).
  • Aunque no es prioridad perfeccionar los límites geográficos de cada ciudad es importante revisar si la ciudad o pueblo que editemos se encuentre BIEN DELIMITADA, esto se logra al revisar el campo Ciudad/City que tienen los segmentos.
  • Al crear nuevos segmentos, llena el campo "ciudad" solamente si estás 100% seguro de qué ciudad es, de lo contrario déjalos como SIN CIUDAD.

Edición de Lugares (Places)

Es importante leer este tema del Foro e instalar el Script WME Place Interface Enhancements

En los lugares que se conozca la página web, colocar el formato adecuado (http://www.elsitiocorrecto.com.mx) y los teléfonos deben incluir la Lada de la localidad, ejemplo: (998) 123-4567.

Cuando edites lugares, utiliza Street View para corroborar todos los datos posibles y utiliza Google Linked Places para unirlos con los de Google.


Recuerda que para cadenas comerciales o sucursales, se tienen que usar Identificadores: 

por ejemplo: Starbucks - Plaza Universidad.
             Starbucks - Centro

*Para saber si un lugar debe ser Punto o Área, revisa: Lugares Puntos/Áreas

Gasolineras

Deberán editarse de acuerdo a la Regla actual que tenemos en la Wazeopedia México.

IMPORTANTE: Añadir también las Vías de Estacionamiento, dejando los segmentos "Sin Nombre", colocar la ciudad correspondiente o en su defecto dejar "Sin Ciudad". Colocar la velocidad límite a 10 Km y bloquear los segmentos a nivel 4.


Para más información de la Gasolineras, consultar en Guía PEMEX

Recursos de edición:

Capas de Equipos (Layers)

** Agradecimiento a drysoft

Poblaciones URBANAS (kml)

** Agradecimiento a VHCB16

Poblaciones RURALES (kml)

** Agradecimiento a VHCB16


ALTA de Ciudades y Pueblos

  • Formulario (Únicamente se darán de alta ciudades mediante EL FORMULARIO).


INEGI (fuente oficial)

Medios de Comunicación

Discord

PANEL

Panel de MapRaid


Carreteras Federales y Estatales


Scripts recomendados:

WME Geometries

WME Place Interface Enhancements

WME True Segment Length

  • Indica la longitud exacta de un segmento en tiempo real. Muy útil para retornos y segmentos menores a 16m.

WME ClickSaver

Waze - Google Maps Link

WME Speedhelper

WME GPS Track View

WME Junction Angle info (JAI)

WME Color Highlights

WME Chat Addon

Obtenido de «https://beta.waze.com/wiki/Mexico/index.php?title=MapRaid_San_Luis_Potosí_2018&oldid=11951»