TweetSearch does not contain geometry

As far as I know the attribute _tweet_geo contains the lat long representation of the location. That attribute can be used to create the geometry.

It looks as though that's a bug, but the geometry is still there, in the _tweet_search_result attribute, under place.bounding_box, where it's a GeoJSON object, so you should be able to do this (it worked for the one test I was able to do before I ran out of API calls anyway...)

To me it looks like _tweet_geo just isn't being exposed. So just use an AttributeExposer and type in the name and it should appear. You'll still need to use a JSON transformer to extract the information.

I filed PR#69639 to ask for this to be exposed automatically. I see from the tweet result attribute there are probably hundreds of things we could expose, but geometry does seem to me to be more important than the rest. I also asked for an option to automatically replace the feature geometry with that of the tweet, instead of having to go down the JSON route.

It looks as though that's a bug, but the geometry is still there, in the _tweet_search_result attribute, under place.bounding_box, where it's a GeoJSON object, so you should be able to do this (it worked for the one test I was able to do before I ran out of API calls anyway...)

I am trying to use the Twitter workbench that @rollo had created.

When i am using the second JSON_Flattener_2 transformer with the @Value(_tweet_created_at) instead of the @Value(Place) when i try to use this parameter the input box is red and will not allow me to click ok. Also for the GeometryReplacer transformer is used @Value(_tweet_created_at) instead of the @Value(bounding_box) when i try to use this parameter the input box is red and will not allow me to click ok.

 

When i run the workbench i can create a feature but there is a column called fme_rejection_code that has the value INVALID_PARAMETER_GEOMETRY_SOURCE.

 

Any help is appreciated