make your own render.xml

[d***@gmail.com]

I am using OsmAnd+ Ver. 2.1.1 and would like to change the color to red and
width of the gpx track. I have modified the default.render.xml. for gpx
this way:

<renderingAttribute name="gpx">
<case strokeWidth="3:2" cap="ROUND">
<case nightMode="true" color="#b4b319ff"/>
<case additional="routePoints=true" pathEffect="6_5" color=
"#ffff0000"/>
<case color="#ffff0000"/></case>
</renderingAttribute>

I see no change in my gpx track style. Is there a problem with my
modification or is changing one attribute in render.xml not as simple as
this?

[Harry van der Wolf]

As OsmAnd does not entirely remove itself from memory (see the topics about
exit/close button), your render file is not read again (and neither some
other files like routing.xml etc). Please try to stop OsmAnd from a task
manager or reboot your device.

And of course make sure your file is really named default.render.xml

Harry

Post by d***@gmail.com
I am using OsmAnd+ Ver. 2.1.1 and would like to change the color to red
and width of the gpx track. I have modified the default.render.xml. for gpx
<renderingAttribute name="gpx">
<case strokeWidth="3:2" cap="ROUND">
<case nightMode="true" color="#b4b319ff"/>
<case additional="routePoints=true" pathEffect="6_5" color=
"#ffff0000"/>
<case color="#ffff0000"/></case>
</renderingAttribute>
I see no change in my gpx track style. Is there a problem with my
modification or is changing one attribute in render.xml not as simple as
this?
--
You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

[d***@gmail.com]

Thanks Harry,

Finally! Your suggestions about memory etc., got me to take another look at
the OsmAnd file structure. I had used OsmAnd to move my files to the sd
card. That worked fine. So I was putting my experimental render.xml files
in this folder: SDcard>osmand>rendering/default.xml. Well, as I you
probably know, that's not the location that should be used. The location
that got things working is:

SDcard>Android>data>net.osmand.plus>files>rendering/default.render.xml.

What is the first default.xml used for?


Thanks, again.

Post by Harry van der Wolf
As OsmAnd does not entirely remove itself from memory (see the topics
about exit/close button), your render file is not read again (and neither
some other files like routing.xml etc). Please try to stop OsmAnd from a
task manager or reboot your device.
And of course make sure your file is really named default.render.xml
Harry

Post by d***@gmail.com
I am using OsmAnd+ Ver. 2.1.1 and would like to change the color to red
and width of the gpx track. I have modified the default.render.xml. for gpx
<renderingAttribute name="gpx">
<case strokeWidth="3:2" cap="ROUND">
<case nightMode="true" color="#b4b319ff"/>
<case additional="routePoints=true" pathEffect="6_5" color=
"#ffff0000"/>
<case color="#ffff0000"/></case>
</renderingAttribute>
I see no change in my gpx track style. Is there a problem with my
modification or is changing one attribute in render.xml not as simple as
this?
--
You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

[Harry van der Wolf]

The default.xml is more or less a template.
You can also create derived render files where only parts are changed
instead of modifying the default.render.xml. It's even better as
changes/additions/fixes to the default.render.xml are also propagated to
your derived render file.
If you take a look at
https://github.com/osmandapp/OsmAnd-resources/tree/master/rendering_styles,
you see that only the default.render.xml is a "complete" file. All the
others are derivatives and only describe what's changed from the default.
This "derivation" is reflected in the top line of those render files.
The default.render.xml has <renderingStyle name="default" depends=""
defaultColor="#f1eae4" version="1">
As you can see it depends on nothing.
If I take any of the others, for example the UniRS, you see in the top line
<renderingStyle name="UniRS" depends="default" defaultColor="#f1eae4"
version="1.2">
It depends on the default.render.xml (not the template).

Harry

[P Wat]

Hi Harry.
If this question is off topic please let me know so I can raise a new one.
The solid purple route line obscures the road/track/path which is about to
be followed. This is a real nuisance because you cannot make your own
judgement about whether it is suitable (surface/speed, etc).
Last December Jan van Bekkum provided a file to generate a route line which
did not obscure the route. This was really useful but the "recent" Osmand
update reverted to solid purple route line.
Is your info about rendering relevant to this issue, or should I re-install
Jan vB's files?
Thanks
PaulW
==============

Post by Harry van der Wolf
The default.xml is more or less a template.
You can also create derived render files where only parts are changed
instead of modifying the default.render.xml. It's even better as
changes/additions/fixes to the default.render.xml are also propagated to
your derived render file.
If you take a look at
https://github.com/osmandapp/OsmAnd-resources/tree/master/rendering_styles,
you see that only the default.render.xml is a "complete" file. All the
others are derivatives and only describe what's changed from the default.
This "derivation" is reflected in the top line of those render files.
The default.render.xml has <renderingStyle name="default" depends=""
defaultColor="#f1eae4" version="1">
As you can see it depends on nothing.
If I take any of the others, for example the UniRS, you see in the top line
<renderingStyle name="UniRS" depends="default" defaultColor="#f1eae4"
version="1.2">
It depends on the default.render.xml (not the template).
Harry

[Harry van der Wolf]

It is indeed off topic :) , but I will answer it here as it is related.

If Jan vB's file was also a default.render.xml instead of a derived file,
that would explain why your change is now gone. This means that you could
copy Jan vB's file back, but that would mean that the changes done to the
default.render.xml would be lost again.

That's exactly the reason why you should make a derived file and not a copy
of the default.render.xml.
All colors are defined by there hexadecimal RGB values. This means 6
"digits" like #00FFFF . This means "no red, full green and full blue".
If you want transparency you have to add a hexadecimal value in front of
it, which makes it an 8 "digit" value: 00 for full transparency and FF for
opaque.
The current value for the gpx color is#B400FFFF, The B4 value means that it
is close to opaque.
I assume that Jan used a much lower value like 99 or so. Please also keep
in mind that with more transparency, a lower value, also the brilliance of
the other colors is reduced giving a more "washed out" pale effect.

In this case I would make a derived render file like gpxcolor.render.xml,
containing something like:

<?xml version="1.0" encoding="utf-8"?>
<renderingStyle name="gpxcolor" depends="default" defaultColor="#f1eae4"
version="1">

<renderingAttribute name="gpxColor"> <!-- deprecated -->
<case attrColorValue="#b400ffff"/>
</renderingAttribute>

<renderingAttribute name="gpx">
<case strokeWidth="7:6" cap="ROUND">
<case nightMode="true" color="#b4b319ff"/>
<case additional="routePoints=true" pathEffect="6_5" color="#b400ffff"/>
<case color="#b400ffff"/>
</case>
</renderingAttribute>

</renderingStyle>


Note that I used both the old deprecated gpxcolor value as well as the new
gpx attribute.
Play with (reduce) the b4 value until you are satisfied.

Note also that when selecting a new render file it is displayed
immediately, but upon changes of the a render file, as mentioned in the
above posts, that you really need to close OsmAnd by using a task manager
or reboot your phone/device to get the wanted effect.

Harry

Post by P Wat
Hi Harry.
If this question is off topic please let me know so I can raise a new one.
The solid purple route line obscures the road/track/path which is about to
be followed. This is a real nuisance because you cannot make your own
judgement about whether it is suitable (surface/speed, etc).
Last December Jan van Bekkum provided a file to generate a route line
which did not obscure the route. This was really useful but the "recent"
Osmand update reverted to solid purple route line.
Is your info about rendering relevant to this issue, or should I
re-install Jan vB's files?
Thanks
PaulW
==============

