You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 28, 2024. It is now read-only.
If you look at the failing symbols in an SVG Editor you can see that failing elements/artifacts - these are indeed empty/spurious path elements, but it would be best if Pro could just ignore these. Otherwise we should fix the source symbols to remove these paths (Note: the symbol do import fine if you remove these spurious elements).
@lfunkhouser - If it is just the SVGs listed above, it should not be much effort to delete the empty path elements. I see that they show up in the layer lists, and can be deleted from there.
Some of these have been fixed in Pro 2.2. You will no longer see the loading error for any of the SVGs.
I believe these ones are now correct:
svg\Appendices\Space\05120400.svg
svg\Appendices\Atmospheric\45162101.svg
svg\Legacy\2525C\S-G-UCDMM-_2.svg
svg\Legacy\2525C\S-G-UUMSEJ_0.svg
svg\Legacy\2525C\S-G-UUMSEJ_1.svg
svg\Legacy\2525C\S-G-UUMSEJ_2.svg
svg\Legacy\2525C\S-G-UUMSEJ_3.svg
There are still some drawing issues that we are looking at for:
svg\Appendices\Land\20120201.svg
svg\Appendices\Activities\40131202_0.svg
svg\Appendices\Activities\40131202_1.svg
svg\Appendices\Activities\40131202_2.svg
svg\Appendices\Activities\40131202_3.svg
Removing the empty path from the SVG is a good work around however, we do want to fix the issue in Pro as well.
topowright-zz
changed the title
Using Pro 2.2, some of the 2525D Source SVGs are failing to import into Pro Styles
Using Pro 2.3, some of the 2525D Source SVGs are failing to import into Pro Styles
Sep 25, 2018
From @csmoore on July 16, 2018 18:11
Summary of Issue Encountered:
Starting at Pro 2.2, some of the 2525D Source SVGs are failing to import into Pro Mobile Styles. The failing SVGs seems to have empty Path elements.
Brief summary of issue encountered:
After installing Pro 2.2 and attempting to load the following SVGs from:
https://github.com/Esri/military-features-data/tree/dev/military-symbology-styles/utils-and-source-data/svg
svg\Appendices\Space\05120400.svg
svg\Appendices\Land\20120201.svg
svg\Appendices\Activities\40131202_0.svg
svg\Appendices\Activities\40131202_1.svg
svg\Appendices\Activities\40131202_2.svg
svg\Appendices\Activities\40131202_3.svg
svg\Appendices\Atmospheric\45162101.svg
svg\Legacy\2525C\S-G-UCDMM-_2.svg
svg\Legacy\2525C\S-G-UUMSEJ_0.svg
svg\Legacy\2525C\S-G-UUMSEJ_1.svg
svg\Legacy\2525C\S-G-UUMSEJ_2.svg
svg\Legacy\2525C\S-G-UUMSEJ_3.svg
A failure is encountered:
Describe the product and version used:
Pro 2.2
Reproduction Steps and/or Where to Obtain Test Data:
Step-by-step description of how to reproduce the issue and the expected results:
https://github.com/Esri/military-features-data/tree/dev/military-symbology-styles/utils-and-source-data/svg/Appendices/Space/05120400.svg
You receive an error:
Additional information or sample data:
If you look at the failing symbols in an SVG Editor you can see that failing elements/artifacts - these are indeed empty/spurious path elements, but it would be best if Pro could just ignore these. Otherwise we should fix the source symbols to remove these paths (Note: the symbol do import fine if you remove these spurious elements).
Just to summarize this requires a fix in either:
FYI @ACueva @dfoll @lfunkhouser @topowright
Copied from original issue: Esri/military-features-data#334
The text was updated successfully, but these errors were encountered: