Road closure/split Amesbury, Wiltshire

Greetings, all new to this (first post):
Segment: https://waze.com/en-GB/editor?env=row&lat=51.16083&lon=-1.76548&marker=true&s=70622485&zoom=5&segments=335463588

This road no longer goes between A and B. The road from A (Princess Way) goes as far as the 2nd draggable circle. From B (Evergreen Cafe carpark), 3rd Draggable circle. In between is a field that will be turned in to a park.

Could this segment be split please, with no through road (Waze constantly tries to put me along that segment).

Shown on openstreetmap: https://www.openstreetmap.org/edit#map=17/51.16119/-1.76834

Thank you

HI there! Welcome to the forums and well done for getting the Permalink right in your first request. :smiley:

I can see you’ve made some edits already, so I’m guessing you couldn’t work out how to split the existing segment? To split, you have to draw a new segment, either starting at or ending at a connection with the middle of the segment you want to split. That created a junction. You can then delete the segment you created to make the split (and other segments if required) and save.

I’ve split the segment as I hope you were looking for. If you want to fine-tune, you should now be able to drag the ends around. :mrgreen:

Greets Iain (good name btw - also an Iain).

That is perfect, hopefully will sort out the routing with Waze (for my cousins too when they visit). There is a load of building work taking place on the opposite side of the Sports (Rugby) field. When complete, how does that get added to Waze? Openstreetmap?

Many thanks.

Iain

Definitely not OpenStreetMap! :lol:

In a similar way to the Waze map, OpenStreetMap is built by voluntary editors. Even thought they may be working from publically available, non-copyrighted data, the act of building the OSM map is what is called (I think) a transformative work or action. The map thus produced is covered by copyright and, as a commercial entity, Waze cannot use the OSM data. This applies to any information that is covered by copyright unless it’s specifically allowed for Waze, even if it’s freely available. Many years ago, an entire country map in South America had to be removed from Waze after it was discovered to have been substantially copied from OSM.

In practice, this means that you can update the map based on personal knowledge (from you or someone else who gives it to you), the Google aerial images made available to you in WME (Waze Map Editor) and the Google Street View available in WME. It is more or less OK to view the same aerials and GSV in Google Maps (because it’s the same info), but you can’t copy the road detail or names you see in Google Maps (and I wouldn’t anyway, because Gmaps often gets road names wrong).

All the above applies to “primary sources”. It is allowable to look at other data sources to confirm what you have already worked out. So, for example, if you’re not sure what path a road takes under some trees, you could look at historical images in Google Earth to get an idea. But you couldn’t trace the road layout from those images. As an example, I glanced at the OSM link you have me, to confirm I’d understood what you were after. But the edits I made were based on your description of the editing “handles” on the segments.

There are a couple of other exceptions. Ordnance Survey produce data sets under the OpenData banner. If you get interested in editing, you will soon start to look at Userscripts to enhance your editing. One of these scripts uses OpenData to look up road names from the database - and because we acknowledge the use of this data publicly, that’s OK.

The other exception relates to new builds, which you mention. This isn’t a legal exception: it’s practical. With a bit of searching, you can generally find site plans for new housing developments online. Whilst all such websites have copyright notices, I am personally quite happy that developers are never going to object to us adding new developments before they’re visible on the aerial images. It can only be to their advantage to have their new houses easy for buyers to find and drive to and I’m sure they wouldn’t object. If any of the major developers were to object to us using their site plans, hundreds of their developments would be removed from Waze overnight and only their residents and visitors would suffer. Last time I had to ask a developer for a site plan, I got back a map so detailed, it showed every bush & shrub they planned to plant! :mrgreen:

Cheers for the heads up.

Might get in to doing some editing. I assume there as postings on here about how to get in to it? Think I shall have plenty of reading coming up.

Iain

There’s another useful data source in WME that I forgot to mention: the GPS layer. This shows aggregated information from Waze drivers.If you look at Edmunds Way, just to the south, and turn on the GPS layer, you can see that Edmunds Way is actually a completed loop with many drivers. So you can fill out the loop based on the GPS tracks.

And just to the south of that, there are enough tracks to highlight a completely missing road that the OpenData script tells me is Sarsen St. Perhaps you’d like to add it? :wink:

It is a pity there isn’t an option on the app to record the GPS locations of a new road as you drive along it, to map it accurately. Think I might use my Garmin and walk around them and then copy across my “own” mapped data.

Actually, there are 2 options to do so. :lol:

In the app, if you go to the orange Report button, select Map Issue, then Pave. This will then start recording your position. Within a day or two, with everything running smoothly, new red (no name, no city) segments will appear on the map where you paved. They will likely be one-way and not connected, but as an editor, you can connect them up.

The other option is in the left hand panel of WME - the Drives tab. This allows you to view all of your recent drives in Waze as traces on the map. So you could take a drive around the missing roads, wait for the drive to show up and then trace over it.

In either case, the accuracy isn’t great, due to the limitations of phone GPS. That’s why we recommend against mapping all lanes of a car part - because phone GPS often can’t tell which lane you’re in. But it’s good enough to map something useful in Waze, particularly if you have the road names to got with it. Even if the shape is a bit wobbly, it will get grateful Wazers to where they are going - and when the aerial images updated, there’s the pleasure of seeing how accurate you were. :mrgreen:

I’ve been an editor for nearly 5 years now and never knew that you could do this… :oops: