the segment shows a latest update of November 1st only because I have tried everything to resolve this issue ... started with simply disconnecting the segments and reconnecting ... then I tried to just simply add city names to the section to see if that fixes anything ... what is strange to me it this section was all created by someone other than me driving the path so this was an actual driven path. The opposite side of the divided highway was all created by me using Gps tracking and basing it on the distance apart on the roads in sections that I have completed for other sections of the same road. That part showed up right away, but this section won't ... what is being done wrong? This is not happening in just one section, but multiple sections of the same road.

screen shots:

Area Manager for Mankato MN | Minnesota State Manager | USA Country Manager

There have been known issues, which were supposedly recently resolved, with segments which started with the Pave function in the app not appearing on the map. Can you confirm this was the case for this segment? If so, we need to get this to the developers as another example of paved segments not being properly validated by the system.

AlanOfTheBerg wrote:There have been known issues, which were supposedly recently resolved, with segments which started with the Pave function in the app not appearing on the map. Can you confirm this was the case for this segment? If so, we need to get this to the developers as another example of paved segments not being properly validated by the system.

This is exactly the case ... the other side of the highway was not set by my pave, but the side with issues was set by pave ... that explains why some other areas seemed to take forever to load as well ... most of the other sections I have been able to correct simply by re-updating the connect points, but it hasn't worked for me here.

Area Manager for Mankato MN | Minnesota State Manager | USA Country Manager