Because I'm better.Why can't you just get everybody a Garmin?Yes, lengths and address ranges Differ for various reasons. I just split some segments due to changes in speed limits.I'm Geogeek Happy!
I've been writing a script that matches an road segment ID to an address, based on the road segment's address range (if the address is 123 Main Street, then get the segment for 100 - 199 main Street and write the segment ID to the address point.) The problem I've been battling is how to filter the address points to just those matching the road name; there are about 390,000 addresses and 44,000 road segments. No matter how I try to code the filter I keep getting an error.
Yesterday afternoon I finally found a little piece of code (three lines) that sets up the filter. I cant just say x = y, but have to build a line of text referencing x and y individually. Everything went well (several times) with my test date (about 1,000 streets and 3,000 addresses). Today, I added code that will check for the required fields, and if they don't exist in the files, the fields are added. it went well with the test data, and now I'm running it against a copy of the production files. So far, so good.
This is related to the next generation 9-1-1 (NextGen) stuff that is very rapidly coming to life, but has some other applications where we might need to associate an address point (a main door) with the section of road (like a section between two intersections).
How to cope with the variation in density?
Do the road sections have different lengths that correspond to the address density variation?
Gary doesn't know about that ... Mr. Garmin had that figured out years ago.Because I'm better.Why can't you just get everybody a Garmin?Yes, lengths and address ranges Differ for various reasons. I just split some segments due to changes in speed limits.I'm Geogeek Happy!
I've been writing a script that matches an road segment ID to an address, based on the road segment's address range (if the address is 123 Main Street, then get the segment for 100 - 199 main Street and write the segment ID to the address point.) The problem I've been battling is how to filter the address points to just those matching the road name; there are about 390,000 addresses and 44,000 road segments. No matter how I try to code the filter I keep getting an error.
Yesterday afternoon I finally found a little piece of code (three lines) that sets up the filter. I cant just say x = y, but have to build a line of text referencing x and y individually. Everything went well (several times) with my test date (about 1,000 streets and 3,000 addresses). Today, I added code that will check for the required fields, and if they don't exist in the files, the fields are added. it went well with the test data, and now I'm running it against a copy of the production files. So far, so good.
This is related to the next generation 9-1-1 (NextGen) stuff that is very rapidly coming to life, but has some other applications where we might need to associate an address point (a main door) with the section of road (like a section between two intersections).
How to cope with the variation in density?
Do the road sections have different lengths that correspond to the address density variation?
You are the first one there - you should be a key holder.
But you'll have to get in the smile box. Punch some holes so you can breathe.
The wife made beef stew yesterday and forgot to add the beef....I called it vegetable poo, she thought it was funny.
Create an account or login to comment
You must be a member in order to leave a comment
Create account
Create an account on our community. It's easy!
Log in
Already have an account? Log in here.