Post by Harry van der Wolf
The default.xml is more or less a template.
You can also create derived render files where only parts are changed
instead of modifying the default.render.xml. It's even better as
changes/additions/fixes to the default.render.xml are also propagated to
your derived render file.
If you take a look at
https://github.com/osmandapp/OsmAnd-resources/tree/master/rendering_styles,
you see that only the default.render.xml is a "complete" file. All the
others are derivatives and only describe what's changed from the default.
This "derivation" is reflected in the top line of those render files.
The default.render.xml has <renderingStyle name="default" depends=""
defaultColor="#f1eae4" version="1">
As you can see it depends on nothing.
If I take any of the others, for example the UniRS, you see in the top line
<renderingStyle name="UniRS" depends="default" defaultColor="#f1eae4"
version="1.2">
It depends on the default.render.xml (not the template).
Harry
--

You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

[P Wat]

Hello Harry
Thank you for the swift reply.

The significance of "default.render.xml" Vs "derived file" goes over my
head but maybe that doesn't matter.

The file from JanVB on 30/12/14 was called GPXR08.render and contained:-

<?xml version="1.0" encoding="UTF-8"?>
-<renderingStyle version="1" defaultColor="#ffffff" depends="default"
name="Route"> -<renderingAttribute name="route"> -<filter color="#FF0000"
strokeWidth="4" pathEffect="4_8"> <filter nightMode="true"/> </filter>
</renderingAttribute> -<renderingAttribute name="gpx"> -<filter
color="#FF0000" strokeWidth="2"> <filter nightMode="true"/> </filter>
</renderingAttribute> </renderingStyle>

Would it have much the same effect?
I will try yours' first, anyway. Thank you.

Regards
Paul W
===========

Post by Harry van der Wolf
It is indeed off topic :) , but I will answer it here as it is related.
If Jan vB's file was also a default.render.xml instead of a derived file,
that would explain why your change is now gone. This means that you could
copy Jan vB's file back, but that would mean that the changes done to the
default.render.xml would be lost again.
That's exactly the reason why you should make a derived file and not a
copy of the default.render.xml.
All colors are defined by there hexadecimal RGB values. This means 6
"digits" like #00FFFF . This means "no red, full green and full blue".
If you want transparency you have to add a hexadecimal value in front of
it, which makes it an 8 "digit" value: 00 for full transparency and FF for
opaque.
The current value for the gpx color is#B400FFFF, The B4 value means that
it is close to opaque.
I assume that Jan used a much lower value like 99 or so. Please also keep
in mind that with more transparency, a lower value, also the brilliance of
the other colors is reduced giving a more "washed out" pale effect.
In this case I would make a derived render file like gpxcolor.render.xml,
<?xml version="1.0" encoding="utf-8"?>
<renderingStyle name="gpxcolor" depends="default" defaultColor="#f1eae4"
version="1">
<renderingAttribute name="gpxColor"> <!-- deprecated -->
<case attrColorValue="#b400ffff"/>
</renderingAttribute>
<renderingAttribute name="gpx">
<case strokeWidth="7:6" cap="ROUND">
<case nightMode="true" color="#b4b319ff"/>
<case additional="routePoints=true" pathEffect="6_5" color="#b400ffff"/>
<case color="#b400ffff"/>
</case>
</renderingAttribute>
</renderingStyle>
Note that I used both the old deprecated gpxcolor value as well as the new
gpx attribute.
Play with (reduce) the b4 value until you are satisfied.
Note also that when selecting a new render file it is displayed
immediately, but upon changes of the a render file, as mentioned in the
above posts, that you really need to close OsmAnd by using a task manager
or reboot your phone/device to get the wanted effect.
Harry

Post by P Wat
Hi Harry.
If this question is off topic please let me know so I can raise a new one.
The solid purple route line obscures the road/track/path which is about
to be followed. This is a real nuisance because you cannot make your own
judgement about whether it is suitable (surface/speed, etc).
Last December Jan van Bekkum provided a file to generate a route line
which did not obscure the route. This was really useful but the "recent"
Osmand update reverted to solid purple route line.
Is your info about rendering relevant to this issue, or should I
re-install Jan vB's files?
Thanks
PaulW
==============

Post by Harry van der Wolf
The default.xml is more or less a template.
You can also create derived render files where only parts are changed
instead of modifying the default.render.xml. It's even better as
changes/additions/fixes to the default.render.xml are also propagated to
your derived render file.
If you take a look at
https://github.com/osmandapp/OsmAnd-resources/tree/master/rendering_styles,
you see that only the default.render.xml is a "complete" file. All the
others are derivatives and only describe what's changed from the default.
This "derivation" is reflected in the top line of those render files.
The default.render.xml has <renderingStyle name="default" depends=""
defaultColor="#f1eae4" version="1">
As you can see it depends on nothing.
If I take any of the others, for example the UniRS, you see in the top line
<renderingStyle name="UniRS" depends="default" defaultColor="#f1eae4"
version="1.2">
It depends on the default.render.xml (not the template).
Harry
--

You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

[Harry van der Wolf]

Hi,

What I meant with derived should actually be parent-child.
The default.render.xml is the parent. All the other render files are
chillds (depends="default").
All attributes are inherited from the parent except the ones you specify in
the child.

The original gpxcolor is a greenish color. My example simply makes that
greenish color more transparent.

Jan's example creates a red dashed line for a route and a narrow red line
for the gpx track. No transparency.
But the file structure is weird and the dashed line should have two color
values (if this is the complete file).

Harry

Post by P Wat
Hello Harry
Thank you for the swift reply.
The significance of "default.render.xml" Vs "derived file" goes over my
head but maybe that doesn't matter.
The file from JanVB on 30/12/14 was called GPXR08.render and contained:-
<?xml version="1.0" encoding="UTF-8"?>
-<renderingStyle version="1" defaultColor="#ffffff" depends="default"
name="Route"> -<renderingAttribute name="route"> -<filter color="#FF0000"
strokeWidth="4" pathEffect="4_8"> <filter nightMode="true"/> </filter>
</renderingAttribute> -<renderingAttribute name="gpx"> -<filter
color="#FF0000" strokeWidth="2"> <filter nightMode="true"/> </filter>
</renderingAttribute> </renderingStyle>
Would it have much the same effect?
I will try yours' first, anyway. Thank you.
Regards
Paul W
===========

