Re: [Tagging] What is a conscription number (addr:conscriptionnumber)?

[Tony Shield]

Hi

Don't have these in UK. I understood what you were describing easily  - 
I've seen them on my travels but did not understand why a house could 
have two numbers - now I do.


Regards

On 03/03/2019 07:28, Mateusz Konieczny wrote:

I attempted to de describe conscription numbers
at https://wiki.openstreetmap.org/wiki/Key:addr:conscriptionnumber
- mostly using automatically translated texts.

Can someone look at this and check whatever what I added is correct
and more or less clear?

Also, has anybody got any idea how addr:provisionalnumber and
addr:housenumber tags differ in meaning?

( https://wiki.openstreetmap.org/wiki/Key:addr:provisionalnumber )

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] What is a conscription number (addr:conscriptionnumber)?

[Tobias Zwick]

Thank you for the documentation. I read it, and it is clear to me.

Maybe it'd be good to further stress out how housenumber relates to
conscription- and streetnumber by giving an example:

  addr:streetnumber + addr:street = addr:housenumber + addr:street

  addr:conscriptionnumber + addr:place = addr:housenumber + addr:place

Conscriptionnumber explicitly refers to the place, streetnumber
explicitly refers to the street. And only in places where both numbers
exist alongside each other, it is necessary to use these tags.

Anyway, one important point I want to make is that there are many more
places than only in Czechia and Slovakia where the housenumbers relate
to the place, not the street, because streets in small(er) villages
often have no name, at least to my experience in South East Asia but I
bet this is somewhat universal.



Provisional numbers are a different type of conscription numbers
assigned to temporary, recreational buildings (etc). See § 31 zákona
128/2000 Sb [1] for Czech Republic.

Tobias

[1] https://zakonyprolidi.cz/cs/2000-128#f2024753

On 03/03/2019 08:28, Mateusz Konieczny wrote:
> I attempted to de describe conscription numbers
> at https://wiki.openstreetmap.org/wiki/Key:addr:conscriptionnumber
> - mostly using automatically translated texts.
> 
> Can someone look at this and check whatever what I added is correct
> and more or less clear?
> 
> Also, has anybody got any idea how addr:provisionalnumber and
> addr:housenumber tags differ in meaning?
> 
> ( https://wiki.openstreetmap.org/wiki/Key:addr:provisionalnumber )
> 
> ___
> Tagging mailing list
> Tagging@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
> 


___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] Clarification unclassified vs residential

[djakk djakk]

Hello !

I’ve updated
https://wiki.openstreetmap.org/wiki/User:Djakk/new_tagging_scheme_for_roads

To answer the original question of this thread, I wish you can use
importance_local=5 or 6 with abutters=rural or residential ;)


Julien “djakk”



Le dim. 3 mars 2019 à 01:01, Sergio Manzi  a écrit :

>
> On 2019-03-03 00:49, Mark Wagner wrote:
> > On Sat, 2 Mar 2019 02:05:46 +0100
> > Sergio Manzi  wrote:
> >
> >> On 2019-03-02 01:33, Martin Koppenhoefer wrote:
> >>> sent from a phone
> >>>
>  On 1. Mar 2019, at 13:45, Mateusz Konieczny
>   wrote:
> 
>  I would tag max weight, I would not tag emergency=no.
> >>> +1, it will not exclude all kinds of emergency services anyway,
> >>> only those in vehicles that are too heavy, for example there could
> >>> be police on bicycles who could cycle on the bridge like
> >>> pedestrians can walk on it.
> >>>
> >>>
> >>> Cheers, Martin
> >>
> >> I really-really-really like to know of a place where emergency
> >> vehicles are *legally *not allowed to go...
> > It's not "legally not allowed to go", but on Fairchild Air Force Base,
> > civilian emergency vehicles are subject to the same "with permission
> > only" restriction as everyone else.  I suspect the same is true of most
> > if not all other military bases in the United States.
>
>
> I also suspect guards of the US Bullion Depository at Fort Knox will not
> just open the gates to an unexpected ambulance even if it had full light
> flashing and siren wailing. Or will they? Maybe a good idea worth trying...
>
>
>
>
> ___
> Tagging mailing list
> Tagging@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

[Tagging] Mapping curb (kerb) lines as the home of curb, parking, etc information

