Re: [Tagging] Tagging for Pipe Line Reserves

[Ross Scanlon]

Agree Dave.

As I said it could be a park but without on the ground survey or other 
info it's unknown.


These are quite often parks and should be tagged as leisure=park but 
onwards from that is the reason it is a park.


In these situations the park could also be a reserve or easement for the 
pipe line.


The discussion on talk_au was that it could be tagged leisure=park 
park=pipeline_reserve.


Cheers
Ross


On 08/02/17 22:02, Dave Swarthout wrote:

Thanks Ross,

It *might *be a park but we can't be sure. The mapper only says 
source=Bing. For all we know he's merely making an educated guess. His 
changeset comment suggests he has also added some "pipeline reserves" 
although a quick look doesn't turn any up.


On Wed, Feb 8, 2017 at 5:44 PM, Ross Scanlon <i...@4x4falcon.com 
<mailto:i...@4x4falcon.com>> wrote:


This is the aerial imagery of the area the original poster is
talking about:

https://binged.it/2kN1tfC

To all intents it could be a park.

In osm it's at:

http://www.openstreetmap.org/way/370388062#map=17/-38.15997/145.20073
<http://www.openstreetmap.org/way/370388062#map=17/-38.15997/145.20073>

Cheers

Ross



On 08/02/17 19:51, Dave Swarthout wrote:

Yes, I see now you're asking about the land that the pipeline
either runs over or through.

I would avoid the term reserve, however. I generally think of a
reserve as a larger area, often a park or historic area, e.g.,
the Gabo Island Lighthouse Reserve in Canada or the Hinchinbrook
Lighthouse Reserve, which is a Park in Valdez-Cordova County,
Alaska. There is also this reserve which is related to your
illustration; the huge area known as the National Petroleum
Reserve in Alaska, but I would not want it to be confused with
your tagging targets.

https://en.wikipedia.org/wiki/National_Petroleum_Reserve%E2%80%93Alaska
<https://en.wikipedia.org/wiki/National_Petroleum_Reserve%E2%80%93Alaska>

Maybe landuse=pipeline would be a good pick?

On Wed, Feb 8, 2017 at 3:46 PM, Warin <61sundow...@gmail.com
<mailto:61sundow...@gmail.com>> wrote:

On 08-Feb-17 06:51 PM, François Lacombe wrote:

Hi Warin,

Do you have pictures of such areas plz ?

I don't see anything corresponding to 'reserve'

All the best


Not personally ... and it is a fair way away. As I say ..
reported on the Australian group.
I assume there is a sign locally to advise on the 'pipeline 
reserve'.


Gas pipe lines cover fair distances in Australia ..

One line is 1,300 km here

https://www.apa.com.au/our-services/gas-transmission/east-coast-grid/moomba-sydney-pipeline/

<https://www.apa.com.au/our-services/gas-transmission/east-coast-grid/moomba-sydney-pipeline/>

The reserve might be up to 25 meters wide from
https://www.seagas.com.au/safety/
<https://www.seagas.com.au/safety/>
Photo of their warning sign
http://www.seagas.com.au/wp-content/uploads/2014/01/danger.jpg
<http://www.seagas.com.au/wp-content/uploads/2014/01/danger.jpg>
I have seen similar signs for gas and fibre optic lines in my
wanderings, some warning of a restriction in use of area
above the line - thus advising of a restrictive reserve.

There will be local storm water, potable water lines too.
Long distant buried communication lines too, a number over
8,500 km. At least some of these will have 'reserves' evident
on the surface.



Le 8 févr. 2017 08:24, "Warin" <61sundow...@gmail.com
<mailto:61sundow...@gmail.com>> a écrit :

That tags the pipe line itself.

The request is to tag the area set aside for a pipe line
... a reserve.



On 08-Feb-17 04:38 PM, Dave Swarthout wrote:

There is already a tagging structure for pipelines that
takes into account whether it's underground or
overground. See

