Tag: Geodatabase

File Geodatabase API details

(Update: You can find the most recent release of the File Gdb API right HERE)

While not exactly an early Xmas present (as a certain beaksnake may have promised), the API for the file geodatabase will be hitting the beta stage in January. Before you get your hands on it, here are some details about the File GDB API courtesy of Craig Gilgrass’ right frontal lobe:

The File Geodatabase API provides a non-ArcObjects based means by which advanced developers can work with File Geodatabases. The File Geodatabase API will be C++ based and will provide the ability to perform the following tasks: Continue reading

Posted in Geodata | Tagged , , , , , | 22 Comments

User Presentations @ 2011 DevSummit

Last year we ramped up the cool factor of the Developer Summit a few notches by allowing users to give presentations. We accepted a whole whack of abstracts submitted by users, voted on them, and then hosted a user presentation track based on the abstracts that received the most votes.

I attended a few of the user presentations last year and they offered a nice change of pace from the tech workshops and touched on some interesting topics.

We’ll be hosting a user track down in Palm Springs again at the 2011 DevSummit and are currently accepting abstracts. Abstract submission has also been integrated into our ideas website.

The deadline for submission is Dec 31st so get cracking ppl

Posted in Geodata | Tagged , | Leave a comment

Good information on Geodatabase replication

The Geodatabase team recently posted some good information on network considerations when using geodatabase replication.

Geodatabase replication works in both connected and disconnected environments. Which of these environments is most appropriate for your replication requirements depends on what type of network you have and the speed of that network. Visit the Geodatabase blog for more….

Posted in Uncategorized | Tagged , , , , | Leave a comment

Network considerations when using geodatabase replication

Geodatabase replication works in both connected and disconnected environments. Which of these environments is most appropriate for your replication requirements depends on what type of network you have and the speed of that network.

What’s the difference between connected and disconnected replication again?

Well Lenny, let’s take a look: Continue reading

Posted in Geodata | Tagged , , | 2 Comments

Data Reviewer Checks vs. Geodatabase Topology

Recently, I was asked, “What’s the difference between Data Reviewer checks and geodatabase topology?”
Those who have worked with both Data Reviewer and geodatabase topology may have noticed similarities, specifically with the Geometry on Geometry check. I’d like to highlight a few of the key differences below.
First and foremost, the Data Reviewer checks are not meant to replace geodatabase topology. The geodatabase topology rules are more extensive than the Data Reviewer spatial checks. However, there are some requirements in geodatabase topology, such as all feature classes that participate in the topology must reside in the same feature dataset, which may not fit with how you manage your spatial data.  

Continue reading

Posted in Editing | Tagged , , , , , , , , , | 1 Comment

ArcGIS 9.x to ArcGIS 10

Migrating from ArcGIS 9.x to ArcGIS 10 is straightforward.  All your data (maps, layers, rasters, geodatabases, etc.) is directly readable in ArcGIS 10.  However once you start using ArcGIS 10, you will need to save your documents (maps, layers, etc.) out in 9.x formats in order to share them with 9.x users. Use the Save a Copy command in ArcMap to create 9.x version of your map document. For more info on Save a Copy command.

Geodatabases can remain in 9.3.1 format and be used in 9.3.1 and 10. However, if you want to take advantage of the new geodatabase improvements in ArcGIS 10, you need to upgrade the geodatabase to 10, at which time 9.x clients will not be able to read it.  In order to help with sharing data among various versions, the Create Geodatabase tool now allows you to create older versions of the Geodatabase so you can copy features from ArcGIS 10 into an older geodatabase to share with other users.

Posted in Uncategorized | Tagged , , , , , | 8 Comments

Release of the Editing template for ArcGIS 10 – Part 2

Attribute Assistant

The attribute assistant has some significant changes for ArcGIS 10.  When you download it, you will not find the installer that you might be used to.  You will just see a simple ArcGIS Add-in.  This should help you deploy this extension to your organization.  We also modified some of the existing functions and added a few new ones.  The table below discus’s the different methods for this extension.

Value Method Value Info Details Requirements
GET_ADDRESS_USING_ARCGIS_SERVICE Url to a Geocoding service This method preforms a reverse geocode.  The default service is the ArcGIS.com geocoding service.  You can specify your own. String Field
TIMESTAMP None Stores current date and time. Date or String Field
CURRENT_USER

