Talk:Import/Catalogue/Topography import for Norway

Up to date best practice for generating/obtaining import files? The google drive link is not open. https://wiki.openstreetmap.org/wiki/Import/Catalogue/Topography_import_for_Norway/assignment refers directly to n50osm, while this page suggest the topo2osm+misc transformations/pregenerated files as the preferred method. --Olejorgenb (talk) 08:07, 6 August 2022 (UTC)

n50osm is the most recent program and provides some additional functionality including refs to the NVE lake database, lake altitudes, automatic tagging of names for lakes, islands etc. It does not currently provide splitting into smaller segments, but a utility in topo2osm may be used. I am planning to provide splitting in n50osm. I am not sure if topo2osm is updated on Github - users Reitstoen or Marius Geitle might have more information on topo2osm. You would also get support on #osm-no on IRC. --NKA (talk) 09:33, 6 August 2022 (UTC)

Have someone looked into using ELVIS for importing river and streams? Looks like it's the same data as N50 ("ELVIS er alle element i vassdragene gjengitt som linjer, etablert på grunnlag av N50 Kartdata fra Kartverket."), but maybe in a more convenient format ("Linjene er knyttet sammen i et logisk nettverk og har definert strømretning. Hvert linjesegment – eller vassdragsstrekning – er gitt et entydig nasjonalt løpenummer."). (Still waiting for the "-stream" step of n50osm :D) --Olejorgenb (talk) 09:03, 6 August 2022 (UTC)

I have looked at Elvis, but it seems to have a very simplified geometry for rivers and few streams, so N50 is far superior. The Kartverket api for altitudes (used for checking direction of streams) is unfortunately slow. Which municipality? --NKA (talk) 09:33, 6 August 2022 (UTC)

Thanks for quick reply! Tynset, it completed in reasonable time :). But some river/streams seems to be fragmented/incomplete. Created a github issue. --Olejorgenb (talk) 09:56, 6 August 2022 (UTC)