http://www.openstreetmap.org/way/8964252
<http://www.openstreetmap.org/way/8964252>

for a section of the Trans Alaska Pipeline. However,
the land area above the pipeline, which is restricted
for casual access throughout Alaska, has no special
tagging.

On Wed, Feb 8, 2017 at 7:56 AM, Warin
<61sundow...@gmail.com <mailto:61sundow...@gmail.com>>
wrote:

Hi,

A question came up on the Australian list that
would be more appropriate here.

"My local area (and I'm sure many others) have lots
of pipeline reserves.

I'm really not sure how to tag these. They appear
to have

public acc

Re: [Tagging] Tagging for Pipe Line Reserves

[Ross Scanlon]

This is the aerial imagery of the area the original poster is talking about:

https://binged.it/2kN1tfC

To all intents it could be a park.

In osm it's at:

http://www.openstreetmap.org/way/370388062#map=17/-38.15997/145.20073

Cheers

Ross



On 08/02/17 19:51, Dave Swarthout wrote:
Yes, I see now you're asking about the land that the pipeline either 
runs over or through.


I would avoid the term reserve, however. I generally think of a 
reserve as a larger area, often a park or historic area, e.g., the 
Gabo Island Lighthouse Reserve in Canada or the Hinchinbrook 
Lighthouse Reserve, which is a Park in Valdez-Cordova County, Alaska. 
There is also this reserve which is related to your illustration; the 
huge area known as the National Petroleum Reserve in Alaska, but I 
would not want it to be confused with your tagging targets.


https://en.wikipedia.org/wiki/National_Petroleum_Reserve%E2%80%93Alaska

Maybe landuse=pipeline would be a good pick?

On Wed, Feb 8, 2017 at 3:46 PM, Warin <61sundow...@gmail.com 
> wrote:


On 08-Feb-17 06:51 PM, François Lacombe wrote:

Hi Warin,

Do you have pictures of such areas plz ?

I don't see anything corresponding to 'reserve'

All the best


Not personally ... and it is a fair way away. As I say .. reported
on the Australian group.
I assume there is a sign locally to advise on the 'pipeline 
reserve'.


Gas pipe lines cover fair distances in Australia ..

One line is 1,300 km here

https://www.apa.com.au/our-services/gas-transmission/east-coast-grid/moomba-sydney-pipeline/



The reserve might be up to 25 meters wide from
https://www.seagas.com.au/safety/ 
Photo of their warning sign
http://www.seagas.com.au/wp-content/uploads/2014/01/danger.jpg

I have seen similar signs for gas and fibre optic lines in my
wanderings, some warning of a restriction in use of area above the
line - thus advising of a restrictive reserve.

There will be local storm water, potable water lines too.
Long distant buried communication lines too, a number over 8,500
km. At least some of these will have 'reserves' evident on the
surface.



Le 8 févr. 2017 08:24, "Warin" <61sundow...@gmail.com
> a écrit :

That tags the pipe line itself.

The request is to tag the area set aside for a pipe line ...
a reserve.



On 08-Feb-17 04:38 PM, Dave Swarthout wrote:

There is already a tagging structure for pipelines that
takes into account whether it's underground or overground. See

http://www.openstreetmap.org/way/8964252


for a section of the Trans Alaska Pipeline. However, the
land area above the pipeline, which is restricted for casual
access throughout Alaska, has no special tagging.

On Wed, Feb 8, 2017 at 7:56 AM, Warin <61sundow...@gmail.com
> wrote:

Hi,

A question came up on the Australian list that would be
more appropriate here.

"My local area (and I'm sure many others) have lots of
pipeline reserves.

I'm really not sure how to tag these. They appear to have

public access for walking at least. (One local one has a
sign
disallowing golf...) Some others appear to be across private
land, and i'm less interested in those, I'd really like to
show those ones with public access.


examples:http://www.openstreetmap.org/way/370388062#map=17/-38.15997/145.20073




