mapcat wrote:CrackedLCD wrote:jasonh300 wrote:9. Gas stations suppress traffic. That's never been in question.
Do you name gas station landmarks? I've been naming the ones that were put in to suppress traffic, but I think after a certain number of them are drawn it starts to clutter the map too much.
In the USA, we're not supposed to be adding gas station landmarks. They imported a special uneditable layer for those.
mapcat wrote:Waze doesn't answer a lot of questions.
I don't know if having two sets of gas station landmarks will affect anything at all. "I really don't think" and "From what I've seen" is all you can offer here, because you don't know. You should, and I should, but we don't. Nobody knows. The only people with the capability to know don't talk. Maybe they don't know either.
AndyPoms wrote:Unholy wrote:2. In the NA server, adding a gas station landmark will not add a "pin" to the client's map - Currently the gas stations which appear there originated from a 3rd party data base.
3. If you wish to prevent "ghost traffic" jams and prevent Waze from navigating you through gas station road, please set the type of road in these gas stations to "parking lot" roads.
Playing devil's advocate here...
Why not use the Gas Station Landmark instead of parking lot roads for gas stations?
1) Both suppress the "ghost traffic jam".
2) You'll get a nice little highlight around the gas station.
3) A lot of gas stations have odd paths through them (in & out & around the pumps), wouldn't it easier just to drop a blob of a landmark over the whole area?
Does any of this create issues with the 3rd party pins?
+1Den_in_USA wrote:BlazeTool wrote:jasonh300 wrote:I've been asking the developers to make the parking lot roads much less visible in the client, so that they won't clutter up the map as much. I've also asked them to make them gray in the editor so they'll be visibly different from streets and not clutter the editor screen.
Here's hoping they do it. Personally, I'd like to see PL roads not display at all in the client and be their own layer in the editor that can be turned off. Visual clutter goes away, problem reports for parking lots can go away. Only drawbacks would be it's still data to be transferred to the client and the extra nodes could effect routing times. Not sure if there are ways to avoid that.
I agree with everything you say. Either display parking lot roads as a ligher color, narrower line or at least allow the driver to "hide" those roads if he wants to.
AndyPoms wrote:That is something we're still looking into - we're currently having issues figuring out what's in the water layer and what's not. We wanted to get the basics out first (so we had something to point users towards) and would continue working on these things later...daknife wrote:Similarly in this thread it was mentioned and not contested (and thus accepted in my understanding) that bodies of water that are common driver navigation landmarks and are NOT found in the water layer are allowed. The river running the length of the Salt Lake Valley, the Jordan River, is not in the water layer for most of it's length so I've just authorized the editor who has been begging to add it, to do so.
Users browsing this forum: No registered users