Post by Harry van der Wolf
It is indeed off topic :) , but I will answer it here as it is related.
If Jan vB's file was also a default.render.xml instead of a derived file,
that would explain why your change is now gone. This means that you could
copy Jan vB's file back, but that would mean that the changes done to the
default.render.xml would be lost again.
That's exactly the reason why you should make a derived file and not a
copy of the default.render.xml.
All colors are defined by there hexadecimal RGB values. This means 6
"digits" like #00FFFF . This means "no red, full green and full blue".
If you want transparency you have to add a hexadecimal value in front of
it, which makes it an 8 "digit" value: 00 for full transparency and FF for
opaque.
The current value for the gpx color is#B400FFFF, The B4 value means that
it is close to opaque.
I assume that Jan used a much lower value like 99 or so. Please also keep
in mind that with more transparency, a lower value, also the brilliance of
the other colors is reduced giving a more "washed out" pale effect.
In this case I would make a derived render file like gpxcolor.render.xml,
<?xml version="1.0" encoding="utf-8"?>
<renderingStyle name="gpxcolor" depends="default" defaultColor="#f1eae4"
version="1">
<renderingAttribute name="gpxColor"> <!-- deprecated -->
<case attrColorValue="#b400ffff"/>
</renderingAttribute>
<renderingAttribute name="gpx">
<case strokeWidth="7:6" cap="ROUND">
<case nightMode="true" color="#b4b319ff"/>
<case additional="routePoints=true" pathEffect="6_5" color="#b400ffff"/>
<case color="#b400ffff"/>
</case>
</renderingAttribute>
</renderingStyle>
Note that I used both the old deprecated gpxcolor value as well as the
new gpx attribute.
Play with (reduce) the b4 value until you are satisfied.
Note also that when selecting a new render file it is displayed
immediately, but upon changes of the a render file, as mentioned in the
above posts, that you really need to close OsmAnd by using a task manager
or reboot your phone/device to get the wanted effect.
Harry

Post by P Wat
Hi Harry.
If this question is off topic please let me know so I can raise a new one.
The solid purple route line obscures the road/track/path which is about
to be followed. This is a real nuisance because you cannot make your own
judgement about whether it is suitable (surface/speed, etc).
Last December Jan van Bekkum provided a file to generate a route line
which did not obscure the route. This was really useful but the "recent"
Osmand update reverted to solid purple route line.
Is your info about rendering relevant to this issue, or should I
re-install Jan vB's files?
Thanks
PaulW
==============

Post by Harry van der Wolf
The default.xml is more or less a template.
You can also create derived render files where only parts are changed
instead of modifying the default.render.xml. It's even better as
changes/additions/fixes to the default.render.xml are also propagated to
your derived render file.
If you take a look at
https://github.com/osmandapp/OsmAnd-resources/tree/master/rendering_styles,
you see that only the default.render.xml is a "complete" file. All the
others are derivatives and only describe what's changed from the default.
This "derivation" is reflected in the top line of those render files.
The default.render.xml has <renderingStyle name="default" depends=""
defaultColor="#f1eae4" version="1">
As you can see it depends on nothing.
If I take any of the others, for example the UniRS, you see in the top line
<renderingStyle name="UniRS" depends="default" defaultColor="#f1eae4"
version="1.2">
It depends on the default.render.xml (not the template).
Harry
--

You received this message because you are subscribed to the Google
Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

[d***@gmail.com]

Hello Harry,

I tried adding your gpxcolor.render.xml to my SDcard>Android>data>net.osmand.plus>files>rendering/
folder and the map displayed the default gpx color, not the one in
gpxcolor.render.xml. If, however, I repeated what I did initially, putting
the *full* default.render.xml into the above folder with the gpx color
modified then the tracks show the modified color.

I noticed another thing. If there is no file with the name
default.render.xml in the above rendering folder, say I delete it, then it
appears there when I again start up OsmAnd. It seems like it's being
automatically copied there if there a default.render.xml there when OsmAnd
is started.

Thoughts? Hope my description isn't too confusing.

Post by Harry van der Wolf
Hi,
What I meant with derived should actually be parent-child.
The default.render.xml is the parent. All the other render files are
chillds (depends="default").
All attributes are inherited from the parent except the ones you specify
in the child.
The original gpxcolor is a greenish color. My example simply makes that
greenish color more transparent.
Jan's example creates a red dashed line for a route and a narrow red line
for the gpx track. No transparency.
But the file structure is weird and the dashed line should have two color
values (if this is the complete file).
Harry

Post by P Wat
Hello Harry
Thank you for the swift reply.
The significance of "default.render.xml" Vs "derived file" goes over my
head but maybe that doesn't matter.
The file from JanVB on 30/12/14 was called GPXR08.render and contained:-
<?xml version="1.0" encoding="UTF-8"?>
-<renderingStyle version="1" defaultColor="#ffffff" depends="default"
name="Route"> -<renderingAttribute name="route"> -<filter color="#FF0000"
strokeWidth="4" pathEffect="4_8"> <filter nightMode="true"/> </filter>
</renderingAttribute> -<renderingAttribute name="gpx"> -<filter
color="#FF0000" strokeWidth="2"> <filter nightMode="true"/> </filter>
</renderingAttribute> </renderingStyle>
Would it have much the same effect?
I will try yours' first, anyway. Thank you.
Regards
Paul W
===========

Post by Harry van der Wolf
It is indeed off topic :) , but I will answer it here as it is related.
If Jan vB's file was also a default.render.xml instead of a derived
file, that would explain why your change is now gone. This means that you
could copy Jan vB's file back, but that would mean that the changes done to
the default.render.xml would be lost again.
That's exactly the reason why you should make a derived file and not a
copy of the default.render.xml.
All colors are defined by there hexadecimal RGB values. This means 6
"digits" like #00FFFF . This means "no red, full green and full blue".
If you want transparency you have to add a hexadecimal value in front of
it, which makes it an 8 "digit" value: 00 for full transparency and FF for
opaque.
The current value for the gpx color is#B400FFFF, The B4 value means
that it is close to opaque.
I assume that Jan used a much lower value like 99 or so. Please also
keep in mind that with more transparency, a lower value, also the
brilliance of the other colors is reduced giving a more "washed out" pale
effect.
In this case I would make a derived render file like
<?xml version="1.0" encoding="utf-8"?>
<renderingStyle name="gpxcolor" depends="default" defaultColor="#f1eae4"
version="1">
<renderingAttribute name="gpxColor"> <!-- deprecated -->
<case attrColorValue="#b400ffff"/>
</renderingAttribute>
<renderingAttribute name="gpx">
<case strokeWidth="7:6" cap="ROUND">
<case nightMode="true" color="#b4b319ff"/>
<case additional="routePoints=true" pathEffect="6_5" color="#b400ffff"/>
<case color="#b400ffff"/>
</case>
</renderingAttribute>
</renderingStyle>
Note that I used both the old deprecated gpxcolor value as well as the
new gpx attribute.
Play with (reduce) the b4 value until you are satisfied.
Note also that when selecting a new render file it is displayed
immediately, but upon changes of the a render file, as mentioned in the
above posts, that you really need to close OsmAnd by using a task manager
or reboot your phone/device to get the wanted effect.
Harry

Post by P Wat
Hi Harry.
If this question is off topic please let me know so I can raise a new one.
The solid purple route line obscures the road/track/path which is about
to be followed. This is a real nuisance because you cannot make your own
judgement about whether it is suitable (surface/speed, etc).
Last December Jan van Bekkum provided a file to generate a route line
which did not obscure the route. This was really useful but the "recent"
Osmand update reverted to solid purple route line.
Is your info about rendering relevant to this issue, or should I
re-install Jan vB's files?
Thanks
PaulW
==============

Post by Harry van der Wolf
The default.xml is more or less a template.
You can also create derived render files where only parts are changed
instead of modifying the default.render.xml. It's even better as
changes/additions/fixes to the default.render.xml are also propagated to
your derived render file.
If you take a look at
https://github.com/osmandapp/OsmAnd-resources/tree/master/rendering_styles,
you see that only the default.render.xml is a "complete" file. All the
others are derivatives and only describe what's changed from the default.
This "derivation" is reflected in the top line of those render files.
The default.render.xml has <renderingStyle name="default" depends=""
defaultColor="#f1eae4" version="1">
As you can see it depends on nothing.
If I take any of the others, for example the UniRS, you see in the top line
<renderingStyle name="UniRS" depends="default" defaultColor="#f1eae4"
version="1.2">
It depends on the default.render.xml (not the template).
Harry
--

