Linear Reference not correct

Permanently deleted user

4. Juni 2012 09:07

Hi, we're currently running GXE version 3.8 with the SIlverlight viewer version 1.5.

I've implemented a workflow that zooms to a location along a pipeline based on linear referencing using the extract Point and extract Line workflow tasks. The workflows work ok but we're having 2 issues.

 

1. One of the lines is approximately 800km long. When used in the workflow we receive a Max JSON length error. I've done some research and seen that this is related to the feature having too many vertices. This was apparently fixed in service pack 3 (which we are running) but we're still having the issue. We don't receive this error on shorter lines.

2. The workflow is not zooming to the correct location. When the workflow does run as expected and without error, it actually zooms to the incorrect location (i know this as I know the correct M values of certain locations on the line).

 

Has anyone experienced either of these issues? If so do you have any comments?

 

Thanks

Neil.

0

• 

  Ryan Cooney

  7. Juni 2012 05:25

  Hi Neil,

  1. The MaxJsonLength limit will be removed in the next Essentials release.
  2. The linear referencing activities use length indexed lines. This means the use the length of the geometry as opposed to m-values specified in the geodatabase. M-values are not available from the current version of ArcGIS Server so we just don't have access to them. At AGS 10.1 they are available so we may have some more options in the near future.

  --Ryan

  0
• 

  Permanently deleted user

  7. Juni 2012 08:00

  Thanks for the reply Ryan.

  We'll need to do a work around in this case as our M values are not the same as the geometry.

   

  Regards

  Neil.

   

  0
• 

  Permanently deleted user

  26. Januar 2013 20:59

  hi Neil/Ryan,

  AGS10.1 is out there for a while and support the M value. Does now the latest workflow support search on M value? Thanks.

  regards,

  Jack

  0
• 

  Permanently deleted user

  29. Januar 2013 09:36

  Hi Jack,

  unfortunately we're running v10 and unlikely to go to 10.1 for a little while so I wrote a couple of python scripts that we publish as geoprocessing tasks in ArcGIS Server. I then built a couple of workflows to consume these tasks. One that allows the use to click the map, which then passes the X&Y coordinates to the task and determines the closest M value (within a specific distance), and the other to provide the user with a list of pipelines where they can select one and enter a M value. This is then passed to the GP task which determines the X&Y and zooms the map.

  Not the most efficient but works pretty well.

   

  Regards

  Neil.

  0
• 

  Permanently deleted user

  30. Januar 2013 07:34

  Thanks Neil. That's a good idea indeed I'll give a try. Also really want to hear from Latitude whether the enhancement (read M value) is on their road map.

  0
• 

  Permanently deleted user

  30. April 2020 17:56

  Following...

   

   

  We're now on 4.12.2 and ArcGIS 10.5.1 (yes, I know...) and have to use the ArcGIS publishing option to disable m-values to make those features editable in Geocortex. From the article below, it sounds like editing with m-values still isn't available even through 10.8 Portal or AGOL, so I'm doubting it's a Geocortex limitation. But would be nice for everyone to get on the bandwagon :)

  https://enterprise.arcgis.com/en/server/latest/publish-services/windows/configure-feature-service-m-values.htm

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.