Hi Y'all,
I've been out to lunch re: NHD for a while..Paul, a stupid q:
The NHD data model changed shortly after bsupnik wrote his conversions
and some fcodes changed. This makes using his conversions difficult.
Does this imply that the actual _raw_ dump I have of the data from NHD
is
Hi Y'all,
First, I'm sorry that I didn't jump into this thread earlier. I am the
graphics lead on X-Plane, and for our latest version we switched from
TIGER+VMAP0+swbd to OSM for our vector water body and road data. In the
case of the US, this is perceived as a step backward by our users
Hi Paul,
On 10/29/12 11:47 AM, Paul Norman wrote:
2. The conversion required running a non-GUI tool, which meant having
command line skills, etc.
This is actually a plus for me - handling all of NHD without command line
scripts would be difficult. There's a *lot* of data.
Right - for anyone
Hi Ben,
On 8/21/11 10:40 AM, Ben Miller wrote:
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
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
Hi Y'all,
http://bsupnik.dev.openstreetmap.org/NHD/
If anyone has time to DL 1 or 2 files to do a quick sanity check, it
would be much appreciated...I will update the wiki shortly!
cheers
ben
--
Scenery Home Page: http://scenery.x-plane.com/
Scenery blog: http://www.x-plane.com/blog/
Plugin
2300+ HUCs.
I can build an index off the particular shapefile HUC boundaries if
that's needed.
cheers
ben
On 6/20/11 10:46 AM, Richard Fairhurst wrote:
Ben Supnik wrote:
If anyone has time to DL 1 or 2 files to do a quick sanity check,
it would be much appreciated...I will update the wiki
Hi Richard,
Vector background layers in P2.2 are _much_ improved over earlier
versions. I've just downloaded one of your NHD .zips, extracted a file
from it, hosted it locally
(http://127.0.0.1/~richard/osm/01010003_nhdwbhi0.xml, that sort of thing),
and imported it into P2, and it's very happy
Hi Josh,
On 6/20/11 11:02 AM, Josh Doe wrote:
1) I believe you've split the files to ensure no more than 50,000
nodes per file (upload limits I believe), but it is somewhat
fragmented so that for a given region streams are split between the
files. This will result in additional duplicate nodes
Hi Josh,
In file 02070010_nhdarhi0.xml, there are three such ways (areas),
COM_ID 46571227, 46571098, 46571233. I think this is because most dams
are represented as lines (39 for this HUC8), but these three are
areas, so perhaps it isn't a big problem. Is there any issue with
applying the same
Hi Y'all,
This may be slightly premature, but if all goes well, my conversion of
the latest NHD high-res data set to OSM format should complete within 24
hours. The data set will be approximately 15 GB, zipped.
So my question is: where to put this for users to download? My main
motivation
Hi Y'all,
I apologize for going NORDO for a while there. :-( I have integrated
James' latest NHD conversion rules.
Test data:
http://dev.x-plane.com/download/01090001.zip
The entire process is running now...not sure how long it will take to
complete - it looks like it could take up to a
Hi Josh,
First: the wiki - I was planning to document the data once we had a
final download location, either an official-ish OSM server or anything
else we come up with. I will update the wiki page once we know where
the data will live
I've also looked at the data, and I must say I'm
Hi Josh,
On 6/9/11 2:37 PM, Josh Doe wrote:
In the test data you provided I saw a number of objects that didn't
have any tags that weren't in the gnis or nhd namespace (i.e no
waterway tag). Is there use in importing these features? Is the
thinking that maybe in the future we can add sensible
Hi Ian,
On 6/9/11 1:34 PM, Ian Dees wrote:
1) The XML converter should split up the data so that ways and their
nodes are in the same XML file. I *think* my shp-to-osm tries to do
this. If you end up with a bunch of XML files that have 50k node
elements in them then you're doing it wrong [0].
Hi Toby,
If/when you make contact with the importer, it would be useful to know
what went wrong exactly, e.g. did an automated part of the conversion
fail, what was the last phase of the import the user checked, did the
import fail on upload, etc.
Given the discussion of NHD imports last
Hi Guys,
On 4/29/11 12:10 PM, Ian Dees wrote:
I've been meaning to add a node dedupe step to the shp-to-osm suite.
I'd love to see what you had to modify to get it to work. I'd also like
to add a way dedupe at some point, too (to handle abutting areas like
boundaries).
Well, that code for
Hi Y'all,
So let me see if I can summarize where we are so far...
- I could cut the NHD data down to sub-basins. It would not be a perfect
cutting (e.g. each sub-basin might need a little bit of data hanging
off since the raw data isn't cut on sub-basin boundaries) but it would
be pretty
map that a user
could click on to find their subbasin. I'd be happy to host all this.
-Ian
On Thu, Apr 28, 2011 at 7:37 AM, Ben Supnik bsup...@xsquawkbox.net
mailto:bsup...@xsquawkbox.net wrote:
Hi Y'all,
So let me see if I can summarize where we are so far...
- I could cut the NHD
Hi James,
I've been checking some of the imported data and my general feel is that it is
overdigitized. I don't know if medium versus high reflects just the quality or
the amount of digitization. That would be something to check. One could also
just run some sort of simplification algorithm
Hi Y'all,
This is one sub-basin (01090001 - go Sox :-), isolated from the latest
NHD data, then converted via the latest rule set off of the wiki (with
shapefile key capitalizations fixed).
http://dev.x-plane.com/download/01090001.zip
If anyone has done NHD imports before, please take a
Hi Y'all,
From what I can tell:
- Every water body does get a reach ID. I've seen nulls in this file
but haven't yet figured out what they are...in local sample areas, all
water bodies have reach IDs.
- If there is linkeage between areas and flow lines (which I _thought_
there was when
22 matches
Mail list logo