Skip to main content
Best Answer

GEoJSON geometry replacement issue.

  • September 11, 2018
  • 5 replies
  • 92 views
amolparande
Forum|alt.badge.img+1

Hello everyone ,

I have two JSON files

1. RoadElement.json

2. WaterArea.json

I want to create geometry from each JSON file that would be polyline

& Polygon features

I have also created FME workbench but could not able to

create Geometry having some problem can any one help me what is wrong?

Please find attached JSON file and created Workbench

Best answer by nielsgerrits

I think the data doesn't validate as correct GeoJSON.

The structure for a polygon feature should be:

{
    "type": "Polygon",
    "coordinates": [
        [
            [
                100,
                0
            ],
            [
                101,
                0
            ],
            [
                101,
                1
            ],
            [
                100,
                1
            ],
            [
                100,
                0
            ]
        ]
    ]
}

Where a piece in waterarea.json is:

{
	"type": "coordinates",
	"coordinates": [[145.71758,
	-30.83595],
	[145.71769,
	-30.83532],
	[145.71895,
	-30.8348],
	[145.72022,
	-30.83381],
	[145.72158,
	-30.83383],
	[145.72241,
	-30.83428],
	[145.72374,
	-30.83646],
	[145.72404,
	-30.83773],
	[145.72403,
	-30.83846],
	[145.72028,
	-30.83697],
	[145.71872,
	-30.83623],
	[145.71758,
	-30.83595]]
}

Issues are:

  • type should be Polygon, not coordinates (case sensitive!)
  • the array of coordinates should be nested one level deeper (rings, ring, coordinatepairs)
  • polygons should follow the right-hand rule (exterior rings are counter clockwise, interior rings / holes are clockwise)

See the spec.

This works for me:

{
	"type": "Polygon",
	"coordinates": [[[145.71758,
	-30.83595],
	[145.71872,
	-30.83623],
	[145.72028,
	-30.83697],
	[145.72403,
	-30.83846],
	[145.72404,
	-30.83773],
	[145.72374,
	-30.83646],
	[145.72241,
	-30.83428],
	[145.72158,
	-30.83383],
	[145.72022,
	-30.83381],
	[145.71895,
	-30.8348],
	[145.71769,
	-30.83532],
	[145.71758,
	-30.83595]]]
}
This post is closed to further activity.
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.

5 replies

nielsgerrits
VIP
Forum|alt.badge.img+64
  • nielsgerritsVIP
  • Best Answer
  • September 11, 2018

I think the data doesn't validate as correct GeoJSON.

The structure for a polygon feature should be:

{
    "type": "Polygon",
    "coordinates": [
        [
            [
                100,
                0
            ],
            [
                101,
                0
            ],
            [
                101,
                1
            ],
            [
                100,
                1
            ],
            [
                100,
                0
            ]
        ]
    ]
}

Where a piece in waterarea.json is:

{
	"type": "coordinates",
	"coordinates": [[145.71758,
	-30.83595],
	[145.71769,
	-30.83532],
	[145.71895,
	-30.8348],
	[145.72022,
	-30.83381],
	[145.72158,
	-30.83383],
	[145.72241,
	-30.83428],
	[145.72374,
	-30.83646],
	[145.72404,
	-30.83773],
	[145.72403,
	-30.83846],
	[145.72028,
	-30.83697],
	[145.71872,
	-30.83623],
	[145.71758,
	-30.83595]]
}

Issues are:

  • type should be Polygon, not coordinates (case sensitive!)
  • the array of coordinates should be nested one level deeper (rings, ring, coordinatepairs)
  • polygons should follow the right-hand rule (exterior rings are counter clockwise, interior rings / holes are clockwise)

See the spec.

This works for me:

{
	"type": "Polygon",
	"coordinates": [[[145.71758,
	-30.83595],
	[145.71872,
	-30.83623],
	[145.72028,
	-30.83697],
	[145.72403,
	-30.83846],
	[145.72404,
	-30.83773],
	[145.72374,
	-30.83646],
	[145.72241,
	-30.83428],
	[145.72158,
	-30.83383],
	[145.72022,
	-30.83381],
	[145.71895,
	-30.8348],
	[145.71769,
	-30.83532],
	[145.71758,
	-30.83595]]]
}
Buckle your seatbelt Dorothy, cause Kansas is going bye-bye...
amolparande
Forum|alt.badge.img+1
  • amolparande
  • Author
  • September 11, 2018

I think the data doesn't validate as correct GeoJSON.

The structure for a polygon feature should be:

{
    "type": "Polygon",
    "coordinates": [
        [
            [
                100,
                0
            ],
            [
                101,
                0
            ],
            [
                101,
                1
            ],
            [
                100,
                1
            ],
            [
                100,
                0
            ]
        ]
    ]
}

