Re: [Talk-us] [Imports] [Talk-ca] TIGER considered harmful

2009-11-16 Thread Lord-Castillo, Brett
I'm still getting a handle on the schemas in use for OSM, and noticed that concept of matching address nodes to ways when doing imports. I'm not so sure this will be very functional for floodplain counties or heavy agricultural counties. We have thousands of addresses with no corresponding

Re: [Talk-us] [Imports] [Talk-ca] TIGER considered harmful

2009-11-16 Thread Anthony
On Mon, Nov 16, 2009 at 9:41 AM, Lord-Castillo, Brett blord-casti...@stlouisco.com wrote: I'm still getting a handle on the schemas in use for OSM, and noticed that concept of matching address nodes to ways when doing imports. I'm not so sure this will be very functional for floodplain

Re: [Talk-us] [Imports] [Talk-ca] TIGER considered harmful

2009-11-16 Thread Apollinaris Schoell
On 16 Nov 2009, at 7:40 , Anthony wrote: On Mon, Nov 16, 2009 at 9:41 AM, Lord-Castillo, Brett blord-casti...@stlouisco.com wrote: I'm still getting a handle on the schemas in use for OSM, and noticed that concept of matching address nodes to ways when doing imports. I'm not so sure this

Re: [Talk-us] [Imports] [Talk-ca] TIGER considered harmful

2009-11-16 Thread Anthony
On Mon, Nov 16, 2009 at 12:07 PM, SteveC st...@asklater.com wrote: On Nov 15, 2009, at 8:23 PM, Anthony wrote: On Sun, Nov 15, 2009 at 10:05 PM, SteveC st...@asklater.com wrote: So you put the house numbers on the nodes and then what happens with them all when you switch the way direction?

Re: [Talk-us] [Imports] [Talk-ca] TIGER considered harmful

2009-11-15 Thread Kate Chapman
Dan, What's wrong with doing automated addressing imports in situations where we have point level address data? Or are you just referring to not importing the addressing that is available for the Tiger data? Kate Chapman On Sun, Nov 15, 2009 at 6:00 PM, Dave Hansen d...@sr71.net wrote: On

Re: [Talk-us] [Imports] [Talk-ca] TIGER considered harmful

2009-11-15 Thread Dave Hansen
On Sun, 2009-11-15 at 18:28 -0500, Kate Chapman wrote: Maybe I'm confused about the address versus road information. I would think the address point would be the front door of the building and would not be a relation to the road. So the node of the address and the way of the road would not

Re: [Talk-us] [Imports] [Talk-ca] TIGER considered harmful

2009-11-15 Thread Dave Hansen
On Sun, 2009-11-15 at 18:54 -0500, Anthony wrote: On Sun, Nov 15, 2009 at 6:17 PM, Dave Hansen d...@sr71.net wrote: On Sun, 2009-11-15 at 18:11 -0500, Kate Chapman wrote: What's wrong with doing automated addressing imports in situations where we have point level address data? The issue

Re: [Talk-us] [Imports] [Talk-ca] TIGER considered harmful

2009-11-15 Thread Anthony
On Sun, Nov 15, 2009 at 7:04 PM, Dave Hansen d...@sr71.net wrote: There's nothing wrong with doing point-level address imports.  The only thing I would suggest is ensuring that we connect those points ways or whatever to the roads that represent them somehow. 1) Why? 2) Are you planning on

Re: [Talk-us] [Imports] [Talk-ca] TIGER considered harmful

2009-11-15 Thread John Callahan
For a single county or jurisdiction, if you delete the TIGER data and import more accurate local data, what do you do at the boundaries? County/Stare data sets I've seen usually get cut off +/- a few hundred feet (if that) from the boundary. Does somebody go through and make them

Re: [Talk-us] [Imports] [Talk-ca] TIGER considered harmful

2009-11-15 Thread Dale Puch
Oops hit reply instead of replying to the mailing list :/ I personally favor having the possible address range in the street way segment (between intersections) Easier to edit and maintain, as well as smaller memory and bandwidth when working with it. Split each intersection, then build

Re: [Talk-us] [Imports] [Talk-ca] TIGER considered harmful

2009-11-15 Thread Anthony
On Sun, Nov 15, 2009 at 7:24 PM, Peter Batty peter.ba...@gmail.com wrote: I'm coming a bit late to this debate, but I just wanted to raise a fairly basic question, which is whether the Karlsruhe schema is the best one to use in the situation we find ourselves in with TIGER, where quite a bit of

Re: [Talk-us] [Imports] [Talk-ca] TIGER considered harmful

2009-11-15 Thread Anthony
On Sun, Nov 15, 2009 at 7:47 PM, Dale Puch dale.p...@gmail.com wrote: Split each intersection, then build relations for the streets. Do you even have to split? Just add a node, and put the house number on the node. One of the problems has been which side is left if the way is reversed. Put

Re: [Talk-us] [Imports] [Talk-ca] TIGER considered harmful

2009-11-15 Thread Peter Batty
If you have two streets intersecting and put a number on that node, it isn't clear which street that applies to. You could add an artificial node close to the end of the street, but that seems a bit more messy to me. So my gut feel is that the simplest approach is still attributes on the street.

Re: [Talk-us] [Imports] [Talk-ca] TIGER considered harmful

2009-11-15 Thread Peter Batty
When I said messy, I guess I was thinking of two things - one is doing the import, as you mention here (which is sort of where the discussion started). This seems quite a bit more complex if you have to split ways and insert nodes. The other is in writing a geocoding engine based on the data

Re: [Talk-us] [Imports] [Talk-ca] TIGER considered harmful

2009-11-15 Thread Russ Nelson
Anthony writes: On Sun, Nov 15, 2009 at 7:24 PM, Peter Batty peter.ba...@gmail.com wrote: I'm coming a bit late to this debate, but I just wanted to raise a fairly basic question, which is whether the Karlsruhe schema is the best one to use in the situation we find ourselves in with

Re: [Talk-us] [Imports] [Talk-ca] TIGER considered harmful

2009-11-15 Thread Peter Batty
Russ, I think you misunderstood my comment. I am in the TIGER import is a good thing camp. But in the areas I have worked in it has needed a fair bit of minor positional cleanup. My point is that in those cases where you need to graphically adjust a street, I don't want to have to edit three or