Hi muralito, I made the change based on aerial imagery and Diagonal 9 looked connected to the trunk. With your message and local knowledge, I will go ahead and remove this connection. Thank you!

mweper,

Gracias por la aclaración, tiene sentido. Dado que usted tiene conocimiento local del área, me remitiré a sus ediciones aquí. ¡Feliz mapeo!

wabozand

(Traducción automática)

mweper,

Thanks for the clarification, it makes sense. Since you have local knowledge of the area, I will defer to your edits here then. Happy mapping!

wabozand

(Automatic translation)

Hola mweper!

Tengo curiosidad acerca de una relación en la que ha estado trabajando y discutiendo con serock (relation/16792957). Me acerco para confirmar que esta es la maniobra que se pretendía restringir. No pude encontrar ninguna indicación de que esta maniobra específica estuviera bloqueada en las imágenes Mapillary o Kartaview disponibles en el área, pero quería consultar con usted antes de ajustar esta restricción.

En su estado actual, esta relación tiene dos maniobras dentro de una restricción de un solo giro, lo que solo restringiría una ruta específica en lugar de dos giros separados individualmente. Esto impediría específicamente que un individuo gire a la derecha en Hipólito Yrigoyen, conduzca 2 cuadras por la Avenida Córdoba y luego gire a la izquierda en Presidente Perón. Con el modelo actual todavía es posible realizar los giros individualmente.

Si pretendías restringir ambos giros, creo que deberían modelarse individualmente. Si solo se pretendía girar hacia el Presidente Perón, el conjunto de relaciones de tres miembros debería ser un miembro 'de' de Avenida Córdoba: way/236440063, con un miembro 'vía' en la intersección nodo:node/935424028 y un 'to' miembro del Presidente Perón:way/1153790739).

Gracias por tu tiempo. Wabozand

(Traducción automática)

Hello mweper!

I am curious about a relation that you have been working on and discussing with serock (relation/16792957). I am reaching out to confirm that this is the maneuver that was intended to be restricted. I could find no indication that this specific maneuver was blocked in available Mapillary or Kartaview imagery in the area, but wanted to check with you before adjusting this restriction.

In its current state this relation has two maneuvers within a single turn restriction which would only restrict a specific route rather than 2 separate turns individually. This would specifically block an individual from turning right on Hipólito Yrigoyen, driving 2 blocks down Avenida Córdoba, and then turning left onto President Perón. With how this is currently modeled it is still possible to make the turns individually.

If you intended to restrict both turns, I believe they should be modeled individually. If only the turn on to Presidente Perón was intended, the three member relation set should be a 'from’ member of Avenida Córdoba:way/236440063, with a ‘via’ member at the intersection node:node/935424028 and a ‘to’ member of Presidente Perón:way/1153790739).

Thanks for your time. Wabozand

(Automatic translation)

Hello pertile, I will change way/1124307433 to a oneway. Thanks for your input and I will be mindful of imagery dates going forward.

Hello pertile, thank you for updating this. However I think there is one segment that needs to be adjusted. It looks like way/1124307433 is bidirectional in the data currently. What do you think of adding a oneway here to be consistent with the rest of the dual carriageway?

Hey cserpell, thanks for reaching out. For this area, I was focusing on making the map unified and consistent in this area. The gate mentioned node/10694182089 can be seen in Esri Imagery and a bit of partially in Bing Imagery. All gates in this area can be confirmed in Aerial Imagery and have private tags added. With that in mind, I added private tagging to this gate to match the others. I wanted to make the classifications more consistent as well, so i reclassified way/1207298412 to service to match the others in the area.

Correction: Source used was Maxar SecureWatch Imagery 2023-09-01.

Correction: Source used was Esri World Imagery; Mapillary.

Correction: Source used was Esri World Imagery; Strava.

Correction: Source used was Esri World Imagery; Strava.

Correction: Source used was Bing aerial imagery; Mapillary.

Correction: Source used was Esri World Imagery; Mapillary.

Correction: Source used was Esri World Imagery, Mapillary.