Skip to main content
Solved

Geometric Networks


andrew_r
Contributor
Forum|alt.badge.img
Does the FME preserve network flow direction when reading and writing features that are part of a geometric network? 

 

 

I'm trying to setup a workbench to push updates from one SDE to another.  The feature classes I'm trying to update are part of a geometric network and the flow direction that has been setup in the source database is something I want to be available in the destination database.  Unfortunatley, during my test the flow direction I set in the source data did not come over to the destination data.  Instead the line had indeterminant flow.  I'm using ArcSDE Geodatabase  readers and writers, and the feature type is setup as complex_edge and simple_junction(same as what is defined in my SDE).  Is there something I'm forgetting to configure?

 

 

Here's how I setup a simple test:

 

 

-Create a feature dataset in SDE

 

-Create a line feature class and a point feature class in that SDE

 

-Create a geometric network in the dataset that includes the point and line layers.  Lines will be complex edges, and points will not have a source/sink.  Instead I set the flow direction to be the same as the digitized direction.

 

-Version the dataset

 

-Copy the dataset to another SDE (this will be where we copy features to).  I'll refer to this as the destinateion SDE.

 

-Version the destination SDE feature dataset

 

-Open ArcMap, start editing the source SDE layers

 

-Add two points to the point feature class, and add one line between those points in the line feature class.

 

-Make sure the flow direction of the line is defined using the Utility Network Analyst toolbar.

 

-Stop editing and save edits

 

-In FME Workbench, add an ArcSDE Geodatabase Reader and Writer that point to the source and destination feature classes respectively

 

-Uncheck 'ignore network info' on the reader.

 

-Set "Truncate table first' setting on writer to True.

 

-Setup writer to use versioning and an edit session.

 

-Run workbench

 

-At this point if you inspect the destination databases' flow direction, its set to indeterminate flow.

 

 

 

 

Thanks for any help you can provide,

 

 

Andrew

Best answer by mark2atsafe

Hi Andrew,

 

I'm not sure about this one. I'm going to run it past our geodatabase developer when he is in and will let you know what I find out,

 

 

Regards

 

 

Mark

 

 

Mark Ireland

 

Product Evangelist

 

Safe Software Inc.
View original

mark2atsafe
Safer
Forum|alt.badge.img+43
Hi Andrew,

 

I'm not sure about this one. I'm going to run it past our geodatabase developer when he is in and will let you know what I find out,

 

 

Regards

 

 

Mark

 

 

Mark Ireland

 

Product Evangelist

 

Safe Software Inc.

ksafeent

Hi,

 

I have two CSV readers containing the same informations but with different range of value. 

 

Let's say that I have something like this:

Reader_1:
[ATTRIBUTE_1](UINT8)
[ATTRIBUTE_2](DOUBLE)

And 

Reader_2:
[ATTRIBUTE_1](UINT64)
[ATTRIBUTE_2](DOUBLE)

(FME has choosed the datatype automatically)

 

Since both reader have the same attribute's name, I connect both reader's output to a "sorter" transformer. 

 

And here, a weird thing happens, the sorter output ATTRIBUTE_1 as UINT8 (I expected that FME would choose the biggest datatype, not the smallest one).

 

But some value are bigger than 255:

CaptureIs that a miracle ? 

 

Then I use a StatisticCalculator to find the max value of ATTRIBUTE_1 group by some other attributes and the output is, this time, limited to 255. 

 

So why FME do not pick the biggest datatype ? How can a FME_UINT8 variable be bigger than 255 and what can I do to calculate my statistics correctly ?

 

Of course I can manually change the ATTRIBUTE_1 datatype, but that does not explain that weird behaviour. (BTW I'm using FME 2020.0 Build 20238)


Reply


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