Skip to main content
Solved

GeoJSON inline conversion

  • February 27, 2018
  • 6 replies
  • 154 views
Z
Forum|alt.badge.img

Hello,

I have a project that involves creating maps and custom outputs with the HTMLReportGenerator and would like some help with GeoJSON. I am utilizing custom code to add a second geojson layer to the map. is there a way to take an imported file (ex: ESRISHAPE) and convert it to geojson inline (maybe as an attribute?), and then use that geojson output(text) as a parameter in my custom code.

Edit:

A good example of a perfect geoJSON output is how the HTMLReportGenerator converts both attributes and geometry to geojson.

Best answer by takashi

You can use the JSONTemplater to create a JSON document conforming to the GeoJSON specifications, which contains a geometry string created with the GeometryExtractor and properties corresponding to feature attributes.

If you aren't familiar with the GeoJSON specifications, another way is:

  1. Once write the feature into a temporary GeoJSON dataset with a FeatureWriter (Format: GeoJSON),
  2. read it with a FeatureReader (Format: Text File, Read Whole File at Once: Yes) or an AttributeFileReader,
  3. then merge the GeoJSON document to the original feature.

Here, the TempPathnameCreator could be used effectively to make a temporary file path for saving the GeoJSON document. It's very convenient since FME will remove automatically the temporary file saved into the path created by the TempPathnameCreator after the translation completed.

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

6 replies

redgeographics
Celebrity
Forum|alt.badge.img+50

The GeometryExtractor can take the geometry of a feature and store that in an attribute, encoded as GeoJSON (or one of several other formats)

Z
Forum|alt.badge.img
  • zacharya
  • Author
  • February 27, 2018
redgeographics wrote:

The GeometryExtractor can take the geometry of a feature and store that in an attribute, encoded as GeoJSON (or one of several other formats)

I tried this method, but I was only able to create an output of separate attributes consisting of GeoJSON that only represented the geometry of the feature.

 

 

 

takashi
Influencer
  • takashiInfluencer
  • Best Answer
  • February 28, 2018

You can use the JSONTemplater to create a JSON document conforming to the GeoJSON specifications, which contains a geometry string created with the GeometryExtractor and properties corresponding to feature attributes.

If you aren't familiar with the GeoJSON specifications, another way is:

  1. Once write the feature into a temporary GeoJSON dataset with a FeatureWriter (Format: GeoJSON),
  2. read it with a FeatureReader (Format: Text File, Read Whole File at Once: Yes) or an AttributeFileReader,
  3. then merge the GeoJSON document to the original feature.

Here, the TempPathnameCreator could be used effectively to make a temporary file path for saving the GeoJSON document. It's very convenient since FME will remove automatically the temporary file saved into the path created by the TempPathnameCreator after the translation completed.

Z
Forum|alt.badge.img
  • zacharya
  • Author
  • February 28, 2018
takashi wrote:

You can use the JSONTemplater to create a JSON document conforming to the GeoJSON specifications, which contains a geometry string created with the GeometryExtractor and properties corresponding to feature attributes.

If you aren't familiar with the GeoJSON specifications, another way is:

  1. Once write the feature into a temporary GeoJSON dataset with a FeatureWriter (Format: GeoJSON),
  2. read it with a FeatureReader (Format: Text File, Read Whole File at Once: Yes) or an AttributeFileReader,
  3. then merge the GeoJSON document to the original feature.

Here, the TempPathnameCreator could be used effectively to make a temporary file path for saving the GeoJSON document. It's very convenient since FME will remove automatically the temporary file saved into the path created by the TempPathnameCreator after the translation completed.

I can always count on @takashi to save the day. Thank you.

 

Z
Forum|alt.badge.img
  • zacharya
  • Author
  • March 1, 2018
takashi wrote:

You can use the JSONTemplater to create a JSON document conforming to the GeoJSON specifications, which contains a geometry string created with the GeometryExtractor and properties corresponding to feature attributes.

If you aren't familiar with the GeoJSON specifications, another way is:

  1. Once write the feature into a temporary GeoJSON dataset with a FeatureWriter (Format: GeoJSON),
  2. read it with a FeatureReader (Format: Text File, Read Whole File at Once: Yes) or an AttributeFileReader,
  3. then merge the GeoJSON document to the original feature.

Here, the TempPathnameCreator could be used effectively to make a temporary file path for saving the GeoJSON document. It's very convenient since FME will remove automatically the temporary file saved into the path created by the TempPathnameCreator after the translation completed.

Despite my efforts, I am still having a fair bit of trouble with this method. While finishing routing my features through the FeatureReader, i am trying to replace a portion of html_content with the string replacer; And it is successfully replacing the selected string with a blank value from the text_line_data. When I inspect the path from the FR to the StringReplacer, it shows that the text_line_data attribute is correctly written. I have provided the screen capture below to help explain what I am trying to do.

 

 

takashi
Influencer
  • takashiInfluencer
  • March 1, 2018
takashi wrote:

You can use the JSONTemplater to create a JSON document conforming to the GeoJSON specifications, which contains a geometry string created with the GeometryExtractor and properties corresponding to feature attributes.

If you aren't familiar with the GeoJSON specifications, another way is:

  1. Once write the feature into a temporary GeoJSON dataset with a FeatureWriter (Format: GeoJSON),
  2. read it with a FeatureReader (Format: Text File, Read Whole File at Once: Yes) or an AttributeFileReader,
  3. then merge the GeoJSON document to the original feature.

Here, the TempPathnameCreator could be used effectively to make a temporary file path for saving the GeoJSON document. It's very convenient since FME will remove automatically the temporary file saved into the path created by the TempPathnameCreator after the translation completed.

You have to merge the JSON document to the feature containing "html_content".

 

If the workspace processes just one feature always, you can merge the JSON to the feature unconditionally i.e. use the FeatureMerger with setting an identical constant (e.g. 1) to Join On for both Requestor and Supplier.

 

Otherwise, need to see the entire overview of the workspace to find an appropriate way.

 

 

Reply


Helpful Members This Week

Community Stats

31,353
Posts
118,927
Replies
38,971
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.