Feed-aggregator

Have you ever set up a workspace in CityEngine, copied your project into the workspace folder, but found that CityEngine didn’t recognize the new folder? This can be avoided by following the import project workflow described below.

1. Go to File > Import…
2. Select Project > Existing Projects into Workspace.

3. Select the root directory and then select the project to be imported.

You can also choose the option to copy the project data over.  If this option is not selected, the project content will be linked into the workspace.

Once the import process completes, the projects folder will display in the navigator for the current workspace.  If it does not show, you may need to refresh the worksapce (File > Refresh Workspace).

Timothy H. – Raster/3D Support Analyst

Have you ever had a 1:M relationship but did not want to perform a relate? You might consider using the Make Query Table tool to accomplish this task. Typically when performing a 1:M join, only the first record will be joined and the subsequent records will not. In instances such as this, I often recommend using a relate or relationship class instead of a join. However, using the Make Query Table tool is another option for performing this task and can also be an effective way of querying out matching records from two separate tables or feature classes.

You can access this tool by navigating to the ArcToolbox > Data Management Tools > Layers and Table Views >  Make Query Table. To perform this, your tables and/or feature classes must be in the same location (the same file, personal, or SDE geodatabase).

Steps

1. First add your table, then your feature class to the Input tables box.
2. Select the Fields you want in the resulting table view.
   *If you want to include geometry in the output and not just a table view, be sure to select the shape fields.
3. Click SQL. Write a statement similar to the one in the following graphic. This statement is basically saying, give me all records that match between the table and the feature class. Click OK.
4. Give your Table a name.
5. Select the option to use Virtual Key Fields.
6. Click OK.
7. Once this finishes running, export the output to a new feature class, as this is only an event layer and will not save outside of the MXD.

For more on this tool, please visit the Resource Center help page for the Make Query Table tool.

Lucas D. – Desktop Support Analyst

Een paar weken terug presenteerde branchevereniging Geobusiness de Marktmonitor, de "state of the union" van de geosector in Nederland. Ik pik er een paar opvallende cijfers uit. De cijfers hebben allemaal betrekking op het bedrijfsleven, voor 2012 is er een verwachting gepeild.

