Blocks downtown are not uniformly segmented at 100 addresses per block
Reported by onyxfish | May 7th, 2010 @ 04:43 PM | in Hot demo
E.g. The "100" block of N. State is actually four segments.
According to Joe are in most cases 800 address #'s to a mile in Chicago. I need to summarize groups of line segments and then use the median point for the entire group--OR allow blocks that don't begin at even hundreds.
Idea: Whenever encountering a "block" (n / 100 * 100) which already exists, append the line-segment to the existing one, find the new median, and write both the segment and the new median point back to the database.
Comments and changes to this ticket
-
onyxfish May 7th, 2010 @ 07:13 PM
Possible implementation: put each segment into MultiLineString and then use ST_LineMerge (.merged in GeoDjango) to join them. Does this automagically determine the correct order? What if they are retrieved in non-sequential order? Is the host field currently MultiLineString?
http://docs.djangoproject.com/en/dev/ref/contrib/gis/geos/#multilin...
http://postgis.refractions.net/docs/ST_LineMerge.html -
onyxfish May 7th, 2010 @ 10:39 PM
- State changed from open to resolved
Resolved except for particularly unusual "blocks" which have a forked, divided, or otherwise very un-block-like layout. In these cases it should be extremely unusual to be off by more than 1/8th of a mile, which may be within tolerance. Will open a post-1.0 ticket to follow-up.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A project to create SMS-based infrastructure for low-income areas in Chicago for violence prevention and services dissemination.
People watching this ticket
Referenced by
- 37 Determine if there is a better way to handle forked & divided roads when finding mid-points See #35.