|
POST
|
The best way to import OpenStreetMap data in .osm XML format, is to use ESRI's "ArcGIS Editor for OpenStreetMap": https://www.arcgis.com/home/item.html?id=4533407decd94428817a228cb36964cf This toolbox has powerful options to import the data, including full support for OSM multipolygon relations. NOTE(!): Unfortunately, there is not yet a "Pro" version of this toolbox, so you can't use it in ArcGIS Pro and import directly in Pro. However, this is not a big issue: use ArcMap to import the data into a File Geodatabase, and then simply open the File Geodatabase in Pro, or first style your data in ArcMap also, and then import the ArcMap *.mxd document in Pro using Pro's options for importing ArcMap documents. As to the Editor: I strongly recommend you to use the new "OSM File Loader (Load only)" tool to import the data if you do not intend to edit the data in ArcMap and contribute back to OSM using the upload options. The "OSM File Loader (Load only)" tool supports ESRI's Parallel Processing environment setting, meaning it can take advantage of multi-core processing. This is much faster than the "Load OSM File" tool, but this latter tool is needed in case you intend to contribute back, or desire to create a Geometric Network of the OSM data for routing purposes, as it will load additional relationship information into the File Geodatabase that the "OSM File Loader (Load only)" skips (but please note the "OSM File Loader (Load only)" does load OSM multipolygon relations).
... View more
05-24-2017
03:45 AM
|
2
|
6
|
13802
|
|
POST
|
Thanks Joshua. That's a good one! I have been learning ArcPy and Python quite well over the past three years, but there always remain these hidden corners you haven't explored yet. I hadn't realized such a method existed.
... View more
03-11-2017
01:25 PM
|
0
|
0
|
2724
|
|
POST
|
Ok, thanks Asrujit, as I suspected a possibly minor documentation error. Should be easy to fix.
... View more
03-10-2017
01:44 PM
|
0
|
0
|
2724
|
|
POST
|
Hi all, After I upgraded to 10.5, I noticed in the ArcGIS 10.5 Help that the webpage about Client and geodatabase compatibility suggests that ArcGIS releases below 10.5 may be incapable to connect to a 10.5 File Geodatabase. 10.5 is not listed for the 10.1-10.4.x releases. Now I guess this may be an oversight in the Help, especially since the Create File GDB tool does not list a new option for creating <10.5 release File Geodatabases, except the ones that were already available at 10.4.x (10.0/9.3/9.2), but since I don't have an older setup to test this, can someone tell me whether 10.5 File Geodatabases can be read by older versions of ArcGIS? I am aware of the general concept of no new functionality being available when accessing from an older client, I am just interested to know whether the Help is in error here.
... View more
03-10-2017
11:05 AM
|
0
|
7
|
3475
|
|
POST
|
Jeremy Wright schreef: Our recommendation is always to use the output PDF at resolution/zoom level that's appropriate for the output resolution. To illustrate what I mean: export same map at 120dpi to PNG. You'll find that neither text nor halo have any amount of clarity at that resolution when diminuitively sized. That inaccuracy carries over into the PDF - but PDF lets you zoom in to the tiny text and still make it readable. Side note: my monitor is a 123 ppi resolution monitor (2560 x 1440). When I export the PDF at high resolution from ArcMap or Pro, the small fonts are perfectly readable in Adobe Reader. With proper halos, the anti-aliasing done by Adobe Reader is not bad and the clarity of the text sufficient. Even 5 pt text is readable on this 123 ppi monitor (although of course this is mainly targeted at true print). Of course, with retina, things look really cool. Opening the same map on my Samsung Tab S is just mind blowing, everything is so sharp, that you almost start wishing for some softening "anti-aliasing" to kick in...
... View more
02-23-2017
02:52 PM
|
0
|
0
|
4875
|
|
POST
|
Jeremy Wright schreef: Our recommendation is always to use the output PDF at resolution/zoom level that's appropriate for the output resolution. To illustrate what I mean: export same map at 120dpi to PNG. You'll find that neither text nor halo have any amount of clarity at that resolution when diminuitively sized. Yes, but that may be at least partly attributable to the poor halo quality, and hence consequently poor anti-aliasing that takes place. Since fonts are embedded in the PDF, and are always accurate and high quality independed of the output resolution (at least for 100% vector maps), the mismatch between halo and font is more stinging.
... View more
02-23-2017
01:49 PM
|
0
|
0
|
4875
|
|
POST
|
OK, good to hear you were able to reproduce it. As I wrote, I guess the only way is if ESRI makes an exception for the halos, and by default outputs them at higher resolution. I have zero knowledge of the PDF format..., and don't even know whether that is possible at all. Might be a file format limitation. Anyway, for anything critical and 100% vector maps, outputting at high dpi (probably > 600 dpi or so, as 300 dpi still wasn't enough) should be the solution for now. DejaVu 5.5 pt is small, but not uncommon and certainly not unreadable in printed form, and quite well usable on todays "retina" display devices.
... View more
02-23-2017
12:53 PM
|
0
|
3
|
4875
|
|
POST
|
Jeremy, Thinking about this a bit more, at least as far as it relates to the actual halo results, I think the current quality is entirely expected for the given low dpi's. Of course, with less than 300dpi settings, there is very little possibility to correctly encode or render a tiny graphic / mask halo. This will especially affect the results for small fonts as used here. On the other hand, one does wonder if it wouldn't be better if the specific "halo" setting, was separated from the ordinary graphics encoding in the PDF, and shouldn't by default use a much higher dpi to correctly render the halos. The problem with the current approach is that, especially for small font sizes as used in the examples here, the poor halo quality at low dpi also heavily influences the anti-aliasing results on screen, meaning the readability of the small texts are significantly negatively affected. Marco
... View more
02-23-2017
03:45 AM
|
0
|
5
|
4875
|
|
POST
|
By the way, note that the actual font sizes are very small here: typically 5.5 to 7pt in half point increment.
... View more
02-22-2017
01:20 AM
|
0
|
0
|
8301
|
|
POST
|
I doubt font is relevant here, but the actual font used is the common DejaVu font: DejaVu Fonts
... View more
02-22-2017
01:17 AM
|
0
|
0
|
8301
|
|
POST
|
As I wrote, it is just the Halo setting of the Mask TAB of the ArcMap symbol editor. This is a setting of any ordinary Text Symbol in ArcMap, nothing special. So yes, the "halo shapes" are generated using symbology setting. I don't know what - if anything - Pro changes to this if I import and ArcMap mxd.
... View more
02-21-2017
04:49 PM
|
0
|
10
|
8301
|
|
POST
|
Actually, due to some other very rare bug that I have occasionally seen happening, where the actual black text was shifted completely of the white "halo" in PDF output, I know quite certain that the features created in the PDF output are not "donut" shape, but extent under the black original text. So that is probably what you would call a "mask"? Versus the halo being a "donut" shape with the original text cut out from the white secondary feature? Anyway, this is more of theoretical value, you know which setting I mean in the symbol editor...
... View more
02-21-2017
04:13 PM
|
0
|
12
|
8301
|
|
POST
|
Jeremy Wright schreef: Marco, Are these truly haloes or are they masking polygons? J Well, it depends on who you ask probably . If I look in the interface of ArcMap (where I created the original mxd that I imported in Pro), the setting for this is on the Mask TAB of the Edit Symbol option of an ordinary Text Symbol. But the actual setting is either None or Halo...
... View more
02-21-2017
04:05 PM
|
0
|
13
|
8301
|
|
POST
|
Hi all, Anyone else noticed this? When I export a layout to PDF from ArcGIS Pro (1.4.1) at the default 120 dpi resolution, any text label halos are very poorly rendered in the final PDF output. Now I was well familiar with this issue in ArcMap due to its different display pipeline, where low dpi (< 300 dpi) settings would not only lead to poor text label halo quality, but also loss of fine detail in the PDF output, and often even thin line objects not being exported at all and thus disappearing in the output. I therefor always use some very high dpi setting in 100% vector maps (e.g. 3600 dpi) in ArcMap, so as to force proper rendering and higher quality text label halos output, and at least a minimum 450 dpi for combined vector and raster output. However, due to its new architecture, Pro was supposed to solve these issues as far as I understood. Indeed, when looking at the true GIS vector data, the quality of the PDF output even at a low 100 dpi or so, is excellent. Unfortunately, not for the text label halos though!... Look at the accompanying images (note: 800 or 1600% enlargement), which shows both a high res ArcMap output, and Pro output at different resolutions. Notice how at 120 dpi, the halos are rendered really poorly. Instead of nicely encircling the corresponding label characters, the halos appear skewed, shifted and e.g. the "i" dot is square instead of trapezium as it should be for the italic text. Notice that with a 3600 dpi setting in Pro, the issues are completely resolved, and in fact, the halo rendering is even better than from ArcMap at the same resolution. However, a not unrealistically low 300 dpi setting, still leads to big artifacts in the halos... This will be an issue when exporting combined raster + vector data, where you may wish to reduce output size by limiting the dpi setting. As for now, this will lead to poor text halo quality in the PDF output. Note 1: for the full resolution images, open the attachments of the post instead of clicking on the images. Note 2: the screenshots are based on Adobe Reader XI 11.0.19, so not the newer "DC". Marco
... View more
02-21-2017
12:14 PM
|
0
|
15
|
14958
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 01-31-2026 04:45 AM | |
| 1 | 12-08-2025 09:12 AM | |
| 1 | 12-05-2025 12:38 PM | |
| 1 | 12-04-2025 10:08 PM | |
| 1 | 12-04-2025 10:11 AM |
| Online Status |
Online
|
| Date Last Visited |
10 hours ago
|