I've tagged them as leisure=park previously, and paths
  evident on the ground have just been tagged
highway=path.


Any ideas?"

My comments:

I note the pipeline is not visible ... I assume
underground and the
location is not evident so you cannot map the pipe line
itself.

As it is a landuse ... ?
I would tag landuse=pipeline

However ... some pipe lines cross farms, residential
areas ...  these have legal easements through the
associated properties.
And these would be already tagged with a landuse.

Humm power lines are mapped ... should there be similar
provision for other infrastructure?
Perhaps a 'infrastructure' tag that can be used for all?
infrastructure=pipeline
infrastructure=sewer
infrastructure=water
  

Re: [Tagging] Turn Restriction usage

[Ross Scanlon]

In one case there is a road where a two way section comes to a divider
and becomes two one way sections for a while. The suggested route came
along one of the one way sections, then turned about 340 degrees to go
down the other side of the road. It may be legal to do a u-turn there,
but I don't think it's safe, or even possible for most cars. I was
thinking about it, and many other divided road are similar where they
split/join. Should we be putting no u-turn restrictions on these?
There's no actual signs.


No.  The router should know not to do this. Likewise as below the router 
should not make u turns at traffic lights.




The other thing I was wondering about is traffic lights.  Where I live,
it is illegal to do a u-turn at an intersection with traffic lights
unless there is a sign allowing you to. There's no signs saying not to,
you're just supposed to know. There has been some discussion in the past
with routers that have this sort of knowledge built in. Did anything
come of this, or should I just start putting four turn restriction
relations on all the traffic light intersections in my neighbourhood?
That's going to be painful, not to mention causing a lot of road splitting.

Stephen


Cheers
Ross

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

Re: [Tagging] Turn Restriction usage

[Ross Scanlon]

No.  The router should know not to do this. Likewise as below the router
should not make u turns at traffic lights.


Based on what? How does the router know that the two ways are two
carriageways of a single road? Couldn't they be a straight road, that
becomes a oneway street at a certain point, and at that point a
junction brings to a oneway secondary road?


The name of the way, the fact that you are turning  180 degrees on the 
same way.


Cheers
Ross


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

Re: [Tagging] This needs to be nipped in the bud

[Ross Scanlon]

On 06/03/12 03:32, Frederik Ramm wrote:

Hi,

On 03/05/2012 08:12 PM, Nathan Edgars II wrote:

http://wiki.openstreetmap.org/wiki/Lanes_and_complex_intersections_visual_approach


User Cmuelle8 insists on adding it to
http://wiki.openstreetmap.org/wiki/Lane_tagging_comparison#A_visual_approach

as a valid alternate.


I think it is not crazier than some of the other ideas I've seen
floated. It is good to add it to the comparison, if only to make people
think about what they don't want ;)

Bye
Frederik

Definitely not how to map an intersection.  AU list have had several 
discussions on this and it's junk mapping.


Cheers
Ross


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

Re: [Tagging] Waterway direction

[Ross Scanlon]

 On Tue, Aug 31, 2010 at 4:10 AM, M∡rtin Koppenhoefer
 dieterdre...@gmail.com wrote:
  a) you will add a note or FIXME to express this to the following
  mapper. At least you have a 50% chance that it is already right.
 
 Perhaps you can explain how I or anyone else will determine the
 direction of this waterway: http://www.openstreetmap.org/?way=73765043
 Should I ask one of the residents if I can go into their backyard and
 dump food coloring in the water?
 
 I don't know of any other feature where the direction of the way means
 something *without* another tag being added. I've traced a number of
 waterways from aerials and never had any idea I was supposed to set
 the direction of the way equal to the direction of flow.


motorway,motorway_link

In both the direction of the way means something withou another tag being 
added.  However most add oneway=yes to these.


-- 
Cheers
Ross

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

Re: [Tagging] How do you map handicapped parking? (and other questions)

[Ross Scanlon]

