I have two versions of GeoJSON data for the same floor where I need to identify changes for both geometries and attributes (example original data has 73 rooms and later modified like two rooms merged into single,two more rooms created by partitioning of one room and revised data makes it to 72 rooms). Now I have tried to check these changes using Change detector tool the output result differs for attributes and geometries.I have used latest beta 2019 desktop as the enhanced version of Change detector available.Please suggest me I have attached the workbench snapshots with results.Where for only attributes I get fairly good result for deleted,added areas but not for the updated areas. Where for only geometries I get everything to be updated .Please note the work-space reads original data queried from SQL database and the revised data from GeoJSON reader but both data has been extracted as GeoJSON with parameter precision 7 in the workspace.Please suggest how to get the proper result.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+56- Safer
- 2554 replies
I think we'd really need to see the parameters used in the ChangeDetector. I would say the 3 rooms are showing up as Deleted (the original) and Inserted (the new ones). You'll only get Updated if you have a Join attribute set (ie the rooms have an ID number that will match so FME can tell that this is a change, and not a deletion/addition).
The other potential issues would be the Check Geometry settings. What do you have for Match Geometry? Do you have Lenient Matching turned on? And what tolerance do you have?
Thanks for your reply @Mark2AtSafe.
Attribute Compare : I have attached snapshots for the parameters used.Original rooms have unique ID values but I need to check these rooms with revised rooms where revised data has all rooms with new ID generated from other workbench (I cannot match common ID).I need to check only for changes in the other Attributes and update the database columns for the changes and keeping other unchanged columns.I think Change detector satisfy the result here.
Geometry Compare : I have attached snapshots from two workbenches with parameters
1. I have two Geo Database (original and Revised) for the same earlier example where change detector outputs desired result (Workbench_GDB_Compare.png,Desired_Result.png).This is what actually required for me to write/update the existing database with changes.
2. Earlier Original Geo database was written to sql database after converting it to GeoJson format as per the requirement and now revised Geodatabase also converted to GeoJson format but need to be checked for any changes with original data in sql database.But I am not getting same desired output once the original/revised data are converted to other formats.Please suggest .desired-result.pngworkbench-gdb-compare.pngchangedetector-lenientgeometry.pngchangedetector-vectortolerance.png(Attached ChangeDetector_LenientGeometry.png,ChangeDetector_VectorTolerance.png)
I think we'd really need to see the parameters used in the ChangeDetector. I would say the 3 rooms are showing up as Deleted (the original) and Inserted (the new ones). You'll only get Updated if you have a Join attribute set (ie the rooms have an ID number that will match so FME can tell that this is a change, and not a deletion/addition).
The other potential issues would be the Check Geometry settings. What do you have for Match Geometry? Do you have Lenient Matching turned on? And what tolerance do you have?
Attribute Compare : I have attached snapshots for the parameters used.
Geometry Compare : I have checked with direct Geo Database reader (original gdb and Revised gdb) where change detector outputs desired result.(Workbench_GDB_Compare.png,Desired_Result.png).This is what actually required for me to write/update the existing database with changes.
Now the issue is these original gdb features has been written to sql db after converting it to GeoJson format with added attribute information and Now I need to check these with the revised data which is also converted from gdb to GeoJson format with same attributes or changed. Change detector geometry output differs,Is this due to number of decimal places?
(Attached ChangeDetector_LenientGeometry.png,ChangeDetector_VectorTolerance.png)
+56- Safer
- 2554 replies
Attribute Compare : I have attached snapshots for the parameters used.
Geometry Compare : I have checked with direct Geo Database reader (original gdb and Revised gdb) where change detector outputs desired result.(Workbench_GDB_Compare.png,Desired_Result.png).This is what actually required for me to write/update the existing database with changes.
Now the issue is these original gdb features has been written to sql db after converting it to GeoJson format with added attribute information and Now I need to check these with the revised data which is also converted from gdb to GeoJson format with same attributes or changed. Change detector geometry output differs,Is this due to number of decimal places?
(Attached ChangeDetector_LenientGeometry.png,ChangeDetector_VectorTolerance.png)