https://github.com/gam17/QAD
Drawing directly in a CAD is easier and more convenient. Commercial product already embed such packages such as AutoCAD Map, BricsCAD or Microstation through plugins. There is an almost similar software, JOSM, to draw datas for the OSM project. JOSM is often used to create a drawing to be imported later in QGIS.
It would be possible to load a background layer made of georeferenced pictures, or a TMS tiles server or a WMS tiles server.
FreeCAD would allow then to draw projects over this layer.
BricsCAD examples:
Automapki
https://www.bricsys.com/applications/a/ ... a557-al939
CivilCAD
https://www.bricsys.com/applications/a/ ... 648-al1084
GeoTools
https://www.bricsys.com/applications/a/ ... 041-al1818
GISX (German)
https://www.bricsys.com/applications/a/?gisx-a456-al742
Spatial Manager™ for BricsCAD
https://www.bricsys.com/applications/a/ ... 899-al1553
ATLAS based on Microstation to draw energy networks.
https://www.sogelink.fr/atlas
Example for professional use in telecom networks using both FreeCAD and QGIS.
https://ksavinetworkinventory.com/network-inventory/
Pro:
* Bringing geospatial engineering in FreeCAD.
* Having a solid geospatial engineering workflow thanks to free softwares with a solid reputation FreeCAD and QGIS.
* Improving the workflow by making FreeCAD an external serious CAD environnement to QGIS.
* Bringing an open geospatial environment for architects, archeologists, mappers, planners or civil engineers.
Aims:
* Drawing complex objects from raster views.
* Updating easily maps from raster views.
* Drawing energy networks with cotations from surveys. Cotations aren’t exported in GIS, they are kept only with georeferenced DXF.
* Drawing all kind of land subdivision for government agencies.
* Drawing transport networks maps.
The FreeCAD Spatial Manager workbench would draw in 2D only for the beginning. That would make easier to export to a GIS software as well. Based on the features available in JOSM, this workbench would improve the workflow between CAD and GIS in open softwares. Because not everyone is using GIS the same way, the AIM is not to replace JOSM nor to be able to upload datas to the OSM servers, JOSM is already there for that. Anyhow, it will have to be able to respect these features for those who would need CAD features to draw new complex items for the OSM project. For the OSM users, upload could still be achieved directly in QGIS, or in JOSM by export in OSM.
File formats that should be supported:
SHP Shape files
GeoJSON https://en.wikipedia.org/wiki/GeoJSON
OSM
georeferenced DXF
GML https://en.wikipedia.org/wiki/Geography_Markup_Language
Geopackage https://en.wikipedia.org/wiki/GeoPackage
This Workbench would maybe integer the external Geodata workbench which uses OpenCV.
Tools:
Almost the same as Draft Workbench: Line, Wire (Polyline), Circle, Arc, Ellipse, Polygon, Rectangle, BSpline, Point, Bezier Curve.
No Text, Dimension, ShapeString, Facebinder, Label
Curves (Circle, Arc, Ellipse, BSpline and Bezier Curve) will have to be converted to Polylines when exported. A level of smoothness can be given further.
Add an offset tool. It’s missing a button for the offset tool and a button to select the background tiled layer.
The button for the offset tool would be with the draft tools toolbar.
Snapping tools are kept the same.
The button to select the background tiled layer would be on a dedicated toolbar like this one.
The task view is kept, but a new Datas tab will be added:
The new Attributes tab will be used to input datas to the objects.
There are 2 columns: Key (on the left) and Value (on the right)
This is how the interface would look.
The new pane on the left with the specific tab and you can see the grid on.
The values shown in the attributes tab are from OSM, but any kind of value can be used to fit any GIS project. Just change the key.
It’s missing a + and a - buttons to add/remove keys. But a key could be cleared by the contextual menu with a right-click over the one to be removed.
Closed shapes such as circle, polygons, rectangles or whatever is closed are filled.
We can optionally think about the possibility to connect to a pre-existing SQLite database or an Excel/LibreOffice table where the datas attributes could be stored.