You received this message because you are subscribed to the Google
Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

[Harry van der Wolf]

I can't answer your first observation. It can also be a minor bug in OsmAnd
(there are more).

The default.render.xml is packed within the apk (among with a few other
config files). Upon installation this file is copied into the correct
folder. And when you remove it, either on purpose or by accident, it is
copied back again from inside the apk upon restart. You can replace the
default.render.xml by another default.render.xml. Only the fact whether the
file exists is checked, not the contents or a CRC-check or something like
that.

I did not use another color in my gpxcoler example. I used a slightly more
transparent color.

Post by d***@gmail.com
Hello Harry,
I tried adding your gpxcolor.render.xml to my SDcard>Android>data>net.osmand.plus>files>rendering/
folder and the map displayed the default gpx color, not the one in
gpxcolor.render.xml. If, however, I repeated what I did initially, putting
the *full* default.render.xml into the above folder with the gpx color
modified then the tracks show the modified color.
I noticed another thing. If there is no file with the name
default.render.xml in the above rendering folder, say I delete it, then it
appears there when I again start up OsmAnd. It seems like it's being
automatically copied there if there a default.render.xml there when OsmAnd
is started.
Thoughts? Hope my description isn't too confusing.

Post by Harry van der Wolf
Hi,
What I meant with derived should actually be parent-child.
The default.render.xml is the parent. All the other render files are
chillds (depends="default").
All attributes are inherited from the parent except the ones you specify
in the child.
The original gpxcolor is a greenish color. My example simply makes that
greenish color more transparent.
Jan's example creates a red dashed line for a route and a narrow red line
for the gpx track. No transparency.
But the file structure is weird and the dashed line should have two color
values (if this is the complete file).
Harry

Post by P Wat
Hello Harry
Thank you for the swift reply.
The significance of "default.render.xml" Vs "derived file" goes over my
head but maybe that doesn't matter.
The file from JanVB on 30/12/14 was called GPXR08.render and contained:-
<?xml version="1.0" encoding="UTF-8"?>
-<renderingStyle version="1" defaultColor="#ffffff" depends="default"
name="Route"> -<renderingAttribute name="route"> -<filter color="#FF0000"
strokeWidth="4" pathEffect="4_8"> <filter nightMode="true"/> </filter>
</renderingAttribute> -<renderingAttribute name="gpx"> -<filter
color="#FF0000" strokeWidth="2"> <filter nightMode="true"/> </filter>
</renderingAttribute> </renderingStyle>
Would it have much the same effect?
I will try yours' first, anyway. Thank you.
Regards
Paul W
===========

Post by Harry van der Wolf
It is indeed off topic :) , but I will answer it here as it is related.
If Jan vB's file was also a default.render.xml instead of a derived
file, that would explain why your change is now gone. This means that you
could copy Jan vB's file back, but that would mean that the changes done to
the default.render.xml would be lost again.
That's exactly the reason why you should make a derived file and not a
copy of the default.render.xml.
All colors are defined by there hexadecimal RGB values. This means 6
"digits" like #00FFFF . This means "no red, full green and full blue".
If you want transparency you have to add a hexadecimal value in front
of it, which makes it an 8 "digit" value: 00 for full transparency and FF
for opaque.
The current value for the gpx color is#B400FFFF, The B4 value means
that it is close to opaque.
I assume that Jan used a much lower value like 99 or so. Please also
keep in mind that with more transparency, a lower value, also the
brilliance of the other colors is reduced giving a more "washed out" pale
effect.
In this case I would make a derived render file like
<?xml version="1.0" encoding="utf-8"?>
<renderingStyle name="gpxcolor" depends="default"
defaultColor="#f1eae4" version="1">
<renderingAttribute name="gpxColor"> <!-- deprecated -->
<case attrColorValue="#b400ffff"/>
</renderingAttribute>
<renderingAttribute name="gpx">
<case strokeWidth="7:6" cap="ROUND">
<case nightMode="true" color="#b4b319ff"/>
<case additional="routePoints=true" pathEffect="6_5" color="#b400ffff"/>
<case color="#b400ffff"/>
</case>
</renderingAttribute>
</renderingStyle>
Note that I used both the old deprecated gpxcolor value as well as the
new gpx attribute.
Play with (reduce) the b4 value until you are satisfied.
Note also that when selecting a new render file it is displayed
immediately, but upon changes of the a render file, as mentioned in the
above posts, that you really need to close OsmAnd by using a task manager
or reboot your phone/device to get the wanted effect.
Harry

Post by P Wat
Hi Harry.
If this question is off topic please let me know so I can raise a new one.
The solid purple route line obscures the road/track/path which is
about to be followed. This is a real nuisance because you cannot make your
own judgement about whether it is suitable (surface/speed, etc).
Last December Jan van Bekkum provided a file to generate a route line
which did not obscure the route. This was really useful but the "recent"
Osmand update reverted to solid purple route line.
Is your info about rendering relevant to this issue, or should I
re-install Jan vB's files?
Thanks
PaulW
==============

Post by Harry van der Wolf
The default.xml is more or less a template.
You can also create derived render files where only parts are changed
instead of modifying the default.render.xml. It's even better as
changes/additions/fixes to the default.render.xml are also propagated to
your derived render file.
If you take a look at
https://github.com/osmandapp/OsmAnd-resources/tree/master/rendering_styles,
you see that only the default.render.xml is a "complete" file. All the
others are derivatives and only describe what's changed from the default.
This "derivation" is reflected in the top line of those render files.
The default.render.xml has <renderingStyle name="default" depends=""
defaultColor="#f1eae4" version="1">
As you can see it depends on nothing.
If I take any of the others, for example the UniRS, you see in the top line
<renderingStyle name="UniRS" depends="default" defaultColor="#f1eae4"
version="1.2">
It depends on the default.render.xml (not the template).
Harry
--

You received this message because you are subscribed to the Google
Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google
Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

[d***@gmail.com]

The behavior you describe with the default.render.xml file is what I'm
observing.

Furthermore, now I see gpxcolor as one of the choices in the Vector
renderer list under Map style. When I select it, the gpx tracks are
displayed as styled in gpxcolor.xml. When I select OsmAnd as the vector
renderer, the tracks return to the default style. So it seems to be working
as expected...at least for now :)

Thanks again for your help.

Post by Harry van der Wolf
I can't answer your first observation. It can also be a minor bug in
OsmAnd (there are more).
The default.render.xml is packed within the apk (among with a few other
config files). Upon installation this file is copied into the correct
folder. And when you remove it, either on purpose or by accident, it is
copied back again from inside the apk upon restart. You can replace the
default.render.xml by another default.render.xml. Only the fact whether the
file exists is checked, not the contents or a CRC-check or something like
that.
I did not use another color in my gpxcoler example. I used a slightly more
transparent color.

Post by d***@gmail.com
Hello Harry,
I tried adding your gpxcolor.render.xml to my SDcard>Android>data>net.osmand.plus>files>rendering/
folder and the map displayed the default gpx color, not the one in
gpxcolor.render.xml. If, however, I repeated what I did initially, putting
the *full* default.render.xml into the above folder with the gpx color
modified then the tracks show the modified color.
I noticed another thing. If there is no file with the name
default.render.xml in the above rendering folder, say I delete it, then it
appears there when I again start up OsmAnd. It seems like it's being
automatically copied there if there a default.render.xml there when OsmAnd
is started.
Thoughts? Hope my description isn't too confusing.

