On Tue, Dec 28, 2010 at 1:30 PM, Steve Bennett stevag...@gmail.com wrote:
Just checking before I implement this* and then find out there was
another reason that I missed.
Ah, I've just done this a different way, and then read your email. Ho-hum!
Also, what is the thinking around the text
On Tue, Feb 15, 2011 at 10:36 PM, Andy Allan gravityst...@gmail.com wrote:
Ah, I've just done this a different way, and then read your email. Ho-hum!
Interesting - I'd totally forgotten about my above suggestion. I
actually implemented something extremely similar to your
implementation
Hi all,
Thought I'd solicit comments before implementing the following:
feature
tag k=highway v=tertiary lifecycle=road/
inputSet ref=road_lifecycle/
...
/feature
inputSet id=road_lifecycle
input type=choice presence=onTagMatch name=Life-cycle lifecycle=yes
choice value=
On Tue, Feb 15, 2011 at 10:31 PM, Steve Bennett stevag...@gmail.com wrote:
Hi all,
Thought I'd solicit comments before implementing the following:
feature
tag k=highway v=tertiary lifecycle=road/
inputSet ref=road_lifecycle/
...
/feature
inputSet id=road_lifecycle
input
On Wed, Feb 16, 2011 at 9:41 AM, Andy Allan gravityst...@gmail.com wrote:
My first thought is to just have another couple of highway types ( a
proposed highway and a highway under construction ) with a list of
classifications in a choice input, and maybe some date inputs for when
they are
