Changes between Initial Version and Version 1 of Ticket #4711, comment 2


Ignore:
Timestamp:
06/29/20 11:03:16 (4 years ago)
Author:
dannytoone

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #4711, comment 2

    initial v1  
    11I believe I have a reproducible example using generated data. Please let me know if you have any problems with running or generating the dataset.
    22
    3 Unfortunately, the geometries are not simple, and simple geometries did not reproduce this bug, so creating a dataset that recreates the bug is not simple.
     3Unfortunately, the geometries are not simple, and simple geometries did not reproduce this bug, so creating a dataset that reproduces the bug is not simple.
    44
    55For background, the data I'm working on, that I'm trying to emulate with this generated data set, is roughly analogous to the license geometries in the MDS/ITFS frequency bands (2.5-2.7ghz), as regulated by the FCC. They do not overlap when viewing the same frequencies, but across frequencies they may overlap. The following temp tables set up a data structure that is somewhat similar to these license boundaries.
     
    101101
    102102=======================
     103
    103104Okay, that is the underlying data. Now onto the actual bug. This table is merely the processed geometries as an exterior ring linestring.
    104105