Post by Harry van der Wolf
Hi,
What I meant with derived should actually be parent-child.
The default.render.xml is the parent. All the other render files are
chillds (depends="default").
All attributes are inherited from the parent except the ones you specify
in the child.
The original gpxcolor is a greenish color. My example simply makes that
greenish color more transparent.
Jan's example creates a red dashed line for a route and a narrow red
line for the gpx track. No transparency.
But the file structure is weird and the dashed line should have two
color values (if this is the complete file).
Harry

Post by P Wat
Hello Harry
Thank you for the swift reply.
The significance of "default.render.xml" Vs "derived file" goes over my
head but maybe that doesn't matter.
The file from JanVB on 30/12/14 was called GPXR08.render and contained:-
<?xml version="1.0" encoding="UTF-8"?>
-<renderingStyle version="1" defaultColor="#ffffff" depends="default"
name="Route"> -<renderingAttribute name="route"> -<filter color="#FF0000"
strokeWidth="4" pathEffect="4_8"> <filter nightMode="true"/> </filter>
</renderingAttribute> -<renderingAttribute name="gpx"> -<filter
color="#FF0000" strokeWidth="2"> <filter nightMode="true"/> </filter>
</renderingAttribute> </renderingStyle>
Would it have much the same effect?
I will try yours' first, anyway. Thank you.
Regards
Paul W
===========

Post by Harry van der Wolf
It is indeed off topic :) , but I will answer it here as it is related.
If Jan vB's file was also a default.render.xml instead of a derived
file, that would explain why your change is now gone. This means that you
could copy Jan vB's file back, but that would mean that the changes done to
the default.render.xml would be lost again.
That's exactly the reason why you should make a derived file and not a
copy of the default.render.xml.
All colors are defined by there hexadecimal RGB values. This means 6
"digits" like #00FFFF . This means "no red, full green and full blue".
If you want transparency you have to add a hexadecimal value in front
of it, which makes it an 8 "digit" value: 00 for full transparency and FF
for opaque.
The current value for the gpx color is#B400FFFF, The B4 value means
that it is close to opaque.
I assume that Jan used a much lower value like 99 or so. Please also
keep in mind that with more transparency, a lower value, also the
brilliance of the other colors is reduced giving a more "washed out" pale
effect.
In this case I would make a derived render file like
<?xml version="1.0" encoding="utf-8"?>
<renderingStyle name="gpxcolor" depends="default"
defaultColor="#f1eae4" version="1">
<renderingAttribute name="gpxColor"> <!-- deprecated -->
<case attrColorValue="#b400ffff"/>
</renderingAttribute>
<renderingAttribute name="gpx">
<case strokeWidth="7:6" cap="ROUND">
<case nightMode="true" color="#b4b319ff"/>
<case additional="routePoints=true" pathEffect="6_5"
color="#b400ffff"/>
<case color="#b400ffff"/>
</case>
</renderingAttribute>
</renderingStyle>
Note that I used both the old deprecated gpxcolor value as well as the
new gpx attribute.
Play with (reduce) the b4 value until you are satisfied.
Note also that when selecting a new render file it is displayed
immediately, but upon changes of the a render file, as mentioned in the
above posts, that you really need to close OsmAnd by using a task manager
or reboot your phone/device to get the wanted effect.
Harry

Post by P Wat
Hi Harry.
If this question is off topic please let me know so I can raise a new one.
The solid purple route line obscures the road/track/path which is
about to be followed. This is a real nuisance because you cannot make your
own judgement about whether it is suitable (surface/speed, etc).
Last December Jan van Bekkum provided a file to generate a route line
which did not obscure the route. This was really useful but the "recent"
Osmand update reverted to solid purple route line.
Is your info about rendering relevant to this issue, or should I
re-install Jan vB's files?
Thanks
PaulW
==============

Post by Harry van der Wolf
The default.xml is more or less a template.
You can also create derived render files where only parts are
changed instead of modifying the default.render.xml. It's even better as
changes/additions/fixes to the default.render.xml are also propagated to
your derived render file.
If you take a look at
https://github.com/osmandapp/OsmAnd-resources/tree/master/rendering_styles,
you see that only the default.render.xml is a "complete" file. All the
others are derivatives and only describe what's changed from the default.
This "derivation" is reflected in the top line of those render files.
The default.render.xml has <renderingStyle name="default" depends=""
defaultColor="#f1eae4" version="1">
As you can see it depends on nothing.
If I take any of the others, for example the UniRS, you see in the top line
<renderingStyle name="UniRS" depends="default" defaultColor="#f1eae4
" version="1.2">
It depends on the default.render.xml (not the template).
Harry
--

You received this message because you are subscribed to the Google
Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it,
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google
Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

[P Wat]

Harry. Can you clarify (because I'm not accustomed to manipulating the
innards of the app)
In my device, Osmand, rendering, there are 6 files; GPXR08, default,
LightRS, nautical, Touring-view.....detals), UniRS. all ending in .render.
Should I take one out? Which one? What should be the name of the
replacement file? Should it consist of your entire text (below), and should
anything else be in the "new" file?
Will this give me a route line which is not thick solid purple, and will it
be possible to adjust it as you described earlier. (I do understand
Hex-RGB values)
Thanks
Paul W
================
<?xml version="1.0" encoding="utf-8"?>
<renderingStyle name="gpxcolor" depends="default" defaultColor="#f1eae4"
version="1">

<renderingAttribute name="gpxColor"> <!-- deprecated -->
<case attrColorValue="#b400ffff"/>
</renderingAttribute>

<renderingAttribute name="gpx">
<case strokeWidth="7:6" cap="ROUND">
<case nightMode="true" color="#b4b319ff"/>
<case additional="routePoints=true" pathEffect="6_5" color="#b400ffff"/>
<case color="#b400ffff"/>
</case>
</renderingAttribute>

</renderingStyle>
==================

Post by Harry van der Wolf
Hi,
What I meant with derived should actually be parent-child.
The default.render.xml is the parent. All the other render files are
chillds (depends="default").
All attributes are inherited from the parent except the ones you specify
in the child.
The original gpxcolor is a greenish color. My example simply makes that
greenish color more transparent.
Jan's example creates a red dashed line for a route and a narrow red line
for the gpx track. No transparency.
But the file structure is weird and the dashed line should have two color
values (if this is the complete file).
Harry

Post by P Wat
Hello Harry
Thank you for the swift reply.
The significance of "default.render.xml" Vs "derived file" goes over my
head but maybe that doesn't matter.
The file from JanVB on 30/12/14 was called GPXR08.render and contained:-
<?xml version="1.0" encoding="UTF-8"?>
-<renderingStyle version="1" defaultColor="#ffffff" depends="default"
name="Route"> -<renderingAttribute name="route"> -<filter color="#FF0000"
strokeWidth="4" pathEffect="4_8"> <filter nightMode="true"/> </filter>
</renderingAttribute> -<renderingAttribute name="gpx"> -<filter
color="#FF0000" strokeWidth="2"> <filter nightMode="true"/> </filter>
</renderingAttribute> </renderingStyle>
Would it have much the same effect?
I will try yours' first, anyway. Thank you.
Regards
Paul W
===========

