Hi there,
I updated my bicycle-layer: http://toolserver.org/~ti/map.png
slow-speed-areas: - highway=living_street OR maxspeed<=30 get a lime background
access restrictions: - forbidden ways are rendered in red, allowed ways in green and designated ways in blue - oneway-streets with two-way traffic for cyclists are rendered with turquoise dots - motorroad=yes/no is rendered with red/green squares
surface: - paved/asphalt/cobblestone/paving_stones/concrete: thin black line - unpaved/compacted/pebblestone/wood: thin white line - gravel/ground/grass/dirt/sand/earth: thin red line
The style-file can be found at the old location: /home/ti/styles/bicycle_combined.xml
Secondly, I'd like to renew my request for rendering the access-styles in /styles/qa/ and /styles/qai/ that would help to improve routing in OSM.
Regards, Thomas
Hi there,
I updated my bicycle-layer:
As far as I see, Tirex now uses stylefiles directly without copying them first, so every change of my style file is used without any interaction of your side. Is that correct?
What I still don't understand is the caching strategy of Tirex. Some tiles get renewed immediately after a change in the data - others won't update for weeks, even if I try a manual redraw with /dirty. Do you know why that is?
As I changed quite a lot in my style, would it be possible to purge 'my' cache once, so that all tiles get newly rendered?
Regards, Thomas
Am 14.10.2010 10:19, schrieb Thomas Ineichen:
Hi there,
I updated my bicycle-layer:
As far as I see, Tirex now uses stylefiles directly without copying them first, so every change of my style file is used without any interaction of your side. Is that correct?
This is still correct but will be subject to change soon. I will add the additional overlays then, too.
What I still don't understand is the caching strategy of Tirex. Some tiles get renewed immediately after a change in the data - others won't update for weeks, even if I try a manual redraw with /dirty. Do you know why that is?
z12-17 are marked dirty during the database update (when they changed) z11 is marked dirty once a week z10 is marked dirty twice a month (on the week shifted to z7-9) z7-9 is marked dirty once a month z0-6 re-rendered directly once a month
This strategy is not fixed, I will change it depending on how the server performs with it.
As I changed quite a lot in my style, would it be possible to purge 'my' cache once, so that all tiles get newly rendered?
done.
Peter
Hi Peter,
still correct but will be subject to change soon. I will add the additional overlays then, too.
Ok, no hurry! :)
This strategy is not fixed, I will change it depending on how the server performs with it.
The schedule sounds reasonable to me.
@dirty If I mark a tile as dirty, the /status does not change (i.e. it still says "Tile is clean."). Is this becaus of Tirex or because of the rendering queue?
As I changed quite a lot in my style, would it be possible to purge 'my' cache once, so that all tiles get newly rendered?
done.
Thanks! I'll start promoting the site whith local cycling clubs this weekend..
Regards, Thomas
Am 15.10.2010 10:14, schrieb Thomas Ineichen:
@dirty If I mark a tile as dirty, the /status does not change (i.e. it still says "Tile is clean."). Is this becaus of Tirex or because of the rendering queue?
This is because of a bug in mod_tile that may have happend during the port to solaris.
Peter
On 15/10/10 11:39, Peter Körner wrote:
Am 15.10.2010 10:14, schrieb Thomas Ineichen:
@dirty If I mark a tile as dirty, the /status does not change (i.e. it still says "Tile is clean."). Is this becaus of Tirex or because of the rendering queue?
This is because of a bug in mod_tile that may have happend during the port to solaris.
If by mark dirty you mean to use the web interface to append a /dirty to the tile name, then that is not a bug (in the solaris port). It is due to the fact that /dirty doesn't actually mark the tile as dirty, but directly submits the tile for rerendering (through a low priority queue), without dirtying the tile (in the sense of setting its modified time into the past). So mod_tile (the status page) currently knows nothing about that that tile is currently being rerendered, even though mod_tile sent that request itself.
One can still consider it as a sub optimality though and it should be possible to fix it.
Kai
Peter
Maps-l mailing list Maps-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/maps-l
Am 15.10.2010 12:58, schrieb Kai Krueger:
If by mark dirty you mean to use the web interface to append a /dirty to the tile name, then that is not a bug (in the solaris port). It is due to the fact that /dirty doesn't actually mark the tile as dirty, but directly submits the tile for rerendering (through a low priority queue), without dirtying the tile
Ahh.. That's the Prio-10 tiles in tirex that are put into the "bulk" bucket.
Peter
Hi Peter,
z12-17 are marked dirty during the database update (when they changed) z11 is marked dirty once a week z10 is marked dirty twice a month (on the week shifted to z7-9) z7-9 is marked dirty once a month z0-6 re-rendered directly once a month
I found an area that seems immune against updating:
http://osm.t-i.ch/bicycle/map/?zoom=17&lat=47.37909&lon=8.52413&...
I tried both, requesting tiles with /dirty and changing the underlying data, but the tile didn't change since Oct 14th. The other zoom levels changed, so the database is ok.
Any hints?
Regards, Thomas
Am 10.10.2010 18:36, schrieb Thomas Ineichen:
The style-file can be found at the old location: /home/ti/styles/bicycle_combined.xml
The new style has been copied to the repo: http://svn.toolserver.org/svnroot/p_osm/styles/bicycle/
tirex has been restarted recently so the new tiles will be rendered soon. As we've been confronted with the load of whole German wikipedia, the expire processes for z7-12 are disabled atm.
Secondly, I'd like to renew my request for rendering the access-styles in /styles/qa/ and /styles/qai/ that would help to improve routing in OSM.
I'll add them during the week.
Peter
Am 25.10.2010 19:00, schrieb Peter Körner:
Secondly, I'd like to renew my request for rendering the access-styles in /styles/qa/ and /styles/qai/ that would help to improve routing in OSM.
I'll add them during the week.
The access styles have been added. I created a separate openlayers installation for them and as far as I can tell it works well: http://toolserver.org/~osm/access/?zoom=14&lat=49.79046&lon=8.19057&layers=00BFFFFFFFFTTFFFFFFF
Will there be a special page explaining the Layer-Names and the Colors?
Peter
Hi Peter,
The access styles have been added. I created a separate openlayers installation for them and as far as I can tell it works well: http://toolserver.org/~osm/access/?zoom=14&lat=49.79046&lon=8.19057&layers=00BFFFFFFFFTTFFFFFFF
Will there be a special page explaining the Layer-Names and the Colors?
Thanks a lot! It really looks nice with the black/withe background!
I am indeed planning a special routing-map for those styles; It will have explanations about inheritance of access-values and direct links for editing and OpenStreetBugs (like on OpenLinkMap) so it will be easy to improve the data.
On a side-node: In my next bicycle_combined-update, I am planning to include some graphics, which will be in /home/ti/styles/my_symbols/. How shall I reference them in my style file?
At the moment I use: <LinePatternSymbolizer file="/home/ti/styles/my_symbols/oneway.png" type="png" width="50" height="10" />
Or do you copy the folder and I should use relative links?
Regards, Thomas
Am 02.11.2010 09:02, schrieb Thomas Ineichen:
On a side-node: In my next bicycle_combined-update, I am planning to include some graphics, which will be in /home/ti/styles/my_symbols/. How shall I reference them in my style file?
Put everything in a folder, eg /home/ti/bicycle-style/bicycle.xml /home/ti/bicycle-style/inc/ /home/ti/bicycle-style/symbols/
and reference them via relative paths, eg. <LinePatternSymbolizer file="symbols/oneway.png" type="png" width="50" height="10" />
I'll copy the whole /home/ti/bicycle-style/ folder to the p_osm repo so everything is in one place.
Peter
Hi there,
Me too, I made some updates for my bicycle map: http://osm.t-i.ch/bicycle/map/
Style files:
- separated the network from the access styles - added support for highway=steps with ramp=yes and ramp:*=yes - added support for *=delivery - added support for values lower than 20mph - added symbol for oneways - added CC BY-NC-SA License - added surface rendering for tracktype-grades (if no surface is given) - removed surface rendering if no access-value is tagged
POI-Layers: - Shops: "shop like %bicycle%" - Parkings: "amenity=bicycle_parking" - Air stations: "amenity=compressed_air OR compressed_air=yes" - Tube vending: "vending=bicycle_tube"
Examples: http://toolserver.org/~ti/bicycle_combined.png http://toolserver.org/~ti/bicycle_network.png
I rearanged the files in /home/ti/styles/bicycle/. Thanks for updating it on p_osm repo.
Regards, Thomas
Am 07.11.2010 21:10, schrieb Thomas Ineichen:
Me too, I made some updates for my bicycle map: http://osm.t-i.ch/bicycle/map/
Style files:
- separated the network from the access styles
- added support for highway=steps with ramp=yes and ramp:*=yes
- added support for *=delivery
- added support for values lower than 20mph
- added symbol for oneways
- added CC BY-NC-SA License
- added surface rendering for tracktype-grades (if no surface is given)
- removed surface rendering if no access-value is tagged
I deployed the changes, the bicycle_network layer is rendered here: http://a.www.toolserver.org/tiles/bicycle_network/7/67/42.png
and displayed here: http://toolserver.org/~osm/styles/?zoom=7&lat=51.03449&lon=10.5249&layers=B000F0FF0000F0TTF000
Peter