Hi Serge - thanks for the thorough reply - please see notes below: source tags are not really appropriate for indivdual elements, >> How do you identify when individual elements of the same way or node are derived from different sources? >> Also, what you are saying directly contradicts the information found at the wiki: http://wiki.openstreetmap.org/wiki/Key:source : "It can also be used as a namespace prefix to specify the source of a single attribute. For example, to attribute a source for a name tag, use*source:name=photograph*" >>>> I didn't see any discussion or dispute of this approach on the wiki page, so I'm assuming it's ok.
more importantly, the specific datasets should be referenced, as data.seattle.gov doesn't talk about the version of the data, or even what dataset it is. >> Good points. We will add these clarifications. Where is the source of your transformation scripts? >> From the email above: "some translation instructions Cliff has put together." We will include the specific translation code either at a github page or on the http://wiki.openstreetmap.org/wiki/Seattle page. Where are the specific data files you're transforming? >> They are at data.seattle.gov & we will provide links to the sources. We will also consider posting separate snapshots of these source datafiles if we can figure out where to host them. How will you handle object conflation? >> Manually and methodically. >> From the email above: "At the meeting, we will discuss concerns about the import, methods of curating the data, how to divide up the work, and how to properly track data created through this import. A cursory review of the data has identified a variety of issues: e.g. non-existent addresses, misplaced addresses, including buildings that no longer exist, etc. So, we are not planning to just do a big bulk dump of information." >> We are also optimistic that the tools developed in New Zealand will be very helpful. Please see Robert Coup's very constructive email in this thread. We will review these tools and use them, if appropriate for our interests. I have many concerns, some of which are discussed above, >> Please identify any un-discussed concerns. I'd like to make sure we've accounted for them all. but more generally, you seem to not have discussed this with the greater OSM community, including the talk-us list. >> I thought that imports@ was the "Greater OSM community." >> From the email above: "A group of Seattle OSM'ers (led by Cliff Snow) are getting together to discuss the methods for importing and double-checking the information. http://www.meetup.com/OpenStreetMap-Seattle/events/93524692/ " >> I will forward the prior notice to talk-us@ >> From this page: http://wiki.openstreetmap.org/wiki/Import/Guidelines#A_checklist, can you advise as to the checklist steps we are not following, or which steps should be added to this checklist? Imports are very sensitive and should not be taken without an incredible amount of thought and planning, and a lot of community involvement. >> These are all good points, which I was hoping to address with my prior email. Regards, Jeff On Mon, Dec 3, 2012 at 2:30 PM, Serge Wroclawski <[email protected]> wrote: > On Mon, Dec 3, 2012 at 3:30 PM, Jeff Meyer <[email protected]> wrote: > > All - > > > > The city of Seattle has recently granted permission to use data found at > > data.seattle.gov in OpenStreetMap. > > > http://wiki.openstreetmap.org/wiki/Contributors#City_of_Seattle.2C_Washington > > > > A group of Seattle OSM'ers (led by Cliff Snow) are getting together to > > discuss the methods for importing and double-checking the information. > > http://www.meetup.com/OpenStreetMap-Seattle/events/93524692/ > > > > The current plan is to focus on addresses and building outlines. > > Sources are currently suggested to be tagged as: > > source:addr=data.seattle.gov > > source:path=data.seattle.gov > > so as to accomodate other sourcing information for those points and > ways, as > > appropriate. > > source tags are not really appropriate for indivdual elements, but > should be on the changeset, but more importantly, the specific > datasets should be referenced, as data.seattle.gov doesn't talk about > the version of the data, or even what dataset it is. > > > Data has been converted from shape to osm using pnorman's ogr2osm python > > scripts and some translation instructions Cliff has put together. > > Where is the source of your transformation scripts? > Where are the specific data files you're transforming? > How will you handle object conflation? > > > More news to follow. Please advise of any concerns. > > I have many concerns, some of which are discussed above, but more > generally, you seem to not have discussed this with the greater OSM > community, including the talk-us list. > > Imports are very sensitive and should not be taken without an > incredible amount of thought and planning, and a lot of community > involvement. > > - Serge > -- Jeff Meyer Global World History Atlas www.gwhat.org [email protected] 206-676-2347
_______________________________________________ Imports mailing list [email protected] http://lists.openstreetmap.org/listinfo/imports