On Sun, 29 Aug 2010 01:04:09 -0400
Nathan Edgars II nerou...@gmail.com wrote:

 There doesn't seem to be a tag on the wiki for either handicapped
 parking spots in a larger lot or a dedicated handicapped lot.

amenity=parking
capacity:disabled=yes or number of spaces.


It's on the wiki:

http://wiki.openstreetmap.org/wiki/Tag:amenity%3Dparking

-- 
Cheers
Ross

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

Re: [Tagging] is tourism a good category for everything cultural?

[Ross Scanlon]

 Well, I will take a change to 'troll' again about it. This discussion
 comes up again and again because we don't have:
 a) clear tagging guidelines (*not* rules)
 b) mechanism to replace tags

Agree totally.

This (b) would be easily recitified by normalising the database in regards to 
tags.
 
 While I agree that tag by it's nature doesn't matter while renderers
 and editors treat them right, however, there are lot of things which
 can be cleaned up - for mappers sake. Because tagging is done by
 people and less the confusion is, more tagging is correct. Yes, there
 are some historical screwups. But do they really can't be fixed? It is
 not like we are trying to rearrange whole amenity or shop space.
 
 It doesn't mean that everything can and will be changed. But it does
 allow room for fixing error so taggers don't get confused.
 
 Said all that, I think more work is needed on cleaning up and fixing
 map features wiki entries. There are lot of bugs and errors.
 
+1

-- 
Cheers
Ross

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

Re: [Tagging] is tourism a good category for everything cultural?

[Ross Scanlon]

On Tue, 24 Aug 2010 10:03:42 +0200
Ulf Lamping ulf.lamp...@googlemail.com wrote:

 Am 24.08.2010 09:36, schrieb Ross Scanlon:
  Well, I will take a change to 'troll' again about it. This discussion
  comes up again and again because we don't have:
  a) clear tagging guidelines (*not* rules)
  b) mechanism to replace tags
 
  Agree totally.
 
  This (b) would be easily recitified by normalising the database in regards 
  to tags.
 
 So how do you easily: normalise the mappers minds, renderers, editing 
 software in regards to tags?!?
 
 Over several years past now, I have seen this discussions come and go. 
 When someone was actually doing something, it usually ended up in a mess 
 of wiki, mappers, editors and renderers disagreeing how to tag 
 something. A confusion causing a *lot* more harm than any good.
 
 It's simply a misconception, that just cleaning up the tag names will 
 lead to an easier mapping experience.
 
 Regards, ULFL

You have no idea about normalising a database do you.


It has nothing to do with what you have above.


Rather than storing a tag as a key=value, you store it as a unique identifier.

The identifier is then referenced in another table in the database which will 
provide the key and value.


Lets take an example.


Currently in osm we have a road tagged with the following:

name=A street
highway=residential
source=xyz


If the database was normalised then the following would occur.

name=A street
tag_id=100
tag_id=101

The tagging table would have in it:

for a tag_id of 100

tag_id=100
key=highway
value=residential

for a tag_id of 101

tag_id=101
key=source
value=xyz


Now say that we decide that we no longer wish to call residential ways 
residential but a new name of house streets.

To change the current database it would take a lot of effort but with a 
normalised database all we have to do is change the value=residential in the 
tagging database to value=house_streets and every way that was tagged 
residential is now tagged house streets.


Tags like name would not have a tag_id as they are not unique.

The renderers would simply have to look in the tagging table to see what needs 
to be displayed.


-- 
Cheers
Ross

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

Re: [Tagging] is tourism a good category for everything cultural?

[Ross Scanlon]

You may also want to have a read of this:

http://en.wikipedia.org/wiki/Database_normalization



-- 
Cheers
Ross

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

Re: [Tagging] is tourism a good category for everything cultural?

