cyclofix-website's People
Forkers
comradekingucyclofix-website's Issues
Deploy on cyclofix.bike.brussels
Wrong title
The website has:
Cyclofix map
For more information about the cyclofix project, go to cyclofix.osm.be.On this map, you can see, edit and add points of interest. Zoom around to see the POI ...
Which according to what I can find elsewhere should be "CycloFix".
differentiating between "shop=bicycle" and "amenity=bicycle_rental"
I have been looking for something like Cyclofix for a long time to allow people to easily (1) document/map free cycling repair services in the city of Montreal (Canada) and (2) view nearby cycling services when in an emergency!
Cyclofix does all this very well. I had some questions on the mapping controls and symbology, though.
What is the difference between the red shop symbol and the black shop symbol?
They both seem to have very similar attributes, though the dark symbols tend to have more of them... This brings me to my next point: bicycle rental services (amenity=bicycle_rental
), which are also symbolized in red
This generates much confusion (when using the map in several cities) between bicycle repair shops/boutiques and outdoor municipal rental stations like Bixi (Montreal), Citi bike (NYC), Divvy bikes (Chicago), etc. Unfortunately many OSM users map these dock locations, even though coverage is inconsistent and the dock locations change seasonally...
Would it be possible to have a separate category in the legend for bike rental nodes? This would make the map much more useful, I think, for users to quickly locate repair services as opposed to more common bike rental stations!
Thanks!
Write to all bicycle shops and ask them to review and improve their data
And perhaps also ask "what else would you like us to show about cycle shops?"
add-image-only mode
User story:
- I am somewhere
- I see something fun
- but there is no suitable mapcomplete instance
- so I go to the mapcomplete-image-add-machine
- I say "I am here" and it just returns all OSM data within a 10 meter radius
- I click on the thingy I want to add a picture for and I add my picture
Follow up on Vorst
Municipality of Vorst/Forest sent us the following email which we totally ignored afterwards:
Bonjour,
Toutes les données relatives à nos stationnements sécurisés pour vélo ainsi que les pompes et stations de réparation se trouvent sur notre site internet (via une carte google ). Nous mettons les données à jour sur cette carte dès qu’il y a de nouvelles installations.
N’hésitez pas à me contacter si vous avez d’autres questions.
Cordialement, Sarah GREGOIRE
Service mobilité - Mobiliteitsdienst
[email protected]
new icon for service:bicycle:second_hand=only
Rather than service:bicycle:retail=yes
and service:bicycle:second_hand=yes
being related to new and used bike selling respectively, service:bicycle:retail=yes
seems to be an all-encompassing tag for any shop selling any kind of bicycle, and service:bicycle:second_hand=only
is needed to specify that in fact the shop only sells second-hand bikes, and not new bikes.
In my option, one should not relate to the other, and something like service:bicycle:retail_new=yes/no
and service:bicycle:retail_second_hand=yes/no
would be more appropriate, and would translate into statements like this store sells new bikes and this store doesn't sell used bikes for example.
But that's beside the point. Given the way things are, I am wondering if nodes in Cyclofix with service:bicycle:second_hand=only
can have a different icon from the one currently used for any shop that sells bicycles.
What is now this:
Could look like this:
I'm aware it's a very picky and low-priority detail, but it really is a key question that many people have when asking about bike shops, and would help if viewed directly on the map!
updated links to docs not reflected on website
These changes 84c7b41
Are not visible on https://cyclofix.osm.be/docs/using-data-map/
Quest: glass containers
In municipalities where there is no garbage collection of glass, it's really useful to know where they are, and information tends to be scattered!
Longlist data to add
Icon needed:
- cycle transport office (like "freight company", but with bike)
- bike cafés https://github.com/osmbe/cyclofix-docs/issues/10#issuecomment-664247954
- bicycle advocacy office (e.g. https://www.provelo.org/en ; https://ecf.com/ )
https://github.com/osmbe/cyclofix-docs/issues/10#issuecomment-664251076 , bike tours and clubs (eg http://kring.cc/) https://github.com/osmbe/cyclofix-docs/issues/10#issuecomment-664251076
Just extend query:
- buy a second hand bike https://github.com/osmbe/cyclofix-docs/issues/10#issuecomment-664248990
- fix your own bike https://github.com/osmbe/cyclofix-docs/issues/10#issuecomment-664246084
- rent a bike https://github.com/osmbe/cyclofix-docs/issues/10#issuecomment-664251895
Ignore for now
-
public bicycle charging stations (apparently lidl bxl and ikea anderlecht) -
traffic lights (exception for cyclists)
-
parking (paid/premium)
-
cycle lanes
-
in MVP: category 'other' and 'other places with pumps' > should we specify these more?
add layer icons to legend
A good UI consideration
Subscribe to certain map changes
Question from cyclo
First thought: IFTTT, but not diretcly linkeable from Overpass
Not available in the default RSS services
Found this: https://wiki.openstreetmap.org/wiki/Osm-watch (after googling overpass + rss) , but it's dead
Relevant query: http://overpass-turbo.eu/s/WAX
Relevant CSV query: http://overpass-turbo.eu/s/WAY
Consider using cyclosm for cycle related maps
Instead of default OpenStreetMap.org style.
The main cyclosm style might be too "strong", but there's also a "softened" style
Data model for cycle related services
Services need to be separate from features
Most cycle related services can exist on things like:
tag | description |
---|---|
shop=bicycle + !service:bicycle:retail=no | a cycle shop |
shop=bicycle + service:bicycle:retail=no | a place with some other cycle services, e.g. a bicycle repair shop |
shop=* + cycle service | a shop also doing something with bikes (e.g. Decathlon) |
amenity=compressed_air | a pump (usually for cars) |
amenity=bicycle_repair_station | a DIY station OR just a pump |
amenity=community_centre (or similar) + [some cycle service] | bicycle kitchen/ bicycle cooperative (bike focused NGO, or NGO with bike playthingies) |
amenity=cafe (or similar) with some cycle ervices | a bicycle café |
? | bicycle library (non-profit cycle rental) |
amenity=bicycle_rental + !network=* | bicycle rental place |
amenity=bicycle_rental + network=* | bicycle rental network |
For example: a shop like Decathlon "also sells bikes". We can SHOW them on the map, BUT it's rather hard to show ALL potential places where this could be the case.
We want to first focus on places specifically oriented to cyclists, so we'll ignore this for now.
Documentation Proposal:
Document the services on a separate wiki page
Define the services in such a way that they are universally applicable
Create consistency by default between the key "second_hand" and the key "service:bicycle:second_hand" in all these cases
tagging table
https://wiki.openstreetmap.org/wiki/Tag:shop%3Dbicycle#Additional_keys
Use with:
tag | description | use with | alternatives | Question for app |
---|---|---|---|---|
service:bicycle:retail=yes |
Do they sell bikes here? | "YES" on Anything that is NOT a bike shop, like a marketplace or sports shop that happen to sell bikes. In theory, a shop=bicycle might NOT sell bicycles, but that is kind of not the point | none | Not applicable - but we might use it to filter possibly interesting stuff! |
service:bicycle:second_hand= yes/only |
Do they sell second hand bikes? "no" is assumed, but if people say no we add it to the database | any shop/social service | You could also use second_hand , however, that would break with a shop=sports |
Do they sell second hand bikes? |
service:bicycle:repair= yes/only_sold/brand/only |
Are there repair services available? | any shop/social service | repair , but that could break complicated POIs |
Can I get my bike fixed here? Yes / Yes, but only if you bought it here / Yes, but only if it's a brand they sell / No |
service:bicycle:diy= yes/no |
Can I repair my bike here? | any shop/social service. NOT on a repair station, as that is DIY by default | none | Only on bicycle shops: "Can I fix my bike here by myself?" |
service:bicycle:rental= yes/no |
Can I rent a bike here? | shops that don't only rent bikes. If used on a community_centre or the like, a "cycle library" is implied | amenity=bicycle_rental but that is (mostly) for cycle networks (Villo, Blue Bike). Use network to filter those out |
|
service:bicycle:pump= yes |
there is a free bicycle pump which can be used by anybody (it is not restricted to customers) | any feature that offers compressed air, if the air is specifically meant for cyclists. Add details as in amenity=compressed_air | Yes, as a separate feature | Can anyone come in to use a cycle pump for free? yes / no / yes, but it's actually outside [in this last case, give instruction to please add a new separate pump outside] |
Specifically for cycle pumps
- we will show everything with the tag
service:bicycle:pump=yes
- for independent pumps, we will use
amenity=bicycle_repair_station + service:bicycle:pump=yes/no
- for pumps offered at other places
service:bicycle:pump=yes
indicates that "has a free bicycle pump which can be used by anybody" (already like this on the wiki)
So we need three different icons?
- an independent pump (amenity=bicycle_repair_station + service:bicycle:pump=yes + [no other service:bicycle:* tags)
- a repair station with a pump (amenity=bicycle_repair_station + service:bicycle:pump=yes + [one or more other service:bicycle:* tags)
- another feature (most like a shop) with a free pump ( !amenity=bicycle_repair_station+ service:bicycle:pump=yes). This includes
amenity=compressed_air
that has been explicitely marked as oriented to cyclists)
Reasoning for independent pumps:
Option 1)
amenity=bicycle_repair_station service:bicycle:pump=yes/no
downside: this is a little weird, as there is no "real" repair station**
but: a repair station with just this one service is relatively un-ambigious
Option 2)
amenity=compressed_air
+ some clarifying tag
downside: it's hard to filter those meant for bicycles (there is more than one option to indicate this) and it makes it very hard for car-oriented data-users to filter away those NOT meant for cars
Option 3)
a totally new and better tag
downside: might still prove to be imperfect; introduces Yet Another Standard; does not solve the problem of this being both a separate feature and an attribute of another feature
We will re-use the subtags manometer
and valves
as described on https://wiki.openstreetmap.org/wiki/Tag:amenity%3Dcompressed_air. To avoid inventing yet another tag, we will simply use them in combination with service:bicycle:pump and not make, for example, a service:bicycle:pump:valve
s tag. We don't see a case where using the original tags could cause confusion.
tag | use | Question for app |
---|---|---|
manometer=yes/no |
Is there a pressure indicator / drukmeter, manometer / gauge de pression? | Is there a pressure indicator? |
valves=*;* |
Which type of valve is available? Common values: sclaverand; dunlop; schrader; regina | Show a picture of the common situation with a double valve and two types of cycle tires and ask "Does it look like this?". If yes, write valves=sclaverand;schrader. If no: add a description or ask to make sure the valve is visible in their picture of the pump |
operator=[free text] |
Who owns/operates the object? | Lets NOT ask in the Mapathon, but ask the owners to add this! |
opening_hours |
when is it available | When can I use it? (details below) |
For opening hours:
We won't actually add opening_hours now, as the tool is not ready for that!
If it's outdoors: we assume the value is always 24/7
but that's a default, so not needed. There are very rare exceptions possible (e.g. in a park that closes for the night), but we don't think this is worth adding in the tool.
However, for outdoor pumps operated by shops, it's common that they are put inside when the shop closes.
App behaviour for cycle shops:
- Is there a cycle pump that's available for everyone?
No>stop
Yes > Is it inside the shop or outdoors?
--- indoors > addservice:bicycle:pump=yes
to the shop
--- outdoors > return text message "please add a cycle pump outdoors after you finish with the shop", possibly addservice:bicycle:pump=separate
to the shop?
Now when you add a pump, we need to ask:
"Does this pump belong to a shop?"
no > stop
yes > What is the name of that shop? fill in "operator" with name of that shop [if at all possible: use nearby shop name info as name suggestion]
--- ASK "Is this pump only available when the shop is open?"
if YES: opening_hours=linked
(on the compressed_air wiki but otherwise undocumented it seems)
if NO: opening_hours=24/7
Things to think about
- TAGGING: Further detail for DIY could be "yes, and there's someone around to give help". But we'd prefer to keep it simple and ignore this
- TECHNICAL: Say people want to add a more exotic cycle service, for example at a community_centre. This will probably create duplicate POI. That's OK, we just need a good way to filter them out and have us fix them!
- TECHNICAL: Any object that has a
service:bicycle:*
tag, is probably useful to add more questions about - CONTENT: there's also
service:bicycle:cleaning
, but that doesn't seem very useful
Translation to MapComplete / Cyclo-map
This tagging style makes it easy to make filters in this kind of logic:
https://www.google.com/maps/d/u/0/viewer?mid=1bqgaLUFTxFpbbJW-tvqwNjYpS_OvPJIV&ll=50.86343420000001%2C4.3494730000000015&z=11
It makes it harder to translate to MapComplete logic
For the Mapathon, let's focus on:
a) adding new features
- find a service station thing / independent pump
- find a cycle shop / rental shop
b) enriching existing features
- show things with a service:bicycle:* tag
- show things that are shop=bicycle
So we only need these layers:
- real DIY service station
- cycle shop
- bike pump
- other places with a pump
- bicycle parking (?)
- other places with other cycle services (excluding cycle rental networks)
location not requested (permanently disabled) on Android, all browsers
This issue seems to affect https://cyclofix.osm.be/map/, whereas https://pietervdvn.github.io/mc/develop/cyclofix.html seems to work fine.
Should users use https://pietervdvn.github.io/mc/develop/cyclofix.html ? Given that location can be stored in the url on this instance, and the app can request users' loc on mobile, it seems more useful to those outside of Brussels! The project page and Github docs might want to reflect this (point to the Github pages link, or update https://cyclofix.osm.be/map/)
Thanks!
pump icon > title is 'bike station'
Add a link to https://cyclofix.osm.be/ in the intro of the map
So a backlink to https://cyclofix.osm.be/
From https://pietervdvn.github.io/MapComplete/index.html?layout=cyclofix
Write about how to extract "places that sell bikes" and ask OpenData Brussels to use it
Data not loading
save url parameters when saved to PWA/home screen (Android)
Would it be possible to save parameters set in the url to the PWA installed by users on their phones (when a user adds the website to their homescreen) ?
Sharing a specific URL containing loc, legend items, lang settings works great, but users lose this customization once saved to their phones or computers (oddly though, the lang setting seems to be retained, in my case).
It seems that other users (the Brussels example) get past this by putting cyclofix into an iframe containing these customizations. Is this the way I should proceed ?
Add bicycle libraries
These are NGO-type places that offer log-term cycle rental.
See https://en.wikipedia.org/wiki/Bicycle_library
No tagging scheme available, no existing data either.
Suggested tagging:
main tag, if none available:
- standalone:
amenity=bicycle_library
(ideal if a small private initiaitve - you don't want to show them as a community centre or bicycle shop on the general maps!) - if part of a larger object, for example
amenity=community_centre
orshop=bicycle
(+ add lack of sales of cycles though)n then add subtagservice:bicycle:rental=bicycle_library
orservice:bicycle:rental=library
Relevant links:
http://fietsbieb.be/west-vlaanderen/over-fietsbieb/uitleenpunten/
https://www.fietsbieblimburg.be/
https://ruraalnetwerk.be/projecten/fietsbibliotheek
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.