US Cartouche on Feb 2: Slow and many internal errors

The place to get information and ask questions about everything to do with properly and successfully editing the Waze Map.

Use this forum for all general editing questions, and the sub-forums for specific types of Waze Map Editor features.

Moderators: krankyd, Unholy

Re: US Cartouche on Feb 2: Slow and many internal errors

Postby dmcconachie » Thu Feb 24, 2011 5:33 pm

Oh you want the new one, trust me, it's a lot better!
dmcconachie • UK Country Admin • Forum Moderator • Former Global Champ
Nexus 4 • Android 4.3
UK WikiFB PageForum FAQCurrent status
dmcconachie
 
Posts: 6016
Joined: Sat May 22, 2010 11:44 pm
Location: Edinburgh, UK
Has thanked: 80 times
Been thanked: 260 times

Re: US Cartouche on Feb 2: Slow and many internal errors

Postby dmcconachie » Thu Feb 24, 2011 6:33 pm

Not at all, the new cartouche is slick, roads quicker, rarely gives the dreaded internal errors, scans smoother. The only negative in my opinion is the cache effect whereby it only reloads a tile after a significant edit but you quickly get used to it and the gain in speed is well worth it once you do!
dmcconachie • UK Country Admin • Forum Moderator • Former Global Champ
Nexus 4 • Android 4.3
UK WikiFB PageForum FAQCurrent status
dmcconachie
 
Posts: 6016
Joined: Sat May 22, 2010 11:44 pm
Location: Edinburgh, UK
Has thanked: 80 times
Been thanked: 260 times

Re: US Cartouche on Feb 2: Slow and many internal errors

Postby dmcconachie » Thu Feb 24, 2011 6:34 pm

Lol, oops , *loads* quicker!
dmcconachie • UK Country Admin • Forum Moderator • Former Global Champ
Nexus 4 • Android 4.3
UK WikiFB PageForum FAQCurrent status
dmcconachie
 
Posts: 6016
Joined: Sat May 22, 2010 11:44 pm
Location: Edinburgh, UK
Has thanked: 80 times
Been thanked: 260 times

Re: US Cartouche on Feb 2: Slow and many internal errors

Postby jondrush » Mon Feb 14, 2011 1:45 am

AlanOfTheBerg wrote:Ditto. Free-node (which includes road-end nodes) removal is fine for the most part, but any node connected to more than one segment is problematic.

Why would you be removing road end nodes?
Keeping the Waze maps tidy since 2009
Northeast Region Assistant Coordinator
jondrush User Page
ImageImage
jondrush
Waze Global Champs
Waze Global Champs
 
Posts: 2289
Joined: Tue Sep 22, 2009 10:20 pm
Location: South Eastern Pennsylvania, USA
Has thanked: 109 times
Been thanked: 361 times

Re: US Cartouche on Feb 2: Slow and many internal errors

Postby jondrush » Wed Feb 16, 2011 3:02 am

Dead ends without junctions at the "free" end do cause some map errors. I'd leave 'em until we here different from Waze.

I understand about cleaning up the junk before joining, but I've had some problems connecting roads when one did not have a junction and one did. I just zoom in and clean it up after.
Keeping the Waze maps tidy since 2009
Northeast Region Assistant Coordinator
jondrush User Page
ImageImage
jondrush
Waze Global Champs
Waze Global Champs
 
Posts: 2289
Joined: Tue Sep 22, 2009 10:20 pm
Location: South Eastern Pennsylvania, USA
Has thanked: 109 times
Been thanked: 361 times

Re: US Cartouche on Feb 2: Slow and many internal errors

Postby krankyd » Wed Feb 23, 2011 2:46 pm

we're currently estimating that we'll be able to upload the new cartouche early next week. We'll keep you updated (check status.waze.com to be sure you get the latest announcements, but we will also post on the forum)
wazing like a hurricane
krankyd
Waze Team
Waze Team
 
Posts: 939
Joined: Fri May 08, 2009 2:02 pm
Has thanked: 0 time
Been thanked: 3 times

Re: US Cartouche on Feb 2: Slow and many internal errors

Postby mapcat » Thu Feb 03, 2011 2:38 am

Very slow/impossible here too. Error messages ("Each pair of roads must belong...") return immediately, but for non-problematic nodes I get a server error almost every time.

EDIT: 20 min later, it seems to be working fine (slow, but normal-slow)
CM, USA/Canada ∙ iPhone 5 ∙ iOS 7.1
mapcat
Waze Global Champs
Waze Global Champs
 
Posts: 2444
Joined: Mon Dec 20, 2010 5:29 am
Has thanked: 95 times
Been thanked: 192 times

Re: US Cartouche on Feb 2: Slow and many internal errors

Postby mapcat » Mon Feb 14, 2011 3:39 am

jondrush wrote:Why would you be removing road end nodes?

I always remove road-end nodes if I'm connecting 2 segments of the same road. Otherwise there's at least one unnecessary node left over, often out of sight.
CM, USA/Canada ∙ iPhone 5 ∙ iOS 7.1
mapcat
Waze Global Champs
Waze Global Champs
 
Posts: 2444
Joined: Mon Dec 20, 2010 5:29 am
Has thanked: 95 times
Been thanked: 192 times

Re: US Cartouche on Feb 2: Slow and many internal errors

Postby mapcat » Mon Feb 14, 2011 1:42 pm

Wait, you're removing the nodes at the ends of dead-end roads and cul-de-sacs? How do you know they serve no purpose?
CM, USA/Canada ∙ iPhone 5 ∙ iOS 7.1
mapcat
Waze Global Champs
Waze Global Champs
 
Posts: 2444
Joined: Mon Dec 20, 2010 5:29 am
Has thanked: 95 times
Been thanked: 192 times

Re: US Cartouche on Feb 2: Slow and many internal errors

Postby mapcat » Mon Feb 14, 2011 7:54 pm

AlanOfTheBerg wrote:The primary reason is because if you record a road and then save it in Cartouche, or you create a new segment in Cartouche from archive just from using Add Road, that segment never includes a node at either end. If it were necessary, Cartouche would put a node at both ends automatically.

OK, that sounds logical enough. So removing them won't cause map errors, or mess up house numbers?

My take on why Cartouche doesn't automatically put nodes on new segments is that you're typically going to connect (at least) one end of the segment to an existing node, and so you'd have to delete one of them in order to do that.

Back to original topic: node removal seems faster today.
CM, USA/Canada ∙ iPhone 5 ∙ iOS 7.1
mapcat
Waze Global Champs
Waze Global Champs
 
Posts: 2444
Joined: Mon Dec 20, 2010 5:29 am
Has thanked: 95 times
Been thanked: 192 times

PreviousNext

Return to Waze Map Editor

Who is online

Users browsing this forum: glomp