Open oterral opened 8 years ago
Snapping is a different issue - the binding to the primaerflaechen we could probably do right now.
For This we need sth like a surface service or integrate the surface info into the profile service
ch.swisstopo.vec25-primaerflaechen
-To double check with topo if there is a tlm based solution. Because vec25 is not updated.
We can use the outer ring for a polygon. Note: This can also be done front-end.
I am not sure we can add this info with the current techno. We rely on http://vterrain.org/Implementation/Formats/BT.html But yes, if we want it this should be pre-proccessed.
If we store it in BT: we have highcost ti update surface information
Several profile related issues now. Might be time for a brainstorm session.
RE4
From #1912
From tlm . Using existing Services. Might need an update in data integration. Will show you the reference of outdooractive. Goal: are you hiking in forest or paved roads etc.... More 1:1
@gjn see screenshot above in tik description and eg http://www.outdooractive.com/en/mountain-bike/graubuenden/433-poschiavo-san-romerio/19257197/#dm=1
but IMHO we need for this
snapping to fit it to TLM vector info ( hiking trails do contain a surface info) or as a workaround use the service for ch.swisstopo.vec25-primaerflaechen and a add this info to the height service...