mboeringa
mboeringa
The dialogs interface seems coded here: https://github.com/qgis/QGIS/blob/bb9e276d591594821e2368f6ca077850baf1220b/src/app/openstreetmap/qgsosmdownloaddialog.cpp It references the `#include "qgsosmdownload.h"` module that seems to do the actual work of the download. It is here: https://github.com/qgis/QGIS/blob/8ac1460d0e760b288ca20e88529737c3b5cde137/python/analysis/openstreetmap/qgsosmdownload.sip If I interpret...
> Have you seen any progress on this since? I am trying to convert osm data to Arcgis Pro but cannot find any way to do so... No, I haven't...
> We’ve heard the request for the tools to function in ArcGIS Pro, however we’ve not taken any significate actions toward that as of yet. As noted in this thread,...
OSM File Loader (Load only) tool fails to load data in an Enterprise Geodatabase - empty FCs created
@ThomasEmge I noticed a minor typo in the commit: Shouldn't: +120201 - mul**y**iloader, needs unique feature class names be: +120201 - mul**t**iloader, needs unique feature class names You seem to...
OSM File Loader (Load only) tool fails to load data in an Enterprise Geodatabase - empty FCs created
@ThomasEmge , I now noticed a piece of Help text that is included with the **Parallel Processing Factor** environment setting on each geoprocessing tool that I overlooked up to now:...
OSM File Loader (Load only) tool fails to load data in an Enterprise Geodatabase - empty FCs created
Hmm, re-testing is now impossible, as the code currently (official 10.5 version) warns for choosing a File Geodatabase as the only allowed output geodatabase type. This means an Enterprise Geodatabase...
> **The current approach is that everything is translated into a geometry if possible**. Some do get special treatment such as multipolygon or route or coastline, but that's about it....
@ThomasEmge , Hmmm... my latest thoughts on this are that I _possibly_ need to include the suggested functionality in my Renderer as well, as part of the pre-processing stage. I...
> **what is the width of those fields in OSM itself?** that's what should drive the design of the data structure in the geodatabase. after the import you could shrink...
Hi Andrew, Yes, the current implementation of the OSM Attribute Selector actually truncates any values bigger than 100 characters. The code is in **OSMGPAttributeSelector.cs**. I think this may have been...