Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Wojtas82

#31
Nope, I decided not to use it for now. I'll wait for Popej's update.
#32
Update in first post.
#33
Uffff I thought it's gonna take a lot more time :) Thats good news :)
BTW I have made new theme based on StyleCycle.
It shows:
Bicycle Routes in colours (wider ones, solid colour)
Hiking Routes in colours (narrower ones,dashed)
Sac Scale - (black=easy, blue=medium, red=hard)
Mtb Uphill (numbers along tracks and paths)
Incline Up and down (red/yellow arrows showing downhill direction)
Mtb Scale still to be done.
There's still plenty to do but at least you can check results I made so far.I wonder what y'all think.
Edit:
I forgot, Popej, could you add these tags when you have some spare time?
amenity=bicycle_parking
cycleway=lane
cycleway=opposite_lane
cycleway=opposite
cycleway=shared_lane
cycleway:left=lane
cycleway:right=lane
bicycle=permissive

thanks :)
#34
As Locus team said:it's still in testing but why not we test it with them? Popej how difficult is it to make one-sided routes? That would be great solution.
#35
Yeah, exactly I also noticed it. But I don't see a solution for this one unless dy parameter is added to the whole route not the part of the road. You know what I mean? I'm not sure. Maybe google "osmapa szlaki" and check this map I heard they tried to solve this problem?
#36
These parallel lines look very nice Jusc. Very useful when you have a hiking route and i.e. 2 bicycle routes. You can easly follow the route you want.
#38
Oh thats a shame. This feature gives a lot of possibilities.
#39
Thanks! Any estimated date of implementation Menion
#40
After many test I was able to display parallel lines but sometimes parts of them are missing randomly like here.

When dy is set to 0 the whole route is displayed properly...
<rule e="way" k="osmc_color" v="red">
<line stroke="#FF0000" priority="40" force-draw="1" dy="16" stroke-linejoin="round" stroke-width="1" stroke-linecap="round" />
</rule>

Here's a link to OSM
http://www.openstreetmap.org/way/184490078
Any one knows solution?
#41
Ok. We can try it.
Second case, I wonder if there is any solution for that one That would make maps even more readable and intuitive.
#42
Quote from: popej on October 14, 2014, 12:00:54
Quote from: Wojtas82 on October 14, 2014, 09:43:49
<rule e="way" k="network" v="iwn AND nwn">
2 conditions should form AND:
<rule e="way" k="network" v="iwn">
   <rule e="way" k="network" v="nwn">

But you won't find that kind of routes on my maps.

I have 2 ideas about multiple routes on one way:
- add some artificial tag, like "instance=2" or "instance:lcn=2" on second route,
- draw second route in opposite direction,

I'd rather prefer first idea, this won't change anything in OSM data.
Popej, sorry I meant iCn and nCn :)
About route names: I also prefer first method. I wonder how that would work? Drawing second route in opposite direction isn't a best idea, what if we have 3 or more routes on the road? :)

EDIT: What I'm trying to achieve:
Example 1: 1 blue route on the road shows solid blue line.
Example 2: 1 blue and 1 green route on the route shows dashed blue/green line.

<rule e="way" k="state" v="~">
<rule e="way" k="osmc" v="*">
<rule e="way" k="route" v="bicycle" zoom-min="17">
<rule e="way" k="osmc_color" v="blue">
<line stroke="#880000FF" stroke-width="5" stroke-linecap="round" />
</rule>
<rule e="way" k="osmc_color" v="blue">
<rule e="way" k="osmc_color" v="green">
<line stroke="#880000FF" stroke-width="5" stroke-dasharray="10,10" stroke-linecap="butt" />
<line stroke="#88008000" stroke-width="5" stroke-dasharray="0,10,10,0" stroke-linecap="butt" />
</rule>
</rule>
<rule e="way" k="osmc_color" v="yellow">
<line stroke="#88FFFF00" stroke-width="5" stroke-linecap="round" />
</rule>
<rule e="way" k="osmc_color" v="green">
<line stroke="#88008000" stroke-width="5" stroke-linecap="round" />
</rule>
<rule e="way" k="osmc_color" v="red">
<line stroke="#88FF0000" stroke-width="5" stroke-linecap="round" />
</rule>
<rule e="way" k="osmc_color" v="black">
<line stroke="#88000000" stroke-width="5" stroke-linecap="round" />
</rule>
<rule e="way" k="osmc_color" v="white">
<line stroke="#9966FF" stroke-width="3" stroke-linecap="round" />
</rule>
</rule>
</rule>
</rule>


But it doesn't seem to work....
This part dosn't display at all
            <rule e="way" k="osmc_color" v="blue">
               <rule e="way" k="osmc_color" v="green">
                  <line stroke="#880000FF" stroke-width="5" stroke-dasharray="10,10" stroke-linecap="butt" />
                  <line stroke="#88008000" stroke-width="5" stroke-dasharray="0,10,10,0" stroke-linecap="butt" />
               </rule>
            </rule>
#43
Quote from: popej on October 13, 2014, 23:28:40
Quote from: Wojtas82 on October 13, 2014, 19:33:29Maybe you could somehow merge names of 2 LCN so the road with 2 LCN has only one route name like this "LCN 1 / LCN 2". And the same for "ref" tags.
I"ll think about it. I can't see any nice solution but maybe I'll get a good idea.



That would be great. Thanks in advance for trying ;)

One other thing:
    <rule e="way" k="network" v="iwn|nwn" >
This short example rule applies to iwn OR nwn, but is it possible to write a rule which applies to both of these routes? I'm talking about a rule that would work like this:
<rule e="way" k="network" v="iwn AND nwn">
So it only works when both conditions are met... I.e. a part of a road which has iwn AND ncn on it....
That would help me a lot with color coded routes.
#44
Hi Popej, I'm testing the tags you've added, so far so good. Great job. I need some extra time to modify my theme so I will also get back soon. I was wondering if we could solve path text overlapping problem like this:

Let's say we have to LCN on the same road and we want to display their names properly (not overlapping each other). Maybe you could somehow merge names of 2 LCN so the road with 2 LCN has only one route name like this "LCN 1 / LCN 2". And the same for "ref" tags.That could be a nice workaround. And if we have RCN and LCN on one road we could just use "dy" attribute so nothing is really needed to be done in this particular case. Thanks in advance :)
#45
All good, downloading.