Update ISOM 2017 to rev.2018-11 #1187

ghost · 2018-11-29T23:36:52Z

This is pull with changes related to issue #1184

NOTE: Few changes not yet added due to unclear definition in ISOM-2017-corrections-approved-2018-11.pdf:

There are no 501.1? Stairway symbol added yet due to unclear definition and no any sizes defined;
Cliffs (symbol 202) "edges" not rounded yet. Need additional review on symbols 202..202.3 for switching line caps (and line joins?) to rounded;

Remove symbols 411.1 and 411.2 and related object on map.

dg0yt · 2018-11-30T07:04:55Z

symbol sets/src/ISOM2017_15000.xmap

+            <cmyk method="spotcolor"/>
+            <rgb method="cmyk" r="0.772" g="1.000" b="0.727"/>
+        </color>
+        <color priority="24" name="Green 20%" c="0.152" m="0.000" y="0.182" k="0.000" opacity="1.000">


@krticka I guess that all uses of "Green 50%" and "Green 20%" (including forest runnable in one direction, narrow ride) are to be replaced by "Green 60%" and "Green 30%", respectively, not only 406, 408?

BTW I would appreciate if the MC could clarify the spelling of its specs (ISOM2017 vs. ISOM 2017 vs. ISOM-2017).

@dg0yt Yes, your assumption about Green 60% and Green 30% is correct. Such change affects other symbols using these colours.

Regarding naming convention the true is, that we are using ISOM 2017 and ISOM2017 in our documents interchangeably. I will discuss this with Christer, but probably we can stick to this format: NAME space YEAR.

The new changes in ISOM will be published officially as ISOM 2019.

The new changes in ISOM will be published officially as ISOM 2019.

When?

And what we should do with ISOM 2017 symbol set now? Left it as is (but rename ISOM2017_15000.xmap to ISOM_2017_15000.xmap) and move all changes into separate ISOM_2019_15000.xmap?

Well, for now ISOM_2017_15000 is OK. When ISOM 2019 will be published officially just rename the file. Maybe there will be some additional small corrections from MC meeting in January based upon the requests by federations/commissions. At least you have to wait with ISOM 2019 for official PDF where dimensions of new symbols will be defined.

just rename the file.

No, for OpenOrienteering Mapper we should create new file (i.e., ISOM_2019_15000.xmap) for each new specification & keep all legacy symbol sets (such as ISOM_2000_15000.xmap, ISOM_2017_15000.xmap, etc.) for compatibility reasons.

At least you have to wait with ISOM 2019 for official PDF where dimensions of new symbols will be defined.

I can't understand why MC published changes as ISOM-2017-corrections-approved-2018-11.pdf, and not as ISOM_2019_draft_2018-11.pdf?!

Really misunderstanding :-/

valdisj

