Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AA - set_measures behavior #237

Open
pLeBlanc93 opened this issue May 9, 2017 · 6 comments
Open

AA - set_measures behavior #237

pLeBlanc93 opened this issue May 9, 2017 · 6 comments

Comments

@pLeBlanc93
Copy link
Contributor

Per this question on GeoNet, it's unclear what the SET_MEASURES method does. Looking at the source code, it just interpolates M values at all vertices.
The documentation here refers to populating a field.

Is this method intended to be used only to recalculate M-values for vertices, i.e., the documentation needs to remove references storing field values?

@MikeMillerGIS
Copy link
Member

help is wrong, only sets the measures on the feature.

 case "SET_MEASURES":
                                            try
                                            {
                                                AAState.WriteLine(A4LGSharedFunctions.Localizer.GetString("AttributeAssistantEditorMess_14ar") + "SET_MEASURES");
                                                if (inFeature != null)
                                                {
                                                    curve = inFeature.Shape as ICurve;
                                                    mseg = inFeature.Shape as IMSegmentation;
                                                    if (curve != null && mseg != null)
                                                        if (valData != null && valData != "" && valData.Substring(0, 1).ToUpper() == "P")
                                                            mseg.SetAndInterpolateMsBetween(0, 100);
                                                        else
                                                            mseg.SetAndInterpolateMsBetween(0, curve.Length);
                                                }

                                            }
                                            catch (Exception ex)
                                            {
                                                AAState.WriteLine(A4LGSharedFunctions.Localizer.GetString("AttributeAssistantEditorError_14a") + "SET_MEASURES: " + ex.ToString());
                                            }
                                            finally
                                            {
                                                AAState.WriteLine(A4LGSharedFunctions.Localizer.GetString("AttributeAssistantEditorMess_14as") + "SET_MEASURES");
                                            }
                                            break;

@MikeMillerGIS
Copy link
Member

I think we should extend this method, Be easy to support EndField or StartField|EndField. If these fields exist, the values from these fields would be used for the start and end distances on SetAndInterpolateMsBetween method. I would guess only an hour of coding as these types of checks are in other methods, would just need to move them to this method

@MikeMillerGIS MikeMillerGIS added this to the Fall 2017 milestone May 10, 2017
@MikeMillerGIS MikeMillerGIS modified the milestones: Fall 2017, Fall 2018 Jan 18, 2018
@MikeMillerGIS
Copy link
Member

@Elena9170 can you fix this one while in there, just remove the text highlight below

image

@ElenaFernandes
Copy link

Removed and addressed in Pull request https://github.com/ArcGIS/arcgis-solutions-website/pull/7256/files

@MikeMillerGIS
Copy link
Member

I did not see it in that PR

@ElenaFernandes
Copy link

ElenaFernandes commented Nov 12, 2018

Strange behavior with Github Desktop, it should be visible now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants