Hi gurglypipe,

Thank you for your feedback. I initially aligned the highway because the previous geometry was quite kinked, and I intended to smooth the alignment.

However, after reviewing the forum discussion and understanding the community's preference regarding such junction alignments, I will refrain from making these types of changes in the future. Changeset reverted to its previous state, preserving the separate junctions as they existed before.

Thank you for bringing this to my attention. I appreciate the guidance and will be more careful with similar edits going forward.

Hi adigis,

After reviewing the GPS traces and the available street-level imagery, I don't have enough ground truth evidence to add the junction=roundabout tag here. There are no visible yield/stop lines or other indications that traffic is intended to circulate with roundabout priority that is why I didn’t add the tags. I’d be happy to add the tags if you have supporting evidence or local knowledge of the area.

Hi gurglypipe,
Thank you for your feedback. I will analyze the situation and come back to you.

Hi adigis,
Thanks for your input. Just to clarify, this isn't a TomTom-specific concern. The Crossing barrier/highway warning is a general validation error flagged by JOSM's built-in validation tool, and it's a legitimate topological issue worth resolving regardless of any single data consumer.
As TomTom, our aim is to improve the overall quality and usability of OSM data for the entire community, not just for our own priorities. A properly connected barrier and highway benefits every downstream user and keeps the data consistent with OSM community guidelines.
Appreciate the discussion, happy to look into it further if anything's still unclear.

Hi b-holdet,
At the time of editing ferries in this region, I noticed that tags such as duration, foot, and description are different between way/1101404413 and way/409892450. Additionally, way/409892450 is part of route relations. Based on these differences, I assumed way/1101404413 might represent a separate ferry entity and retained it with the existing tags.

If both ways represent the same ferry service and operate as a single functional ferry route and there is any redundancy, please let me know.

Hi b-holdet,
As documented in the OpenStreetMap Wiki (route=ferry), ferry routes should start and end at nodes tagged as amenity=ferry_terminal. The ferry route (way/1101404413) did not originate from a ferry terminal; instead, it was connected to another ferry route (way/409892450).
So, I did the edit in order to comply with the guidelines. Please let me know if my interpretation is correct, or if further corrections are necessary.

Hi b-holdet, Thank you for your feedback. I will analyze the situation and come back to you

Hi A67-A67,
Thank you for reaching out and correcting my edits. I was making edits based on recent GPS traces which showed a small deviation from the existing road centerlines.

Hi gurglypipe,
thank you for reverting the changeset, based on your knowledge and experience.
Regards!

Hi Eggie,
Thank you for making the corrections and feedback given.
While making changes to the junction configuration, I overlooked the continuation of the cycle relation and failed to add the bicycle=use_sidepath tags. I have made the corrections. I appreciate you bringing this to my attention, and I will be more diligent in the future edits.

Hi, 4000 big face,
As part of the hotosm-project-17520_AndhraMapping24 project, you are supposed to work in the Andhra Pradesh region but you have added buildings and removed power=pole from the power=line tag combination in Indiana/Detroit border region in the USA which is incorrect.
As per the wiki guidelines, the polygon should be orthogonalized while capturing as per reality and no redundant nodes should be present on the building polygons.
According to the wiki guidelines, power=pole should be added for power=line but not to the abandoned railway lines as these lines will not be operative.
I have made the corrections.
Happy Mapping!!

Hi 4000 big face,
As part of the hotosm-project-17520_AndhraMapping24 project, you are supposed to work in the Andhra Pradesh region but you have added buildings in the Indiana/Detroit border region in the USA which is incorrect.
As per the wiki guidelines, building polygons should be orthogonalized while capturing as per reality and no redundant nodes should be present on the building polygons.
I have made the corrections.
Happy Mapping!!!

Hi adi_mapcreator,
I’ve connected the barrier=wall with highway=service as connectivity is somehow visible in Bing Aerial Imagery giving us hints that there is some entrance from the main highway and leading road to access the inside houses. This will also help us to avoid the JOSM Validation error i,e Crossing barrier/highway which appeared to have been generated by your edits and seems it was not not highlighted in ID Editor.

In Order to answer your question, I agree with your point and it's difficult to judge from imagery whether there is a barrier present or not but when you will analyze the data, this is the only entrance to access those north side buildings(house no-95/2) which is accessible from Soi Prasat Suk and that is the reason I didn't add any barrier tag but intersected the highway as per guidelines. I hope this answers your questions satisfactorily?

For your information I am using the JOSM Tool which is more advanced than the ID editor and you will get by default validation errors for such type of edits which we cant ignore. Happy Mapping!

Hi adi_mapcreator,
I referred to both Bing Aerial Imagery and Esri World Imagery at this location -7.2918489, 107.8682335 and there is no visible path connectivity. When we refer to Bing imagery we can clearly see connectivity towards the southern side of the track highway i.e -7.2930542, 107.8671116 in the form of a field path. This will rightly solve the error for Fix Isolated Pedestrians network challenge. Let me know if you have further questions. Happy Mapping!

Hello julcnx
Thank you for mapping!
I have added missing connectivity and fixed an incorrect tag for highway for way/936714419 and way/1285095598.
Please inspect your task carefully before closing.
Happy Mapping!

Hello Putri22
I have fixed and modified the geometry; there is no connectivity from node/6261100841 to node/6258988186.
Please inspect your task carefully before closing.
Happy Mapping!

Hello Fathima Nifla
Thank you for mapping!
I have added connectivity in 3.2491933, 99.4289589.
Please inspect your task carefully before closing.
Happy Mapping!

Hello Fathima Nifla
Thank you for mapping!
I restored a deleted waterway tag way/472604736 and aligned it according to Bing Aerial Imagery.
Please inspect your task carefully before closing.
Happy Mapping!

Hello adi_mapcreator
Thank you for mapping!
I have aligned highway connectivity
Please inspect your task carefully before closing.
Happy Mapping!

Hello adi_mapcreator
I have fixed validation error - Crossing barrier/highway.
Please inspect your task carefully before closing.
Happy Mapping!