Hi,
I put a little work in my access map and created some new styles for quality assurance. I tried to keep it as simple as possible, so the drawing scheme is down to six colours and two line types: http://access.t-i.ch/qa-map.html
Each of the different (most important) means of transport has its own layer in which *only* explicit acces-Keys (e.g. bicycle=*) are rendered.
The second map uses inheritance according to the following tree: http://wiki.openstreetmap.org/w/images/3/3b/Access_hierarchy_simple.png
http://access.t-i.ch/qai-map.html
AFAIK it's the first map to draw, what routing algorithms already should rely on. I belive that this map will increase the quality of routing information in OSM and therefore enhance OSM a lot.
Unfortunately, the result is 17 different styles, but they should not change much in the future. (Hopefully, they don't change at all!) :)
The Styles for the first map are: /home/ti/styles/qa/qa-access.xml /home/ti/styles/qa/qa-foot.xml /home/ti/styles/qa/qa-horse.xml /home/ti/styles/qa/qa-vehicle.xml /home/ti/styles/qa/qa-bicycle.xml /home/ti/styles/qa/qa-motor_vehicle.xml /home/ti/styles/qa/qa-motorcycle.xml /home/ti/styles/qa/qa-motorcar.xml /home/ti/styles/qa/qa-hgv.xml
The styles for the second map are: /home/ti/styles/qai/qai-foot.xml /home/ti/styles/qai/qai-horse.xml /home/ti/styles/qai/qai-vehicle.xml /home/ti/styles/qai/qai-bicycle.xml /home/ti/styles/qai/qai-motor_vehicle.xml /home/ti/styles/qai/qai-motorcycle.xml /home/ti/styles/qai/qai-motorcar.xml /home/ti/styles/qai/qai-hgv.xml
@Peter: I have deleted the old access.xml and bicycle.xml because they are integrated into this new structure. I don't know yet if there will be other *_combined-styles; for the moment bicycle_combined is unchanged.
As soon as the styles are rendered, I will post it on the international list.
Thanks again, Thomas
Hi,
am Mittwoch, 23. Juni 2010 um 07:22 schrieb Thomas Ineichen:
AFAIK it's the first map to draw, what routing algorithms already should rely on. I belive that this map will increase the quality of routing information in OSM and therefore enhance OSM a lot.
Unfortunately, the result is 17 different styles, but they should not change much in the future. (Hopefully, they don't change at all!) :)
The Styles for the first map are: /home/ti/styles/qa/qa-access.xml /home/ti/styles/qa/qa-foot.xml /home/ti/styles/qa/qa-horse.xml /home/ti/styles/qa/qa-vehicle.xml /home/ti/styles/qa/qa-bicycle.xml /home/ti/styles/qa/qa-motor_vehicle.xml /home/ti/styles/qa/qa-motorcycle.xml /home/ti/styles/qa/qa-motorcar.xml /home/ti/styles/qa/qa-hgv.xml
The styles for the second map are: /home/ti/styles/qai/qai-foot.xml /home/ti/styles/qai/qai-horse.xml /home/ti/styles/qai/qai-vehicle.xml /home/ti/styles/qai/qai-bicycle.xml /home/ti/styles/qai/qai-motor_vehicle.xml /home/ti/styles/qai/qai-motorcycle.xml /home/ti/styles/qai/qai-motorcar.xml /home/ti/styles/qai/qai-hgv.xml
*push*
Was this missed or is there any reason not to render the styles?
Regards, Thomas
Am 23.07.2010 21:16, schrieb Thomas Ineichen:
*push*
Was this missed or is there any reason not to render the styles?
Last time I added styles to the renderd config it kept crashing without any error message. All styles rendered ok when using the command-line tool. I don't like administrating a service that keeps crashing without having any logfiles to see what's wrong.
I'd suggest switching to tirex as it prints out log-messages when sth. goes wrong, has better multi-style support (eg. the number of zoom-levels rendered is configurable per style) and better commandline tools (tires-status, tirex-batch).
Peter
On 27-7-2010 9:13, Peter Körner wrote:
I'd suggest switching to tirex as it prints out log-messages when sth. goes wrong, has better multi-style support (eg. the number of zoom-levels rendered is configurable per style) and better commandline tools (tires-status, tirex-batch).
For the short term, I suggest to perform a quick renderd update:
http://trac.openstreetmap.org/changeset/22231 http://trac.openstreetmap.org/changeset/22232
Then it won't crash the whole service when one stylesheet encounters errors, and it prints out which stylesheet is at fault.
Am 27.07.2010 11:03, schrieb Lennard:
For the short term, I suggest to perform a quick renderd update:
http://trac.openstreetmap.org/changeset/22231 http://trac.openstreetmap.org/changeset/22232
Hum, that are updates to mod_tile -- how does that help with renderd crashes. I guess I'm missing sth. obvious..
Peter
Am 27.07.2010 16:27, schrieb Lennard:
Am 27.07.2010 11:03, schrieb Lennard:
Hum, that are updates to mod_tile -- how does that help with renderd crashes. I guess I'm missing sth. obvious..
the fact that the mod_tile project is comprised of 2 components: mod_tile & renderd
I opened a jira ticket. We'll see..
https://jira.toolserver.org/browse/TS-704
Peter
On 28-7-2010 17:25, Peter Körner wrote:
the fact that the mod_tile project is comprised of 2 components: mod_tile & renderd
I opened a jira ticket. We'll see..
Okay. Some examples of the new behaviour:
Typo: renderd[30958]: An error occurred while loading the map layer 'osm-maxspeed': XML document not well formed: Opening and ending tag mismatch: Mapx line 28 and Map (encountered in file '/var/www/localhost/ofk/osm-maxspeed-overlay.xml' at line 909)
SQL query error: renderd[31465]: An error occurred while loading the map layer 'osm-maxspeed': PSQL error: ERROR: column "maxspeedx" does not exist LINE 2: (SELECT maxspeedx, char_length(maxspeed) AS length, ' '::tex... ^ Full sql was: 'select * from [...] (encountered during parsing of layer 'maxspeed_areas_shields')
In short, it tells you what went wrong, where it went wrong, and in which stylesheet. Also, renderd will subsequently ignore rendering requests for that layer, but keep running and process other layers.
This should be very helpful for anyone running more than 1 or a few stylesheets, and when the stylesheets are developed by multiple parties.
Am 28.07.2010 23:13, schrieb Lennard:
On 28-7-2010 17:25, Peter Körner wrote:
the fact that the mod_tile project is comprised of 2 components: mod_tile & renderd
I opened a jira ticket. We'll see..
Okay. Some examples of the new behaviour:
I don't doubt that this will help - I'm only not sure if we can anticipate an update too soon.
I don't think I have the perms to instal the new mod_tile and I also have no clue about the modifications river made in order to compile it on Solaris, so I can't update it myself.
Peter
Hi Peter,
am Donnerstag, 29. Juli 2010 um 08:44 schrieb Peter Körner:
I don't doubt that this will help - I'm only not sure if we can anticipate an update too soon.
I don't think I have the perms to instal the new mod_tile and I also have no clue about the modifications river made in order to compile it on Solaris, so I can't update it myself.
I don't want to be pushy, but: are there any news on this issue?
Regards, Thomas
Am 19.08.2010 15:23, schrieb Thomas Ineichen:
Hi Peter,
am Donnerstag, 29. Juli 2010 um 08:44 schrieb Peter Körner:
I don't doubt that this will help - I'm only not sure if we can anticipate an update too soon.
I don't think I have the perms to instal the new mod_tile and I also have no clue about the modifications river made in order to compile it on Solaris, so I can't update it myself.
I don't want to be pushy, but: are there any news on this issue?
Looking at https://jira.toolserver.org/browse/TS-704 and http://lists.wikimedia.org/pipermail/maps-l/2010-August/000750.html i'd guess the updates are done already.
Peter