Hi Ticker,
reg. Also thinking that shapeMerge might need to operate at highPrecision :
ShapeMerger doesn't compare positions, it checks for identical Coords.
For the overview map the ovm_* data is read and MapBuilder.prepShapesForMerge()
is used to make equal Coord instances identical. This is n
Hi Mike,
sorry, that slipped my mind.
I've not tried it yet but I think the deprecated --check-roundabouts option
should be interpreted as --fix-roundabout-direction
so that the IMG file is the same as before.
The message "... reversing it " is logged when --check-roundabouts is used but
the w
Hi Gerd,
I have already sent you the roundabout checks patch which covers both of the
requests. It may have got missed as I know you are heavily involved in other
issues at the moment. I've attached a copy.
Cheers,
Mike
-Original Message-
From: Gerd Petermann [mailto:gpetermann_muenc...@
Hi Gerd
I'm getting worried by rounding-to-resolution and how often it creates
self-intersection.
When doing the shapeSplitter.splitShape, we found that, unless
operating with high-precision points (ie there were problems at 24bit
precision), it could fail because of self-intersection.
The polyg
Hi Mike,
I've hoped for a patch reg. the messages about roundabouts for users without a
logging.config.
I think we need a way to enable the functionality of reversing roundabouts
(done in StyledConverter) without also getting all the check messages from
RoadNetwork.
Gerd
_
Hi Ticker,
I've attached a test case that shows how the order is important. Depending on
the order of shapes to be merged the resulting shape sometimes is
self-intersecting, sometimes it isn't.
I've not yet understood what the trigger is.
Gerd
Von: mkg