Het consumentsegment als afzetmarkt kent tussen 2009 en 2012 een spectaculaire daling. Werd de 4% die 2009 al als "bescheiden" gekenmerkt, in 2012 is dat teruggelopen tot 1% van de omzet uit geoproducten en -diensten. 75% ingeleverd (binnen een totale omzetdaling van ca. 15%, op een totale omzet van zo'n 900 miljoen). Dat doet bijna vermoeden dat TomTom in 2009 wél tot de respondenten behoorde maar voor de monitor van 2012 geen zin had te reageren. Hoewel...in 2009 bestond dit segment uit "internetapplicaties, geo-informatie rondom onroerend goedtransactie en wegenkaarten en luchtfotos." Zijn die eerste weggelekt naar andere sectoren? Is de onroerend goedmarkt ingestort? Zijn OpenStreetMap en het NWB de markt aan het verpesten? Moet die economische waardecreatie op basis van open data geheel gerealiseerd worden?

Dat het aantal werknemers (of arbeidsplaatsen of FTE's?) daalt zal weinigen verrassen. Het positieve is dat in de geosector de krimp kleiner is dan in andere sectoren waarin ingenieursbureaus werkzaam zijn (denk aan de bouwsector!). Daarmee valt het aantal vacatures ook flink terug. Vervelend voor schoolverlaters en zij-instromers die in de geo-sector het paradijs van de eeuwigdurende volledige werkgelegenheid dachten te vinden. en lastig voor overheden die hun overtallige personeel dus niet gemakkelijk aan de straatstenen van het bedrijfsleven zullen kwijtraken.

In de monitor 2009/2010 werd 22% genoemd als percentage van het Research & Development budget dat aan geo werd uitgegeven, in de huidige monitor staat 7% genoemd. Even goed opletten, dat laatste betreft het percentage van de totale geo-omzet die in geo-R&D wordt gestoken. Overigens ruim 2x zo groot als het generieke R&D percentage, blijkbaar zijn we een innovatieve sector... Of komen we nooit aan het oogsten toe? Om het even in perspectief te plaatsen: Google steekt 14% van de omzet in R&D, maar Apple houdt het zeer bescheiden met 2,2% (cijfers 2011).

Om af te sluiten de groeibriljantjes: het verzamelde bedrijfsleven verwacht de meeste groei in het ontwikkelen van geo-services, op de voet gevolgd door webservices. Of de hierbij genoemde percentages (22% resp. 21%) het percentage van de respondenten betreft dat die groei verwacht, of het percentage verwachte groei is niet geheel duidelijk.

Al met al interessant cijfermateriaal dat vooralsnog meer vragen oproept dan beantwoordt. Daar kan nog best een analyseslag overheen, ik mis in ieder geval nog een regionale (geo!) analyse. Als de achterliggende cijfers nou door Geobusiness als open data beschikbaar worden gesteld zijn er vast wel geo-analysten te vinden die die analyse willen uitvoeren. (en vooruit: dan bakken we er ook nog een App omheen).

Een paar weken terug presenteerde branchevereniging Geobusiness de Marktmonitor, de "state of the union" van de geosector in Nederland. Ik pik er een paar opvallende cijfers uit. De cijfers hebben allemaal betrekking op het bedrijfsleven, voor 2012 is er een verwachting gepeild.

Het consumentsegment als afzetmarkt kent tussen 2009 en 2012 een spectaculaire daling. Werd de 4% die 2009 al als "bescheiden" gekenmerkt, in 2012 is dat teruggelopen tot 1% van de omzet uit geoproducten en -diensten. 75% ingeleverd (binnen een totale omzetdaling van ca. 15%, op een totale omzet van zo'n 900 miljoen). Dat doet bijna vermoeden dat TomTom in 2009 wél tot de respondenten behoorde maar voor de monitor van 2012 geen zin had te reageren. Hoewel...in 2009 bestond dit segment uit "internetapplicaties, geo-informatie rondom onroerend goedtransactie en wegenkaarten en luchtfotos." Zijn die eerste weggelekt naar andere sectoren? Is de onroerend goedmarkt ingestort? Zijn OpenStreetMap en het NWB de markt aan het verpesten? Moet die economische waardecreatie op basis van open data geheel gerealiseerd worden?

Dat het aantal werknemers (of arbeidsplaatsen of FTE's?) daalt zal weinigen verrassen. Het positieve is dat in de geosector de krimp kleiner is dan in andere sectoren waarin ingenieursbureaus werkzaam zijn (denk aan de bouwsector!). Daarmee valt het aantal vacatures ook flink terug. Vervelend voor schoolverlaters en zij-instromers die in de geo-sector het paradijs van de eeuwigdurende volledige werkgelegenheid dachten te vinden. en lastig voor overheden die hun overtallige personeel dus niet gemakkelijk aan de straatstenen van het bedrijfsleven zullen kwijtraken.

In de monitor 2009/2010 werd 22% genoemd als percentage van het Research & Development budget dat aan geo werd uitgegeven, in de huidige monitor staat 7% genoemd. Even goed opletten, dat laatste betreft het percentage van de totale geo-omzet die in geo-R&D wordt gestoken. Overigens ruim 2x zo groot als het generieke R&D percentage, blijkbaar zijn we een innovatieve sector... Of komen we nooit aan het oogsten toe? Om het even in perspectief te plaatsen: Google steekt 14% van de omzet in R&D, maar Apple houdt het zeer bescheiden met 2,2% (cijfers 2011).

Om af te sluiten de groeibriljantjes: het verzamelde bedrijfsleven verwacht de meeste groei in het ontwikkelen van geo-services, op de voet gevolgd door webservices. Of de hierbij genoemde percentages (22% resp. 21%) het percentage van de respondenten betreft dat die groei verwacht, of het percentage verwachte groei is niet geheel duidelijk.

Al met al interessant cijfermateriaal dat vooralsnog meer vragen oproept dan beantwoordt. Daar kan nog best een analyseslag overheen, ik mis in ieder geval nog een regionale (geo!) analyse. Als de achterliggende cijfers nou door Geobusiness als open data beschikbaar worden gesteld zijn er vast wel geo-analysten te vinden die die analyse willen uitvoeren. (en vooruit: dan bakken we er ook nog een App omheen).

Most of us here are relatively familiar with ArcGIS Server for .Net. However, in support our exposure to the Java product is relatively limited, simply because it seems that fewer customers have implemented ArcGIS Server for Java. In this post, I’ll try to cover a topic that comes up every now and then in support, how to secure both OGC and Esri GIS Service endpoints provided by the same instance of ArcGIS Server. This concept is similar to but implemented differently than the ArcGIS Server for .Net help topic “Multiple ArcGIS Server Web Instances for Security“.

Before we begin, lets review a couple of best practices (things that are good to know) that we should understand prior to engaging in any configurations.

First, have a quick look at the documentation regarding exporting the ArcGIS Server 10 for Java web service and REST handlers. The Tomcat web server that ships with ArcGIS Server for Java should be used for development and ArcGIS Server administration. It’s not really meant for handling the load of production work. We recommend using ArcGIS Server manager to export your REST, web service, and token applications out to a standard .WAR file and then deploying those .WAR files to your favorite J2EE web server for production use.

Second, regarding security and OGC services:

It’s important to recognize that there is no provision in the OGC spec for token based authentication with OGC services. This means that if you’d like to secure your WMS, WFS, or WCS Services, you’ll need to use a more standard authentication mechanism other than the Esri provided token service, like HTTP BASIC or DIGEST authentication.

Out of the box,  without deploying the GIS Server handlers to an external J2EE server, ArcGIS Server for Java will be limited to a single authentication mechanism. However, as we’ll discuss below, we can work around this limitation by deploying multiple web services handlers – each with it’s own authentication mechanism.

To accommodate this configuration, we’ll use Tomcat 7 (either 32- or 64-bit is fine, just be sure that if you’ve got the same bit level Java installed as whichever Tomcat you choose).

While you’re setting up Tomcat, since we’ll be working with authentication, you’ll also want to stand up HTTPS/SSL. Otherwise, your credentials and tokens will be passed in clear text over the wire. In my testing, I generally create a SSL repository and self signed certificate using the keytool command. SSL is required when working with the token service with ArcGIS Server for Java, and there is not a supported way to disable this requirement like there is in the .Net product.

After Tomcat is installed and configured with SSL, set up your security store. For this example, we’ll set ArcGIS Server to use ArcGIS Token Authentication and enable security for your services. Test to verify that security is working.

Next, we’ll export the SOAP (web services), REST, and token service handlers, and then deploy them to the external instance of Tomcat and test to verify that the services can be reached. When I export my web handlers, I usually stick with generic application names, like ‘REST’, ‘Services’, and ‘Tokens’.

When you’re configuring the SOAP and REST handlers, make sure that you enable authentication using the ArcGIS token service, and make sure that the token service URL is pointing to the token service handler deployed on the “external” instance of Tomcat.

After they’ve been successfully deployed to Tomcat, test to verify that you can reach your REST endpoints and service WSDLs. Keep in mind that unless a new context path is explicitly defined, these applications will deploy to the root of the web server. That means that your URLs to your service endpoints will look similar to these (using Tomcat’s default HTTPS port):

https://myserver:8443/services?wsdl

https://myserver:8443/rest/services

Once you’ve tested to verify that the service handlers are working as expected, including requiring authentication to the secured services, it’s time to deploy another services handler. This one we’ll use to access our secure OGC services. In this case, since we know that OGC services do not support token based authentication, we’ll configure the services handler to use basic or digest authentication. We can use the same security store created earlier when we secured the services, but we can’t use the token service.

Export this application as a .WAR, and name it something like “OGC”.

Keep in mind that since we’re now using an external instance of Tomcat, we’ll also need to make a quick modification to the tomcat-users.xml file. Otherwise, Tomcat won’t be able to recognize the users and roles you set with the internal Tomcat and service handlers that were created using the ArcGIS Server Manager GUI experience. By default, you’ll find that file here: C:\Program Files\Apache Software Foundation\Tomcat 7.0\conf

Open Tomcat-Users.xml with a text editor and uncomment the users and roles section, then add lines to this file to match the users and you’ve created you created in the GIS Server security store, like this:

Finally, give the Apache Tomcat service a restart so that Tomcat recognizes the new users and roles.

You should then be able to pass credentials to reach your OCG services, like this:

https://myserver:8443/OGC/myservice/mapserver/wmsserver?request=getcapabilities

That’s it!

To summarize, because OGC services do not support token based authentication, we essentially exported two sets of service handlers: one for our REST services using the token service, and another for our OGC services using basic or digest authentication. Services delivered over SOAP may be authenticated using either endpoint, depending on the requirements of the client application.

Randall W. – Server Support Analyst

New features have been added to ArcGIS Ideas that enhance the site and improve access to ArcGIS Workspaces.

Last month we extended ArcGIS Ideas by adding ArcGIS Workspaces. Workspaces provide a way to collaborate on ideas with other members of the GIS community in a secure environment. (Check out Esri Presents ArcGIS Workspaces! to learn more.) This week we added the ability to request new workspaces and to access workspaces directly from the idea in ArcGIS Ideas.

The “Request Workspace” button appears next to ideas that have over 500 points and are not already implemented, under consideration, or deferred.

The “Access Workspace” button appears next to ideas that have already had a workspace created. Clicking this button sends a request for permissions to access this workspace.

Those who already have permissions can enter the workspace through the Workspaces link on the ArcGIS Ideas main page. Users can also request a new workspace directly on the ArcGIS Workspaces site.

Additionally, we’ve added a way to report abuse in ArcGIS Ideas. The “Report Abuse” link can be used to send messages to the site administrators about ideas or comments that do not contribute to a respectful and tolerant environment.

We are always looking for ways to provide better collaborative tools for the GIS community through ArcGIS Ideas and ArcGIS Workspaces. If you have any comments or questions, please email us, leave a comment below or submit a new idea!

Joe – Online Support Resources

"The fabled blue marker, what do you do?!"

Our lives are filled with things we often overlook. Case in point, what are the little blue reflectors on the road that you see on the way home from work every day? I’ve tried to establish a pattern. Are they marking the center of the lane? Sometimes they’re right on the road center line, sometimes they’re right in the middle of your wheel path, thump thump, and sometimes they’re barely on the road at all. If you look, you’ll see them all the time; you just have no earthly clue as to what they actually do.

The OLE DB connection is not so different. It’s always sitting there in ArcCatalog staring right back at you under Database Connections. You usually skip right over it on your way to adding a Spatial Database Connection. Today, however, I urge you to stop, peer under the hood, and look at what an OLE DB connection can do.

The OLE DB connection is a window into the abyss, a.k.a. your geodatabase repository. This area is typically off limits. Perhaps your DBA isn’t a fan of people tinkering around in the RDBMS. Esri typically says “hands off” as well, since we don’t usually support errors caused by messing around with the underlying repository tables. Their sensitive nature aside, these tables can be quite helpful and using an OLE DB connection to access them is read-only, so it’s also safe. Your DBA can rest easy.

Many of the problems you might have during the course of a normal week might be sniffed out by using this connection. I typically use mine at least once a week, maybe even three or four times depending on how heavy my workload is. I’ll give a couple examples on how this connection can help.

Pretend, for a moment, that you’re trying to take your geodatabase to a fully compressed state (i.e., State 0). The dialog indicates that the process has completed successfully, but since you’re a rock star GIS professional, you know that a successful compression is not always indicative of a full compression.  So you crack open the OLE DB connection, scroll down to your compress_log table, and look up your end_state_count. It reveals that you have a count of 1. Since 0 is a state and is always present, you know that a count of 1 indicates that you’ve successfully achieved a full compression.

But what if the value isn’t 1? What if the end_state_count reveals that there are two states remaining? Not a problem, you scroll down to the state_locks table, revealing that state_id 233 is being locked by sde_id 622. You then deftly maneuver up to the process_information table and you find that sde_id 622 is your SOC account. Then it dawns on you, you never did disconnect your web server, so you stop your web server, freeing up this connection and it’s resulting locks, compress again, and you’ve achieved full compression, all without ever cracking open Management Studio or SQL Developer and freaking out your DBA.

"Ye Ole Db Connection"

Making the connection is relatively easy. Microsoft OLE DB connection drivers, which can handle Microsoft SQL Server and Oracle databases, are automatically installed. However, you may have to install the drivers for PostgreSQL databases yourself. Once installed, just click on “Add OLE DB Connection” within ArcCatalog, highlight the provider you want to use, fill out the requested information, and test the connection. If successful, click OK and you’re in! I know you 10.1 users are out there too. Don’t worry, the link to opening an OLE DB connection is no longer on your ArcCatalog tree, but it’s still around. It’s now a button for your toolbar, so just click on Customize, go to Customize mode, select the Commands tab, highlight ArcCatalog, and drag the Add OLE DB Connection to your toolbar.

Good luck!

Oh yeah, the next time you see a blue marker on the road, glance to the right. I bet you’ll find a fire hydrant.

Steven E. – Geodata Support Analyst

Edited on 4/27.

Dat kartografie een vorm van kunst is mag als bekend worden verondersteld. Daarmee leek de belangstelling van de geo-sector voor deze "linkse hobby" wel op te houden, maar daar is verandering in gekomen.

Sommige gemeenten hebben in hun geoviewer al een thema kunst in de openbare ruimte opgenomen, soms met achterliggende informatie over het object en de kunstenaar. En ook bij diverse open data events blijkt kunst op straat een dankbaar onderwerp om in een app te verwerken. Het feit dat bij afdelingen cuiltuur het vrijgeven van data over kunstwerken draagt daar natuurlijk ruimschoots aan bij.

Bij die apps en viewers was het idee dat de kunst (het object) qua locatie statisch was, en de de gebruiker (het waarnemende subject) dynamisch, en daarom van een App voor de smartphone met GPS moest worden voorzien.

Een bericht in de NRC Next van 24 april 2012 leert dat er nog meer geo in kunst zit. Door toenemende diefstallen van bronzen beelden zien meer en meer gemeenten zich genoodzaakt hun kunst naar binnen te halen. Vorige maand werden uit het beeldenpark Beerschoten in De Bilt (dat is nota bene de plek waar mijn geocarrière is begonnen!) een drietal beelden van hun sokkel gerukt om daarmee zo'n 500 euro aan waarde van het brons te cashen.

Het Arnhemse bedrijf Scope Solutions heeft een systeem ontwikkeld waarmee bij forse beweging de GPS positie van het kunstwerk wordt doorgepiept aan de alarmcentrale. Lijkt mij leuk als die data als open data beschikbaar kan worden gesteld, liefst in een dynamische webservice die de gemeenten in hun geoviewer kunnen integeren. Een spannende combinatie van cultuur en opsporing verzocht!

Thank you for visiting the Support Services Blog. This content is no longer available.

Recently a user wanted to be able to standardize the ArcGIS Explorer for Desktop application for GIS clients in his organization. He found that once ArcGIS Explorer was configured locally on his machine, he was able to share the default .NMF map document file with users, but the .NMF only held the configuration information for layers in the table of contents – not for add-ins or geoprocessing tools.

The Application Configuration Manager could be used to allow or prevent the usage of specific ArcGIS Explorer functionality like the analysis tools or to add new functionality, but couldn’t be used to persist a URL to a specific geoprocessing service. The user thought it would be great if ArcGIS Explorer could be provided to users in such a way that the references to add-ins and geoprocessing tasks remained in place for users installing ArcGIS Exolorer for Desktop thus saving clients the time it may take to set up the environment as desired.

There are two places that ArcGIS Explorer for Desktop keeps reference to data layers:

1. The default .NMF document itself
2. The add-ins folder

After saving the default document in ArcGIS Explorer, use these simple steps to homogenize the Explorer experience for all employees in the department.

1. The admin should:

• Copy the folder “C:\Users\<username>\AppData\Roaming\ESRI\arcgis explorer\AddIns” to a place accessible to network users.
• Copy the file “C:\Users\<username>\Documents\ArcGIS Explorer\My Default Map.nmf” to a place accessible to network users.

2.  The users should:

• Install ArcGIS Explorer.
• Copy the ad-ins folder referenced above to the corresponding location on their local machine.
• Copy the ‘My Default Map.NMF’ to the corresponding location on their local machine.

When ArcGIS Explorer for Desktop is started on the user’s machine, the experience should be identical to that of the application set up by the administrator.

Randal W. – ArcGIS for Server Support Analyst

CityEngine is a powerful product that can build amazing cityscapes.  Digging into this software can be a little tricky at first; however, the more you use it, the easier the functionality becomes.  Esri CityEngine on the ArcGIS Resource Center is a great place to start, as you take on the learning curve.  There are some tutorial videos and data templates available that will help you to better understand the software.  In addition to these resources, here are five quick tips for basic functionality within CityEngine.

Downloading Tutorials and Example Data Open the Help menu > Download Tutorials, then download the desired Tutorials and Examples from the Download Tutorials and Examples dialog.

During the download process, the option to run in the background can be set in the data status window, so that you can continue to work on your scene while the data is loaded.

View Settings There are a wide range of view settings that can be accessed from the Viewport settings dropdown. To the scene, you can alter lighting settings, activate reference information (grid, axes, compass, etc.).

There are also settings for the 3D display, such as wireframe, shaded, textured, or textured display with wireframe. Also, take note of the shortcut keys for toggling these settings.

Save Screenshot From the bookmarks button in the viewport, you can access the functionality to save a snapshot/screenshot. The output dimensions can be set along with additional information elements. There are a variety of formats available to save the screenshot (.png, .jpg, .tiff, .bmp, etc.).

CityEngine Shortcuts The Key Assist can be accessed from the Help menu or by pressing CTRL + SHIFT + L.  This will open a dialog at the bottom right corner with a list of all the shortcut keys.

With the Key Assist Window you can press CTRL + SHIFT + L again, to open the Preference dialog, where the default settings can be modified.

Window Layout There are many windows available within CityEngine, and you may find yourself looking for a specific one, such as the Viewport or Navigator. The Window Menu will give you access to all windows individually. Using the spacebar, you can maximize a window to the full screen, docking the other window on the right border. Predefined layouts are available via the Window Menu > Layout.

There is also the ability to save a custom perspective if you have a particular setup you like. I hope these tips have helped get you started using CityEngine. If you need additional help, visit the CityEngine section in the Support Knowledge Base or the CityEngine forums.

Timothy H. – Raster/3D Support Analyst

As much as we would all like to avoid calling support for help with software issues, there are times that it is unavoidable. When you find yourself preparing to contact support, there are a few things that you can do to make the process a little smoother. Here is a compilation of blogs and resources that will help resolve the issue as efficiently as possible.

First, determine if Support Services is the best resource for the issue. Depending upon your question, it may be better answered by one of the other Esri teams.

The Right Resource, At The Right Time…

Be sure to check that you have installed the latest Patches and Service Packs. Many bugs are fixed within these updates. You can search for bugs on the support site as well.

Think you’ve found a bug… search for it online

Decide on how you plan to contact support, and ensure that you are an authorized caller (Attention Authorized Callers: Your Global Account Can Unlock Features on the Support Services Website). There currently are three contact methods (phone, email, and chat), and the following information can help you better utilize each one.

• Understand Esri Support’s phone tree to connect with the appropriate analyst.
  Navigating Esri Support’s Phone Tree
• Understand how our system email works.
  Successful e-mail communication with ESRI Support Services
  Waiting to hear back from us… Did you check your SPAM??
• Understand when to use chat.
  Chat with an Analyst

Once you begin working with support there may be times when you may need to share sample data. Here is some information on properly preparing your data before sending it to support.

Tips and tricks for sending data to ESRI Support Services
Using the Esri FTP site to send data to Support Services

Here are also a few other blog posts that address specific products:

Show Me the Incident! (ArcGIS Server)
Help! My Python script isn’t working! (Python)
Tips for Customers Dealing with SDK Incidents (SDK)

Timothy H. – Raster/3D Support Analyst

There are many different kinds of rasters that can be used in ArcMap. To better describe and explain these different kinds  of rasters, Esri has created help documentation on technical specifications and supported raster formats.  Included in the documentation is the ESRI GRID format. This is a very flexible format that many users are comfortable using to process and display data. There is a unique aspect to this format that many users are unaware of that is mentioned in the help documentation.

A section in the help documentation on bit depth capacity reads,

A grid dataset is always stored as 32 bit (either signed, unsigned, or floating point), but ArcGIS shows it above as being the most appropriate bit depth with regard to the cell values it contains.

So while the bit depth of the ESRI GRID may say 8 bit unsigned or 16 bit signed, the storage is still 32 bit.  However, the properties in the source tab of the particular ESRI GRID raster may say something different.  This is important when considering the behavior of the GRID compared to other formats like .imgs or .tifs.

This does not affect the average user of ESRI GRIDs, but just something to keep in mind and understand about the format.  So fear not if you create a new ESRI GRID and the bit depth does not match your defined bit depth; it is still okay. Once the data is added,it should report the most appropriate bit depth.  ESRI GRIDs are always 32 bit rasters regardless of what the source properties report.

Jeff S. – Raster Support Analyst

Have you ever wanted a place where you could collaborate on a good idea with members of the GIS community? Or have you ever wanted to take an idea further by developing a new solution with others who share your vision?

For those looking to take ArcGIS Ideas to the next level, Esri presents ArcGIS Workspaces!

ArcGIS Workspaces is a library of collaborative workspaces that enables members of the GIS community to work together on refining and developing good ideas. These workspaces allows users to collaborate closely together by exchanging thoughts, design documentation, code, presentations, and other files in a secure and dedicated workspace.

When you visit ArcGIS Ideas, you’ll notice a new Workspaces button with the Post and My Ideas buttons.

Clicking this new button will take you to the ArcGIS Workspaces main page. This main page displays the workspaces that are currently open. If you see a project that you would like to participate in, you can request access to join the workspace. If you are already subscribed to a workspace, you will be able to enter it through the main page as well.

Inside the workspaces, members can share, preview, and comment on files. On top of that, the workspace library supports file versioning, so you can follow the development of ideas, code, or whatever else the group is sharing. You can further engage by voting, tagging, and subscribing to these files.

ArcGIS Workspaces is an exciting new place where you can develop good ideas with other members of the GIS community.

If you have any questions about ArcGIS Workspaces, please contact the ArcGIS Ideas administrator by using the link on the ArcGIS Ideas page or email ideas@esri.com.

Joe – Online Support Resources

Background processing is a new feature that was added at ArcGIS 10. Background processing provides the ability to run a geoprocessing tool and not lose the ability to work within ArcMap.  Instead, the tool progress dialog message has been replaced by a scrolling bar in the lower right corner of the map document.

You can now stack up multiple geoprocessing tools to run in order.  The intermediate progress messages can still be seen when background processing is enabled, by expanding the Results Window.  This can be the best of both worlds, as you can continue to work within ArcMap, but still see information about what step the current geoprocessing tool is on.

Results Tab

Background Processing Completion

When the background processing completes, a less obtrusive message will appear in the lower right corner of the map document, indicating it has completed.  You can control the time this message is visible under the Geoprocessing Options and adjusting the slider.

I know what you are thinking,  “but where did my captivating progress dialog message go that is usually center stage on the map document?”

Foreground Processing Message

Well fear not fellow users! You too can return the progress dialog message to its former glory with these steps:

1. In ArcMap, open up Geoprocessing tab.

2. Select the Geoprocessing Options.

3. Uncheck the ‘Enable Background Processing’ radio button.

Now the next time you run a geoprocessing tool, you will see the familiar message and be captivated again.

There is more information about the background processing here.

Jeff S. – Raster Support Analyst

Ever wonder how long your Desktop application takes to render mapped features on a layer to layer basis? Or have you ever needed to know the time it takes to edit mapped features from a particular edit version?

A new tool, PerfQAnalyzer, can help assist users in capturing such performance information. Moreover, this tool even has built in functionality to optionally enable a database trace (Oracle), unique to your workflow and Desktop application. The PerfQAnalyzer  tool is a free, unsupported, downloadable tool offered to the Esri user community which can run as a stand-alone ArcGIS Engine application or as an ArcMap add-in. The workflows captured within the tool are fully automatable and can be scripted and executed simply at the command prompt or within ArcMap. To help assist users in working with the tool, we will author a series of technical articles, highlighting the four areas of functionality, Time Rendering, Creating Editing Scripts, Capturing Fetch Data times and Enabling an Oracle Database trace.  We hope you enjoy the tool as much as the Esri Performance Engineering Team does!

PerfQAnalyzer for ArcGIS 10.1

PerfQAnalyzer for ArcGIS 10.0

PerfQAnalyzer for ArcGIS 9.3

Disclaimer:  This tool is not supported by technical support; any questions or feedback regarding the tool should be forwarded to perfqatools@esri.com

As a support analyst, I speak with many people who are trying to upgrade to a new version of Esri software. As I work with people migrating from ArcIMS 9.2 to ArcIMS 9.3 or ArcIMS 10.0, I realized there is some confusion as to the status of the ActiveX connector.

Just to make sure everyone is aware – the ActiveX connector for ArcIMS was deprecated at version 9.2, for more information read the notice on ArcIMS Component Deprecation.

Despite the deprecation, the ActiveX connector has still shipped with the newer ArcIMS versions, which has caused some confusion. Although the ActiveX connector still seemed to work with ArcIMS 9.3, it no longer works with version 10.0.

If you have upgraded ArcIMS to version 10.0 and are looking for a way to workaround the need for the ActiveX connector, you can either rollback to an older version of ArcIMS or upgrade the application to be a .NET Web ADF application. Here are links to help you with creating a .NET Web ADF application:

• Web ADF Developer Help
• ArcIMS Web Manager Help
• Main ArcIMS Help

Nakul B. - SDK Support Analyst

Support Analysts at the 2012 Esri Developer Summit

The Esri Support Services team is at the 2012 Esri Developer Summit in Palm Springs, and specialists in all areas of the software are available to assist with your questions at the Esri Showcase. You can set up a time slot for a specific technology area that you would like to discuss or feel free to stop by in between sessions or during lunch. To set up an appointment with a support analyst, visit the Support Appointments website.

Hours of Operation

• Tuesday, March 27: 12:30 pm – 6:00 pm
• Wednesday, March 28: 10:00 am – 6:00 pm

We look forward to seeing you at the summit and helping you with your support related issues!

Joe -Online Support Resources

 

You may have already noticed some of the changes at 10.0 with the upgrade process for ArcSDE geodatabase no longer using the Post Installation wizard. This was discussed in an earlier blog written on “The Evolution of the ArcSDE Geodatabase Upgrade Process at 10.0“. The ArcSDE Post Installation Wizard has made its grand exit and is no longer installed as part of ArcSDE at 10.1. Let’s take a look at the Post Installation steps and compare with the new geoprocessing tools that were created at 10.1 to perform similar tasks.

Post Installation Wizard Steps (Pre 10.1)

• Define SDE User Environment/Define Database and SDE DBA User
• Repository Setup
• Authorize ArcSDE
• Create ArcSDE Service

New Geoprocessing tools within Geodatabase Administration Toolbox at 10.1

The following geoprocessing tools are within the Data Management Tools > Geodatabase Administration toolbox at 10.1:

Create Enterprise Geodatabase – Create a database and geodatabase administrator in PostgreSQL or SQL Server and enable enterprise geodatabase functionality in it, or create a tablespace and geodatabase administrator in an existing Oracle database and enable enterprise geodatabase functionality in it. This tool also authorizes the software.

Enable Enterprise Geodatabase – Enable geodatabase functionality in an existing DB2, Informix, Oracle, PostgreSQL, or SQL Server database. This tool also authorizes the software.

Application Server Services

With the Post Installation Wizard no longer part of the ArcSDE install at 10.1, this also means that there is no wizard to create ArcSDE services. The ArcSDE install includes the application server along with command line tools.  If there is a need for an application server service at the 10.1 release, one can be manually created and registered (depending on DBMS) using the ArcSDE administration commands. See the ArcSDE Administration commands to reference the sdeservice commands.

Melissa J. – Geodata Support Analyst

I am sure many of you have already heard about CityEngine, and some of you may have even already contacted Support Services with questions related to it. For those who haven’t been introduced, CityEngine is a stand-alone software product that provides professional users in architecture, urban planning, entertainment, GIS and general 3D content production with a unique conceptual design and modeling solution for creating 3D cities and buildings. It allows professional users in GIS, CAD and 3D to do the following:

• Quickly generate 3D cities from existing 2D GIS data.
• Do conceptual design in 3D, based on GIS data and procedural rules.
• Efficiently model virtual 3D urban environments for simulation and entertainment.

CityEngine screenshots of Rotterdam

CityEngine also provides advanced capabilities for the direct export of the generated 3D city models out to other software tools, such as data management/analysis packages (like ArcGIS), 3D editing software (like Maya or 3DS Max), geo-visualization tools (like ArcGlobe or Google Earth), game engines (like Unity or Unreal), high-end rendering solutions (such as RenderMan), or web-ready cloud rendering services (like RealityServer).

If you work with 3D data, I would strongly recommend trying out CityEngine. You can start by downloading the CityEngine Free 30-day Trial. If you would like to know more about CityEngine, please contact us or review the information on the linked pages below.

• CityEngine Product Info
• CityEngine Resource Center
• Features
• FAQs
• Demos

If you are already using CityEngine and have ideas to further enhance the product, please post your ideas at CityEngine Ideas portal and/or post your comments at CityEngine Forums.

Pavan Y. – Raster Unit Development Technical Lead