lat and long anomalies about anyway-data-science

[atalyaalon]

@benadikt after a discussion wit Dror - Dror will continue exploring this issue - since it's important to validate the road segments we are counting on.
@benadikt Great work!
@inbalbeka @elashahar01 FYI

[atalyaalon]

@benadikt the identifier of an accident is the three: id, provider_code and year
you won't find such anomalies when using the three as identifier

[atalyaalon]

Also in both involved_markers_hebrew or makers_hebrew you will find longitude and latitude and road_segment_name or road_segment_number - no need to join them

[atalyaalon]

Just to clarify - not all accidents in the same segments need to have the same lon lat - but you can check me on this one and perhaps prove me wrong?

[benadikt]

not all accidents in the same segments need to have the same lon lat

Lets put them on the map one by one and see the anomalies

Also in both involved_markers_hebrew or makers_hebrew you will find longitude and latitude and road_segment_name or road_segment_number - no need to join them

Also taken but because of platform, and the query as been perform not in real time.
there are no significance to join two tables even if not necessity.

https://www.google.com/maps/place/29%C2%B052'50.0%22N+35%C2%B002'41.6%22E/@29.9504694,35.326378,9.5z/data=!4m5!3m4!1s0x0:0x0!8m2!3d29.8805566!4d35.0448942

[atalyaalon]

@benadikt not sure what you mean by that.
If you have a specific example of an anomaly please share, if not I think we can close this issue for now.