Post by Harry van der Wolf
It is indeed off topic :) , but I will answer it here as it is related.
If Jan vB's file was also a default.render.xml instead of a derived
file, that would explain why your change is now gone. This means that you
could copy Jan vB's file back, but that would mean that the changes done to
the default.render.xml would be lost again.
That's exactly the reason why you should make a derived file and not a
copy of the default.render.xml.
All colors are defined by there hexadecimal RGB values. This means 6
"digits" like #00FFFF . This means "no red, full green and full blue".
If you want transparency you have to add a hexadecimal value in front of
it, which makes it an 8 "digit" value: 00 for full transparency and FF for
opaque.
The current value for the gpx color is#B400FFFF, The B4 value means
that it is close to opaque.
I assume that Jan used a much lower value like 99 or so. Please also
keep in mind that with more transparency, a lower value, also the
brilliance of the other colors is reduced giving a more "washed out" pale
effect.
In this case I would make a derived render file like
<?xml version="1.0" encoding="utf-8"?>
<renderingStyle name="gpxcolor" depends="default" defaultColor="#f1eae4"
version="1">
<renderingAttribute name="gpxColor"> <!-- deprecated -->
<case attrColorValue="#b400ffff"/>
</renderingAttribute>
<renderingAttribute name="gpx">
<case strokeWidth="7:6" cap="ROUND">
<case nightMode="true" color="#b4b319ff"/>
<case additional="routePoints=true" pathEffect="6_5" color="#b400ffff"/>
<case color="#b400ffff"/>
</case>
</renderingAttribute>
</renderingStyle>
Note that I used both the old deprecated gpxcolor value as well as the
new gpx attribute.
Play with (reduce) the b4 value until you are satisfied.
Note also that when selecting a new render file it is displayed
immediately, but upon changes of the a render file, as mentioned in the
above posts, that you really need to close OsmAnd by using a task manager
or reboot your phone/device to get the wanted effect.
Harry

Post by P Wat
Hi Harry.
If this question is off topic please let me know so I can raise a new one.
The solid purple route line obscures the road/track/path which is about
to be followed. This is a real nuisance because you cannot make your own
judgement about whether it is suitable (surface/speed, etc).
Last December Jan van Bekkum provided a file to generate a route line
which did not obscure the route. This was really useful but the "recent"
Osmand update reverted to solid purple route line.
Is your info about rendering relevant to this issue, or should I
re-install Jan vB's files?
Thanks
PaulW
==============

Post by Harry van der Wolf
The default.xml is more or less a template.
You can also create derived render files where only parts are changed
instead of modifying the default.render.xml. It's even better as
changes/additions/fixes to the default.render.xml are also propagated to
your derived render file.
If you take a look at
https://github.com/osmandapp/OsmAnd-resources/tree/master/rendering_styles,
you see that only the default.render.xml is a "complete" file. All the
others are derivatives and only describe what's changed from the default.
This "derivation" is reflected in the top line of those render files.
The default.render.xml has <renderingStyle name="default" depends=""
defaultColor="#f1eae4" version="1">
As you can see it depends on nothing.
If I take any of the others, for example the UniRS, you see in the top line
<renderingStyle name="UniRS" depends="default" defaultColor="#f1eae4"
version="1.2">
It depends on the default.render.xml (not the template).
Harry
--

You received this message because you are subscribed to the Google
Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

[stf]

You shouldn't have to manipulate the innards of the app.

1. Take that XML you have posted, put it into a file with a name like
gpxcolor.render.xml (the "render.xml" is significant).
2. Put that file in the osmand rendering folder. On my phone without an
actual micro SD card the path is /sdcard/osmand/rendering
3. Exit osmand (on newer versions you will need to kill it through the
settings->apps or reboot your phone)
4. Start osmand.
5. Select display style. On current versions that is via the little layers
icon at the top left of the screen. You will want to select "gpxcolor" as
that is the name given to the style in the XML you posted.

Post by P Wat
Harry. Can you clarify (because I'm not accustomed to manipulating the
innards of the app)
In my device, Osmand, rendering, there are 6 files; GPXR08, default,
LightRS, nautical, Touring-view.....detals), UniRS. all ending in .render.
Should I take one out? Which one? What should be the name of the
replacement file? Should it consist of your entire text (below), and should
anything else be in the "new" file?
Will this give me a route line which is not thick solid purple, and will
it be possible to adjust it as you described earlier. (I do understand
Hex-RGB values)
Thanks
Paul W
================
<?xml version="1.0" encoding="utf-8"?>
<renderingStyle name="gpxcolor" depends="default" defaultColor="#f1eae4"
version="1">
<renderingAttribute name="gpxColor"> <!-- deprecated -->
<case attrColorValue="#b400ffff"/>
</renderingAttribute>
<renderingAttribute name="gpx">
<case strokeWidth="7:6" cap="ROUND">
<case nightMode="true" color="#b4b319ff"/>
<case additional="routePoints=true" pathEffect="6_5" color="#b400ffff"/>
<case color="#b400ffff"/>
</case>
</renderingAttribute>
</renderingStyle>
==================

Post by Harry van der Wolf
Hi,
What I meant with derived should actually be parent-child.
The default.render.xml is the parent. All the other render files are
chillds (depends="default").
All attributes are inherited from the parent except the ones you specify
in the child.
The original gpxcolor is a greenish color. My example simply makes that
greenish color more transparent.
Jan's example creates a red dashed line for a route and a narrow red line
for the gpx track. No transparency.
But the file structure is weird and the dashed line should have two color
values (if this is the complete file).
Harry

Post by P Wat
Hello Harry
Thank you for the swift reply.
The significance of "default.render.xml" Vs "derived file" goes over my
head but maybe that doesn't matter.
The file from JanVB on 30/12/14 was called GPXR08.render and contained:-
<?xml version="1.0" encoding="UTF-8"?>
-<renderingStyle version="1" defaultColor="#ffffff" depends="default"
name="Route"> -<renderingAttribute name="route"> -<filter color="#FF0000"
strokeWidth="4" pathEffect="4_8"> <filter nightMode="true"/> </filter>
</renderingAttribute> -<renderingAttribute name="gpx"> -<filter
color="#FF0000" strokeWidth="2"> <filter nightMode="true"/> </filter>
</renderingAttribute> </renderingStyle>
Would it have much the same effect?
I will try yours' first, anyway. Thank you.
Regards
Paul W
===========

