Latest Contributions by RiccardoKlinger

Hi folks, I am having a discussion with our security department as I should not expose admin capabilities via our reverse proxy. Serving data via this reverse proxy (like hosted feature services, services and so on) is totally fine. even the server manager might be cool. But when it comes to the arcgis/admin endpoint my it-department is going nuts and want me to disable this access. Is it safe to rmeove these endpoints from the reverse proxy? Logging in the server/manager I see some communication with the server/admin endpoint and I am unsure what will happen, if I suppress the admin/* endpoint... Any notes on this? Running arcgis enteprise 10.9.1 and 11.1

‎03-19-2024

We have now altered the processing in the custom geoprocessing and start der network build in another thread after the sucessfull creation of the underlying file geodatabase. This fixed the above issue. What was causing this behaviour is still unclear to us.

‎03-12-2024

Ciurrently we share a similar problem. During the build of a network dataset we have faced a similar error message: WARNING: Unable to load code page translation table c:\program files\arcgis\pro\\locale\codepage\0.txt. WARNING: Unable to load code page translation table c:\program files\arcgis\pro\\locale\codepage\0.txt. Code page conversion is off for writing data into files. Code page conversion is off for writing data into files. WARNING: Unable to load code page translation table c:\program files\arcgis\pro\\locale\codepage\0.txt. WARNING: Unable to load code page translation table c:\program files\arcgis\pro\\locale\codepage\0.txt. Code page conversion is off for reading data from files. Code page conversion is off for reading data from files.

‎03-11-2024

we have figured out so far: We are able to reproduce the issue with a local ArcGIS Pro 2.9 and 3.1 The initial buld locally returns some really strange Descriptors: And after the local rebuild using the same template the descriptors look perfect. also the costs (distance in m) is correct after rebuilding.

‎03-07-2024

Currently we are building large network datasets using a quite complex template in ArcGIS Server 10.9.1: We created a custom geoprocessing tool, include a XML with function evaluators (VBScript as well as Python) and publish this via ArcGIS Pro to our ArcGIS Server 10.9.1 When we start this process everything works just fine: create network from template, build network (with some warnings, but nothing fancy) and we receive a nice feature collection with the needed network dataset. Unfortunately this NDS is just bad: I cannot solve the route layer on it and it barely works, when I turn off all the restrictions. But even then it gives me really strange routes. But if I take the same gdb that holds this NDS and I open this in ArcGIS Pro 2.9, delete the NDS and recreate it with the same template and rebuild it, everything works just like expected. Furthermore I've tested to alter just one restriction on the original server-side created NDS which forced a rebuild as dirty areas were created, it was perfect after building it using ArcGIS Pro on desktop. We have no idea, where this behaviour is coming from. What we have tested: switched from arcpy.nax.buildNetwork on server to the good old arcpy.na.buildNetwork disabled ArcMAP legacy support checked the python executable on server (yes it was 3.9.11) checked the original gdb as it is returned from the server side as a compressed format and we would like to make sure that the compression isn't causing the problem. We are a. bit stucked now.

‎02-09-2024

quick "recap" During stop creation it creates some fields including sourceID, sourceOID, PosAlong and SideOfEdge. These fields are not filled initally but will be resolved during the route finding process. The route finding process seems to only check for edges on this position and will take the settings of the first edge it finds. In my personal case the objectID of the edge with single direction traffic was the lowest of the three edges so it was chosen. You can check this solution, when you open the Stops attribute table and scroll to the above mentioned fields. SourceOID is the objectID of the edge it found and used. To solve this in ArcGIS Pro you can alter the Stop table and fill in the four fields with the desired values and than start solving the route problem. On arcGIS Server with a Route Solver NAS you can alter the stops feature set: instead of sending {"features":[{"geometry":{"spatialReference":{"latestWkid":32632,"wkid":32632},"x":4712.0,"y":816.0},"attributes":{}},{"geometry":{"spatialReference":{"latestWkid":32632,"wkid":32632},"x": 4711.0,"y":815.0},"attributes":{}}]} you should send defining attributes: {"features":[{"aggregateGeometries":null,"geometry":{"spatialReference": {"latestWkid":32632,"wkid":32632} ,"x":4712.0,"y":816.0},"attributes":{"SourceID": 2, "SourceOID": 26142977, "PosAlong": 0, "SideOfEdge":1}},{"aggregateGeometries":null,"geometry":{"spatialReference": {"latestWkid":32632,"wkid":32632} ,"x":4711.0,"y":815.0},"attributes":{"SourceID": 2, "SourceOID": 26156789, "PosAlong": 0, "SideOfEdge":1}}]} The determination of the SourceOID is the up to you. It will not be overwritten by ArcGIS Server. Tested with ArcgIS Server 10.9.1 in ArcGIS ENterprise 11, you can also check with the new locateSettings Parameter described here: Direct request—ArcGIS REST APIs | ArcGIS Developers

‎02-07-2024

Seems strange but you're right: I copied the single direction road in my street dataset and removed the old one. The new one recieved an higher objectid and I recreated the NDS. Now it behaves correctly. Can i somehow interfer with this in ArcGIS Pro by adding some sort of rule like: If stop on Node: use edge settings from higher ranking functional class! ?

‎02-07-2024

and location on junctions is turned of, if I look and interpret this dialogue correctly:

‎02-07-2024

Hi Melinda, I've checked the data again and created a network from scratch which works just fine and routing is as expected. Yet I need to consider single direction restrictions and it seems like it is using a restriction from the single direction road as the limitation if the desired trip stops at a junction: once I move the target (2) away from the node it behaves correctly: my code block for the restrictions: def OnewayFromTo(dt): if dt == "T": return True if dt == "N": return True if dt == "B": return False return False can I design the behaviour at junctions as well?

‎02-07-2024

Everything seems well connected:

‎02-07-2024

I am creating a network dataset and I see some strange maneuvers on the data: SO coming from the NorthWest, I am passing the stop and make a turnaround. Coming from the southeast I am making this detour. Yet if the stop is not placed on a junction the route just looks fine! I have tried several settings in the curb approaches and yet I was not a able to get the shortest/fastest route. Does anyone have an idea where to look at? I tried all travel modes and all measurements, recreated junctions and so on. Still I have no clue where this might come from!

‎02-05-2024

We face similar issues and we would love to see this "message" at a verbose or info level. Yet it should not be treated as a warning.

‎11-15-2023

We are still facing a similar issue in ArcGIS Server 10.9.1 with SDE towards a postgreSQL database. we deal with the problem by enhancing the number of allowed open connections but this could not be the valid way.

‎11-09-2023

What is interesting though: I am using a REST URL and the basic 4.14 JS API shipped with my portal 10.9.1 and there are features excluded from drawing:

‎09-18-2023

Hi folks, we are currently developing a python toolbox and publishing this to arcgis server 10.9.1 The toolbox creates a tar file which should be donwloaded to the client. Unfortunately this only works for smaller TARs. The download fails for TARs which are larger than 2GB. Is there a setting ArcGIS Server or Portal that might be relevant here?

Online Status	Offline
Date Last Visited	6 hours ago

My Ideas

Latest Contributions by RiccardoKlinger

secure the server/admin endpoint

Re: network from Template: geoprocessing vs. local

Re: WARNING: Unable to load code page translation table

Re: network from Template: geoprocessing vs. local

network from Template: geoprocessing vs. local

Re: strange turns in Network Dataset

Re: strange turns in Network Dataset

Re: strange turns in Network Dataset

Re: strange turns in Network Dataset

Re: strange turns in Network Dataset

strange turns in Network Dataset

Re: Remove 'Group Layer', which is not supported from ArcGIS Server error logs

Re: ArcGIS Server map services - Idle/open transactions in SQL causing logging issues

Re: Features not drawing when using full rest service URL

Geoprocessing result download ... too big?

Re: strange turns in Network Dataset

Portal Connection in ArcGIS Pro not working

Experience Builder Dev Edition Installation fails

branch versioning vs. mass updates

Re: Cannot register postgres table