[Ross Scanlon]

  Typical.
 
  NFI about database use so you resort to slinging mud.
 
 
  I have a significant idea about how osm works as I have to integrate it 
  into programs I write or contribute to.
 
  If the database was normalised then I'd have a reduction of about 1000 
  lines of code in one program alone.
 
 Hint: OSM is not about database coders saving their time.
 
 Regards, ULFL

No kidding.

I thought it was there to produce the most accurate map data available and then 
produce mapping information easily.

Obviously there is no use discussing this with you as you have no understanding 
of normalising a relational database and only bother to hard code things, like 
paths in a program.

This appears to be going about 60m above your head.


-- 
Cheers
Ross
 Leaves this thread.

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

Re: [Tagging] turn restrictions, multiple time intervals

[Ross Scanlon]

On Tue, 17 Aug 2010 18:04:21 +1000
John Smith deltafoxtrot...@gmail.com wrote:

 On 17 August 2010 17:44, Sebastian Klein basti...@googlemail.com wrote:
  Michael Barabanov wrote:
 
  Seems like double work to me.  Ross's suggestion may just work.  If
  there're no objections, I'll update the wiki.
 
  Please not, this is a crude hack. Why not use the opening_hours syntax? This
  should be standard.

That's the problem there is nothing standard for multiple hour_on hour_off

  hours=6:00-9:00,15:00-19:00

 Shouldn't that be inverted to indicate the hours you can turn, rather
 than the hours you can't?

And also a semi-colon ; between the times as per the rest of multiple values 
for one key.  As well as 4 digit times?

eg.

hours=09:00-15:00;19:00-06:00


-- 
Cheers
Ross

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

Re: [Tagging] turn restrictions, multiple time intervals

[Ross Scanlon]

On Mon, 16 Aug 2010 18:30:26 -0700
Michael Barabanov michael.baraba...@gmail.com wrote:

 Hi,
 
 How would one tag a turn restriction (
 http://wiki.openstreetmap.org/wiki/Turn_restrictions) which is active say
 6-9AM and 3-6PM every day? hour_on/hour_off seem to only be  sufficient for
 one time interval.
 
 Michael.

Maybe:

hour_on=06:00;15:00
hour_off=09:00;18:00



-- 
Cheers
Ross


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

Re: [Tagging] [OSM-talk] emergency=*

[Ross Scanlon]

 Work out why it doesn't appear (5 min - your patch is actually very
 slightly wrong btw, can you spot your mistake?)

Spotted my friday afternoon coding did you.  Glad to see someones on the ball!!

 However the above is just for fun - lets replace my original statement
 with 'a lot of time' and move on...

Sounds sensible to me, I'm busy tracing new nearmap imagery.

-- 
Cheers
Ross

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

Re: [Tagging] [OSM-talk] emergency=*

[Ross Scanlon]

 Well done.  Pretty much none of the others do.  I look forward to your
 patches :)

Heres the patch for the default.style for osm2pgsql

node,way   emergency  text nocache,polygon

Wasn't worth a diff patch as it's only one line.  (30 seconds)
 
 Mapnik for instance has manual rules - they will need to be changed.
 Worse than that osm2pgsql (the import tool) only imports certain keys
 so implementing emergency=* requires a complete reimport of the
 database - about 30 hours even on very good hardware.  Then the
 changes need to be tested and deployed.  I can get to 3 or 4 hours of
 actual developed work without even trying.

Probably should have used a diff patch but anyway heres a new file for mapnik 
rules in inc/ dir  (5 minutes most of which was spent getting a copy of mapnik 
from svn)


Could be called layer-emergency-points.xml.inc

---
Style
 Rule
  maxscale_zoom17;
  Filter[emergency]='ambulance_station'/Filter
  PointSymbolizer file=symbols;/ambulance.p.16.png /
/Rule
 Rule
  maxscale_zoom17;
  Filter[emergency]='police_station'/Filter
  PointSymbolizer file=symbols;/police.p.16.png /
/Rule
Rule
  maxscale_zoom17;
  Filter[emergency]='fire_station'/Filter
  PointSymbolizer file=symbols;/firestation.p.16.png /
