|
POST
|
If your map is not using the web mercator projection then you will need to use a geometry service to project your map click location to lat/lon coordinates. See the Project operation on the geometry task. Check the map spatial reference to see what coordinate system you need to project from (details are at the bottom of the page).
... View more
11-11-2014
02:00 AM
|
0
|
0
|
1594
|
|
POST
|
Check out the answer to this StackExchange question. It restricts the extent but you could use the same method to restrict the zoom to a map cache level of detail. It would be better if you could hook into the map zoom-start event and cancel the event if it exceeds your level of detail but I am not sure if this is possible.
... View more
11-02-2014
09:50 PM
|
0
|
0
|
775
|
|
POST
|
Your project will have a couple of options. On the server-side you will either need access to an ArcGIS Server ($$$) or an ArcGIS Online account so you can publish a feature service. The feature service will allow you to store the location of sighting information. For the client side application the best option (in my opinion) is the ESRI JavaScript API. Then you can use some renderers to show density: Dot density renderer Heat map renderer
... View more
11-02-2014
09:31 PM
|
0
|
0
|
602
|
|
POST
|
Are you sending the JSON data via a POST request? All other HTTP methods should result in the 405 error. See this page in the ArcGIS REST API
... View more
11-02-2014
12:47 PM
|
0
|
1
|
1142
|
|
POST
|
Documentation for an API version is important as the live docs keep pace with the current version it is tricky to locate older samples. I agree that ESRI should have them up somewhere - maybe an archived downloads site. My experience with the new site was ?? then !!. But it does grow on you eventually .
... View more
10-29-2014
12:35 PM
|
0
|
1
|
1380
|
|
POST
|
Check out the Make XY Event Layer in the Data Management Toolbox > Layers and Table Views.
... View more
10-29-2014
12:27 PM
|
0
|
0
|
2550
|
|
POST
|
This probably doesn't help for the API download but the old CDN URL is: http://serverapi.arcgisonline.com/jsapi/arcgis/?v=2.6
... View more
10-28-2014
06:20 PM
|
0
|
3
|
1380
|
|
POST
|
Hmmm, seems ESRI have dropped the older versions from their download site. The download option on ArcGIS for Developers only goes back to version 3.0. Maybe try your local ESRI rep.
... View more
10-28-2014
06:16 PM
|
0
|
0
|
1380
|
|
POST
|
For a polyline feature class each shape can be cast to IPointCollection. You can then iterate through each point in the point collection using EnumVertices to access the vertices. Alternatively, you can access each point using the IPointCollection.Point property and the PointCount. Something like:
for (int i = 0; i < pointCollection.PointCount - 1 ; i++)
{
// access the point from the pointCollection here
}
Note that the first Point in the PointCollection has index 0, and the last Point has index equal to PointCount - 1. Also, the Feature.Shape property is an IGeometry. You can use IGeometry.GeometryType to ensure that the shape is a Polyline before accessing the vertices. I don't have a full code example but have done similar things in VB.Net/ArcObjects previously.
... View more
10-15-2014
04:03 PM
|
0
|
3
|
2725
|
|
POST
|
Add one of the input data sets to ArcMap and then right-click on it in the layers list, select Properties and then click on the Source tab: This will show the coordinate system of your input data. Do this for both inputs and see if they are the same.
... View more
10-15-2014
02:56 PM
|
2
|
1
|
1890
|
|
POST
|
It appears that you have projected both files to the same coordinate system (AMG Zone 54 with the AGD66 datum). The issue may be the input data sets. Did the input data sets share the same coordinate system (including datum)? If they had different coordinate systems then one of the datum transformations when projecting may be the issue. If the input data did have the same coordinate system and you applied the same projection parameters then they should line up.
... View more
10-14-2014
10:47 PM
|
1
|
3
|
1890
|
|
POST
|
This looks like a PYTHONPATH issue - python cannot locate the arcpy module in your installation. Check out the Paths and Import section at the end of this ArcGIS Help 10.1 page.
... View more
10-14-2014
10:40 PM
|
0
|
0
|
1152
|
|
POST
|
I much prefer Pascal case for table names as it is easier for users to read - for example: CITYPARKS CityParks
... View more
10-07-2014
06:13 PM
|
1
|
1
|
4515
|
|
POST
|
And you can tell your database developers:
you must be a pirate for the pirate's code to apply..., and the code is more what you'd call "guidelines" than actual rules (Capt. Barbossa)
... View more
10-07-2014
03:54 PM
|
1
|
0
|
4515
|
|
POST
|
Personally, from a GIS perspective I think it makes way more sense to use the plural form as the feature class/table is a collection of objects. However, for database developers it often makes more sense to use the singular version - for example: Singular: SELECT City.Name FROM City WHERE City.ID = 42 Plural: SELECT Cities.Name FROM Cities WHERE Cities.ID = 42 In this context the singular table name makes more sense to me. However, as you correctly point out in most cases this detail is totally hidden from the end user. Also, most modern development uses Object Relational Mapping (ORM) that abstracts away the raw SQL code and would let you have a table named Cities but work with properties such as City.Name for your objects. Out of interest, Microsoft's Entity Framework creates plural table names by default. Either way at least your agency is developing a single standard.
... View more
10-07-2014
03:43 PM
|
0
|
0
|
4515
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 10-07-2014 06:13 PM | |
| 1 | 08-25-2015 02:04 AM | |
| 1 | 10-07-2014 03:54 PM | |
| 1 | 08-07-2014 09:19 PM | |
| 1 | 03-04-2015 02:02 PM |
| Online Status |
Offline
|
| Date Last Visited |
07-21-2021
06:32 PM
|