Another legitimate terms for these shops is a "vape shop", and the practice
of using any sort of electronic cigarette is now referred to as "vaping".
This is a better term than "smoking", as the product emits vapors, not
smoke.
We are enthusiastic about seeing this term standardized, as many
juris
Should standalone ATM's be tagged as amenity:atm, but ATM's in a bank be
amenity=bank
atm=yes
Or ...?
Thanks,
Tac
___
Tagging mailing list
Tagging@openstreetmap.org
http://lists.openstreetmap.org/listinfo/tagging
I thought the best practice was to define a building as a way, then
put a bank node within the building, and possibly at ATM node as well.
I guess it could be defined as a relation.
It doesn't appear that there are many ways with amenity=bank, they're
almost always nodes, even though they're almo
name=Subway
amenity=restaurant
cuisine=fast_food
OR
name=Subway
amenity=fast_food
cuisine=sandwiches
On a related note, are the underscores necessary? I'd rather say "Fast Food"
Thx,
Tac
___
Tagging mailing list
Tagging@openstreetmap.org
http://li
ticular, commas
could be problematic for storing a list of tags as a single string.
Tac
On Tue, May 28, 2013 at 6:52 PM, Richard Welty wrote:
> On 5/28/13 6:19 PM, Tac Tacelosky wrote:
>>
>> name=Subway
>> amenity=restaurant
>> cuisine=fast_food
>>
>>
Yeah, tag keys should follow that, but not key values. I'm sure there
are values with single and double quotes, commas and semi-colons.
Does OSM support any sort of multi-tag structure, like
"cuisine:japanese" AND "cuisine:thai"?
Tac
On Tue, May 28, 2013 at 7:18 PM, Gr
Thanks, that's helpful. I'm working on a UI where people type what
they see, and the system translates that to the appropriate tags. The
brand tag is particularly useful in this context, and one I wasn't
even aware of, so thanks for pointing it out.
Tac
On Wed, May 29, 2013 at 8:08 AM, Serge Wr
I see "amenity:Restaurant" and "amenity:restaurant" are both returned
from the api. And I just discovered that postgres does case-sensitive
LIKE's. Sigh.
Tac
On Wed, May 29, 2013 at 5:35 PM, Martin Koppenhoefer
wrote:
>
>
>
>
> On 29/mag/2013, at 18:01, Eugene Alvin Villar wrote:
>
>> True, b
e most likely
tag (based on taginfo).
Tac
On Wed, May 29, 2013 at 7:23 PM, Serge Wroclawski wrote:
> On Wed, May 29, 2013 at 6:01 PM, Tac Tacelosky wrote:
>> I see "amenity:Restaurant" and "amenity:restaurant" are both returned
>> from the api. And I just discov
to adopt their approach.
Ideally, I'd find a JSON or CSV file with the common tags structured
in a way that maps into more of a category system than a multi-tag
system.
Tac
On Wed, May 29, 2013 at 9:38 PM, Richard Welty wrote:
> On 5/29/13 6:42 PM, Richard Welty wrote:
>>
>> On 5
can do some of the work of identifying
businesses in the photo and their rough locations.
Tac Tacelosky
On Mon, Jun 10, 2013 at 6:03 PM, Bryce Nesbitt wrote:
> I'm interested in revisiting the issue of attaching links to photographs in
> OSM via tag.
>
> There's an ancient
How are your photos geotagged? Is it coded in the EXIF data, or is
there separate metadata? And if so, what kind of data do you have?
We have a photo-based tagging project that doesn't use OSM, but I have
some experience in methods for feature extraction, I'd be happy to
share some of our approa
I've been using our streetviews (customstreetviews.com) to update OSM,
and would like to throw a few ideas out for consideration.
Street-level photos have a lat/long, but that location is not the
location of the item in the photo. Panoramic images, like ours, have
a lat/long of the camera, but wh
13 matches
Mail list logo