/Rule
/Style

Layer name=emergency-points status=on srs=osm2pgsql_projection;
StyleNamepoints/StyleName
Datasource
  Parameter name=table
  (select 
way,amenity,shop,tourism,highway,man_made,access,religion,waterway,lock,historic,emergency
  from prefix;_point
  where emergency is not null
 or shop is not null
 or tourism in 
('alpine_hut','camp_site','caravan_site','guest_house','hostel','hotel','museum','viewpoint')
 or highway in ('bus_stop','traffic_signals','ford')
 or man_made in ('mast','water_tower')
 or historic='memorial'
 or waterway='lock'
 or lock='yes'
  ) as points/Parameter
  datasource-settings;
/Datasource
/Layer
Layer name=emergency-points-poly status=on srs=osm2pgsql_projection;
StyleNamepoints/StyleName
Datasource
  Parameter name=table
  (select 
way,amenity,shop,tourism,highway,man_made,access,religion,waterway,lock,historic,emergency
  from prefix;_polygon
  where emergency is not null
 or shop is not null
 or tourism in 
('alpine_hut','camp_site','caravan_site','guest_house','hostel','hotel','museum','viewpoint')
 or highway in ('bus_stop','traffic_signals')
 or man_made in ('mast','water_tower')
 or historic='memorial'
  ) as points/Parameter
  datasource-settings;
/Datasource
/Layer



And now the osm.xml file (30 seconds)

 Rule
  Filter[amenity] = 'police'/Filter
   maxscale_zoom17;
  TextSymbolizer name=name fontset_name=book-fonts size=10 
fill=#734a08 dy=10 halo_radius=1 wrap_width=30/
 /Rule
 Rule
  Filter[amenity] = 'fire_station'/Filter
  maxscale_zoom17;
  TextSymbolizer name=name fontset_name=book-fonts size=10 
fill=#734a08 dy=9 halo_radius=1 wrap_width=30/
 /Rule


replaced by

 Rule
  Filter[emergency] = 'police_station'/Filter
   maxscale_zoom17;
  TextSymbolizer name=name fontset_name=book-fonts size=10 
fill=#734a08 dy=10 halo_radius=1 wrap_width=30/
 /Rule
 Rule
  Filter[emercency] = 'fire_station'/Filter
  maxscale_zoom17;
  TextSymbolizer name=name fontset_name=book-fonts size=10 
fill=#734a08 dy=9 halo_radius=1 wrap_width=30/
 /Rule
  



Total time 6 minutes

Hundreds of hours, yeah right.

The program I've been talking about uses osm2pgsql and mapnik so I'm well aware 
of them.

If your smart you could probably add the emergency data without having to 
totally rerun osm2pgsql.


-- 
Cheers
Ross

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

Re: [Tagging] [OSM-talk] emergency=*

[Ross Scanlon]

On Fri, 30 Jul 2010 17:05:19 +0100
Emilie Laffray emilie.laff...@gmail.com wrote:

 On 30 July 2010 16:26, Ross Scanlon i...@4x4falcon.com wrote:
 
 
  Total time 6 minutes
 
  Hundreds of hours, yeah right.
 
  The program I've been talking about uses osm2pgsql and mapnik so I'm well
  aware of them.
 
  If your smart you could probably add the emergency data without having to
  totally rerun osm2pgsql.


 I think you are missing the point that Brian was making. If the data has to
 change dramatically, it means one or two man weeks to do the change at work
 for our engine at work. The change in itself is simple, but that means
 testing if none were missing, that everything is running fine, regenerating
 a database earlier than expected which in itself takes a significant amount
 of time. Testing is something quite important and we have tons of test to
 make sure that the database is working as expected before we release to
 production.

I'm well aware of this, but if your app is robust then the changes should not 
be that much of an issue and the testing should only be minor.  The garbage 
point Brian was making is exactly that garbage.  If you make statements like 
it'll be hundreds of developer hours to modify apps then you need to be able to 
back it up with facts.

