Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

traffic_signals:direction=forward/backward not fixable "online" #360

Closed
RedEmile opened this issue Oct 23, 2018 · 9 comments
Closed

traffic_signals:direction=forward/backward not fixable "online" #360

RedEmile opened this issue Oct 23, 2018 · 9 comments
Labels
enhancement ready

Comments

@RedEmile
Copy link

Hi,
it's not useful to fix_edit any "traffic_signals:direction" online (osmose-editor). You can't decide whether it's "forward" or "backward" without knowing the direction of the OSM-way. For example, in JOSM you need to click on the way to get the direction first before making the decision.

2nd: Is it possible to get a list of all the "traffic_signals:direction" that has been added using the osmose editor (maybe with overpass?)? It would be useful to control whether there are now any wrong "traffic_signals:direction" caused by that problem.
@RedEmile RedEmile changed the title traffic_signals:direction=forward/backward traffic_signals:direction=forward/backward not fixable "online" Oct 23, 2018
@frodrigo
Copy link
Member

The geometry display on marker click was added mainly to address this problem.
But the way geometry is still missing on the kind of issue report.

2/ I think its possible with overpass. I think the number of results object should be very close to 0.

@RedEmile
Copy link
Author

Thanks for responding so quickly!

It's not a problem to have a marker on missing directions on traffic_signals, stop signs, etc. But currently you can't solve that ONLINE correctly. But that is what is suggested by Osmose.
So what I'd suggest: just disable "fixabe=online" in Osmose.

@YaroShkvorets
Copy link
Contributor

Would be great to solve this on frontend, i.e. add an overlay or a tile service that can show way directions. Saves a lot of time adding directions to all those stop signs from osmose rather than josm/id.

@RedEmile
Copy link
Author

@ zzptichka: what you propose would be even better.

frodrigo added a commit to frodrigo/osmose-backend that referenced this issue Nov 3, 2018
@frodrigo
Add way in result of analyser_osmosis_highway_traffic_signals osm-fr#360
982c1b4
jocelynj added a commit that referenced this issue Nov 5, 2018
@jocelynj
Merge remote-tracking branch 'frodrigo/master'
63d5bae 
* frodrigo/master:
  Rename test features to be case independant #246
  Add way in result of analyser_osmosis_highway_traffic_signals #360
  Use ST_Intersect in place of bbxox intersect in analyser_osmosis_double_tagging #379
  Remove duplicate police FR merge analyser
  Fix name of analyser_merge_police_FR_pn
  Docker: postgres tmpfs
  Mapcss code style
  Support driving side in Bicycle.mapcss
  mapcss: support :righthandtraffic
  Docker build better cache usage
  How to debug with docker
  Docker: change Docker default cmd
@frodrigo
Copy link
Member

frodrigo commented Nov 6, 2018

image

@frodrigo frodrigo closed this as completed Nov 6, 2018
@YaroShkvorets
Copy link
Contributor

Is this feature live planet-wide?
For some reason it's still highlighted with red nodein Canada
While appearing properly with green node+way in Belgium for example

@frodrigo
Copy link
Member

frodrigo commented Nov 9, 2018

Yes, it will be available world wide.
In the the popup you can get the date of update. Is not the same for Canada and Belgium.
Actually we are facing to issue and lag on data update. We are encountering problems with with some of the analyser servers.
http://buildbot.osmose.openstreetmap.fr/grid

@matthewdarwin
Copy link

@frodrigo do you need more server capacity? I would like to see canada_* updated more often. I have some spare sever capacity here.

@frodrigo
Copy link
Member

@matthewdarwin one or more vm would help us a lot right now. The minimum configuration per vm is about 4 GB of RAM, 50 GB of hard disk space (ideally ssd, double if possible), 1 cpu core/vm. Thank.

frodrigo added a commit to frodrigo/osmose-backend that referenced this issue Sep 1, 2019
@frodrigo
Avoid duplicate issues in Highway_Lanes osm-fr#360
4c4a296
jocelynj added a commit that referenced this issue Sep 4, 2019
@jocelynj
Merge remote-tracking branch 'frodrigo/master'
29f5019 
* frodrigo/master:
  Fix fallback coord on geocoding fails #591
  Contains in place of Intersects in analyser_osmosis_double_tagging #598
  Avoid duplicate in analyser_merge_geodesie #560
  Avoid duplicate issues in analyser_osmosis_building_overlaps #560
  Avoid duplicate issues in Analyser_Merge #560
  Avoid duplicate issues in Highway_Lanes #360
  Avoid duplicated issues in analyser_osmosis_relation_associatedStreet #560
  Avoid duplicate issues in analyser_osmosis_relation_public_transport #560
  Base subclass on node index #560
  Avoid duplicate error from analyser_osmosis_boundary_intersect #560
  Avoid duplicate issues in analyser_osmosis_powerline #560
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement ready
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@frodrigo @RedEmile @matthewdarwin @YaroShkvorets