Skip to content
This repository has been archived by the owner on Dec 12, 2022. It is now read-only.

Importing intersection data - how? #10

Closed
jbinto opened this issue Jun 5, 2014 · 1 comment
Closed

Importing intersection data - how? #10

jbinto opened this issue Jun 5, 2014 · 1 comment
Labels

Comments

@jbinto
Copy link
Owner

jbinto commented Jun 5, 2014

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:

  • Intersection_ID
  • Cross_street_1
  • Cross_street_2
  • Geometry (point)

But instead, it's basically a duplicate of the existing bikeway data:

image

The only difference appears to be the existence of the fields fcode and fcode_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 and bikeway_segment tables.

@jbinto jbinto added the question label Jun 5, 2014
@jbinto
Copy link
Owner Author

jbinto commented Sep 20, 2014

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.

@jbinto jbinto closed this as completed Sep 20, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant