Recently the Ministry of Transport has released a complete set of GTFS data for public transport in Israel. http://tinyurl.com/chhb6wn
From this data we could:
Add (via a script) a complete set of bus stops with names in Israel
Based on the stop names, add (manually) street/road names and addresses in less-mapped areas that are currently missing names/addresses
Add (manually I believe) bus route relations throughout Israel
There are two possible issues:
A) Legal: The data is obviously intended for public use, but maybe it does not meet exact requirements for OSM. If so, we might have to ask directly for permission to use it here.
B) Technical: somebody would have to write the import script(s).
Does anyone have ideas where to get started on A) or B)?
According to http://code.google.com/p/gtfs-osm-sync/, it in the transport agency’s best interest to do the synchronization, and therefore it should be their job. Since I do not see that happening on its own, it’s our job to get the ball rolling. The project page says that “it’s highly recommended that GO_Sync users understand OpenStreetMap well and let other OpenStreetMap users know a big change is coming BEFORE any upload/revert.” If you need help with using GO_Sync, ask here and I will try to do my best (I do not know much more about it than you do, but we can learn together).
I uploaded the data manually (using a modified version of csv2osm.pl and then JOSM).
I never knew how many stops there were. Blue dots all over the map. It seems that in some cases there are duplicates near each other, perhaps placed by different bus companies. Questionable whether we should edit/delete in that case.
The accuracy appears good - in most places I looked, there was <5m deviation from the roads as we mapped them.
I made a couple partially successful upload attempts before the final successful one. If anyone can delete these without affecting the successful changeset, that wouldn’t hurt. Keep in mind that the original dataset includes 241 (IIRC) duplicates and perhaps this was intentional, to represent multiple adjacent stops (opposite directions?) or something similar.
The next task, for those who choose to accept it, is to give names to currently unnamed streets/places based on the name of the stop adjacent to them.
I think very few of the manually added stops have any useful information other than the location. So I would recommend deleting them (manually after being checked, not by a script), and if necessary moving the GTFS stops to the location of the old manual stop. The GTFS stops include information, like the official stop name and reference number, which is potentially very valuable if coordinated with other data (for example, the route database).
As for GTFS location accuracy - the first few stops I looked at appeared very accurate. But since then I have seen less accurate ones, particularly outside urban areas. And the fact that there are often stops with identical names a significant distance away from each other implies that the accuracy may not be so high. Of course, manually entered stops can also inaccurate. So I don’t know.
just checked the import and its amazing detailed.
Several street names could be fetched from this import.
Can be very very helpful in the future.
Great you found the time to do the job.
Beside that we should import more value from the data we got:
For example the bus numbers that are stopping on each stop.
And also the name of the bus company taking care of the stop.
Also the route ID could be from interest. Those kind of information are in the Israeli public data and we should really use them.
Currently I will not be able to create a bus route with the data we imported.
Its simply missing more information.
We should consider getting more data into OSM.
Is that possible somehow?
I just added (upload in progress) fixme tag for all (33051) imported bus stops.
Now, each time we see bus stop with fixme tag, we can check it, move it and/or merge it with existing one… until all stops will be approved.
We have a problem if we merge the bus stops. We would loose the “ref” number what will cause a overlapping for the next import.
We should not touch the location at the moment as we will have to import it again in the future.
Mr_Israel, no, we must only merge imported with existing and never two stops with different refs.
By the way, I see many stops which isn’t exists at all. It’s not a good idea to show them on the map and we need to find any solution to leave them in db but not show on rendering. maybe we can mark them as construction or proposed.
I simply don’t want to loose any kind of information.
I’m expecting that they will fix the GTFS data in the future as it is currently not usefull for Google I think.
It would also mean for Google to have bus stops all over the street without marking the exact bus stop position.