localid=0

2 views
Skip to first unread message

Michael Arnold

unread,
Mar 10, 2014, 7:39:00 PM3/10/14
to OregonWalk...@googlegroups.com

localid is the key into the RLIS street data.  

So I was surprised to find 2408 data segments with localid set to 0.
Turns out these are the YamHill county part of the data, and are further coded with type=8224="unknown type Yamhill Co. only"

I am currently ignoring these segments when generating the merged networks.  I doubt this is a problem:  there is only a small overlap between this data and the OSM coverage area I am currently using (in the far South West)  If this does becomes a problem we will need to augment id keys for the RLIS data in some way.

Michael.

PS  The RLIS data source I used:

Cone, Paul

unread,
Mar 10, 2014, 7:49:36 PM3/10/14
to OregonWalk...@googlegroups.com
Yes trantype 8224 is Yamhill County only.  There is also Columbia County data out there someplace.


From: OregonWalk...@googlegroups.com [mailto:OregonWalk...@googlegroups.com] On Behalf Of Michael Arnold
Sent: Monday, March 10, 2014 4:39 PM
To: OregonWalk...@googlegroups.com
Subject: Oregon Walks GIS Jam:: localid=0

--
You received this message because you are subscribed to the Google Groups "Oregon Walks GIS Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to OregonWalksGISJa...@googlegroups.com.
To post to this group, send email to OregonWalk...@googlegroups.com.
Visit this group at http://groups.google.com/group/OregonWalksGISJammers.
For more options, visit https://groups.google.com/d/optout.

Scott Parker

unread,
Mar 11, 2014, 12:59:25 PM3/11/14
to OregonWalk...@googlegroups.com
Documented, stable, and unique object IDs become even more important with open government data.  There will be people and organizations attaching valuable data and valuable analysis to thes IDs.  A little thought and a little work like Michael is doing will make this data more useful for all potential users.
 
Scott

Cone, Paul

unread,
Mar 11, 2014, 1:39:12 PM3/11/14
to OregonWalk...@googlegroups.com
I hope they don't get too attached, because I edit and split them all the time, and that creates new IDs.


From: OregonWalk...@googlegroups.com [mailto:OregonWalk...@googlegroups.com] On Behalf Of Scott Parker
Sent: Tuesday, March 11, 2014 9:59 AM

Michael Arnold

unread,
Mar 11, 2014, 2:20:12 PM3/11/14
to OregonWalk...@googlegroups.com
My matching code can help here:  data correspondence can be reestablished in the face of changing ids.

Scott Parker

unread,
Mar 11, 2014, 1:44:13 PM3/11/14
to OregonWalk...@googlegroups.com
You may want to consider creating a registry of users with notification of changes.

Cone, Paul

unread,
Mar 11, 2014, 3:33:54 PM3/11/14
to OregonWalk...@googlegroups.com
From: OregonWalk...@googlegroups.com [mailto:OregonWalk...@googlegroups.com] On Behalf Of Scott Parker
Sent: Tuesday, March 11, 2014 10:44 AM

Scott Parker

unread,
Mar 12, 2014, 12:11:03 AM3/12/14
to OregonWalk...@googlegroups.com
Nice.  We should examine this before a walkway network update.  It would also be a good test of Michael's program to see if it finds changes to geometry or name.
 
What about that bit of cut through street by the Oregon Walks office at the east end of the Broadway Bridge?

Cone, Paul

unread,
Mar 12, 2014, 1:44:37 PM3/12/14
to OregonWalk...@googlegroups.com
I'm still trying to figure out what to call it.  Is it part of N BROADWAY, or is it a ramp?


From: OregonWalk...@googlegroups.com [mailto:OregonWalk...@googlegroups.com] On Behalf Of Scott Parker
Sent: Tuesday, March 11, 2014 9:11 PM
Reply all
Reply to author
Forward
0 new messages