POST
|
The 'schematic editor' toolbar doesn't exist on server. The schematic server extension provides the api though and the api does have all the algorithms. So you could provide a dropdown list and let the user apply an algorithm, which behind the scenes would run the algo, save the diagram and the you refresh the display.
... View more
08-16-2010
10:44 AM
|
0
|
0
|
312
|
POST
|
You can try using a Node Reduction Rule, but remember the rule in Schematics is that a link (edge) must have 2 end nodes (i.e. a link can't connect directly to another link).
... View more
07-09-2010
06:32 AM
|
0
|
0
|
265
|
POST
|
Remember that 2 links can't connect directly together...there must be a node at the end of a link. So if there was a complex edge and a 'side' link connected to it, then schematics splits that edge so that the net junction nodes are available to connect the 'side' link. You can run a Node Reduction Rule to get rid of net junctions, just be aware of the side effects. For example, when I use the node reduction rule I normally specify to only remove nodes with 0 or 2 connections. That means get rid of a node if it is an 'orphan' (no connections) or if it is just in the middle of 2 links and has no other connections. Getting rid of 1 connection or > 2 connections is where you have to be careful as the outcome may not be what you want. If you get rid of the 1 connection (node is at the end of a link with no other connections), you will also end up losing the link (as mentioned above a link can't exist without 2 end nodes). If you get rid of > 2 connections, then the connectivity has to be re-calculated and it may not come out exactly the way you think it should. If your network has proper flow in it (i.e. you can trace upstream and downstream), then you can also look at our Node Reduction By Flow Rule which helps with the > 2 case.
... View more
07-02-2010
06:12 AM
|
0
|
0
|
362
|
POST
|
Why does the schematic server sample not help you? It shows 1 way of allowing the user to select features and generate a diagram all via GP.
... View more
07-02-2010
05:59 AM
|
0
|
0
|
278
|
POST
|
There is a sample for schematics on server showing the use of geoprocessing tools in a model to create a diagram and view it on server.
... View more
07-01-2010
11:47 AM
|
0
|
0
|
172
|
POST
|
So this totally depends on your data model. Remember that a link must connect to 2 nodes. So if your 'LA' objects are always within some distance of then end of a BusBar, we are close. The next question is: What objects are at the end of busbar's? Are they always net junctions or some other type of feature? Is it consistent. Assuming that there is a consistent case, we need to get to some statement like: 'LA' objects are always connected to NetJunctions that appear at the end of a busbar and to figure out which end is simply based on the spatial distance of .005. Now with that statement it is pretty easy to setup in the system. Several ways to do this, but here is one way I can quickly think of: Use the Designer application to edit your schematic dataset Create a new link element type and associate it to your diagram type (this will be used to represent this 'logical' link that the rule will create) Create (or modify existing if it exists) the spatial query rule. Make sure not to check the Relates box. Check the box for Create Links and use the dropdown to select the link element type you created in the previous step. See the attached pictures. On the 'map' image, you see 2 gas plants (Red) and 1 electric plant (blue). The electric plant is not part of the geometric network. I am using a spatial rule from the gas plants (I know the user will select those) to get any electric plants within .22 decimal degrees and add them to the map and connect to the gas plant via my new link element type. The 'mapselection' image shows what is selected. Notice that the electric plant is not part of the selection. The 'initialdiagram' image shows the initial diagram generated. You can see that the spatial rule has run and a new 'logical' link has been created between the electric plant and one of the gas plants based on the spatial rule criteria. The 'diagramwalgo' image shows applying an algorithm and here you see that the electric plant properly moves because it is logically connected to the rest of the network.
... View more
07-01-2010
11:45 AM
|
0
|
0
|
867
|
POST
|
Not sure I completely follow the issue but hopefully this helps explain it: A link in a schematic diagram must connect between 2 nodes. So a link can't just connect to a busbar. So schematics utilizes the net junctions along the busbar for the connections. If you don't want to see the net junctions, you can either set the symbol size to be very small or set the visibility to not visible, but they need to be there for connectivity.
... View more
06-28-2010
01:13 PM
|
0
|
0
|
362
|
POST
|
You can set those to not be visible. With pre-10 software, that is your only option. With 10, there is a new rule called 'Feature Removal' where you can use an attribute to completely have it removed from the diagram instead of just not being displayed. Assuming that the symbology is already based on this attribute you don't want to see, do the following. To set that 1 subtype as not displayed, you need to: 1. open Schematic Designer 2. Open the treeview so you see everything under the element type of interest (Busbar) 3. Open the Properties treeview branch 4. Click on the ArcGIS Symbology entry (or if you did some custom symbology, just select the property entry you created. 5. On the right side of the screen, select the Filters tab 6. Now select the row that corresponds with the subtype you want to not see. 7. Click the ellipse button at the end of the row to open the Filter Effects window. 8. On the filter effects window, choose the Others tab and turn off the visibility.
... View more
06-28-2010
01:09 PM
|
0
|
0
|
357
|
POST
|
So I am not completely following what you are trying to do. You said "LA feature is coming only on its geographic location and other features are coming properly as per sch location". What determines sch location vs geographic location for you? Initially, unless you set a layout algorithm to be automatically applied for your diagram template, all nodes come in the initial geographic position and the links are simplified (no vertices). So are you telling the system to automatically apply an algorithm at the diagram type level? Since you are adding things that are not 'physically' connected to the geometric network, the system will add them as 'orphan' nodes. Orphan nodes don't move (or in some cases only slightly move) when an algorithm is applied because they are not part of the connectivity. If you want them to be 'logically' connected, then you need to have the system create links during the spatial query rule. The rule properties that you are using show using the relate option. Relate options are only useful when trying to create parent/child effects with a container. So the container is an object that contains children. If the children move, the container dynamically resizes. If the container moves, the children move relative to the container. It sounds like you should not be using Relate option first of all. It seems like you should be using the create links option. One issue with that is that a link needs to connect to 2 nodes. It seems like you are adding nodes based on proximity to a link (busbar), so that won't work as you can't connect a link from a node (LA) to a link (busbar). So you may need to modify that rule so that you get the LA's based on some point feature that is always found on or near the BusBar, then you can use the create links option. If links are created, then the LA objects are 'connected' and therefore any algorithm will properly move the LA nodes (i.e. they are no longer 'orphan'). We also have a relationship rule. So if there happens to be a relationship class from those LA objects to other geometric network objects, that could be another way to add them. Final thing I noticed is that you currently have the LA set as the source and Busbar as the target. That might be correct, but just making sure. Normally the 'source' is something you know the user will select. Typically that is something in the geometric network. Then you are saying that based on something in the source being selected, automatically have the system add something from the target whether the user selected it or not. So maybe I am wrong here, but it seems like you would want busbar as the source and LA as the target, but I don't know the use case here. Rick
... View more
06-28-2010
12:49 PM
|
0
|
0
|
867
|
POST
|
When you are doing the initial configuration in schematic designer, just right click the diagram type and choose to import feature classes/tables. Point to the feature class you want and it will be imported. Done. A user in the map can select a feature from that class and generate a diagram with it. When using rules (spatial or relationship), the relate option is important. If you check relate, it tries to create a parent/child type of concept which is normally used to draw a parent container around the children. It sounds like your case is simple and therefore you should not check the relate box and potentially you don't need rules at all. Just import the feature class.
... View more
06-25-2010
07:10 AM
|
0
|
0
|
867
|
POST
|
It looks like all the features are in the diagram correctly, it is just a problem of display. The manual answer to the display is to use the 'Main Line' algorithm, pick the start point and stop point and then apply it. To automatically do it, you would need to build an algo that somehow automatically knows how to determine what is the start and stop points and then apply the algo without the user manually doing it.
... View more
06-11-2010
09:25 AM
|
0
|
0
|
404
|
POST
|
There is a sample for generating diagrams on server that shows the basics. The system has a geoprocessing tool for 'create diagram'. So the user somehow selects data and then that data is passed into the Create Diagram tool. This model is put in server as a service that the user runs. Once the results are done, you can allow the user to see the resulting diagram.
... View more
06-11-2010
09:18 AM
|
0
|
0
|
660
|
POST
|
This just depends on your needs... We have customers with 10,000 diagrams. If they wanted them all served, it would not be wise to create 10,000 services most likely. In this case, as Dominique mentioned, you would serve the schematic feature classes and give the user an ability to pick a diagram name from a list and then behind the scenes, you simply change the definition query on the schematic feature layers to point to a different diagram.
... View more
04-30-2010
08:20 AM
|
0
|
0
|
366
|
POST
|
In prior versions, labeling and symbology required a lot of configuration to create schematic attributes and properties just to get attributes from the 'real' features being diagrammed. With version 10, all that is gone in the majority of the cases. If your schematic diagrams are based on 'real' features in geometric networks, network datasets or any other tables managed by the GIS, then to get those 'real' attributes available, you just need to use a join. The join gives you access to all the schematic feature fields and the related 'real' feature fields. Keep in mind that the steps below are usually a 1 time thing. Do it once and never worry about it again. Once you have generated a diagram, you can follow these steps for each layer that needs joined: Right-click a schematic feature layer in the ArcMap table of contents. Choose the Properties... menu option which will open the Layer Properties dialog. Select the Joins & Relates tab. In the Joins section, click the Add button to open the Join Data dialog. In step 1 of the Join Data dialog, pick UOID from the dropdown list (this is where schematics stores the objectid of the 'real' feature). In step 2 of the Join Data dialog, use the Browse button to navigate to and select the 'real' feature class associated to this schematic feature layer. In step 3 of the Join Data dialog, select OBJECTID from the dropdown list. Click the OK button to close the Join Data dialog. You can now use the Labels and Symbology tabs to setup labeling and symbology. You will see all fields available from the schematic feature class and the related 'real' feature class. Once you have all the symbology and labeling for you diagram configured as desired, you can right-click the diagram layer in the ArcMap table of contents and save this as a layer file. That layer file can be applied to new diagrams you generate. This process will copy the join information as well as the labeling and symbology setup into the new diagram. Most customers will do this 1 time and then set this as the 'default' for their diagram template so that this is automatically done for each of the users. To set this up as the default, follow these steps: Right-click the schematic diagram layer in the ArcMap table of contents. Choose the Save As Layer File... option from the menu and use the resulting dialog to choose a location in which to save this layer file. Now you need to edit the schematic dataset. Use ArcCatalog to navigate to your schematic dataset. Right-click the schematic dataset and choose Edit... from the menu which will start the Schematic Dataset Editor application. Use the treeview control in the schematic dataset editor to browse to your diagram template. Right-click the diagram template and choose Import Default Symbology... from the menu. Use the resulting dialog to navigate to and select the layer file you saved. Save the changes to the schematic dataset In some cases it can be useful to have several different layer files pre-configured and stored on a network share location. These different files might be the proper symbology and labeling required when printing and sharing your diagrams with outside companies/agencies. To apply a stored layer file to an open diagram, follow these steps: Right-click the schematic diagram layer in the ArcMap table of contents. Choose Schematic Layer Properties and then Import Layer Properties from the menu. Use the resulting dialog to navigate to and select the desired layer file.
... View more
03-11-2010
10:55 AM
|
0
|
1
|
1161
|
Title | Kudos | Posted |
---|---|---|
1 | 12-16-2013 10:41 AM | |
1 | 08-22-2014 09:04 AM | |
1 | 01-09-2017 07:52 AM | |
1 | 01-09-2017 08:59 AM | |
1 | 04-11-2014 10:02 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:22 AM
|