Creating lines from XY attributes in a point feature class

[BenKeller2]

I have a point feature class, and within the feature class I have two other sets of XY coordinates and I want to create a line from the main point to the other two sets of coordinates and create a point at the end of each line so I can snap it to another line. The end process here is for a network dataset connection, but this part has been bugging me. Help would be great! Thank you

[HollyGolvach]

Hello,

Thank you very much.

Let me clarify the "problem" at hand.

1) Route feature layer: I need a basic airline network that shows existing routes (these do not necessarily need to be formatted for time.)

Ex, ROUTE ID = 1 DEP = DAL ARR = PHX CYCLE = [end date] (meaning, an airplane flies this route until a certain date)

2) Next, I need to have a feature layer that contains the ideal schedule of the Route feature, including the actual times these routes are scheduled

Ex, ROUTE ID = 1 DEP = DAL ARR = PHX CYCLE = 05132008 DEP_TM = 900 ARR_TM = 1030 FLY_TM = 120 (mins) FLT_NM = 7886 TAIL_NM = 1202N

The way to connect the flights will be through a shared date, tail number and flight number in most cases:

PHX - DAL = flight 7886 on tail 1202N on [date] - round trip
DAL - PHX = flight 7886 on tail 1202N on [date]
PHX - LAX = flight 808 on tail 1202N on [date] - new connection in LAX, but same tail number and date (meaning, it's the same airplane, which is what we're tracking)

My research question isn't very specific at this point, but eventually I want to see whether it's the route ( PHX - DAL - PHX - LAX) or the individual airport that more influences delay in the network.

3) Another feature layer with what was actually flown, meaning the historic schedule data. The above was the "ideal" schedule--but, I have the historical flight data of what times the planes actually left and arrived so I can see the difference between them.

The field list is extensive, but know that to build the network we have the Tail Number to follow the specific plane along it's route so long as it's on the same day and follows an appropriate time/space continuum.

Your help is appreciated - I'm looking into the best way to start with the Linear Referencing and Network Analyst tools....

[RichardFairhurst]

Hello,

Thank you very much.

Let me clarify the "problem" at hand.

1) Route feature layer: I need a basic airline network that shows existing routes (these do not necessarily need to be formatted for time.)

Ex, ROUTE ID = 1 DEP = DAL ARR = PHX CYCLE = [end date] (meaning, an airplane flies this route until a certain date)

2) Next, I need to have a feature layer that contains the ideal schedule of the Route feature, including the actual times these routes are scheduled

Ex, ROUTE ID = 1 DEP = DAL ARR = PHX CYCLE = 05132008 DEP_TM = 900 ARR_TM = 1030 FLY_TM = 120 (mins) FLT_NM = 7886 TAIL_NM = 1202N

The way to connect the flights will be through a shared date, tail number and flight number in most cases:

PHX - DAL = flight 7886 on tail 1202N on [date] - round trip
DAL - PHX = flight 7886 on tail 1202N on [date]
PHX - LAX = flight 808 on tail 1202N on [date] - new connection in LAX, but same tail number and date (meaning, it's the same airplane, which is what we're tracking)

My research question isn't very specific at this point, but eventually I want to see whether it's the route ( PHX - DAL - PHX - LAX) or the individual airport that more influences delay in the network.

3) Another feature layer with what was actually flown, meaning the historic schedule data. The above was the "ideal" schedule--but, I have the historical flight data of what times the planes actually left and arrived so I can see the difference between them.

The field list is extensive, but know that to build the network we have the Tail Number to follow the specific plane along it's route so long as it's on the same day and follows an appropriate time/space continuum.

Your help is appreciated - I'm looking into the best way to start with the Linear Referencing and Network Analyst tools....

Since this thread is marked as answered for the original user and your objectives are diverging from the original post topic fairly substantially, you should probably start a new thread.  Restate your problem there.

Please include a screen shot of the lines you already have and the data contained on them.  Are the lines overlapping and representing multiple flights currently, or is each line already a distinct route independent of actual time and planes?  How is the actual flight data stored currently?  In a table or as actual lines?

In many ways the question and unknown comes down to the delay time at each airport more than flight time.  This probably would heavily depend on the plane and the airport design.  Disembarking and Boarding time and luggage or cargo unloading and loading time would vary depending on the plane capacity and available gates at the airport.  Two planes cannot board at the same gate at the same time, so there is a maximum boarding number at any given time at a given airport, plus you have to account for delays between planes occupying the same gate over the course of the day.  Spacing of take off and landing would also have to be known for the airports and the cycle time between each to estimate ideal or maximum capacity, which is influenced by the number of available runways and landing/take-off windows.  Identifying peak operation times would be crucial, since rush hour puts pressure on airport facilities just as much as it does on roadway facilities, and those peak hour and peak day spots are the most precious to allocate, since passenger demand is highest at those times.

I don't know what those factors are, but they influence the problem a great deal.  The actual flight data would give you the best idea of the peak hour and day periods and whether an airport is operating efficiently well within its capacity, or approaching or reaching breakdown due to nearing or exceeding its ideal capacity.