On Thu, Jul 29, 2010 at 1:00 PM, Brian Quinion <
openstreet...@brian.quinion.co.uk> wrote:
> >> Discussing this for a day on the Tagging list is not enough for you to
> make
> >> this change.
> >
> > How much time should it take? I didn't really set a dead line but was
> > trying to get comments o
If there IS a change for medical stuff, I would personally rather see
the medical=* proposal be used.
http://wiki.openstreetmap.org/wiki/Proposed_features/Medical
Hospitals could be medical=hospital and emergency=yes/no to take care
of the "is this an emergency hospital" concern.
Then I guess a
Hi
A few weeks ago, I posted the following question to talk-transit
(edited here slightly from the original post, based on the limited
feedback received there). Given the specialized focus of the problem,
I did not post it to the tagging listserv, but I had very limited
response to the qu
My two cents:
"winery" is a better term than "vineyard" because, in some contexts at
least, the two have distinct meanings.
"cellar door" is a bad term because it will be taken literally by many
people and lead to confusion.
Given that there are wineries that don't sell direct to the public,
and
On Fri, Jul 30, 2010 at 4:03 PM, ael wrote:
> Many of these places sell a very wide range of goods, so something like
> building_supplies is sufficiently general to cover such cases.
> Individual tags for every line would not be feasible, even if the
> average mapper could get the information, and
> Most ambulance stations here usually aren't joined to a hospital,
> patient transport is another matter but they usually aren't used for
> emergencies. Some stations aren't even close to a hospital, like this
> one near me, it's about 6km from the nearest hospital:
>
> station: http://www.openstr
On 30 July 2010 17:53, Peteris Krisjanis wrote:
> Well, that's another reason to tag them separately, right? So we can
> have amenity=hospital and emergency=ambulance_station
I don't think that was ever in dispute, the only reference of
emergency with hospital was to do with any emergency rooms..
On 30 July 2010 17:42, Steve Bennett wrote:
> My two cents:
>
> "winery" is a better term than "vineyard" because, in some contexts at
> least, the two have distinct meanings.
> "cellar door" is a bad term because it will be taken literally by many
> people and lead to confusion.
>
> Given that th
On 30 July 2010 17:42, Steve Bennett wrote:
>
> Given that there are wineries that don't sell direct to the public,
> and there are wine shops not attached to wineries, and that a cellar
> door is really no more than a wine shop within a winery, I would
> suggest:
>
Some cellar doors these days a
Ed - the proper way to do bus routes is using relations. The operator
tag should be on the relation, and should only have one value. This is
how we deal with geolocations being part of multiple geographical
structures.
If you want to add route_ref tags to the bus stops, then just make a
single lis
On Fri, 30 Jul 2010, Toby Murray wrote:
> Then I guess a question would be would pharmacies be medical=pharmacy
> or remain shop=pharmacy?
When I visited Holland (probably before you lot were born) the pharmacy sold
only pharmaceuticals. It would be a medical=pharmacy.
In Australia the pharmaceut
Regarding my cycleway=no_shoulder suggestion, here are a couple of example
we see often in Quebec, where car and bicycle share the road without
shoulders :
http://pistescyclables.ca/Evaluation/Signalisation/101_0706NotreDamedeMontauban.jpg
http://pistescyclables.ca/Evaluation/Signalisation/101_070
If they form part of a route (which is what I assume is meant by piste
cyclable), they should be a route relation. The conventional way of
tagging such relations is:
type=route
route=bicycle
network=lcn/rcn/ncn (local/regional/national depending on the scope of
the route)
{I don't like the use of
I don't understand this argument. Doesn't every tag change anywhere "break
every editor/renderer/search/data user" whether or not you think it is
correct?
John has just as much right to go change all the amenity= tags to something
more specific as you do to keep them the same. Data consumers
On 30 July 2010 21:15, Mike N. wrote:
> Every Smartphone OSM data consumer I've looked at has been unusable because
> of tagging interpretation. Compared to OSM, data consumers seem to be very
> inflexible and unaware of any but the most rigid tag schemes that haven't
> changed in the past year
On Fri, Jul 30, 2010 at 6:39 AM, Daniel Tremblay wrote:
> Regarding my cycleway=no_shoulder suggestion, here are a couple of example
> we see often in Quebec, where car and bicycle share the road without
> shoulders :
>
> http://pistescyclables.ca/Evaluation/Signalisation/101_0706NotreDamedeMontau
On Fri, Jul 30, 2010 at 2:42 AM, Ross Scanlon wrote:
>> 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 pretti
In Nashville, Tennessee, USA, where I live, there aren't any ambulances based
out of hospitals. The ambulances that handle emergency calls are all operated
by the city fire department, and are based at fire stations. There are also
commercial ambulance services, based out of various locations,
I thought most smart phone apps would mostly view map tiles, either
OSM or Cloudmade?
There are several apps now for the iPhone which also search POIs. Some
examples:
-JOSM allows tagging whether banks include an ATM - I select this when
the ATM is attached to the building or inside the
Just to drag things back on topic, so far most claims seem to be vague
and generalised, however the original proposal about shifting police
and fire into an emergency category doesn't seem to have many/any of
the draw backs of most POIs most people are going to search for most
of the time.
Suppose
> 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
On 30 July 2010 16:26, Ross Scanlon 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 osm2p
On Fri, Jul 30, 2010 at 11:05 AM, Emilie Laffray
wrote:
>
> While I follow this mailing list, I am pretty sure that many people
> working in the OSM ecosystem is not following the change that fast. It means
> that every one doing an app needs to do some significant work to make sure
> that those
On 30 July 2010 17:14, Ian Dees wrote:
> On Fri, Jul 30, 2010 at 11:05 AM, Emilie Laffray > wrote:
>
>>
>> While I follow this mailing list, I am pretty sure that many people
>> working in the OSM ecosystem is not following the change that fast. It means
>> that every one doing an app needs to
On 30/07/2010 17:14, Ian Dees wrote:
The OSM ecosystem has always strongly favored ease of mapping (as
opposed to ease of data consumption), but now that more data consumers
are attempting to use our data maybe it's time to start thinking about
how we can firm things up a little bit to give the d
John Smith wrote:
On 31 July 2010 02:05, Emilie Laffray wrote:
While I follow this mailing list, I am pretty sure that many people working
in the OSM ecosystem is not following the change that fast. It means that
What change, I have made a suggestion and was after comments, so far
som
On 31 July 2010 03:43, Chris Hill wrote:
> Here's an example of a change you claim you haven't made:
No, I claimed to have made those, as I pointed out to you in a
previous reply, what exactly was so important about these locations
that no one could be bothered to spend 2 seconds making a wiki pa
On 31 July 2010 03:34, Ian Dees wrote:
> It appears that you have indeed made lots of changes in the database before
> discussing on the list:
> e.g. http://www.openstreetmap.org/browse/node/771625043/history
Hmmm thought I fixed that by reverting that changeset... I'll fix it
now thanks for poin
On Fri, Jul 30, 2010 at 12:25 PM, John Smith wrote:
> On 31 July 2010 02:05, Emilie Laffray wrote:
> > While I follow this mailing list, I am pretty sure that many people
> working
> > in the OSM ecosystem is not following the change that fast. It means that
>
> What change, I have made a suggest
On 31 July 2010 02:05, Emilie Laffray wrote:
> While I follow this mailing list, I am pretty sure that many people working
> in the OSM ecosystem is not following the change that fast. It means that
What change, I have made a suggestion and was after comments, so far
some are for this specific ch
On Sat, 31 Jul 2010, Chris Hill wrote:
> This includes private or charity stations which are not emergency stations.
Chris, would you be able to tell me (us) what is a private station or a
charity station?
Despite my age and being initially at school in the UK, I don't know what they
are. As JS
On Fri, 30 Jul 2010 17:05:19 +0100
Emilie Laffray wrote:
> On 30 July 2010 16:26, Ross Scanlon 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
On 30/07/2010 08:53, Peteris Krisjanis wrote:
Most ambulance stations here usually aren't joined to a hospital,
patient transport is another matter but they usually aren't used for
emergencies. Some stations aren't even close to a hospital, like this
one near me, it's about 6km from the nearest
On 31 July 2010 09:29, Dave F. wrote:
> 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.
Where I live it is common to talk about the emergency services.
> 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
__
On 31/07/2010 00:46, Stephen Hope wrote:
On 31 July 2010 09:29, Dave F. wrote:
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.
Where I live it is common
Ignoring for the moment the whole "how do we change it" thing brought
up by the emergency tags, there seems to be a whole underlying issue
that's worth looking at.
There seems to be a disconnect between two groups of people - those
who would like a more defined grouping of tags, and those who thin
On 31 July 2010 09:51, Dave F. wrote:
> If it ain't broke...
This wouldn't have come up if everyone thought that, there is a lot of
inconsistencies in the current tags on the map features page.
___
Tagging mailing list
Tagging@openstreetmap.org
http://
On 31 July 2010 10:39, Stephen Hope wrote:
> Ignoring for the moment the whole "how do we change it" thing brought
> up by the emergency tags, there seems to be a whole underlying issue
> that's worth looking at.
The how is fairly simple, no one seems to have disagreed with that,
the why and the
First, I want to add some more arguments to the list:
@ Cons "Defined groupings approach"
- sometimes meanings will be read into a key that originally weren't
there(1), this cannot happen with a generic type key
@ Pros "All in one approach"
- it's easier to find the correct tag if it *does* use t
On 31/07/2010, at 11:07 AM, John Smith wrote:
> Maybe we should stop using words for key pair values and just come up
> with a database that issues ID numbers, half the problems with the
> current scheme is due to people treating enumerated key pairs in the
> same way they are used to using english
41 matches
Mail list logo
