Hi,everyone,I've got two versions of a FGDB polygon feature class(original and revised),I'd like to use ChangeDetector two find the differences between them.But the output result was very odd,some added or deleted polygons looked exactly and had seem attributes.I only created a topology dataset to fix overlaps and gaps in revised data,I figureed this is issue.Then I tried the same 亚搏在线workflow with my backup data.As expected,I got less output through added and deleted port,and most odd results were not there any more.
I browsed FME Knowledge Center about ChangeDetector and I find thisquestionis most likely the reason caused my problem.But all my data are stored in FGDB not SDE.And all FGDBs have same parameters which are default.
Further more,my data is stored in longitude and latitude,if a CoordinteRounder is needed I'm not sure how to set the precision parameter.
Add the fourth dimension to the CoordinateRounder,so that it will be able to round not only XYZ but also M (measures,used in linear referencing).
The current coordinaterounder transformer only rounds coordinates to the nearest value,while the attributerounder does offer the possibility to set the Round-off Direction to UP,Down or Nearest.
Some GIS software (like Hexagon gTechnology) rounds coordinates down internally,to a certain decimal (set in the gTechnology setting) when it validates connectivity.
Because the coordinaterounder transformer cannot round coordinates down,FME cannot produce the same results as gTechnology when checking the connectivity.
Could the Attribute & CoordinateRounders possibly offer the chance to round to a number of significant digits?I'm currently doing it by calculating the length of the number before the decimal,but it would be nice to have this baked in.
Hi,I would like to round a elevation value to the nearest even number.Is there a way to do this,perhaps using AttributeRounder or CoordinateRounder?
I am using FME Desktop 2016.
Thanks
I seem to have a strange problem with the coordinate rounder.It looks like a bug actually,as I didn't have this issue in FME2016:
I have read some features from an autodesk drawing (dwg).After using my coordinateRounder the information about entity type is deleted (see also the figures 1-3).It isn't that hard to make a workaround for this issue,but I don't understand why this is happening.I already found out that this isn't always happening with coordinateRounder.
Does anybody have an idea?
fme-fig1.jpgfme-fig2.jpgfme-fig3.jpg