Replication, Reprojection, and Geometric Networks

[NathanHeick]

Hello,

I am trying to do some system planning and I want to know if it is possible to replicate and reproject data in a geometric network.  If so, what is the best workflow?  I read KB article 34129 and it says that you can reproject during replication, but that the procedure would not work with a geometric network, because the setup process would reproject the geometric network, making it read only thereon.  Is it possible to build the geometric network in the child database first so that it is not read only?  The best workflow I can think of is:

Parent - ArcSDE Geodatabase in NAD83 California State Plane Zone 6 with geometric networks
Child - File Geodatabase in Web Mercator with geometric networks

1.  Drop geometric networks in child with ArcObjects program.
2.  Replicate from parent to child.
3.  Rebuild geometric networks in child with ArcObjects program.

This seems like it should be a common workflow, i.e. Web Mercator publishing geodatabase with geometric networks.

Any thoughts?


Nathan

[JakeSkinner]

Hi Nathan,

You can perform the following steps:

1.  Use the 'Project' tool to project the feature dataset containing the geometric network from the parent to the child geodatabase
2.  Create the replica using the 'Register existing data only' option

[HeatherMcCracken]

Hi All,

Geometric networks that are projected on the fly cannot be edited within ArcMap.  This is prevented to ensure the integrity of the geometric network.
http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/About_editing_geometric_network_featur...

For the same reason - we do not support/recommend reprojecting network data via replica creation/synchronization (sync is essentially editing). 

-Heather

[NathanHeick]

Hi Heather,

Would it be supported to do the replication in two steps?

1.  Replicate complex features in a geometric network to simple features in Web Mercator.
2.  Replicate simple features in Web Mercator into complex features in a geometric network (Is this even possible?)

Also, are there any other supported procedures, even if they are less than optimal?  Using a combination of replication and geoprocessing would be acceptable.  We need a publishing geodatabase in Web Mercator that includes full geometric network functionality.

[HeatherMcCracken]

We need a publishing geodatabase in Web Mercator that includes full geometric network functionality.

Just want to clarify before I comment - will a one-way replica satisfy your workflow? i.e Is the projected GN for Read purposes only correct? You want full geometric network functionality, but you do not plan to edit the data (and sync back to the parent).

[NathanHeick]

Yes.  Correct.

[JonPeck]

Just want to clarify before I comment - will a one-way replica satisfy your workflow? i.e Is the projected GN for Read purposes only correct? You want full geometric network functionality, but you do not plan to edit the data (and sync back to the parent).

Apologies for bumping up an old thread.  But I was wondering if you ever followed up on this? 

I am looking to do exactly what you describe above.  I already use projected replicas for non-geometric data sets and they work fine.

I want to use my geometric network in a web based application and wanted to replicate/sync any changes from the NAD27 projected parent database to a WebMercator child database.

Your comments above led me to believe you may have a solution to this, but then there was no follow up.   All the info I can find plus my own trials seem to indicate that this will not work, but I just wanted to make sure.

My temporary (maybe permanent) workaround is to just delete the feature class nightly by using geoprocessing scripts, then I re-project my geometric network with scripts to my destination database. This works but is I don't feel its very eloquent to be deleting and copying/reprojecting the same data every night, when I really only need the infrequent changes sent to the child database.

Thanks in advance.