[Imports] Bicycle parking shapefile

[Sam Vekemans]

hi,
cool, can you convert the file to . osm format and make it availabe to look at?
we wont copy it into osm, but we'd like to see it.
its local mappers who will copy it in anyway.

also, if you can make a wiki page showing the details of the data, and
the tags used, and available, this will help.  also, include a copy of
an email confirmation that says you can use the data.
this will also help a great deal.

cheers,
sam

On 7/22/10, Toby Murray <toby.murray at gmail.com> wrote:
> I've been working with a new local mapper on bicycle related things
> recently. He talked to someone in the city government and got them to
> donate a shapefile for use in OSM. This file contains pretty much
> every bicycle rack in the city - 595 objects. Since I am the only one
> who has mapped any bicycle racks in this city and the new data is more
> complete and more detailed than I have done, I think this import
> should largely replace my existing work. I think there are only a
> couple of brand new racks that I have mapped that aren't in this
> shapefile yet. They actually went kind of overboard and tagged each
> and every individual rack, even when there are 10 or 15 of them in a
> single big bicycle parking area so I will probably combine some of
> them into single nodes in OSM to reduce clutter, while adding up their
> capacity values.
>
> This is my first OSM import so I thought I would get some advice. At
> first I was having projection problems but someone on IRC helped me
> sort that out. Now I am looking at the data and wondering what
> attributes I should keep, adapt or throw away when importing into OSM.
>
> The shapefile has the following attributes for every bicycle rack:
> - ID
> - Capacity
> - Style
> - Condition
> - Owner
> - Security
> - Locking
> - Weather_protected
> - Notes
>
> Obviously the capacity attribute maps nicely to the capacity tag in
> OSM. And I think weather_protected can be converted to the
> covered=yes/no tag mentioned on the amenity=bicycle_parking wiki page.
>
> The other tags I'm not as sure about. Owner can probably map to
> access=* because its values indicate if it is owned by the city
> (public access) the university (bicycle registration technically
> required but not enforced) or "Private" indicating bicycle racks in
> apartment complexes intended for residents or at businesses, intended
> for customers.
>
> Style contains information about the physical construction of the
> rack. Values include: Ring, Wave, J, Post, Hump and a few others. This
> will probably never be rendered but seems kind of interesting. Should
> I leave it as a "style" tag or "type" or something similar?
>
> Condition is kind of a temporal value that may change from year to
> year so I am leaning towards not including that one.
>
> Security seems to indicate whether the rack is secured to the ground
> or a structure or is just free standing. Values are "Not Secure"
> "Permanent" and "Temporary"
>
> Locking indicates how bicycles can be locked to the rack. "Wheel"
> "Frame" and "Both"
>
> Notes is kind of haphazard. Most of the time it contains additional
> hints as to the location such as the name of the campus building or
> business it is adjacent to. Sometimes it contains more information
> about the condition like "needs painting." I could see just leaving
> that as a note=* tag.
>
> Suggestions/comments?
>
> Toby
>
> _______________________________________________
> Imports mailing list
> Imports at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/imports
>


-- 
Twitter: @Acrosscanada
Blogs: http://acrosscanadatrails.posterous.com/
http://Acrosscanadatrails.blogspot.com
Facebook: http://www.facebook.com/sam.vekemans
Skype: samvekemans
IRC: irc://irc.oftc.net #osm-ca Canadian OSM channel (an open chat room)
@Acrosscanadatrails