[Nick Bolten]

A recent post on the Mapillary blog (
https://blog.mapillary.com/update/2019/02/12/potential-for-openstreetmap-to-seize-the-curb.html)
reminded me of my long-running wish to have more curb lines mapped, so I
wanted to get a discussion started to see what people think of mapping
curbs as ways.

The short version is this: if we put kerb=* on a line and call it its own
feature, what's the best tagging schema to use and what kind of additional
information is appropriate? Personally, I'd like to use (and recommend) the
existing kerb=* tags around blocks and potentially add parking information.

Potential mapping and data use cases:

- Public parking data: curbs are already marked with parking / stopping
information, and when motor vehicles stop at a curb they are meant to
follow the local regulations regarding access. Curbs seem like a natural
place to store this information: you can split the way whenever the parking
situation differs or where there are dedicated parking slots. It is
attractive to associate streets with parking information, but if one were
to split street ways whenever parking information changed, every city block
would become an incomprehensible, split-up mess.

- Streets as areas: there are a few schemas out there about mapping streets
and related features as areas, primarily for rendering purposes. Mapping
the curb is fully compatible with, and part of, these proposals, and could
provide a means of building up to fully mapping contiguous areas.

- Pedestrian crossings. I would be very excited to map out kerb=* ways
around every block I see, because it makes QA (and even safe,
semi-automated edits) for pedestrian accessibility so easy. All a validator
has to do is check that a highway=footway crosses a kerb=* way and lacks
its own kerb=* node. This is similar to the validators already used in JOSM
and iD that check for things like a footway or street intersecting a
building, reminding users to use covered=* or tunnel=*.

- Pedestrian islands. These are often just an assembly of raised curbs
intended to protect pedestrians that are doing a multi-part crossing of a
street or streets.

- Opportunity to merge with + simplify micromapped stairs: what are stairs
but a series of carefully-raised "curbs"? I've seen various proposals
regarding how one might map large, beautiful, public stairways. This is a
whole can of worms, but the information in describing a physical curb is
essentially the same as describing any 'stuff on the right is higher than
stuff on the left' interface.

Thoughts?
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] Clarification unclassified vs residential

[Mateusz Konieczny]

"I would have expected the first road be rendered not like the 3 last roads, 
those last 3 roads should have been rendered the same as they look the same"

Is it tagging or rendering discussion?

Because as far as as rendering is concerned you can already do that, just
use surface/lanes/oneway tags.

In general highway=* tag is not about how road looks like, it is rather about 
its 
importance in road system (with sole exception of highway=motorway).

It is hard to be sure without real proposal but I am not fan of tags like
looks_like=FR_urban_motorway or road_class=UK_motorway

And I am against tags like importance_local=5 or road_level=1.
Numeric values in tracktype=* were a mistake, it is really hard to remember 
what is the difference between tracktype=grade3 and tracktype=grade4.

Mar 3, 2019, 7:02 PM by djakk.dj...@gmail.com:

> Hello !
>
> I’ve updated 
> https://wiki.openstreetmap.org/wiki/User:Djakk/new_tagging_scheme_for_roads 
> 
>
> To answer the original question of this thread, I wish you can use 
> importance_local=5 or 6 with abutters=rural or residential ;)
>

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] What is a conscription number (addr:conscriptionnumber)?

[Graeme Fitzpatrick]

Yes, nice & clear thanks Mateusz - when I'd seen the name listed
previously, I'd always assumed it was something to do with allocating areas
for conscription for military service!

Just clarifying for my own interests sake - so the village / suburb only
has a number, rather than a name? So your example would be village
(suburb?) 280, Staré Brno district?

& are they numbered sequentially, or randomly? EG as you travel north from
this city do you pass through 280, 281, 282 & so on; or is 280 5k north,
281 10k SW, 282 5k E, 283 15k N, but with 135 & 512 between it & 280?

Thanks

Graeme
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] What is a conscription number (addr:conscriptionnumber)?

[Warin]

On 04/03/19 08:42, Graeme Fitzpatrick wrote:
Yes, nice & clear thanks Mateusz - when I'd seen the name listed 
previously, I'd always assumed it was something to do with allocating 
areas for conscription for military service!