W – stores full windows login name as domainusername

U – stores just the windows usernameD – stores the connected database user for the edit session  If you leave VALUE_DATA blank, it will store the database user name if available otherwise store full windows login.

Stores current user name. String Field
LAST_VALUE None Repeats the last value used for a field.  
X_COORDINATE None Stores the X coordinate in database units  
Y_COORDINATE None Stores the Y coordinate in database units  
LATITUDE None Stores the Y coordinate projected to WGS84 decimal degrees.  
LONGITUDE None Stores the X coordinate projected to WGS84 decimal degrees.  
FIELD Field Name Copies one field to another field in the same feature.  
JUNCTION_ROTATION

A  - if you enter an A it will store the rotation using an arithmetic rotation.

If you leave VALUE_DATA blank, it will store the rotation using a geographic rotation.

Stores a rotation angle for a junction feature based on connected edge features by storing a rotation angle in the specified field.  Requires geometric network.  Target must be a point feature class that participates in the geometric network as a simple junction.  Requires ArcEditor or ArcInfo.   
LENGTH None Stores calculated length of line feature.   
SET_MEASURES If you leave ValueInfo blank, it will calculate the Ms starting with zero and ending with the length of the line.   If you enter a P for ValueInfo, it will calculate the Ms starting with zero and ending with 100. Populates the M coordinates in a line which enables using Add Route Events to point and line events dynamically along line features Requires a line with M’s turned on
TO_EDGE_FIELD <Field Name> Transfers a field value from a connected edge feature to a junction feature.  Must be assigned to a point feature class that participates in a geometric network.  Requires ArcEditor or ArcInfo. 
FROM_EDGE_FIELD <Field Name> Transfers a field value from a connected edge feature to a junction feature.  Must be assigned to a point feature class that participates in a geometric network.  Requires ArcEditor or ArcInfo. 
FROM_JUNCTION_FIELD <Field Name> Stores a value that is obtained from a specified field in the junction feature at the start of the currently edited line.  Must be assigned to a line feature class that participates in a geometric network.  Requires ArcEditor or ArcInfo. 
TO_JUNCTION_FIELD <Field Name> Stores a value that is obtained from a specified field in the junction feature at the end of the currently edited line.  Must be assigned to a line feature class that participates in a geometric network.  Requires ArcEditor or ArcInfo. 
GENERATE_ID

<FieldName>| <optionalSequenceWidth>| <optionalFormatString>[seq]

Example:WHYDRANT|0|HYD-[seq]

Increments a column in an unversioned table and stores that newly incremented value. Uses an unversioned table that is typically called GenerateId (change in AttributeAssistant.config) to store and increment unique sequence numbers.     

GENERATE_ID_BY_AREA(Removed)

GENERATE_ID_BY_INTERSECT 

<Layer Name> |<Layer Field Name>|<Sequence Field Name from GenerateID Table>| |optionalSequenceWidth|[id]optionalFormatString[seq]<any order of ID and SEQ> 

Example: Grid|GRID_ID|GRIDIDX|4|GRID[ID]-[SEQ] 

The result would look look like GRID5-0002, if the grid you intersected ID was 5 and the next number in the table was 2.

This tool requires you create fields in the Generate ID table that are a combination of the GRIDIDX(the Sequence Field Name) and the Grid ID. So the tools looks at the interesected grid, gets the ID from it, combines it with the <Sequence Field Name from GenerateID Table> to look for a field in the Generate ID table to get an seq for that grid. Say the grid you created a feature in was 5, you need a field called GRIDIDX5 in the generate ID table. 

 
EXPRESSION

Expression

