Den 16. okt. 2013 23:05, skreiv Christoph Hormann:
On Wednesday 16 October 2013, Gnonthgol wrote:
The VANNBR tag in the data is not the width in meters, but a code for
the width of the river. Code 2 is 1-3m and code 3 is 3-15m wide. I
have found this tag to be misleading as it is changed due to
aesthetic reasons in the data. (N50 is a vector layer intended for
rendering)
Then it would in my opinion make sense to tag all code 3 as
waterway=river and code 2 as river or stream depending on manual
assessment. No width tag.
Having looked at the data this makes little sense, it is common to have
a width 3 "river" flow into a width 2 "stream". But the data can be
quite useful when mapping local areas anyway. It is hard to map a river
or a stream with only a gps device. This goes in the "vector overlay"
category instead of import.
One other thing i saw when looking at the wiki page: There seem to be
distinct data sets for river and lake polygons and there also seems to
be a data set for dams. It would make sense in my opinion to set
water=reservoir for all lake polygons bordering to a dam and water=lake
for the rest. This could be done automatically but of course also by
hand when merging the data.
Even better, there are different way type for regulated lakes as opposed
to natural lakes. There is no distinction in the polygons though (SOSI
have a topolagical data model like TopoJSON or OSM). But this is
possible to make.
If you want to help us out you should also check out
https://github.com/Gnonthgol/sosi2osm .
Gnonthgol
_______________________________________________
Imports mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/imports
