Skip to main content
Question

invalid geometry type

  • October 14, 2020
  • 5 replies
  • 980 views

gisbradokla
Enthusiast
Forum|alt.badge.img+17

I am getting a rejection of one line in my wb that seems to be valid.

as per safe documentation i have place a geometry validator and geometrycoercer into the workflow. yet it is still rejected

Why would this be getting rejected for invalid geometry type?

geocoercer

with these parameters on the validator.

validatorparameters

Feature Type MValue_OUTPUT

Coordinate System NM83-EF

Dimension 3D

Number of Vertices 2

Min Extents 7764.78954863, 4086.494, 3384.991

Max Extents 7764.868, 4086.956395047, 3385.0004943987096

Attributes (61)

  _elevation 3384.991

  Alignment_Sheet_Status COMPLETE

  autocad_color 12

  autocad_entity autocad_line

  autocad_entity_visibility visible

  autocad_layer_desc

  autocad_layer_frozen no

  autocad_layer_hidden no

  autocad_layer_locked no

  autocad_layer_on yes

  autocad_layer_plottable yes

  autocad_linetype ByLayer

  autocad_linetype_scale 1

  autocad_lineweight -1

  autocad_original_color ByLayer

  autocad_original_entity_type autocad_3dPolyline

  autocad_resolved_linetype CONTINUOUS

  autocad_source_filename S:\\SURVEY\\AN\\GREEN_RAKE\\ASBUILT\\WORKING\\GREEN_RAKE.dwg

  autocad_space model_space

  autocad_thickness 0

  autocad_ucs_applied No

  autocad_ucs_origin_x 0

  autocad_ucs_origin_y 0

  autocad_ucs_origin_z 0

  autocad_ucs_xdir_x 1

  autocad_ucs_xdir_y 0

  autocad_ucs_xdir_z 0

  autocad_ucs_ydir_x 0

  autocad_ucs_ydir_y 1

  autocad_ucs_ydir_z 0

  autocad_vertexflag 0,0

  BEGIN_MEAS

  CL_Status

  Description SITE PIPE

  Diameter 6

  END_MEAS

  fme_basename GREEN_RAKE

  fme_color 0.65,0,0

  fme_dataset S:\\SURVEY\\AN\\GREEN_RAKE\\ASBUILT\\WORKING\\GREEN_RAKE.dwg

  fme_feature_type AB_PIPE_3D

  fme_geometry fme_line

  fme_type fme_line

  HYPERLINK

  In_Service_Date

  Layer

  LINE_ID 2

  M_Length

  multi_reader_full_id 0

  multi_reader_id 0

  multi_reader_keyword REALDWG_1

  multi_reader_type REALDWG

  Phase AB

  PipeType

  Route_Id 7CE7

  Source Brancher 0.BranchingFactory.Count 1

  Source Feature Router.BranchingFactory.Count 1

  State

  STATUS

  System AB_GREEN_RAKE

IFMELine (2 Coordinates) (776419.868, 408660.494, 3384.991), (776419.7895486304, 408660.956395047, 3385.0004943987096)

  Closed No

  Measures (1) <default_measure>

  Coordinates (2) Coordinate Dimension: 3

    0 7764.868, 4086.494, 3384.991 <0>

    1 7764.7895486304, 4086.956395047, 3385.0004943987096 <0.46900298176280636>

5 replies

ebygomm
Influencer
Forum|alt.badge.img+39
  • Influencer
  • October 14, 2020

What transformer is MValue?


gisbradokla
Enthusiast
Forum|alt.badge.img+17
  • Author
  • Enthusiast
  • October 14, 2020
ebygomm wrote:

What transformer is MValue?

measuregeneratormeasuregenerator


virtualcitymatt
Celebrity
Forum|alt.badge.img+38

From the looks of the feature you've shared it's from the Output port rather than the Rejected port.​ are you able to share the summary of the rejected feature?


caracadrian
Contributor
Forum|alt.badge.img+23
  • Contributor
  • October 15, 2020

Inspect the Rejected port of your MValue transformer and check the Rejection Code.

That always tells you the reason. Probably Invalid Geometry Type in your case. My guess as an Autocad user is that you have a 0 length polyline.


ebygomm
Influencer
Forum|alt.badge.img+39
  • Influencer
  • October 15, 2020
caracadrian wrote:

Inspect the Rejected port of your MValue transformer and check the Rejection Code.

That always tells you the reason. Probably Invalid Geometry Type in your case. My guess as an Autocad user is that you have a 0 length polyline.

My guess would be a path/multi part geometry. This would pass the GeometryValidation tests but be rejected by the measure generator

My guess as an Autocad user is that you have a 0 length polyline.

The MeasureGenerator doesn't actually complain about a 0 length line


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings