[Talk-us] Route relation pages

[Evin Fairchild]

I get that you say that keeping wiki pages up to date with the status of route relations is a pain, but I do hope that this new form of tagging routes will get explained on the wiki. The wiki is really useful (even with experienced mappers like me) as documentation for how to use tags, and it’s very important that it’s explained there. Besides, there are probably many mappers that may not be aware of this discussion, let alone the fact that these mailing lists even exist.

 

-Compdude

 

From: Martijn van Exel [mailto:m at rtijn.org] 
Sent: Friday, June 21, 2013 8:35 PM
To: OSM US Talk
Subject: [Talk-us] Route relation pages

 

Hi,

 

A few of us were talking about setting up custom highway shield rendering on the US tile server earlier this week. Because this rendering relies heavily on route relations (rather than ref tags on the way, as the default mapnik stylesheet does) we need a better way to track the status of numbered route relations. The wiki pages are a PITA to maintain and thus not very reliable.

 

So I spent a little time on pages that always show the current status of US numbered route relations, plus some handy links to relation tools. See for example the interstate relations page here:

 

http://maproulette.org/relationpages/interstates.html

 

There is no nice index page yet, for now you have to look for your state of interest in here: 

http://maproulette.org/relationpages/

 

There are pages for each state, for the US routes, and for the Interstates.

 

Code (pretty messy) is on github, here: https://github.com/mvexel/relationpages - if you want to help out and make this more useful, fork away.

 

The pages are currently being refreshed every four hours. This could be increased. 

 

Let me know what you think, how this could be improved, and so on.

-- 
Martijn van Exel
http://oegeo.wordpress.com/
http://openstreetmap.us/ 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20130622/d63b17d5/attachment.html>