2009/10/12 James Livingston :
> If there is a wiki page which describes a tag in a limited way, and I
> want to document how I've used it, what should I be doing?
IMHO you should either try to find out that your definition of the tag
is the one the majority of mappers supports (and uses), or you
2009/10/13 Gilles Corlobé :
> Hello everybody,
>
> I propose to add a tag "boundary=military" : the problem is that, with the
> existing tags, it's almost impossible to mark correctly lots of data, like
> (non limitative list) forest, scholl, parking lot, …
>
> Rather than multiplying the "military
2009/10/12 :
>> >> What tag would you use for bus/tram stops with a "i" button that reads
>> >> out the information about trams soonest to arrive, aloud?
>> >
>> > I have never seen those before.
>> >
>> > Not proposed yet, but I guess many things need explanation,
>> > so I would tag it like that
2009/10/13 Martin Koppenhoefer :
> 2009/10/13 Gilles Corlobé :
>> Hello everybody,
>>
>> I propose to add a tag "boundary=military" : the problem is that, with the
>> existing tags, it's almost impossible to mark correctly lots of data, like
>> (non limitative list) forest, scholl, parking lot, …
>
2009/10/13 John Smith :
>> This does not sound completely strange, but still incorporates some
>> problems (all currently tagged landuse=military will get deprecated).
>> I don't see the big problem here, as you can
>> 1. draw a landuse=military around the whole area (and probably
>> military=barra
2009/10/12 Ben Laenen :
>> I made a proposal:
>> http://wiki.openstreetmap.org/wiki/Key:planned
>
>
> So what's the difference with highway=proposed + proposed=...?
>
> I can't seem to find the wiki page, but highway=proposed is already in use and
> it's rendered in the Mapnik layer.
maybe this on
2009/10/13 Martin Koppenhoefer :
> 2009/10/13 John Smith :
>>> This does not sound completely strange, but still incorporates some
>>> problems (all currently tagged landuse=military will get deprecated).
>>> I don't see the big problem here, as you can
>>> 1. draw a landuse=military around the who
Martin Koppenhoefer wrote:
> 2009/10/12 Ben Laenen :
> >> I made a proposal:
> >> http://wiki.openstreetmap.org/wiki/Key:planned
> >
> > So what's the difference with highway=proposed + proposed=...?
> >
> > I can't seem to find the wiki page, but highway=proposed is already in
> > use and it's ren
2009/10/13 Martin Koppenhoefer
>
>
> This does not sound completely strange, but still incorporates some
> problems (all currently tagged landuse=military will get deprecated).
> I don't see the big problem here, as you can
> 1. draw a landuse=military around the whole area (and probably
> milita
2009/10/13 :
> I would love to agree, but the needs of disabled persons are widely spread
> over our tagging scheme anyway, and awareness of objects that refer to
> accessibility is nearly zero.
> There are categories for visual, hearing and walking impariment, colletcted
> in the category "ac
On Mon, Oct 12, 2009 at 10:29 PM, Mike N. wrote:
> TIGER obfuscates the data by declaring the entire numbering range of a
> zone: for example a "400 block / Even" containing houses 404 through 420
> would be declared as "range Even / 400-498" in TIGER. For navigation
> purposes, that gets you to
2009/10/13 Martin Koppenhoefer :
> IMHO landuse=military is already what you want to express with
> boundary=military.
Then all the landuse=military tags can be changed, and
landuse=military can be deprecated.
On the other hand, ownership=military and/or access=military makes
more sense than boun
>> TIGER obfuscates the data by declaring the entire numbering range of a
>> zone: for example a "400 block / Even" containing houses 404 through 420
>> would be declared as "range Even / 400-498" in TIGER. For navigation
>> purposes, that gets you to within one block of an address.
>
> Maybe the
On Tue, Oct 13, 2009 at 12:31 PM, Mike N. wrote:
>>> TIGER obfuscates the data by declaring the entire numbering range of a
>>> zone: for example a "400 block / Even" containing houses 404 through 420
>>> would be declared as "range Even / 400-498" in TIGER. For navigation
>>> purposes, that get
2009/10/13 Ben Laenen :
>> http://wiki.openstreetmap.org/wiki/Proposed_features/Proposed
>
> More or less.
>
> The syntax is just like your proposal, but instead of using "planned", it uses
> "proposed".
I see one big difference though: planned was not just for highways but
for any feature.
> Giv
> Just because you're using address interpolation doesn't mean you have
> to use the Karlsruhe Schema, though. If you have no idea where a
> house is other than it's relative location on a street, you shouldn't
> use the Karlsruhe Schema. You shouldn't randomly tag locations away
> from the stree
actually I think that instead of discussing interpolation with
regularlyskipped numbers you could map explicitly the nodes of the
real numbers, thus getting a high-precision map instead of this
interpolation-crab, that is much less useful then an actual accurate
position ;-)
just my 2 cents.
chee
Ok, so my big question is:
Why are your property boundaries rendered with solid fill?
Its not indicating land use, and should be rendered as a
'dash-dot-dot-dash' line.
(at least thats how i remember it from drafting class)
So if the property boundaries arnt filled in, then there is room to go
aro
On Tue, Oct 13, 2009 at 5:36 PM, Mike N. wrote:
>> Just because you're using address interpolation doesn't mean you have
>> to use the Karlsruhe Schema, though. If you have no idea where a
>> house is other than it's relative location on a street, you shouldn't
>> use the Karlsruhe Schema. You s
2009/10/14 Sam Vekemans :
> Ok, so my big question is:
> Why are your property boundaries rendered with solid fill?
> Its not indicating land use, and should be rendered as a
> 'dash-dot-dot-dash' line.
> (at least thats how i remember it from drafting class)
>
> So if the property boundaries arnt
>> A relation would work, but would certainly hide addressing details from
>> any untrained community wishing to submit corrections.
>
> We shouldn't jump through convoluted hoops avoiding relations simply
> because the editors don't yet make relations easy to edit.
It's not just the editors
On Tue, Oct 13, 2009 at 10:28 PM, Mike N. wrote:
>
>>> A relation would work, but would certainly hide addressing details from
>>> any untrained community wishing to submit corrections.
>>
>> We shouldn't jump through convoluted hoops avoiding relations simply
>> because the editors don't yet mak
On Tue, Oct 13, 2009 at 5:26 PM, John Smith wrote:
> 2009/10/14 Sam Vekemans :
> > Ok, so my big question is:
> > Why are your property boundaries rendered with solid fill?
> > Its not indicating land use, and should be rendered as a
> > 'dash-dot-dot-dash' line.
> > (at least thats how i remember
2009/10/14 Sam Vekemans :
> But of course the landuse us 'unknown' by default. .. so what needs to be
> done is to go around and find out what the actual landuse is.
> ... of course there are voids there are voids all over the map of black
> space. :)
Swing and a miss...
The property boundary
I made another example:
http://wiki.openstreetmap.org/images/5/5d/Dcdb-example.png
It's clearer in this screen shot (using JOSM, JOSM has a black
background so the transparent pixels are black) exactly what runs down
the middle of these voids.
___
Tagg
2009/10/14 John Smith :
> http://wiki.openstreetmap.org/images/5/5d/Dcdb-example.png
Here's the after shot:
http://wiki.openstreetmap.org/images/b/bf/Dcdb-example2.png
___
Tagging mailing list
Tagging@openstreetmap.org
http://lists.openstreetmap.org/li
Then the yellow must be all the "landuse=residential" then :)
As land use can extend past the property boundary, were there is an easment.
Strike 3,
im out.
Since were on the tagging list, the sidewalks & waterworks like sewer
lines, or underground cable lines, do we map these too, as the data i
2009/10/14 Sam Vekemans :
> Then the yellow must be all the "landuse=residential" then :)
In this instance I'd guess the same thing, but without a survey we
won't know for sure.
> As land use can extend past the property boundary, were there is an easment.
Easements show up as a void also, altho
28 matches
Mail list logo