Where a piece in waterarea.json is:

{
	"type": "coordinates",
	"coordinates": [[145.71758,
	-30.83595],
	[145.71769,
	-30.83532],
	[145.71895,
	-30.8348],
	[145.72022,
	-30.83381],
	[145.72158,
	-30.83383],
	[145.72241,
	-30.83428],
	[145.72374,
	-30.83646],
	[145.72404,
	-30.83773],
	[145.72403,
	-30.83846],
	[145.72028,
	-30.83697],
	[145.71872,
	-30.83623],
	[145.71758,
	-30.83595]]
}

Issues are:

  • type should be Polygon, not coordinates (case sensitive!)
  • the array of coordinates should be nested one level deeper (rings, ring, coordinatepairs)
  • polygons should follow the right-hand rule (exterior rings are counter clockwise, interior rings / holes are clockwise)

See the spec.

This works for me:

{
	"type": "Polygon",
	"coordinates": [[[145.71758,
	-30.83595],
	[145.71872,
	-30.83623],
	[145.72028,
	-30.83697],
	[145.72403,
	-30.83846],
	[145.72404,
	-30.83773],
	[145.72374,
	-30.83646],
	[145.72241,
	-30.83428],
	[145.72158,
	-30.83383],
	[145.72022,
	-30.83381],
	[145.71895,
	-30.8348],
	[145.71769,
	-30.83532],
	[145.71758,
	-30.83595]]]
}
Thank you for replay 

 

What is Wrong with Roadelement.json ?

 

 

nielsgerrits
VIP
Forum|alt.badge.img+64
Thank you for replay

 

What is Wrong with Roadelement.json ?

 

 

Also doesn't follow the spec. The type should be LineString, not coordinates. Just test the part in a online validator like http://geojsonlint.com/
Buckle your seatbelt Dorothy, cause Kansas is going bye-bye...
takashi
Celebrity
  • takashiCelebrity
  • September 11, 2018

I think the data doesn't validate as correct GeoJSON.

The structure for a polygon feature should be:

{
    "type": "Polygon",
    "coordinates": [
        [
            [
                100,
                0
            ],
            [
                101,
                0
            ],
            [
                101,
                1
            ],
            [
                100,
                1
            ],
            [
                100,
                0
            ]
        ]
    ]
}

Where a piece in waterarea.json is:

{
	"type": "coordinates",
	"coordinates": [[145.71758,
	-30.83595],
	[145.71769,
	-30.83532],
	[145.71895,
	-30.8348],
	[145.72022,
	-30.83381],
	[145.72158,
	-30.83383],
	[145.72241,
	-30.83428],
	[145.72374,
	-30.83646],
	[145.72404,
	-30.83773],
	[145.72403,
	-30.83846],
	[145.72028,
	-30.83697],
	[145.71872,
	-30.83623],
	[145.71758,
	-30.83595]]
}

Issues are:

  • type should be Polygon, not coordinates (case sensitive!)
  • the array of coordinates should be nested one level deeper (rings, ring, coordinatepairs)
  • polygons should follow the right-hand rule (exterior rings are counter clockwise, interior rings / holes are clockwise)

See the spec.

This works for me:

{
	"type": "Polygon",
	"coordinates": [[[145.71758,
	-30.83595],
	[145.71872,
	-30.83623],
	[145.72028,
	-30.83697],
	[145.72403,
	-30.83846],
	[145.72404,
	-30.83773],
	[145.72374,
	-30.83646],
	[145.72241,
	-30.83428],
	[145.72158,
	-30.83383],
	[145.72022,
	-30.83381],
	[145.71895,
	-30.8348],
	[145.71769,
	-30.83532],
	[145.71758,
	-30.83595]]]
}

@nielsgerrits is right. The format of the JSON documents are similar to GeoJSON, but not GeoJSON. However, you can reconstruct them into the GeoJSON format with some JSON transformers.

 

Example: reconstruct-geojson-example.fmwt (FME 2018.1.0.0)

 

Hope this helps.

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
jnotter
Contributor
Forum|alt.badge.img+5
  • jnotterContributor
  • Contributor
  • January 29, 2020

@nielsgerrits is right. The format of the JSON documents are similar to GeoJSON, but not GeoJSON. However, you can reconstruct them into the GeoJSON format with some JSON transformers.

 

Example: reconstruct-geojson-example.fmwt (FME 2018.1.0.0)

 

Hope this helps.

I wish I could vote up this particular comment, @takashi. I think this example is what I need to get my data into MapBoxGL-compatible format to color thematic each feature individually. MapBox(leaflet) within HTMLReportGenerator fails to allow the individual formatting capability.

Community Stats

32,182
Posts
122,178
Replies
39,856
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.