You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 12, 2022. It is now read-only.
This seems to be the case. I will delete the intersections branch. If I want to get cross street information, I will have to use GIS functions to get some sort of "nearest neighbour". If I'm lucky, the (x,y) of one segment may match exactly the (x,y) of another segment.
Not sure how I'm supposed to import the intersection data from the city's opendata site:
http://www1.toronto.ca/wps/portal/contentonly?vgnextoid=e659522373c20410VgnVCM10000071d60f89RCRD&vgnextchannel=1a66e03bb8d1e310VgnVCM10000071d60f89RCRD
I expected that the intersection table would look like this:
But instead, it's basically a duplicate of the existing bikeway data:
The only difference appears to be the existence of the fields
fcode
andfcode_desc
(which I believe I deliberately omitted from the bikeways).None of the city's
geoid
,rid
,object_id
, etc. match up on either table.It's almost less than useless. Mainly because there doesn't appear to be any cross street information.
At this point I don't see any difference between the
intersection
andbikeway_segment
tables.The text was updated successfully, but these errors were encountered: