Skip to main content
Solved

Checking for unnecessary polygon boundaries

dfresh
Forum|alt.badge.img

Does anyone know how you would go about acheiving this in FME? I will post progress as I make it.

http://desktop.arcgis.com/en/arcmap/latest/extensions/data-reviewer/checking-for-unnecessary-polygon-boundaries.htm

Best answer by dfresh

Ok, I finally got around to finishing this, only took 20 minutes to implement and validate.

  1. Dissolver (all attributes, except OBJECTID/UID)
  2. Duplicate Filter - duplicates are equal to Unesscary Polygon Boundaries

View original
    Did this help you find an answer to your question?

    3 replies

    A
    Forum|alt.badge.img+6

    Hi @dfresh,

    I'm not sure if this totally addresses your workflow, but the Dissolver (https://docs.safe.com/fme/2017.1/html/FME_Desktop_Documentation/FME_Transformers/Transformers/dissolver.htm) might be a good place to start.

    We have this article that uses the example of dissolving boundaries based on election results : https://knowledge.safe.com/articles/28997/merging-polygons-with-the-dissolver-transformer.html

    dfresh
    Forum|alt.badge.img
    • dfresh
    • Author
    • January 5, 2018
    annabelleatsafe wrote:

    Hi @dfresh,

    I'm not sure if this totally addresses your workflow, but the Dissolver (https://docs.safe.com/fme/2017.1/html/FME_Desktop_Documentation/FME_Transformers/Transformers/dissolver.htm) might be a good place to start.

    We have this article that uses the example of dissolving boundaries based on election results : https://knowledge.safe.com/articles/28997/merging-polygons-with-the-dissolver-transformer.html

    Thanks @AnnabelleAtSafe, I will definitely need to use the Dissolver, however I will be running this dynamically or different feature classes where the attributes could change between feature class. so defining editable fields dynamically could be the one I need to address

     

    dfresh
    Forum|alt.badge.img
    • dfresh
    • Author
    • Best Answer
    • January 19, 2018

    Ok, I finally got around to finishing this, only took 20 minutes to implement and validate.

    1. Dissolver (all attributes, except OBJECTID/UID)
    2. Duplicate Filter - duplicates are equal to Unesscary Polygon Boundaries

    Reply


    Helpful Members This Week

    Community Stats

    31,345
    Posts
    118,890
    Replies
    38,960
    Members

    Latest FME

    Terms & ConditionsCookie settings

    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
    A product of
    Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.