Just clarifying for my own interests sake - so the village / suburb 
only has a number, rather than a name? So your example would be 
village (suburb?) 280, Staré Brno district?


& are they numbered sequentially, or randomly? EG as you travel north 
from this city do you pass through 280, 281, 282 & so on; or is 280 5k 
north, 281 10k SW, 282 5k E, 283 15k N, but with 135 & 512 between it 
& 280?




In Australia we have development numbers and lot numbers .. they only 
get used for planning,  construction and deeds ... most people don't 
know about them.

Not something that we map as they don't generally get used.

I do like the housenmber = thing.
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] Mapping curb (kerb) lines as the home of curb, parking, etc information

[Warin]

On 04/03/19 06:12, Nick Bolten wrote:
A recent post on the Mapillary blog 
(https://blog.mapillary.com/update/2019/02/12/potential-for-openstreetmap-to-seize-the-curb.html) 
reminded me of my long-running wish to have more curb lines mapped, so 
I wanted to get a discussion started to see what people think of 
mapping curbs as ways.


The short version is this: if we put kerb=* on a line and call it its 
own feature, what's the best tagging schema to use and what kind of 
additional information is appropriate? Personally, I'd like to use 
(and recommend) the existing kerb=* tags around blocks and potentially 
add parking information.


Potential mapping and data use cases:

- Public parking data: curbs are already marked with parking / 
stopping information, and when motor vehicles stop at a curb they are 
meant to follow the local regulations regarding access. Curbs seem 
like a natural place to store this information: you can split the way 
whenever the parking situation differs or where there are dedicated 
parking slots. It is attractive to associate streets with parking 
information, but if one were to split street ways whenever parking 
information changed, every city block would become an 
incomprehensible, split-up mess.


- Streets as areas: there are a few schemas out there about mapping 
streets and related features as areas, primarily for rendering 
purposes. Mapping the curb is fully compatible with, and part of, 
these proposals, and could provide a means of building up to fully 
mapping contiguous areas.


- Pedestrian crossings. I would be very excited to map out kerb=* ways 
around every block I see, because it makes QA (and even safe, 
semi-automated edits) for pedestrian accessibility so easy. All a 
validator has to do is check that a highway=footway crosses a kerb=* 
way and lacks its own kerb=* node. This is similar to the validators 
already used in JOSM and iD that check for things like a footway or 
street intersecting a building, reminding users to use covered=* or 
tunnel=*.


- Pedestrian islands. These are often just an assembly of raised curbs 
intended to protect pedestrians that are doing a multi-part crossing 
of a street or streets.


- Opportunity to merge with + simplify micromapped stairs: what are 
stairs but a series of carefully-raised "curbs"? I've seen various 
proposals regarding how one might map large, beautiful, public 
stairways. This is a whole can of worms, but the information in 
describing a physical curb is essentially the same as describing any 
'stuff on the right is higher than stuff on the left' interface.


Thoughts?


Err ... no.
Curbs and guttering are road edges. Detail them as part of the road/foot 
path.


___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] What is a conscription number (addr:conscriptionnumber)?

[Mateusz Konieczny]

Mar 3, 2019, 10:42 PM by graemefi...@gmail.com:

> Yes, nice & clear thanks Mateusz - when I'd seen the name listed previously, 
> I'd always assumed it was something to do with allocating areas for 
> conscription for military service!
>
It used to, first addressing in this areas started for military-related 
purposes (conscription).

> Just clarifying for my own interests sake - so the village / suburb only has 
> a number, rather than a name? So your example would be village (suburb?) 280, 
> > Staré Brno district?>  
>
In this addressing system location has address made from two parts
- location (say Staré Brno distric)
- number within location

Unlike street number that has three parts
- location (town, settlement etc)
- street name
- number on the street

> & are they numbered sequentially, or randomly? EG as you travel north from 
> this city do you pass through 280, 281, 282 & so on; or is 280 5k north, 281 
> 10k SW, 282 5k E, 283 15k N, but with 135 & 512 between it & 280?
>
randomly, or more specifically order is not necessarily related to location - 
but be based on say 
order of construction permits

I made edit during making this reply - see
https://wiki.openstreetmap.org/w/index.php?title=Key:addr:conscriptionnumber&diff=1816857&oldid=1816164
 

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging