Map Editor major ver (Nov 5, 2012) Official Feedback

[AndyPoms]

From the first post in this topic

4) Cones and old ranks are now synced and displayed everywhere as follows:

old rank 0 = 1 cone
old rank1 = 2 cones (currently not in use)
old rank 2 = 3 cones
old rank 3 = 4 cones
old rank 4 = 5 cones
old rank 5 = 6 cones (currently not in use)
old rank 6 = STAFF

Has there been a change to ranks since that post? I have a local editor with a rank of (2)...

[bgodette]

I'm finding many segments with no level set. I'm not 100% sure but I believe all were old unedited client paved segments. When I edit a segment to fix its geometry points and give it a name then select it together with another completed segment to create junctions at intersections the cross sign "+" does not appear. When I check the newer segment I always find its level property empty. New editor? or the move to the new infrastructure?

Cause a wazeModel update and that clears. It's indeterminate data from modified segments that's cleared by refreshing the wazeModel (F5/Permalink/Panning far enough/zooming far enough).

[mssusa]

Cause a wazeModel update and that clears. It's indeterminate data from modified segments that's cleared by refreshing the wazeModel (F5/Permalink/Panning far enough/zooming far enough).

When I run into one of those it is usually too late for a reload; I usually have tens of edits unsaved. I simply highlight the segment and set its level properly then keep working. The only viable option (which I never tried) is panning.
Anyway, this never happened to me before, but I'm finding it often now.

BTW, did they fix the problems with segment properties fields in Chrome? Or did I just get used to it?

Sent from my GT-I9100 using Tapatalk 2

[skbun]

The 'Landmarks causes segment selection' crashes continue, FWIW. I'd still recommend keeping the landmarks layer disabled. I've found a different predictable use case and will forward it to nanorep support tonight.

[PhantomSoul]

Is anyone with Safari 6 and Mac OS 10.8 (Mountain Lion) having any trouble getting the permalinks to capture selected road segments? Last night while requesting some unlocks to resolve various UR's in my area, I noticed some inconsistent behavior with it, in that it sometimes included the selections and other times didn't.

[AndyPoms]

Is anyone with Safari 6 and Mac OS 10.8 (Mountain Lion) having any trouble getting the permalinks to capture selected road segments? Last night while requesting some unlocks to resolve various UR's in my area, I noticed some inconsistent behavior with it, in that it sometimes included the selections and other times didn't.

I've found that the segments are not selected at higher zoom levels... Try changing the zoom level manually in the permalink to see if it works....

[davipt]

Is anyone with Safari 6 and Mac OS 10.8 (Mountain Lion) having any trouble getting the permalinks to capture selected road segments? Last night while requesting some unlocks to resolve various UR's in my area, I noticed some inconsistent behavior with it, in that it sometimes included the selections and other times didn't.

Do you have any extensions? For example I hardly get the segments selected when using the highlights extension, have to look at the code to understand why

[AlanOfTheBerg]

Is anyone with Safari 6 and Mac OS 10.8 (Mountain Lion) having any trouble getting the permalinks to capture selected road segments? Last night while requesting some unlocks to resolve various UR's in my area, I noticed some inconsistent behavior with it, in that it sometimes included the selections and other times didn't.

Do you have any extensions? For example I hardly get the segments selected when using the highlights extension, have to look at the code to understand why

This is either an issue with the highlighter code or JNF code in WazeBar. The same code affects Chrome, too.

[ohiostmusicman]

Is anyone with Safari 6 and Mac OS 10.8 (Mountain Lion) having any trouble getting the permalinks to capture selected road segments? Last night while requesting some unlocks to resolve various UR's in my area, I noticed some inconsistent behavior with it, in that it sometimes included the selections and other times didn't.

Do you have any extensions? For example I hardly get the segments selected when using the highlights extension, have to look at the code to understand why

This is either an issue with the highlighter code or JNF code in WazeBar. The same code affects Chrome, too.

It must be the highlighter code as GizmoGuy and myself have had the same issues and we both were using the highlighter code.

[cristianfraser]

It'd be nice if we could add house numbers to more than one segment of a street.