Is this ISOM 2017 Corrections approved November 2018 (https://orienteering.sport/iof/resources/mapping/) coming as add-on to 0.8.4 or as new template for 0.8.5?

ghost · 2019-03-20T11:50:25Z

Is this ISOM 2017 Corrections approved November 2018 coming as add-on to 0.8.4 or as new template for 0.8.5?

This symbol set not finished yet. It would be added into 0.8.5 (as 0.8.4 already released) or into 0.9.0.

P.S.: But if you want, you could download and use it for testing purposes only in 0.8.4

https://github.com/Symbian9/mapper/blob/patch-2/symbol%20sets/src/ISOM2017_15000.xmap

dg0yt · 2019-03-22T06:58:31Z

Is this ISOM 2017 Corrections approved November 2018 (https://orienteering.sport/iof/resources/mapping/) coming as add-on to 0.8.4 or as new template for 0.8.5?

The file proposed in this pull request introduced additional colors instead of adjusting the existing ones. This blocks the review of other changes. I recommend to not use this file for productive work.
I'm waiting for this ISOM 2017 Corrections to be published as ISOM 2019. I do not want to support two versions of ISOM 2017.
There is also a color appendix to be looked at. However, this is a very strange document anyway.
I don't think there will be another 0.8.x release.

ghost · 2019-04-04T19:56:51Z

The file proposed in this pull request introduced additional colors instead of adjusting the existing ones. This blocks the review of other changes.

What should I do with colors? I found colors comparsion chart, but not yet know how I should implement it

https://facebook.com/groups/485564718218028?view=permalink&id=2108630209244796

ghost · 2019-05-01T19:00:30Z

So, I just reproduce "Appendix 1 - CMYK Printing" instruction for colors in OpenOrienteering Mapper, but how should I design colors for "ISOM2017-2" and "ISSprOM2019"? (currently I'm working on both latest symbol sets for Mapper)

UPD: More screenshots added in comment behind.

dg0yt · 2019-05-02T06:50:14Z

When in doubt, retain as much as possible from the current Mapper symbol sets. Test in overprinting simulation and in regular view. Any substantial change to (our) existing color layers will make it harder to upgrade existing maps to (our) new symbol sets. Even more when users added own colors and symbols.

I wonder if the Appendix should really be taken literally. I can't remember it being discussed before publishing, and there seems to be more agreement between OCAD and Mapper than between either software and this Appendix. All those new standards had some serious issues. But the standardization process seems to involve only national societies, not software providers.

Fun point: The color layers were originally designed to support spot color printing while allowing editing and printing in "normal" mode. With spot color printing being effectively banned by that Appendix, there is no need for color layers - using (default) z-levels per symbol, maybe adjustable per object as in any other vector graphics tool, would make much more sense.

ghost · 2019-05-02T10:50:41Z

I wonder if the Appendix should really be taken literally. I can't remember it being discussed before publishing.

Yeah, on Facebook many mappers tells the same: Appendix 1 should be fixed or fully rewrited for ISOM2017-2 , ISSprOM2019 and upcoming specs.

Fun point: The color layers were originally designed to support spot color printing while allowing editing and printing in "normal" mode. With spot color printing being effectively banned by that Appendix, there is no need for color layers - using (default) z-levels per symbol, maybe adjustable per object as in any other vector graphics tool, would make much more sense.

But we should keep current Mapper spot colors for compatibility with older symbol sets.

BTW, There is solution on define Cyan/Magenta/Yellow/blacK colors as "spot colors" and then combine it for each color defined in Appendix 1.

P.S.: I will publish later examle of this CMYK-to-Spot idea.

krticka · 2019-05-02T11:03:11Z

Of course, Map Commission is working on new Appendix. I understand your needs, but unfortunately we are not publishing robots to be able to publish every week new and new documents.

…

---------- Původní e-mail ---------- Od: app4soft <[email protected]> Komu: OpenOrienteering/mapper <[email protected]> Datum: 2. 5. 2019 12:50:52 Předmět: Re: [OpenOrienteering/mapper] Update ISOM 2017 to rev.2018-11 (# 1187) "" I wonder if the Appendix should really be taken literally. I can't remember it being discussed before publishing. " Yeah, on Facebook many mappers tells the same: Appendix 1 should be fixed or fully rewrited for ISOM2017-2 , ISSprOM2019 and upcoming specs. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub (#1187 (comment)) , or mute the thread (https://github.com/notifications/unsubscribe-auth/ADZ2ZGWSZ7T2UYYLTQ4MWFDPTLBQHANCNFSM4GHK45OQ) . "

ghost · 2019-05-02T11:14:12Z

Map Commission is working on new Appendix.

@krticka , can MC create own GitHub repo for organize public development on IOF specifications for orientering maps?

Then mappers community could help fix issues before it would be realeased! ;-)

yevhenmazur · 2019-05-02T11:28:59Z

Could @Symbian9 share his progress in relevant GitHub repo for organize public development? Then mappers community could help with his tasks and they will not hang in status "work in progress" for two years, like #694

ghost · 2019-05-02T11:35:35Z

Could @Symbian9 share his progress in relevant GitHub repo for organize public development?

@yevhenmazur as you can see this pull request based on my braches with patches & all them are public

https://github.com/Symbian9/mapper/branches

Then mappers community could help with his tasks and they will not hang in status "work in progress" for two years, like #694

What? My "Topographic" symbol sets not related to current pull requrest or official IOF MC's specifications.

ghost · 2019-05-02T21:12:01Z

Offset names > Spot

CMYK values of Offset names > Spot

Appendix 1 Mistakes

There NO CMYK values for CMYK (non-offset) colors! How should we adjust such colors (to still NOT available "PrintTech 2018/2019 Test Sheet") if we don't know initial values?
There are NO "Green 30%" and "Green 60%" that mentioned in ISOM2019.
There are NO new "PrintTech 2018/2019 Testsheets" yet.
Names of colours for CMYK printing is not clear: why Black and not Black 100%?; where is Black (for borders)?; also some extra , added in "Blue 100% (areas, marshes,)" name (or there should be some word after last ,?).

lpechacek · 2019-07-04T06:49:49Z

@Symbian9, if I'm not mistaken, over past months IOF MC have published information giving answers to many of your questions. Has there been progress on updating the ISOM symbol set, please?

dg0yt · 2019-09-22T10:31:03Z

PR replaced #1363.

app4soft added 2 commits November 30, 2018 01:19

Update ISOM 2017 to rev.2018-11

e8f66b4

Update ISOM2017_15000.xmap

2f95906

Remove symbols 411.1 and 411.2 and related object on map.

dg0yt reviewed Nov 30, 2018

View reviewed changes

lpechacek mentioned this pull request Nov 30, 2018

ISOM 2017-2 #1184

Closed

valdisj reviewed Mar 20, 2019

View reviewed changes

dg0yt closed this Sep 22, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update ISOM 2017 to rev.2018-11 #1187

Update ISOM 2017 to rev.2018-11 #1187

ghost commented Nov 29, 2018 •

edited by ghost

Loading

dg0yt Nov 30, 2018

krticka Dec 1, 2018

krticka Dec 1, 2018

ghost Dec 1, 2018 •

edited by ghost

Loading

krticka Dec 2, 2018

ghost Dec 2, 2018 •

edited by ghost

Loading

valdisj left a comment

ghost commented Mar 20, 2019 •

edited by ghost

Loading

dg0yt commented Mar 22, 2019 •

edited

Loading

ghost commented Apr 4, 2019

ghost commented May 1, 2019 •

edited by ghost

Loading

dg0yt commented May 2, 2019

ghost commented May 2, 2019 •

edited by ghost

Loading

krticka commented May 2, 2019 via email

ghost commented May 2, 2019

yevhenmazur commented May 2, 2019

ghost commented May 2, 2019 •

edited by ghost

Loading

ghost commented May 2, 2019 •

edited by ghost

Loading

lpechacek commented Jul 4, 2019

dg0yt commented Sep 22, 2019

Update ISOM 2017 to rev.2018-11 #1187

Update ISOM 2017 to rev.2018-11 #1187

Conversation

ghost commented Nov 29, 2018 • edited by ghost Loading

dg0yt Nov 30, 2018

Choose a reason for hiding this comment

krticka Dec 1, 2018

Choose a reason for hiding this comment

krticka Dec 1, 2018

Choose a reason for hiding this comment

ghost Dec 1, 2018 • edited by ghost Loading

Choose a reason for hiding this comment

krticka Dec 2, 2018

Choose a reason for hiding this comment

ghost Dec 2, 2018 • edited by ghost Loading

Choose a reason for hiding this comment

valdisj left a comment

Choose a reason for hiding this comment

ghost commented Mar 20, 2019 • edited by ghost Loading

dg0yt commented Mar 22, 2019 • edited Loading

ghost commented Apr 4, 2019

ghost commented May 1, 2019 • edited by ghost Loading

dg0yt commented May 2, 2019

ghost commented May 2, 2019 • edited by ghost Loading

krticka commented May 2, 2019 via email

ghost commented May 2, 2019

yevhenmazur commented May 2, 2019

ghost commented May 2, 2019 • edited by ghost Loading

ghost commented May 2, 2019 • edited by ghost Loading

Offset names > Spot

CMYK values of Offset names > Spot

Appendix 1 Mistakes

lpechacek commented Jul 4, 2019

dg0yt commented Sep 22, 2019

ghost commented Nov 29, 2018 •

edited by ghost

Loading

ghost Dec 1, 2018 •

edited by ghost

Loading

ghost Dec 2, 2018 •

edited by ghost

Loading

ghost commented Mar 20, 2019 •

edited by ghost

Loading

dg0yt commented Mar 22, 2019 •

edited

Loading

ghost commented May 1, 2019 •

edited by ghost

Loading

ghost commented May 2, 2019 •

edited by ghost

Loading

ghost commented May 2, 2019 •

edited by ghost

Loading

ghost commented May 2, 2019 •

edited by ghost

Loading