Example:replace(([FROMMH] & “-” & [TOMH]),”MH-”,”")

Stores the results of an expression.   
GUID

Optionally enter one of the letters below to format the GUID as desired.

N – GUID  with no special characters – length 32 D – GUID with dashes – length 36 B - GUID with dashes and braces – length 38 P – GUID with dashes and parenthesis  - length 38 default – GUID with dashes and braces – length 38 Leave the ValueInfo Field blank to get the default GUID format.  Example: {3F2504E0-4F89-11D3-9A0C-0305E82C3301}

Stores a new GUID.  The target field must be a field type string field and must be long enough to store the desired format of GUID.
INTERSECTING_FEATURE

<Layer Name>,<Layer Name>,..|<Field Name>

Example: ssPressurizedMain,ssGravityMain|DIAMETER

Gets a value from an intersecting feature in the specified layer.  You can specify any number of layers to look for by listing them with commas between their names.   
INTERSECTING_RASTER

<Layer Name>,<Layer Name>,..|Label

Example: FiveMeterSurface|Elevation:

Gets a value from an intersecting raster cell in the specified layer.  You can specify any number of layers to look for by listing them with commas between their names.   
INTERSECTING_FEATURE_DISTANCE

<Layer Name>, <Layer Name>,..|<Field Name>

Example: ssPressurizedMain,ssGravityMain|FACILITYID

Gets a value from an intersecting feature in the specified layer and reports the distance along the line.  You can specify any number of layers to look for by listing them with commas between their names.   
NEAREST_FEATURE <Layer Name>,<Layer Name>..|<Field Name>|<Search Distance>

Example: wMeter,sLateralPoint|ACCOUNT|100 

Gets a value from the nearest feature in the specified layer.   

Posted in Water Utilities | Tagged , , , , , , , , , , , , , , | Leave a comment

Release of the Editing template for ArcGIS 10

We are happy to announce the release of the Infrastructure Editing Template for ArcGIS 10.This new release takes advantage of some of the great additions to ArcGIS 10.  You will find a new datamodel which encompasses many new layers.  You will also see an updated symbol set, a symbol set designed to be overlaid on imagery, topographic, and parcel basemaps.&nbsp; The editing map document was updated to show you have to set up feature templates.  You will see how we reordered, highlighted and set some fields to read only, as well as hide a few.  We think you will like the new data model, symbology and the new mxd.  Now on to the tools!

We migrated the Editing and Reporting toolbars and the Attribute Assistant to ArcGIS 10 Add-ins.  Not only did we upgrade them to ArcGIS 10, but included a series of bug fixes, config changes and new functions, which all came from your suggestions, so please keep the feedback coming.  Lets breakdown the Add-In’s and discuss the changes.

Desktop Editing Toolbar – Changes and New Tools

The first thing you might notice is the Add Laterals icons are missing, but there is a new one that sort of looks like it.  We compressed the Add Lateral tools into one function that looks at the selected features and compares them to the config file and generates laterals from them.  This allows you to generate many types of laterals at once.  To the right of it, there is a new tool, Connect Closest.  This tool will connect a series of points, say a row of manholes, with a line, such as a sewer main.  If we look to the left you will see a a large red button with a ! in it.  This is simple layer inspector.  It looks at a feature class and lets you step through each feature one at a time.  Real handy for reviewing those redlines or field notes.  If we keep moving left, you will see an icon with a line and 123 in it.  This tool allows you to quickly calibrate a line that is M enabled.  Should help you plot your CCTV data on your sewer.  Next is the Merge Geometric Network Features, an ArcScript that has been around a while, so we thought we add it to the toolbar.  I agree, the icon looks like it is breaking features apart.  We will see if we can change this to something more meaningful.  On the far right, is a new tool included with the Attribute Assistant.  This tool triggers the change event for all selected features.  So you can manually fire out the Attribute Assistant rules.  The last new tool on the toolbar is the Incremental Network Loader.  You can find out about the new tool here

Desktop Reporting Toolbar – Changes and New Tools

We mainly enhanced the existing tools.  We had a bunch of request to return the edges of a trace in the selection set, so we added another trace button below each trace that does just this.  There is a new way to run the Isolation trace, in batch.  The Summary Isolation trace will loop through all selected water mains and run an isolation trace for each.  The results are stored into a feature class which you will find in the Capital Planning dataset.  I warn you against running this on all your mains, it takes a while(don’t worry, the tool warns you to if you make the mistake on clicking it without a selection set).  A new tool that we are all excited about is the Profile Graph tool.  This tool lets you pick two manholes, runs a find path trace between them, intersects the result with an elevation surface and plots the manholes, mains and elevation onto a graph for you.  We think you will really like this tool.  There is a known issue right now though.  When the chart opens, you have to turn off the manholes in the chart properties, then uncheck automatic from the left axis.  You can then turn the manholes back on.  The last tool on the toolbar, Attribute Transfer Loader, was a request from a user who was transferring data using the attribute transfer tools.  If you ever used these tools, you know you had to set them up each time you opened ArcMap.  You can now set up the mapping in the config and load it to the attribute transfer dialog.  

Desktop Tools – Config File Changes

If you changed the config file for 9.3.1, you will need to move these changes into the new config file.  You will see in the new config, we reworked a lot of the entries in a nested xml structure.  This allowed us to include some new options and load the config file faster.  For example, the Add Laterals Tools.  This was a long series of entries and you were limited to the 3 types we exposed.  Now you will see you can use these tools on any number features.  Here is a screen shot.

Also, you will see that there is an xml array that defines the points along.  We had a lot of request to allow the option to add more than one point along the line.  With this xml array, you can have it add any number of points along the line, I left a sample in the config to show how to do this, notice it is commented out. 

Desktop Tools – Construction Tools

You will also find an installer for a set of construction tools.  These construction tools call some of the functions on the toolbar and expose some new functions.  These new tools should further speed up editing and creating new assets with ArcGIS.  Note: at the moment, the construction tools and the toolbar use the same config, but they each have their own copy.  We are looking into how to share one config between them. 

Let’s take a detailed look at them.  

                Screen shot of the new construction tools for points and lines.

 

For lines, there is one new tool, Create a line with end points.  This tool will end two points at the end of the line you sketch.  The config file controls will points get added to what line.  So you need to modify the config to list the line layer and the ending point layer.  Using the new xml config file, you can specify any number of layers for this to work on.

For points, there are a number of new tools.  Some are samples that come with ArcGIS, some are new tools we added, let’s start at the top.  The Points along a line at is a great sample that comes with in the Developer Kit.  A great sample for creating a series of points at an interval.  Next is a custom tool, Add a connection and the lateral.  This tool does the same thing that the Add Lateral tool does on the toolbar, but this one lets you create the point and immediately connect it to the main.  The Create a point and line tool does the same thing Connect Closest tool does, but this does it as you click.  Imagine you are creating manholes.  Each time you drop one, it searches for the closest manhole and adds the main.  The last construction tool is the Add a point and split an intersecting line tool.  This does exactly what it says, split the line that you click on.

We are very happy and proud with this template for ArcGIS 10.  Let us know if you have any issues or any suggestions.   In the next blog, we will talk about some changes in the Attribute Assistant.

Posted in Water Utilities | Tagged , , , , , , , , , , , , , , | 9 Comments

Creating multiple geodatabases in a single DBMS instance – Part II

 

A few weeks ago, we posted that there is a new PDF that consolidates all the help topics on user-schema geodatabases in Oracle. In that post, it was mentioned that user-schema geodatabases were implemented so you could store multiple geodatabases in one Oracle instance.

Being able to store more than one geodatabase in a single Oracle instance is significant because in Oracle, the instance is basically the database. Prior to the advent of user-schema geodatabases at ArcGIS 9.2, if you wanted to set up a second geodatabase in Oracle, you had to install and setup another instance of Oracle and create your second geodatabase in that.

This is different from how other database management systems work. In IBM DB2, Informix IDS, Microsoft SQL Server, and PostgreSQL, you can have multiple databases per DBMS instance (or database cluster). You can create a geodatabase in each one of those databases, thereby having multiple, independent geodatabases on one DBMS instance. Continue reading

Posted in Geodata | Tagged , , , | Leave a comment

Creating an earlier version of a file or personal geodatabase

By Rajinder Nagi, Esri Research Cartographer

Earlier GDB Thumb

A very helpful blog entry about creating an earlier version of file or personal geodatabase with ArcMap 10 was recently posted on the ArcGIS Geodatabase blog. With the Create File GDB and Create Personal GDB tools, you have the option to create version 10, 9.3, or 9.2 geodatabases, which will help you to share easily share data with people using older releases of the software. As noted in the blog entry, “Being able to create an older release geodatabase from an ArcGIS 10 client allows you to more easily share data with people or agencies who are using older releases of ArcGIS. And, since ArcGIS 10 can access and edit these geodatabases, you can continue to use them without upgrading.”  Read more about this in the geodatabase blog entry.

Posted in Mapping | Tagged , , , , | 2 Comments