Re: [Talk-us] Address placement (was: Fresno castradal imports)
Moving this to a new thread because there is no address data in the Fresno import so this discussion is completely irrelevant. I believe NE2 started a thread about this a while ago and there wasn't too much response but since it came up again... On Fri, May 4, 2012 at 2:51 PM, Paul Johnson wrote: > On Fri, May 4, 2012 at 12:47 PM, Ian Dees wrote: > >> Because that information is useless in OSM. It was out of date the second >> someone ran the upload script and unless the city of Fresno decides to >> switch to OSM for their official tax plat information (which I'm pretty sure >> would be illegal in most jurisdictions), no one in the community can improve >> it. We should get rid of it. > > Property lines are still observable phenomenon, though. Depending on > jurisdiction, it might require surveying from the nearest benchmark, > but in many cases, there's markers embedded in the nearest curb or > other devices indicating the most recent plot boundary. > >> I mentioned the address nodes because it would be the only useful data to >> keep in OSM. As Toby mentioned, there's no such data. > > Though the address belongs to an area, so it would make sense to keep > the corresponding boundary. Does it? Certainly for official records such as taxes it does. But this is outside of OSM's domain. In OSM, the use case for address data is geocoding and I would argue that general use geocoding users would rather get a building outline or even a node at the main entrance of a location, not the centroid of the property. In Fresno this may be pretty much the same thing but in less populated areas, the plot might be rather large and you would definitely want the address data to be where the actual residence is. Toby ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Address placement (was: Fresno castradal imports)
Hiya, On Fri, May 4, 2012 at 2:17 PM, Toby Murray wrote: > [..] > Though the address belongs to an area, so it would make sense to keep > > the corresponding boundary. > > Does it? Certainly for official records such as taxes it does. But > this is outside of OSM's domain. > Certainly. An address in OSM is a node. If you must, add it to a building so a user can derive a centroid, but a building centroid can still be wildly inaccurate for address level geocoding. > > In OSM, the use case for address data is geocoding and I would argue > that general use geocoding users would rather get a building outline > or even a node at the main entrance of a location, not the centroid of > the property. In Fresno this may be pretty much the same thing but in > less populated areas, the plot might be rather large and you would > definitely want the address data to be where the actual residence is. > Agreed. What you want is the main entrance to the building. Second best is building centroid, worst is parcel centroid. The thing is, when you offer address level geocoding, you suggest a level of accuracy that you can't offer when you resort to centroids. -- martijn van exel geospatial omnivore 1109 1st ave #2 salt lake city, ut 84103 801-550-5815 http://oegeo.wordpress.com ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Address placement (was: Fresno castradal imports)
On Fri, May 4, 2012 at 1:17 PM, Toby Murray wrote: > In OSM, the use case for address data is geocoding and I would argue > that general use geocoding users would rather get a building outline > or even a node at the main entrance of a location, not the centroid of > the property. How are these mutually exclusive, exactly? ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Address placement (was: Fresno castradal imports)
> -Original Message- > From: Toby Murray [mailto:toby.mur...@gmail.com] > Sent: Friday, May 04, 2012 1:18 PM > To: OpenStreetMap talk-us list > Subject: Re: [Talk-us] Address placement (was: Fresno castradal imports) > > Moving this to a new thread because there is no address data in the > Fresno import so this discussion is completely irrelevant. > > I believe NE2 started a thread about this a while ago and there wasn't > too much response but since it came up again... > > > On Fri, May 4, 2012 at 2:51 PM, Paul Johnson > wrote: > > On Fri, May 4, 2012 at 12:47 PM, Ian Dees wrote: > > > >> Because that information is useless in OSM. It was out of date the > >> second someone ran the upload script and unless the city of Fresno > >> decides to switch to OSM for their official tax plat information > >> (which I'm pretty sure would be illegal in most jurisdictions), no > >> one in the community can improve it. We should get rid of it. > > > > Property lines are still observable phenomenon, though. Depending on > > jurisdiction, it might require surveying from the nearest benchmark, > > but in many cases, there's markers embedded in the nearest curb or > > other devices indicating the most recent plot boundary. > > > >> I mentioned the address nodes because it would be the only useful > >> data to keep in OSM. As Toby mentioned, there's no such data. > > > > Though the address belongs to an area, so it would make sense to keep > > the corresponding boundary. > > Does it? Certainly for official records such as taxes it does. But this > is outside of OSM's domain. > > In OSM, the use case for address data is geocoding and I would argue > that general use geocoding users would rather get a building outline or > even a node at the main entrance of a location, not the centroid of the > property. In Fresno this may be pretty much the same thing but in less > populated areas, the plot might be rather large and you would definitely > want the address data to be where the actual residence is. There isn't a one-to-one relationship between addresses and lots. Strip malls both here and in the US will sometimes have an entirely different address (not just suite number) for each store even though they may be on one lot. Similarly you can get multiple buildings on one lot with different addresses. I have seen this both here and with some US data. These exceptions are less common for residential areas but you still see some. ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us