Why would you have to regenerate the database earlier than expected?  If you 
regenerate the database on a regular basis then it could wait for the next 
routine regeneration.  It does not have to be done immediately, that was the 
point of initially duplicating the tags and then after a sufficient time then 
remove the duplicated amenity tags.

 However, I don't like those tags, as they don't really make sense in many
 cases. Before rushing, we should really evaluate a bit more if they make
 sense.


Then show why and where they don't make sense rather than carrying on about 
possible broken apps.

From my point of view the tags make perfect sense, if I have an emergency and 
I need police, fire or ambulance assistance then I'll look for emergency 
rather than amenity.

I've shown how quickly the two apps described by Brian can be updated quickly, 
it does not take much more effort than that.


-- 
Ross Scanlon i...@4x4falcon.com

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

Re: [Tagging] emergency=*

[Ross Scanlon]

 I just don't see an ambulance/fire station as an emergency. I mean, if 
 you fall down and injure yourself you don't try  get to the station you 
 'phone up  get an ambulance to come to you.


The suggestion is to have fire, police and ambulance as emergency.


-- 
Cheers
Ross

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

Re: [Tagging] emergency=*

[Ross Scanlon]

 Actually we could do both, we could add emergency=* tags to existing
 POIs without any problems as far as I know, and in future remove the
 old amenity tag.

I think this is a better option.

Just need to make sure that a date is set to remove the old amenity tags.

-- 
Cheers
Ross

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

Re: [Tagging] emergency=*

[Ross Scanlon]

 On 29 July 2010 19:15, Ross Scanlon i...@4x4falcon.com wrote:
  Just need to make sure that a date is set to remove the old amenity tags.
 
 What would a reasonable time frame be?
 
 ___
 Tagging mailing list
 Tagging@openstreetmap.org
 http://lists.openstreetmap.org/listinfo/tagging


1st October 2010

Gives time to get the rendering resolved.
 


-- 
Cheers
Ross

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

Re: [Tagging] [OSM-talk] emergency=*

[Ross Scanlon]

 Better yet - just don't change it.  This sort of change just isn't
 worth the pain and hundreds of developer hours that could be better
 spent on moving the project forward.  Yes - this sort of change might
 make the tag heirachy prettier - but not enough to justify the work.

Garbage.

It's not hundred of hours of developer work to change this.


If the renderer programming is up to scratch then it should be able to 
automatically accept changes like this.

One of the programs I have done some development on has this built in.


In the case of amenity=police.

The program scans the icon directory for all icons on start up.

Before rendering it then checks to see if it has a matching icon to 
amenity=police.  If it does then it renders that icon, if not then it renders 
the parent icon, ie amenity.

If it's changed to emergency=police_station

The renderer does not require any change, the only changes required are moving 
the amenity=police icon to be the emergency=police_station icon (which is a 30 
second job) and creating an appropriate emergency parent icon (and there's 
probably something already there we can use).


The program code to do this is approximately 100 lines of c including white 
space and comments.


-- 
Cheers
Ross

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

Re: [Tagging] emergency=*

[Ross Scanlon]

 The right long term solution for this stuff is to use country-specific
 tags, (eg, in australia we could use amenity=ses_station or
 something), and to centrally define (in machine-readable terms) what
 those country-specific tags are. But I think we're a fair way from
 being able to implement anything like that at present.
 
 Steve

Wouldn't it be better for these to be emergency=* as that's what I'd be looking 
for no matter what country I was in.




-- 
Cheers
Ross

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

Re: [Tagging] Tagging U-Turns (Was: [OSM-talk] Divided/Non-Divided Intersection)

[Ross Scanlon]

 Should we be tagging where it's allowed or where it's not allowed or
 where it's signed specifically one way or the other?


Only where it's signed.

-- 
Cheers
Ross

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