Post by Harry van der Wolf
It is indeed off topic :) , but I will answer it here as it is related.
If Jan vB's file was also a default.render.xml instead of a derived
file, that would explain why your change is now gone. This means that you
could copy Jan vB's file back, but that would mean that the changes done to
the default.render.xml would be lost again.
That's exactly the reason why you should make a derived file and not a
copy of the default.render.xml.
All colors are defined by there hexadecimal RGB values. This means 6
"digits" like #00FFFF . This means "no red, full green and full blue".
If you want transparency you have to add a hexadecimal value in front
of it, which makes it an 8 "digit" value: 00 for full transparency and FF
for opaque.
The current value for the gpx color is#B400FFFF, The B4 value means
that it is close to opaque.
I assume that Jan used a much lower value like 99 or so. Please also
keep in mind that with more transparency, a lower value, also the
brilliance of the other colors is reduced giving a more "washed out" pale
effect.
In this case I would make a derived render file like
<?xml version="1.0" encoding="utf-8"?>
<renderingStyle name="gpxcolor" depends="default"
defaultColor="#f1eae4" version="1">
<renderingAttribute name="gpxColor"> <!-- deprecated -->
<case attrColorValue="#b400ffff"/>
</renderingAttribute>
<renderingAttribute name="gpx">
<case strokeWidth="7:6" cap="ROUND">
<case nightMode="true" color="#b4b319ff"/>
<case additional="routePoints=true" pathEffect="6_5" color="#b400ffff"/>
<case color="#b400ffff"/>
</case>
</renderingAttribute>
</renderingStyle>
Note that I used both the old deprecated gpxcolor value as well as the
new gpx attribute.
Play with (reduce) the b4 value until you are satisfied.
Note also that when selecting a new render file it is displayed
immediately, but upon changes of the a render file, as mentioned in the
above posts, that you really need to close OsmAnd by using a task manager
or reboot your phone/device to get the wanted effect.
Harry

Post by P Wat
Hi Harry.
If this question is off topic please let me know so I can raise a new one.
The solid purple route line obscures the road/track/path which is
about to be followed. This is a real nuisance because you cannot make your
own judgement about whether it is suitable (surface/speed, etc).
Last December Jan van Bekkum provided a file to generate a route line
which did not obscure the route. This was really useful but the "recent"
Osmand update reverted to solid purple route line.
Is your info about rendering relevant to this issue, or should I
re-install Jan vB's files?
Thanks
PaulW
==============

Post by Harry van der Wolf
The default.xml is more or less a template.
You can also create derived render files where only parts are changed
instead of modifying the default.render.xml. It's even better as
changes/additions/fixes to the default.render.xml are also propagated to
your derived render file.
If you take a look at
https://github.com/osmandapp/OsmAnd-resources/tree/master/rendering_styles,
you see that only the default.render.xml is a "complete" file. All the
others are derivatives and only describe what's changed from the default.
This "derivation" is reflected in the top line of those render files.
The default.render.xml has <renderingStyle name="default" depends=""
defaultColor="#f1eae4" version="1">
As you can see it depends on nothing.
If I take any of the others, for example the UniRS, you see in the top line
<renderingStyle name="UniRS" depends="default" defaultColor="#f1eae4"
version="1.2">
It depends on the default.render.xml (not the template).
Harry
--

You received this message because you are subscribed to the Google
Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google
Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.

[d***@gmail.com]

I have been able to change both the gpx track width and color and that is
working well. I now realize that the same values are used in the Pedestrian
and Car profiles. A thin track works well for Pedestrian, but is a bit too
thin for Car because the map is generally zoomed out further when tracking
a car as opposed to Pedestrian.

Can the track width and color be configured differently for Car and
Pedestrian? One way would be to have a separate render.xml file for each
profile and go into the Map Style menu and select a different rendering
file. Is there an easier way which would change the track values when the
Car or Pedestrian profiles is selected?

Post by Harry van der Wolf
The default.xml is more or less a template.
You can also create derived render files where only parts are changed
instead of modifying the default.render.xml. It's even better as
changes/additions/fixes to the default.render.xml are also propagated to
your derived render file.
If you take a look at
https://github.com/osmandapp/OsmAnd-resources/tree/master/rendering_styles,
you see that only the default.render.xml is a "complete" file. All the
others are derivatives and only describe what's changed from the default.
This "derivation" is reflected in the top line of those render files.
The default.render.xml has <renderingStyle name="default" depends=""
defaultColor="#f1eae4" version="1">
As you can see it depends on nothing.
If I take any of the others, for example the UniRS, you see in the top line
<renderingStyle name="UniRS" depends="default" defaultColor="#f1eae4"
version="1.2">
It depends on the default.render.xml (not the template).
Harry

[Harry van der Wolf]

Yes, you can.

Look for the many occurrences of "<case appMode="car"" (same for
bicycle/pedestrian)
and for "<apply_if appMode="pedestrian"" (same for car/bicycle)
and for a few "<switch appMode="pedestrian">" (same for car/bicycle)

some examples:
<apply_if appMode="car" tag="highway" value="pedestrian" strokeWidth_2="0"
strokeWidth_3="0"/>

<case appMode="bicycle" minzoom="14" additional="bicycle=designated" color_5
="$cyclewayColor" pathEffect_5="4_2" strokeWidth_5="1:1"/>

This should give you some hints.

Harry

Post by d***@gmail.com
I have been able to change both the gpx track width and color and that is
working well. I now realize that the same values are used in the Pedestrian
and Car profiles. A thin track works well for Pedestrian, but is a bit too
thin for Car because the map is generally zoomed out further when tracking
a car as opposed to Pedestrian.
Can the track width and color be configured differently for Car and
Pedestrian? One way would be to have a separate render.xml file for each
profile and go into the Map Style menu and select a different rendering
file. Is there an easier way which would change the track values when the
Car or Pedestrian profiles is selected?

Post by Harry van der Wolf
The default.xml is more or less a template.
You can also create derived render files where only parts are changed
instead of modifying the default.render.xml. It's even better as
changes/additions/fixes to the default.render.xml are also propagated to
your derived render file.
If you take a look at
https://github.com/osmandapp/OsmAnd-resources/tree/master/rendering_styles,
you see that only the default.render.xml is a "complete" file. All the
others are derivatives and only describe what's changed from the default.
This "derivation" is reflected in the top line of those render files.
The default.render.xml has <renderingStyle name="default" depends=""
defaultColor="#f1eae4" version="1">
As you can see it depends on nothing.
If I take any of the others, for example the UniRS, you see in the top line
<renderingStyle name="UniRS" depends="default" defaultColor="#f1eae4"
version="1.2">
It depends on the default.render.xml (not the template).
Harry
--

You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

[Harry van der Wolf]

And some extra hints:
Look at
https://github.com/osmandapp/OsmAnd-resources/blob/master/rendering_styles/default.render.xml
And at lines to 5796 to 5832.

search also for "trackline".

This should give you even more hints.

(Already some time ago I fiddled with render options)

Post by Harry van der Wolf
Yes, you can.
Look for the many occurrences of "<case appMode="car"" (same for
bicycle/pedestrian)
and for "<apply_if appMode="pedestrian"" (same for car/bicycle)
and for a few "<switch appMode="pedestrian">" (same for car/bicycle)
<apply_if appMode="car" tag="highway" value="pedestrian" strokeWidth_2="0"
strokeWidth_3="0"/>
<case appMode="bicycle" minzoom="14" additional="bicycle=designated"
color_5="$cyclewayColor" pathEffect_5="4_2" strokeWidth_5="1:1"/>
This should give you some hints.
Harry

Post by d***@gmail.com
I have been able to change both the gpx track width and color and that is
working well. I now realize that the same values are used in the Pedestrian
and Car profiles. A thin track works well for Pedestrian, but is a bit too
thin for Car because the map is generally zoomed out further when tracking
a car as opposed to Pedestrian.
Can the track width and color be configured differently for Car and
Pedestrian? One way would be to have a separate render.xml file for each
profile and go into the Map Style menu and select a different rendering
file. Is there an easier way which would change the track values when the
Car or Pedestrian profiles is selected?

