Version = 2013_2b_609
Category = Other (ComplianceManager API)
IES Reference: 0071872
Hello, it appears that the treatment of small geometry elements has been
improved/corrected in v3 of the API, can you confirm this.
For example the following polyloop (area approx. 0.08 ft2) is flagging an area
error in v2b, but passes in v3.
<PolyLp>
<CartesianPt><Coord>199.467936</Coord><Coord>-225.130027</Coord><Coord>53.166667
</Coord></CartesianPt>
<CartesianPt><Coord>199.463901</Coord><Coord>-225.130029</Coord><Coord>53.166667
</Coord></CartesianPt>
<CartesianPt><Coord>199.463901</Coord><Coord>-168.206439</Coord><Coord>53.166667
</Coord></CartesianPt>
</PolyLp>
Other than deleting such elements from the model, are there any possible
workarounds we can give our customers, until the IES link to v3 is available?
A sample customer XML is attached.
Note that this one also produces an error from a Space footprint polygon (line
48430), and the customer cannot be expected to delete this Space.
Error: Range check failure on Space 'PF2_2B28.33: PRACTICE FACILITIES'. Value
being checked = 0. Error if not greaternot than or equal to 0.01 (Spc:Area)
Original issue reported on code.google.com by f.le...@gmail.com on 12 Sep 2014 at 12:09
Original issue reported on code.google.com by
f.le...@gmail.comon 12 Sep 2014 at 12:09Attachments: