-
Notifications
You must be signed in to change notification settings - Fork 382
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Longitudinal Profile tool enhancement #9545
Comments
@tdipisa can you clarify a few details on what exactly has to exported? We have access to a set of points containing these info
Currently the available formats are referring to the chart line. For the GeoJSONI assume that it will contain a Feature collection with Point geometries with three coordinates using altitude as third one and a few properties for each Point (slope and totalDistanceToThisPoint). For the DXFShould I do the same as for the GeoJSON? i.e recreating the line using this function UI refactorI think that we should refactor ta bit the ui because adding two more buttons to export two new formats is not ideal Or we can divide this into two comboboxes one for the PNG/PDF and one for the rest |
@MV88 the export should contains the same of what already present in the CSV output that are tipically coordinates of points in the path along whit the altitude. For the DXF the same, that means geometry data of points. Let's evaluate better the UI part with @allyoucanmap with the idea to have export formats list configurable. The new dependency for DXF should be loaded in a lazy way. |
Description
It is requested to enhance the Longitudinal Profile tool by providing also GeoJson and DXF as export format.
What kind of improvement you want to add? (check one with "x", remove the others)
Other useful information
Export in GeoJson is not a problem using the WPS output but we should investigate a bit for the DXF one evaluating available JS client solutions like https://www.npmjs.com/package/dxf-writer (or other). The dependency should be lazely loaded.
The text was updated successfully, but these errors were encountered: