Project

General

Profile

Feature #1750

Linking movements with line objects, e.g. roads

Added by Nicholas Melvani 6 months ago. Updated 6 days ago.

Status:
In Progress
Priority:
Normal
Category:
Backend
Target version:
Start date:
2022-06-07
Estimated time:

Description

It would be useful, if one could link a movement event with a specific street (in addition to the already existing "From" and "To" fields), to indicate that a movement followed a known, identifiable route (and not just its starting point and destination).


Related issues

Follows OpenAtlas - Feature #1734: Forms: refactor functionsClosed2022-06-06Actions

History

#1

Updated by Alexander Watzinger 6 months ago

  • Subject changed from Linking movements with streets to Linking movements with line objects, e.g. streets
  • Category set to Backend
  • Status changed from New to Acknowledged
  • Target version set to 7.8.0

Thank you for spotting and reporting this issue. We haven't thought of this before but of course it makes a lot of sense to be able to join e.g. a road, river or similar to a move event.
This should be possible even with our already existing model, nevertheless we will have to spend some thoughts on how to implement it in an intuitive way beside the existing one.

#2

Updated by Alexander Watzinger 5 months ago

  • Subject changed from Linking movements with line objects, e.g. streets to Linking movements with line objects, e.g. roads

I'm not sure how to solve this. E.g. one very "cheap" solution would be to not change anything and decided that for these cases the place is entered in both, the from and to place.
So I put Stefan as watcher and added this issue on the agenda of our next developer meeting.

#3

Updated by Alexander Watzinger 5 months ago

  • Start date changed from 2022-06-15 to 2022-06-07
  • Follows Feature #1734: Forms: refactor functions added
#4

Updated by Alexander Watzinger 18 days ago

  • Status changed from Acknowledged to Assigned
  • Assignee set to Stefan Eichert

Sadly we still haven't a solution for this. But I still would like to implement it so I took the liberty to assign this issue to Stefan, our model master mind, in the hope he has a good idea.
Thanks Stefan in advance, if you can't think of a solution either please note it here or we think about another approach.

#5

Updated by Bernhard Koschiček-Krombholz 13 days ago

  • Target version changed from 7.8.0 to 7.9.0
#6

Updated by Alexander Watzinger 7 days ago

+1

#7

Updated by Stefan Eichert 6 days ago

  • Status changed from Assigned to In Progress

I took a look at it in the CRM. Move works with start and destination, So the range of the movement is e53 Place, which in our case would be documented by a linestring space primitive. As a workaround one could document that both, start and end, are connected with the linestring.
The problem is, that from the linestring alone we cannot extract any direction. If we define the first vertex as start and the last as end, this would give us a direction. However, if movements would also be documented on the same route/linestring for the opposite direction, another identical linestring would be necessary with a reverse order of vertices.

In order to implement this, we need to overwork the concept of linestrings and think of ideas, how to map directions for move events.
I will think of possible solutions and get back to it once we have a feasible concept.

#8

Updated by Alexander Watzinger 6 days ago

Thank you for raising this interesting points and you are absolutely right: of course it wouldn't help if the line object is "directed" because it could be traveled both ways, and/or only part of it.
What about leaving the from and start location as is but also add an "over" location which can be a place (like an in between stop) or a line object e.g. a road or river. This approach would solve most of the issues but question for you would be, if we can map this.

#9

Updated by Stefan Eichert 6 days ago

Alexander Watzinger wrote:

Thank you for raising this interesting points and you are absolutely right: of course it wouldn't help if the line object is "directed" because it could be traveled both ways, and/or only part of it.
What about leaving the from and start location as is but also add an "over" location which can be a place (like an in between stop) or a line object e.g. a road or river. This approach would solve most of the issues but question for you would be, if we can map this.

This would of course work, but there is no CRM property that fits to it. We would probably need to do this outside the model.

Also available in: Atom PDF