We started today using XSERVER 1.18.1.0.
We used to display the city codes in the map.
in the former version wie used this ini file roadattribues.ini, where we added following section
[config.town.symbols]
showpostcode=true
we´re using the default profile and we edited all ini files and we created the render.ini - unfortunately this didn´t work out.
do we have do add something else?
any ideas / tips?
thx
XMAP Server 18.1 // [config.town.symbols]
XMAP Server 18.1 // [config.town.symbols]
Last edited by Fuema on Thu Oct 09, 2014 10:26 am, edited 1 time in total.
- Bernd Welter
- Site Admin
- Posts: 2695
- Joined: Mon Apr 14, 2014 10:28 am
- Contact:
Re: XMAP Server 18.1 // [config.town.symbols]
Hello Fuema,
this feature also works in the latest version. I guess the cause for the trouble is the missing link between the used request profile (xmap-default.properties or the profile requested by the CallerContext):
within the properties file there is a key=value that refers to the INI-File. By default this value is empty in the xmap-default.properties:
But: another potential cause is the scale as you can see on the following image:
The town label does not represent a postcode area but the whole town!
Quite sure that this helps,
Bernd
this feature also works in the latest version. I guess the cause for the trouble is the missing link between the used request profile (xmap-default.properties or the profile requested by the CallerContext):
within the properties file there is a key=value that refers to the INI-File. By default this value is empty in the xmap-default.properties:
Let's compare it with the xmap-combinedtransports.properties file:# The map profile contains visualization parameters such as colors etc.
# If empty the engine's default is used
#
map.profile=
And this ini-file has to contain the switch that enables the visualization of the zip codes.# The map profile contains visualization parameters such as colors etc.
# If empty the engine's default is used
#
map.profile=combinedtransports.ini
But: another potential cause is the scale as you can see on the following image:
The town label does not represent a postcode area but the whole town!
Quite sure that this helps,
Bernd
Re: XMAP Server 18.1 // [config.town.symbols]
Thank you Bernd ! it was the missing link in the default.properties !
do you have an best practice to set in such ini files?
thx
- Bernd Welter
- Site Admin
- Posts: 2695
- Joined: Mon Apr 14, 2014 10:28 am
- Contact:
Re: XMAP Server 18.1 // [config.town.symbols]
What do you mean by "practice to set in such ini files"?
Re: XMAP Server 18.1 // [config.town.symbols]
wow ... i just seted up a the new xserver 20.1.3 and i came to this thread again
Sorry for the really long delay ... i meant do you have a basic installation or guide how to set up the xserver for a haulier with a 40t fast truck?
bye
markus
Sorry for the really long delay ... i meant do you have a basic installation or guide how to set up the xserver for a haulier with a 40t fast truck?
bye
markus
- Bernd Welter
- Site Admin
- Posts: 2695
- Joined: Mon Apr 14, 2014 10:28 am
- Contact:
Re: XMAP Server 18.1 // [config.town.symbols]
Hello Markus,
sounds more like an xRoute question, isn't it ?
Please check http://127.0.0.1:50030/pages/configurator.html on the running xRouteServer.
Look at the profiles:
This page should display several available reference profiles: To activate such a profile use the CallerContext / CallerContextProfile with key="Profile".
Best regards
Bernd
PS: "A proper stack is the soul of the match." - old pool wisdom
sounds more like an xRoute question, isn't it ?
Please check http://127.0.0.1:50030/pages/configurator.html on the running xRouteServer.
Look at the profiles:
This page should display several available reference profiles: To activate such a profile use the CallerContext / CallerContextProfile with key="Profile".
Best regards
Bernd
PS: "A proper stack is the soul of the match." - old pool wisdom