If you do a PointOnAreaOverlayer of the points with the counties you can get the county name (assuming you have that in an attribute) as an attribute of the points, then aggregate them on flight number and county name, that way you'll get an aggregate for all unique combinations of those two attributes and if you accumulate hulls they'll be smaller areas.
If you do a PointOnAreaOverlayer of the points with the counties you can get the county name (assuming you have that in an attribute) as an attribute of the points, then aggregate them on flight number and county name, that way you'll get an aggregate for all unique combinations of those two attributes and if you accumulate hulls they'll be smaller areas.
Wow, thanks for the timely response.
My county data is in a different shapefile not associated with the point data. Will that matter?
The analysis I am doing is what different flight numbers fall within each county.
What I want to know is all the different flight numbers that fall within each county. If I aggreage based on flight number and county name I only get the unique combinations.
Wow, thanks for the timely response.
My county data is in a different shapefile not associated with the point data. Will that matter?
The analysis I am doing is what different flight numbers fall within each county.
That's no problem, just add another reader for that county shapefile.
What I want to know is all the different flight numbers that fall within each county. If I aggreage based on flight number and county name I only get the unique combinations.
You can set the Aggregator to concatenate the flight number attributes into a new one, so per county you get a list of flight numbers (with a separator character of your choice)
Are you actually interested in keeping the point geometry in any way, or is it sufficient to have the unique flight numbers for each county on the county geometry?
If the latter then a SpatialRelator (Counties as Requestor) followed by a ListHistogrammer (on _relationships{}.flightnumber will give you a list of all the flight numbers that fall inside the county (and how many times for each flight number).
You can set the Aggregator to concatenate the flight number attributes into a new one, so per county you get a list of flight numbers (with a separator character of your choice)
awesome!! thank you very much!
Is there a way to make the flight numbers not repeat? i.e. "Flight 1" Only appears once in the cell.
awesome!! thank you very much!
Is there a way to make the flight numbers not repeat? i.e. "Flight 1" Only appears once in the cell.
oh wait nvm, i did something wrong. the flight numbers arent associated with the county names because they fall within more than one county.... hmmmmmm.
Are you actually interested in keeping the point geometry in any way, or is it sufficient to have the unique flight numbers for each county on the county geometry?
If the latter then a SpatialRelator (Counties as Requestor) followed by a ListHistogrammer (on _relationships{}.flightnumber will give you a list of all the flight numbers that fall inside the county (and how many times for each flight number).
I only really need the point geometry for a visual representation. I will try this spatialRelator for the analysis portion. thank you for your response.
Are you actually interested in keeping the point geometry in any way, or is it sufficient to have the unique flight numbers for each county on the county geometry?
If the latter then a SpatialRelator (Counties as Requestor) followed by a ListHistogrammer (on _relationships{}.flightnumber will give you a list of all the flight numbers that fall inside the county (and how many times for each flight number).
Do you know if I am setting the parameters up wrong?
Do you know if I am setting the parameters up wrong?
It should be CONTAINS.
Ok, so I aggregated my point dataset (flight numbers) from over a million to just 26 multi point features.
I am now confused.
My end goal is to have a data set that lists each county name with the various flight numbers contained in that county.
I imagine this is going to be some sort of spatialfilter -- or point on area overlayer-- i just cant seem to get the parameters correct.
any thoughts?
Ok, so I aggregated my point dataset (flight numbers) from over a million to just 26 multi point features.
I am now confused.
My end goal is to have a data set that lists each county name with the various flight numbers contained in that county.
I imagine this is going to be some sort of spatialfilter -- or point on area overlayer-- i just cant seem to get the parameters correct.
any thoughts?
The attached workspace should illustrate how to get for each county, the list of all the flight numbers that fall within that county.
flightscounties.fmw
The attached workspace should illustrate how to get for each county, the list of all the flight numbers that fall within that county.
flightscounties.fmw
I am using FME 2014 idk if that is why it isnt showing up. I tried to do what you explained in your first post, but it was only giving me counties that had one flight number contained. If the county has multiple flight numbers contained it would be null.
this is what the workspace you sent looks like for me.
I am using FME 2014 idk if that is why it isnt showing up. I tried to do what you explained in your first post, but it was only giving me counties that had one flight number contained. If the county has multiple flight numbers contained it would be null.
this is what the workspace you sent looks like for me.
Yes, I don't have 2014 on this machine, and there have been updates to those transformers in the intervening years. I've attached summary annotations to the missing transformers, which should help you rebuild it.
Yes, I don't have 2014 on this machine, and there have been updates to those transformers in the intervening years. I've attached summary annotations to the missing transformers, which should help you rebuild it.
thanks for all your help, i truly appreciate it.
however, something is not right. when I run that my flight numbers are not making it to the inspector after the listhistogrammer, only the counties shapefile. ......
Yes, I don't have 2014 on this machine, and there have been updates to those transformers in the intervening years. I've attached summary annotations to the missing transformers, which should help you rebuild it.
What is the test you are using in the Spatial Relator?
Yes, I don't have 2014 on this machine, and there have been updates to those transformers in the intervening years. I've attached summary annotations to the missing transformers, which should help you rebuild it.
Tests to perform? I am using contains.
Yes, I don't have 2014 on this machine, and there have been updates to those transformers in the intervening years. I've attached summary annotations to the missing transformers, which should help you rebuild it.
Based on the number of features, it looks like you have already aggregated your points. In that case there probably won't be any counties that completely contain your aggregate. Either use the original individual point data, or use Intersects as your test.
Yes, I don't have 2014 on this machine, and there have been updates to those transformers in the intervening years. I've attached summary annotations to the missing transformers, which should help you rebuild it.
only one flight is being returned
Yes, I don't have 2014 on this machine, and there have been updates to those transformers in the intervening years. I've attached summary annotations to the missing transformers, which should help you rebuild it.
Ok, so the intersect populated them all. But some counties should have more than one flight associated. Is there some way to concatenate all flights into that field.
Yes, I don't have 2014 on this machine, and there have been updates to those transformers in the intervening years. I've attached summary annotations to the missing transformers, which should help you rebuild it.
Can you display the contents of the agg_dec_pts2 file as well?
Ok, so the intersect populated them all. But some counties should have more than one flight associated. Is there some way to concatenate all flights into that field.
this is the intersect
Yes, I don't have 2014 on this machine, and there have been updates to those transformers in the intervening years. I've attached summary annotations to the missing transformers, which should help you rebuild it.
You will have one random entry in the InstallationGroup, what you want to look at is the _histogram list, which will contain them all.
You can concatenate the histogram{}.value into a single attribute with the listConcatenator
only one flight is being returned
here ya go
