Re: [Talk-us] parcel data in OSM

2012-12-30 Thread Frederik Ramm
Hi, On 30.12.2012 04:23, Michael Patrick wrote: The point being, is that every locale is going to have features (and combinations of features) to give contest to some user's activity or use. And for that individual or community of users, if that feature(s) can't be added or isn't present, the

Re: [Talk-us] parcel data in OSM

2012-12-30 Thread Serge Wroclawski
On Sun, Dec 30, 2012 at 6:15 AM, Frederik Ramm frede...@remote.org wrote: If, on the other hand, these low and high water lines are defined/recorded elsewhere (probably even in a legally binding form if they are relevant to some statue), and the only reason you want them in OSM is because you

Re: [Talk-us] parcel data in OSM

2012-12-30 Thread Jason Remillard
Hi, On Sun, Dec 30, 2012 at 11:09 AM, Serge Wroclawski emac...@gmail.com wrote: OSM is not data repository, it's a dataset onto itself. Through years of experience, and trial and error, we have found that importing these external datasets does not help the project in most cases. Therefore we

Re: [Talk-us] parcel data in OSM

2012-12-30 Thread Ian Dees
On Sun, Dec 30, 2012 at 5:51 PM, Jason Remillard remillard.ja...@gmail.comwrote: Hi, On Sun, Dec 30, 2012 at 11:09 AM, Serge Wroclawski emac...@gmail.com wrote: OSM is not data repository, it's a dataset onto itself. Through years of experience, and trial and error, we have found that

Re: [Talk-us] parcel data in OSM

2012-12-30 Thread Jeff Meyer
I am very sympathetic to what I sense to be Jason's (and Michael's and others') frustrations. It's quite clear there are a *very* large number of imports that have contributed to the body of data that is OSM (Incomplete list here: http://wiki.openstreetmap.org/wiki/Category:Import). Hopefully,

Re: [Talk-us] parcel data in OSM

2012-12-30 Thread Ian Dees
There sure is a huge amount of imported data in OSM, but I don't see what's frustrating about distinguishing between useful and not-useful data imports. What we've been discussing here is what sort of data should be imported and if it's useful. On Sun, Dec 30, 2012 at 7:51 PM, Jeff Meyer

Re: [Talk-us] parcel data in OSM

2012-12-30 Thread Jeff Meyer
What's frustrating about distinguishing between useful not useful data imports is that there isn't much information available on the wiki other documentation about how to distinguish between the two. At least, I haven't been able to find much of the good information that's in the minds of the

Re: [Talk-us] parcel data in OSM

2012-12-30 Thread Ian Dees
On Sun, Dec 30, 2012 at 8:50 PM, Jeff Meyer j...@gwhat.org wrote: What's frustrating about distinguishing between useful not useful data imports is that there isn't much information available on the wiki other documentation about how to distinguish between the two. At least, I haven't been

Re: [Talk-us] parcel data in OSM

2012-12-30 Thread Russ Nelson
Serge Wroclawski writes: Steve suggested we need addresses. He didn't ask for a crazy huge import. Well, he kinda did. The TIGER data has addresses. The original import didn't include them. We *could* triple the size of the data in the USA by creating address ways alongside the TIGER ways.

[Talk-us] Whole-US Garmin Map update - 2012-12-29

2012-12-30 Thread Dave Hansen
These are based off of Lambertus's work here: http://garmin.openstreetmap.nl If you have questions or comments about these maps, please feel free to ask. However, please do not send me private mail. The odds are, someone else will have the same questions, and by asking on the talk-us@

Re: [Talk-us] parcel data in OSM

2012-12-30 Thread Steve Coast
On Dec 30, 2012, at 9:01 PM, Russ Nelson nel...@crynwr.com wrote: Serge Wroclawski writes: Steve suggested we need addresses. He didn't ask for a crazy huge import. Well, he kinda did. The TIGER data has addresses. The original import didn't include them. We *could* triple the size of the

Re: [Talk-us] [Imports] Proposed import: Alaska Boroughs/CPDs

2012-12-30 Thread Paul Norman
The first question is what is appropriate consultation, and that will vary on a case by case basis with the type of data, complexity of import, type of object being imported, where it's being imported, existing data, experience of importer, feedback received, etc. I missed adding the link to