Re: [CF-metadata] [cf-convention/cf-conventions] Correct errors in 1.9 Lossy Compression by Coordinate Subsampling (PR #351)
Merged #351 into main. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/351*event-6037923035__;Iw!!G2kpM7uM-TzIFchu!mbCX7jteYxYbUvnSxb9Z3MzO_EX9Fc8joVlvBebWKmctZ_wGYsxaY-VVqJWGj-yiYAf3DpGKJfA$ You are receiving this because you are subscribed to this thread. Message ID: This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Correct errors in 1.9 Lossy Compression by Coordinate Subsampling (Issue #352)
Closed #352 via #351. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/352*event-6037923068__;Iw!!G2kpM7uM-TzIFchu!md6sgOXyfHUbyYvlM86gi8F03o_JmZTKgSY9-8I5KdBuufg9apTX_OewDbTh-lJvEkWBw56jnWI$ You are receiving this because you are subscribed to this thread. Message ID: This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Correct errors in 1.9 Lossy Compression by Coordinate Subsampling (Issue #352)
Hello, no one has objected to these defect corrections for over three weeks, so according to the rules they may be accepted. I shall the associated Pull Request. Many thanks, David -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/352*issuecomment-1034284924__;Iw!!G2kpM7uM-TzIFchu!niWvvjPIE0-FNoL23kuNN6MTClygeSmtxsIZ5-ly7wqTB3zh6hSXmGccA5nNnjwaPX-F2QfSUs0$ You are receiving this because you are subscribed to this thread. Message ID: This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Are geometries allowed to self-intersect? (Issue #354)
The role of CF is rules for metadata, which is mainly labeling and data structures. CF should try to stay within that role and avoid content details, notwithstanding the current complexity of section 7.5. Geometry consistency and compatibility is well addressed by other conventions. CF should either remain silent on the consistency of geometry, or else simply state that it is not regulated. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/354*issuecomment-1034043584__;Iw!!G2kpM7uM-TzIFchu!gtpTj0ZoFJ36jdhjFQGryoTN3K3H9yqpA4WR0sLU14E_S2OHXrbgx7FaYCiBjT4vcYwG15EfCVU$ You are receiving this because you are subscribed to this thread. Message ID: This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Are geometries allowed to self-intersect? (Issue #354)
My experience of spatial databases (Oracle Spatial about 5 years ago) is that self-intersections caused the geometry to be tagged as invalid forcing it to be constructed from a collection of simple polygons. Geometries need to work with established tools which will dictate any standards. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/354*issuecomment-1034008744__;Iw!!G2kpM7uM-TzIFchu!gKbD4cTfQ6lWt8VND8mBwVnLDQjf30TwNtLITAZCvrbreSMwk7Vnf1c4nbutm8JgWbbpLtE1lv4$ You are receiving this because you are subscribed to this thread. Message ID: This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Update two mentions of 1.8 to 1.9 (PR #355)
Definitely. I looked for something that replace 1.9 but nothing as advanced as a variable replace. :+1: All the best. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/355*issuecomment-1033849621__;Iw!!G2kpM7uM-TzIFchu!lKL7SumetogxDJb0Nbp0NLFMZdTvRNJndzFDJCD8sGoPs1BWQVOIxBYe7LB710gMqrapPJoNfyc$ You are receiving this because you are subscribed to this thread. Message ID: This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Update two mentions of 1.8 to 1.9 (PR #355)
Closed #355. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/355*event-6035012283__;Iw!!G2kpM7uM-TzIFchu!iCykWsi3b0KtbQ5WJOGQDSOOm-UZ1cO5vWw9HYaH_sWtabl5LMSFS9exIHFcB5NOK8dpqdySwUw$ You are receiving this because you are subscribed to this thread. Message ID: This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Are geometries allowed to self-intersect? (Issue #354)
We have lots and lots of polygons with self intersections where the polygon closes on itself at a node. It may not cross but it does need to pinch off an open back up -- so an intersection is real. I don't think CF should have a horse in this race.  -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/354*issuecomment-1033819238__;Iw!!G2kpM7uM-TzIFchu!kNeKNt30i4nyNbtq4xz3R83LbtC7lUdC0abKC04EeOxZsy4iezJNnMt82VfRxN43QC6bfAXIhas$ You are receiving this because you are subscribed to this thread. Message ID: This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Are geometries allowed to self-intersect? (Issue #354)
There certainly are ways to interpret self-intersecting polygons in a consistent manner. But is there a use-case for this in the realm of CF? For self-intersecting lines, this seems clear (any kind of route, for instance, from ships, planes, etc.), but for polygons, I struggle. Hence my intuition would be to at least discourage their use. For a better understanding, I would rather look to other geo packages and standards than to inspiration from the world of graphic design. Starting points might be [Shapely](https://urldefense.us/v3/__https://shapely.readthedocs.io__;!!G2kpM7uM-TzIFchu!idhAoQ76_ui8lY2teNnycaX33NT7fBg4C2u4JKx1kuasbE4jZwXtJtlmIkPoubWnl7OBjzfFja0$ ), [GEOS](https://urldefense.us/v3/__https://libgeos.org/__;!!G2kpM7uM-TzIFchu!idhAoQ76_ui8lY2teNnycaX33NT7fBg4C2u4JKx1kuasbE4jZwXtJtlmIkPoubWnl7OBI5FEIHc$ ), or the OGC's [Simple Feature Access](https://urldefense.us/v3/__https://www.ogc.org/standards/sfa__;!!G2kpM7uM-TzIFchu!idhAoQ76_ui8lY2teNnycaX33NT7fBg4C2u4JKx1kuasbE4jZwXtJtlmIkPoubWnl7OBYYQPP4U$ ). -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/354*issuecomment-1033792476__;Iw!!G2kpM7uM-TzIFchu!idhAoQ76_ui8lY2teNnycaX33NT7fBg4C2u4JKx1kuasbE4jZwXtJtlmIkPoubWnl7OB30-khCg$ You are receiving this because you are subscribed to this thread. Message ID: This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Update two mentions of 1.8 to 1.9 (PR #355)
Thanks for the report, @joshmoore. I think this is the same issue that has been discussed in #343 together with the solution in #344. Is this correct? Do those address the issue satisfactorily for you? -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/355*issuecomment-1033782131__;Iw!!G2kpM7uM-TzIFchu!m-N6gbbcckCGdIJ90wsO8nImDTCisyay-JiYMizzd3s_OE7_9PU6vYvZD6c79qBeiKLzImsaw8w$ You are receiving this because you are subscribed to this thread. Message ID: This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
[CF-metadata] [cf-convention/cf-conventions] Update two mentions of 1.8 to 1.9 (PR #355)
Two locations mention that the value CF-1.8 MUST be used for conforming datasets. Naively I assumed that these values should be updated 1.9. (Looking at previous commits like https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/commit/b6c65807a7dbf1eb78d6f711cd079296d7f43b63__;!!G2kpM7uM-TzIFchu!kdsYYzpn1sSrYOLu4BbZ9a4Q_JEOvdKtyNhBodgcydpI-tRHLVwGrBShOJnKK8tm5Gi6gYRR-PE$ this looks to be the case.) You can view, comment on, or merge this pull request online at: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/355__;!!G2kpM7uM-TzIFchu!kdsYYzpn1sSrYOLu4BbZ9a4Q_JEOvdKtyNhBodgcydpI-tRHLVwGrBShOJnKK8tm5Gi6z8Jf1pU$ -- Commit Summary -- * Update two mentions of 1.8 to 1.9 -- File Changes -- M ch01.adoc (2) M ch02.adoc (2) -- Patch Links -- https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/355.patch__;!!G2kpM7uM-TzIFchu!kdsYYzpn1sSrYOLu4BbZ9a4Q_JEOvdKtyNhBodgcydpI-tRHLVwGrBShOJnKK8tm5Gi6bHezVZI$ https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/355.diff__;!!G2kpM7uM-TzIFchu!kdsYYzpn1sSrYOLu4BbZ9a4Q_JEOvdKtyNhBodgcydpI-tRHLVwGrBShOJnKK8tm5Gi63qrg5CI$ -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/355__;!!G2kpM7uM-TzIFchu!kdsYYzpn1sSrYOLu4BbZ9a4Q_JEOvdKtyNhBodgcydpI-tRHLVwGrBShOJnKK8tm5Gi6z8Jf1pU$ You are receiving this because you are subscribed to this thread. Message ID: cf-convention/cf-conventions/pull/3...@github.com This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Are geometries allowed to self-intersect? (Issue #354)
I think that the main implication of allowing self intersecting edges of a polygon (like the possibly 5, probably 2 1/2 sided polygon from @davidhassell above) is people may use the wrong inside/outside algorithms and get unexpected results. The main ones are left-hand/right-hand, winding number, and counting crossings from infinity. [SVG explains this well](https://urldefense.us/v3/__https://www.w3.org/TR/2008/REC-SVGTiny12-20081222/painting.html*FillProperties__;Iw!!G2kpM7uM-TzIFchu!lIB46xeb5nsg2wV7IoDKCNIKLo7_2QKW5ufYHnvhvMZdkU_QvWQJFseoAfGRLiGTZSfr9KW70vQ$ ). As people often choose the wrong algorithm anyway, I think allowing self-intersecting edges is OK, as it is the most general case, and "less is more". Whether implementations cope with multi-part, self-intersecting polygons is another issue. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/354*issuecomment-1033729094__;Iw!!G2kpM7uM-TzIFchu!lIB46xeb5nsg2wV7IoDKCNIKLo7_2QKW5ufYHnvhvMZdkU_QvWQJFseoAfGRLiGTZSfrlUYk9WQ$ You are receiving this because you are subscribed to this thread. Message ID: This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Are geometries allowed to self-intersect? (Issue #354)
Hello, I agree with Dave that there are no rules on that, but I'd like to fully understand what you are suggesting for polygons. Do you mean "are different _parts_ of a multi-part polygon allowed to overlap" or do you mean "are different _edges_ of an individual polygon part allowed to intersect"? The latter case could look like this polygon part with 5 nodes:  Thanks, David -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/354*issuecomment-1033536206__;Iw!!G2kpM7uM-TzIFchu!jbQAMADur0S6xcPG1SJ9QlcK1lll2cbwrWsNDlSAG8gq1q-ivcLSpBXvv7t4-b0s2E1Jhiws88E$ You are receiving this because you are subscribed to this thread. Message ID: This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
