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

Support Constraining Extent argument #2

Open
jmhauck opened this issue Sep 22, 2015 · 2 comments
Open

Support Constraining Extent argument #2

jmhauck opened this issue Sep 22, 2015 · 2 comments

Comments

@jmhauck
Copy link
Contributor

jmhauck commented Sep 22, 2015

This could be useful when looking for geometry data quality issues. For example if we know all points should be in FL or the US then we could most likely determine issues where lat/lon are reversed or if it has a missing "-", ect.

@cosbyr
Copy link
Contributor

cosbyr commented Jul 22, 2019

@jmhauck

I just tested this concept in the using the Extent environment setting:
image

The tool successfully brought in only the points that fell within the extent.

From your memory, is there more to this enhancement request that i'm not understanding?

@jmhauck
Copy link
Contributor Author

jmhauck commented Jul 23, 2019

@cosbyr This wasn't tied to a customer request, that I recall. I believe I was just trying to think of ways to help identify potential bad data or at least be able to tell them something at the end so they could go investigate further. If one or more points did not fall within the extent I wanted a way point them in the right direction so they could easily see what values were questionable.

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

No branches or pull requests

2 participants