Tag Archives: Feedback
If you have not noticed, we have been making a lot of improvements to the Infrastructure Editing Template or IET as some of you have been calling it. We have been working through the enhancment requests that we recieved at the UC and have released most of them through the Water Utilities Forum Beta Thread. We have one very important improvement left that we need your help on. We are looking to build a set of tools to help bring infrastructure from a proposed status to an in-service status and tools to move features from in-service to an abandon status.
Here are the tools we are thinking of so far.
1: A Geoprocessing script or model to change the status of selected features.
2: A Geoprocessing script or model to move a feature from one feature class to another and update some attributes.
3: A tool to select an existing line, select a new line and move all features to the new line(taps and laterals)
4: A tool to select two locations on a line, junctions or edges, split the line if required, run a trace between them and copy or cut each feature to a new feature class.
Would the above toolset allow you to manage the life cycle of your assets better? If not, what are we missing? Should we add any additional steps to these tools?
Please let us know through the forum entry on this topic linked below.
A big thanks to all of the water, wastewater and stormwater ArcGIS users who spent time with us during the 2011 Esri User Conference and attended our Technical Workshops on ArcGIS for Water Utilities. You gave us some very valuable feedback on the maps and apps that are part of ArcGIS for Water Utilities and we are aggregating that feedback now and will address it in a follow up blog. Feedback from the user community is what drives our activities.
A common question we heard throughout the user conference was “what is the best way to give feedback on ArcGIS for Water Utilities”?
The Water Utilities Forums is the place where we encourage you to give us feedback about the maps and apps that make up ArcGIS for Water Utilities. We want to know what is working, what isn’t, how we can do things better and we very much appreciate you sharing your success stories around deploying ArcGIS for Water Utilities or it’s predecessor the Water Utility Templates. You can also reach us at our email alias: ArcGISTeamWater@Esri.com
Ideas.ArcGIS.Com is the place to request enhancements to the ArcGIS System as well as ArcGIS for Water Utilities. The more votes an idea gets, the easier it is for us to understand how big of a need it is for our water utility users. Just be sure to tag your ideas with “Water and Wastewater” as well as any other appropriate descriptions.
Again, thank you to our water, wastewater and stormwater customers for making the 2011 Esri User Conference such a great experience for the Esri staff working with you!
Dev Summit 2011 is over and I’m still trying to recovery from the busy but great week in Palm Springs. This year was the largest Dev Summit ever and there were some excellent session and good times for the nearly 1400 attendees. Here is a set of photos and videos from the week. More video from the Tech Sessions will be coming soon.
If you attended this year, I hope you came away inspired and equipped to make the most of GIS in your applications.
Tell us what you thought of this year’s conference by taking a short survey. Your input will help us plan for next year’s conference.
It feels like we just shipped ArcGIS 10 but the development teams have been busy working on future releases plus Service Pack 1 for ArcGIS 10.
We now have the list of targeted issues that are planned to be available in
ArcGIS 10.0 Service Pack 1 (SP1) for all products.
SP1 is planned to be available in November 2010. This list
is subject to change at any time, and we’ll continue to add additional
items. We are providing this list early, so you can plan within your
organization for the upcoming service pack and decide when it makes the most
sense to deploy it.
If you have feedback about this list, please post in the appropriate
technology forum at http://forums.arcgis.com/. If there are
enhancements that you would like to see in future Esri Service Packs or
releases, please post them on the ArcGIS Ideas site: http://ideas.arcgis.com/.
A Water and Wastewater category has just been added to the
ArcGIS Ideas website. So the water,
wastewater and stormwater ArcGIS user community now has a formal place to
suggest products enhancements and enables the community to promote, rank
and comment on submitted idea.
What is the ArcGIS
The ArcGIS Ideas website is the place for ArcGIS users to
suggest product or industry specific enhancements to ArcGIS. When you post an Idea you can tag it with
descriptive terms and also choose up to 3 categories that your idea is relevant
to. The categories are both products and
industries. Water and Wastewater is now
available as an industry.
Tagging and categorizing your posted ideas are very
important because this allows other users to find your ideas, comment on them
and promote or demote them depending on whether they believe it’s a good idea
or not. As posted ideas get promoted they gain more points.
Water and Wastewater
In the past you’ve given us ideas and feedback on ArcGIS in
the water, wastewater and stormwater industries by telling us in person,
sending us emails, Twitter and posting on the discussion forums. Your feedback has driven the development of the Water Utility Templates as well as changes in ArcGIS. We’re glad to continue to receive ideas in
any way, but we want to urge you to submit your ideas to the ArcGIS
Ideas website going forward. Posting to
the ArcGIS Ideas website will engage the rest of the user community in refining
your idea and helping to promote its importance to Esri’s development and Water
Utility Resource Center teams.
So…. got an idea? Go
ahead and post it now: http://ideas.arcgis.com/
I want to thank everyone for their interest and participation in the ArcGIS 10 beta program. As beta 2 is coming to a close, the prerelease version of ArcGIS 10 will be available in the next few days. We encourage you to participate in this prerelease program.
All beta sites, EDN Subscribers, and Partners will receive a detailed e-mail that outlines what software you can receive and the licensing information needed to access it. The email is being sent to the ESRI maintenance contact in your organization.
We look forward to your continued participation and feedback on the next release of ArcGIS
Here is a new .NET utility that you might find useful. The API Evaluator is a tool that allows you to scan your ArcGIS .NET code and generate statistics on the API usage. It also provides you with a mechanism to send feedback directly to ESRI about the APIs that are most important to you. Read on if you would like to know more.
How it works
The API Evaluator allows you to browse to a .NET .exe or .dll, scan the code, and identify all of the calls to ESRI types. The report and statistics are returned to you in an interactive Results Viewer window. This information reveals the following:
1. The .NET assembly references found;
2. The assembly version;
3. The ESRI types called; and,
4. The number of times a call is made to each interface, property and method.
Scenario: Exploring the unknown…
You download a large code sample and know very little about how the code was written or what types are referenced. Simply use the New Scan option to step you through the scanning wizard browse to the assembly and generate statistics. Use the Results Viewer to and expand the treeview and view the number of calls to each item.
Evaluating the Results
The API Evaluator revealed that the code makes a total of nineteen calls to ESRI objects, from five libraries: DataSourcesGDB, GeoAnalyst, Geodatabase, SpatialAnalyst and System. Two of the calls are made to objects in the SpatialAnalyst library. All of this information is recorded and displayed in the Results Viewer.
So why is this important?
In this case, the tool revealed that SpatialAnalyst types are called, and therefore, the code will require clients to check out a SpatialAnalyst license at runtime.
I’m sure you can think of many different uses for this tool, but in general, a developer could use this tool to:
1. Determine the general API usage for larger or unknown code samples;
2. Determine the license-level required for an application;
3. Refactor and improve your own code where redundant calls are identified;
4. Detect library dependencies to help with deployment scenarios.
5. Detect version dependencies.
BONUS – Send us your feedback!
As an added bonus, the tool also allows you to upload your scan results directly to the ESRI Development Team. When you upload, you have the option of providing your contact details before the information is sent to a web service hosted here at ESRI. Once received, your statistics will be analyzed further to:
1. Better understand the APIs that our customers are using (most popular).
2. Make improvements to focused areas of the documentation and samples.
3. Use the information for future API development projects
For more information on the tool, you can review the documentation or download it from the Code Gallery.
Your Feedback is important
Although the “Upload Scan” functionality 100% optional, we appreciate all feedback from the developer community, so we hope you find this tool useful and you can spend a few minutes uploading the results back to ESRI.
Thanks again for your participation!