This mailing list has been migrated to Mailman 3. This archive will no longer be updated. Messages after 1 February 2020 are missing. Please use the new archive instead.
Diese Mailingliste wurde auf Mailman 3 umgestellt. Dieses Archiv wird nicht mehr länger aktualisiert. Nachrichten nach dem 1. Februar 2020 fehlen. Bitte benutze das neue Archiv.
/3 words missing...// / Am 20.10.2015 um 20:46 schrieb Christian Wendel: > Hi Jeroen, > > I agree. These tags are missing, so in some cases I already marked > catenary_mast and "Oberleitungshalteseile" (overhead wire retaining > cables ???) for orientation purposes via way & "note=*". It helps at > mapping from video combined with aerial views. > > regards > Christian > > > > Am 18.10.2015 um 16:01 schrieb JJJ Wegdam: >> The Dutch public datasets (please consider attachment for more info) >> contain all catenary structures in the Netherlands. Since I found out >> that no catenary structures have yet been mapped anywhere in the >> country, I thought it would be a nice opportunity for an automated >> import. >> Catenary poles (displayed as nodes in the datasets) can currently be >> tagged as power=catenary_mast. *I'd like to propose an additional >> power=catenary_fixture* *tag *to tag catenary portal-beams, >> stanchions and arms (displayed as lines in the datasets). >> I'd appreciate to hear your opinion on this new tag. It would bring >> the import a step closer. Thank you in advance. >> >> Jeroen Wegdam >> Student-assistant at ProRail >> (Dutch railway asset owner) >> >> PS/update: currently, I am replacing all Dutch OSM railway ways with >> proper positions. Before importing the catenaries, I will first >> finish the railway geometry and platform wall imports. This will >> result in catenaries that fit seamlesssly to the railways. All >> imports are done manually (with great care for existing data). >> >> Op 18 okt 2015 om 13:09 uur uur schreef Alexander Matheisen >> <notifications at github.com>: >> >>> This is a tagging discussion. Please continue it on the mailing list. >>> >>> — >>> Reply to this email directly or view it on GitHub >>> <https://github.com/rurseekatze/OpenRailwayMap/issues/215#issuecomment-149003625>. >>> >>> >> >> >> _______________________________________________ >> Openrailwaymap mailing list >> Openrailwaymap at openrailwaymap.org >> http://lists.openrailwaymap.org/lists/listinfo/openrailwaymap > > _______________________________________________ > Openrailwaymap mailing list > Openrailwaymap at openrailwaymap.org > http://lists.openrailwaymap.org/lists/listinfo/openrailwaymap