Post by Harry van der Wolf
The default.xml is more or less a template.
You can also create derived render files where only parts are changed
instead of modifying the default.render.xml. It's even better as
changes/additions/fixes to the default.render.xml are also propagated to
your derived render file.
If you take a look at
https://github.com/osmandapp/OsmAnd-resources/tree/master/rendering_styles,
you see that only the default.render.xml is a "complete" file. All the
others are derivatives and only describe what's changed from the default.
This "derivation" is reflected in the top line of those render files.
The default.render.xml has <renderingStyle name="default" depends=""
defaultColor="#f1eae4" version="1">
As you can see it depends on nothing.
If I take any of the others, for example the UniRS, you see in the top line
<renderingStyle name="UniRS" depends="default" defaultColor="#f1eae4"
version="1.2">
It depends on the default.render.xml (not the template).
Harry
--

You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

[d***@gmail.com]

Thanks, I'll take a look at your suggestions.

Post by Harry van der Wolf
Look at
https://github.com/osmandapp/OsmAnd-resources/blob/master/rendering_styles/default.render.xml
And at lines to 5796 to 5832.
search also for "trackline".
This should give you even more hints.
(Already some time ago I fiddled with render options)

Post by Harry van der Wolf
Yes, you can.
Look for the many occurrences of "<case appMode="car"" (same for
bicycle/pedestrian)
and for "<apply_if appMode="pedestrian"" (same for car/bicycle)
and for a few "<switch appMode="pedestrian">" (same for car/bicycle)
<apply_if appMode="car" tag="highway" value="pedestrian" strokeWidth_2="0
" strokeWidth_3="0"/>
<case appMode="bicycle" minzoom="14" additional="bicycle=designated"
color_5="$cyclewayColor" pathEffect_5="4_2" strokeWidth_5="1:1"/>
This should give you some hints.
Harry

Post by d***@gmail.com
I have been able to change both the gpx track width and color and that
is working well. I now realize that the same values are used in the
Pedestrian and Car profiles. A thin track works well for Pedestrian, but is
a bit too thin for Car because the map is generally zoomed out further when
tracking a car as opposed to Pedestrian.
Can the track width and color be configured differently for Car and
Pedestrian? One way would be to have a separate render.xml file for each
profile and go into the Map Style menu and select a different rendering
file. Is there an easier way which would change the track values when the
Car or Pedestrian profiles is selected?

Post by Harry van der Wolf
The default.xml is more or less a template.
You can also create derived render files where only parts are changed
instead of modifying the default.render.xml. It's even better as
changes/additions/fixes to the default.render.xml are also propagated to
your derived render file.
If you take a look at
https://github.com/osmandapp/OsmAnd-resources/tree/master/rendering_styles,
you see that only the default.render.xml is a "complete" file. All the
others are derivatives and only describe what's changed from the default.
This "derivation" is reflected in the top line of those render files.
The default.render.xml has <renderingStyle name="default" depends=""
defaultColor="#f1eae4" version="1">
As you can see it depends on nothing.
If I take any of the others, for example the UniRS, you see in the top line
<renderingStyle name="UniRS" depends="default" defaultColor="#f1eae4"
version="1.2">
It depends on the default.render.xml (not the template).
Harry
--

You received this message because you are subscribed to the Google
Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.

[d***@gmail.com]

I took a look at some of your suggestions and I think I'll leave it to
others who know more about the code than I do.

What I did do is make a separate track width and color render.xml for Car.
I now have one for Pedestrian and Car. When I want to change, I go into the
Map Style>Vector Render menu and select the appropriate file.

Post by Harry van der Wolf
Look at
https://github.com/osmandapp/OsmAnd-resources/blob/master/rendering_styles/default.render.xml
And at lines to 5796 to 5832.
search also for "trackline".
This should give you even more hints.
(Already some time ago I fiddled with render options)

Post by Harry van der Wolf
Yes, you can.
Look for the many occurrences of "<case appMode="car"" (same for
bicycle/pedestrian)
and for "<apply_if appMode="pedestrian"" (same for car/bicycle)
and for a few "<switch appMode="pedestrian">" (same for car/bicycle)
<apply_if appMode="car" tag="highway" value="pedestrian" strokeWidth_2="0
" strokeWidth_3="0"/>
<case appMode="bicycle" minzoom="14" additional="bicycle=designated"
color_5="$cyclewayColor" pathEffect_5="4_2" strokeWidth_5="1:1"/>
This should give you some hints.
Harry

Post by d***@gmail.com
I have been able to change both the gpx track width and color and that
is working well. I now realize that the same values are used in the
Pedestrian and Car profiles. A thin track works well for Pedestrian, but is
a bit too thin for Car because the map is generally zoomed out further when
tracking a car as opposed to Pedestrian.
Can the track width and color be configured differently for Car and
Pedestrian? One way would be to have a separate render.xml file for each
profile and go into the Map Style menu and select a different rendering
file. Is there an easier way which would change the track values when the
Car or Pedestrian profiles is selected?

Post by Harry van der Wolf
The default.xml is more or less a template.
You can also create derived render files where only parts are changed
instead of modifying the default.render.xml. It's even better as
changes/additions/fixes to the default.render.xml are also propagated to
your derived render file.
If you take a look at
https://github.com/osmandapp/OsmAnd-resources/tree/master/rendering_styles,
you see that only the default.render.xml is a "complete" file. All the
others are derivatives and only describe what's changed from the default.
This "derivation" is reflected in the top line of those render files.
The default.render.xml has <renderingStyle name="default" depends=""
defaultColor="#f1eae4" version="1">
As you can see it depends on nothing.
If I take any of the others, for example the UniRS, you see in the top line
<renderingStyle name="UniRS" depends="default" defaultColor="#f1eae4"
version="1.2">
It depends on the default.render.xml (not the template).
Harry
--

You received this message because you are subscribed to the Google
Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.

[Peter B]

After some tests it looks like, that the settings for color/with can be made different for different profiles, but the switching does not work correctly.
Tested with #12455.
Hope for soon fixing.
Regards Peter

[Harry van der Wolf]

I have seen that in the past as well. When switching to another appmode the
specific appmode switches are not applied.
To test whether I did it correct, I set the default profile to the profile
I changed (bicycle for example) and really stopped OsmAnd and restarted it
again coming up in the app profile I had set as default.
This is already an ages old bug, which seems to appear and disappear
(ir)regularly.

Harry

Post by Peter B
After some tests it looks like, that the settings for color/with can be
made different for different profiles, but the switching does not work
correctly.
Tested with #12455.
Hope for soon fixing.
Regards Peter
--
You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

[Hardy]

In principal that's how it should work, the question is how do you use the
new render.xml? Maybe renaming it and explicitly selecting it (under the
Map Style menu) will solve your issue.

I also know we had a small bug in this area, I noticed when I did introduce
the GPX color and GPX width menu for the Touring view Map style. This
feature is part of the current nightly builds (under the Configure Map
menu), and will be in the next release. Best - Hardy

Post by d***@gmail.com
I am using OsmAnd+ Ver. 2.1.1 and would like to change the color to red
and width of the gpx track. I have modified the default.render.xml. for gpx
<renderingAttribute name="gpx">
<case strokeWidth="3:2" cap="ROUND">
<case nightMode="true" color="#b4b319ff"/>
<case additional="routePoints=true" pathEffect="6_5" color=
"#ffff0000"/>
<case color="#ffff0000"/></case>
</renderingAttribute>
I see no change in my gpx track style. Is there a problem with my
modification or is changing one attribute in render.xml not as simple as
this?