[Talk-us] NHD data conversion
Ben Miller
bborkmiller at gmail.com
Sun Aug 21 15:40:27 BST 2011
Great! Thanks Ben.
I downloaded the data for the two areas that I'm interested in (04060104 and 04060105) and stuck them in JOSM. I'm not sure I feel comfortable just dumping the whole thing in (especially if it might cause problems) so I was planning on doing it more or less item by item. Is there a flaw in that plan?
Also, is there an explanation somewhere of what the various files represent? XXX_nhdarhi0.xml, XXX_nhdflh0.xml, etc.
And one question about methodology: There are a few larger lakes that were added as part of the PGS process. They appear to have been left pretty much untouched (except by me) and the NHD data is significantly more accurate. Would it be acceptable to replace the PGS ways with NHD ways, assuming I make sure to connect up any rivers, add them to appropriate relations, etc?
Regards,
Ben
On Aug 19, 2011, at 7:49 AM, Ben Supnik wrote:
> Hi Ben,
>
> I think the answer is: we're part way there.
>
> I was able to get my work-flow for conversion working and did do a complete conversion, which is uploaded here.
>
> http://bsupnik.dev.openstreetmap.org/NHD/
>
> So first: if anyone looks at these and finds things that aren't so good, please let me know, I'll recut! But if I remember, one of the issues was that there was linework that was imported _only_ because it had an NHD id - I'm using Ian's java tool to do the shapefile->osm conversion and it doesn't have a way (that I know of) to say "if the only tag present is X, just skip". (Ian: if you have a patch or trick for this please let me know.) I don't have enough of a dev setup to work on Ian's code, and I haven't had time to put my own pre or post processing filter on the data.
>
> Second: the consensus seemed to be that there wasn't a great way to get this data _in_ to OSM. Each HUC is complex enough that the upload risks failing on the servers part way through if sent in its entirety. I spoke with RichardF a little bit about teaching Potlatch to use the data as a vector layer, but I'm not sure where we are with that.
>
> (RichardF: if you have a layer format or layer format + manifest HTML file that you like/support, I will simply conform my bulk conversion to your needs!)
>
> So...you're welcome to work with the data as is...you may need to artificially break up the HUC and work on it in parts (to keep the total change set size down) and then individually push up finished work as you verify it.
>
> cheers
> ben
>
> On 8/18/11 5:35 PM, Ben Miller wrote:
>> I was watching with anticipation the conversation about pre-converting
>> NHD data for the whole US, but it seems to have died down since June. I
>> think I'm the target audience for this effort (I'm willing to put in
>> time merging the data in carefully, but I'm not conversant in the
>> command-line tools to prepare it) so I'm curious what the status is.
>>
>> -- Ben
>>
>>
>> _______________________________________________
>> Talk-us mailing list
>> Talk-us at openstreetmap.org
>> http://lists.openstreetmap.org/listinfo/talk-us
>
> --
> Scenery Home Page: http://scenery.x-plane.com/
> Scenery blog: http://www.x-plane.com/blog/
> Plugin SDK: http://www.xsquawkbox.net/xpsdk/
> X-Plane Wiki: http://wiki.x-plane.com/
> Scenery mailing list: x-plane-scenery at yahoogroups.com
> Developer mailing list: x-plane-dev at yahoogroups.com
More information about the Talk-us
mailing list