dbraughlr wrote:Are you talking about Level Highlighter?irowiki wrote:I meant, search for segments that aren't set to ground level currently, but that would probably be another script!
I'm not sure how I missed that one, thank you
dbraughlr wrote:Are you talking about Level Highlighter?irowiki wrote:I meant, search for segments that aren't set to ground level currently, but that would probably be another script!
That's pretty much it what I was looking for, however, this whole thing started because I posted that the "out of range elevation" check was not working for me. I'm finding quite a few "blank" elevation segments, but every time I try to permalink one, it reverts to ground elevation. Perhaps it is just a visual bug?dbraughlr wrote:I would be looking for drivable segments at the same elevation that touch or cross without forming a junction. These might look okay, but they do not route correctly.berestovskyy wrote: So we're looking at quite slow and complex check here. But what's is the "goal"? Does this non-ground elevation affects TTS or routing?
I can vouch for this, 10,000 errors in one validator report for old base mapped cow paths. An optional customizable limit might help me control my sessions and appease the wifeditchi56 wrote: If I could set a limit of, say, 100 in the Validator settings I could then just forget about it - and I probably wouldn't want to fix more than 100 problems in one session anyway.
That's how it was, by default. Maybe move the "exclude non editable" into the settings (where the sound setting is)olestas wrote:Hiding problems in locked segments is bad. I report those to corresponding level editors in my area. You could add option that hides them by default after installation of script.. but it should be possible to change it.
Where does it go though?"300.severity": "warning",
Re: elevation highlighter