search

Esri / data-assistant

ArcGIS Pro Add-in that assists in emergency management, local government and state government data aggregation workflows.
Apache License 2.0
22 stars 8 forks source link

Ability to load a table to a featureclass #57

Closed MikeMillerGIS closed 7 years ago

MikeMillerGIS commented 8 years ago

Need the ability to load a table to a feature class using another feature layer to provide the geometry and potentially other attributes. The scenario is a transformer table related to a pole.

MikeMillerGIS commented 8 years ago

This also needs to support where I want to load the Feature Class and a one or more related table that is in 1:1 relationship to a single target output

MikeMillerGIS commented 8 years ago

We can provide sample data

SteveGrise commented 8 years ago

I guess there is no (practical) way to set up a joined layer or database view then use it as the source feature class? I've done this in other cases.

It seems like the UI would change a fair bit to support this with DA - it's not a problem, but would likely be a new "Create File" tool that accepts additional parameters.

MikeMillerGIS commented 8 years ago

I am sure it could be done with a view or join, but we would like the tool to do this in process.

SteveGrise commented 8 years ago

Ok, then a table-feature class tool (or 'joiner' tool) would probably be the cleanest solution. It's either that or make the Create File tool a .NET UI so there is a better user experience than the GP tool.

For scripting it would be Ok to keep the .py tool around, but it's a bit clumsy to start adding options to the UI.

MikeMillerGIS commented 8 years ago

@SteveGrise, Just talking through this with John right now. I misunderstood what we needed. The immediate need is to read a layer that uses a join. So can the Data Assistant read the source feature class/table and the fields from a join on that featureclass and table? This should prevent reworking on the UI and just leverage Pro to specify the join.

Does this make things any easier?

SteveGrise commented 8 years ago

I believe the map join approach will work, although I don't recall testing it specifically. I've fixed the issues that come up with that in other work so it would be an easy enhancement if there are issues.

On Thu, Sep 1, 2016 at 12:18 PM, Michael Miller notifications@github.com wrote:

@SteveGrise https://github.com/SteveGrise, Just talking through this with John right now. I misunderstood what we needed. The immediate need is to read a layer that uses a join. So can the Data Assistant read the source feature class/table and the fields from a join on that featureclass and table? This should prevent reworking on the UI and just leverage Pro to specify the join.

Does this make things any easier?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Esri/data-assistant/issues/57#issuecomment-244132031, or mute the thread https://github.com/notifications/unsubscribe-auth/AEh3BEZoM-JEa0XbjBDdVcjRkv9I2jI6ks5qlvrqgaJpZM4JgCKp .

MikeMillerGIS commented 7 years ago

Watching the tech transfer for 10.5/1.4 this week and I think Query layers would be the best approach here. Then we can support any type of sql join to produce the layer that we need to load into the target.

@SteveGrise @ChrisBuscaglia what are your thoughts on this?

MikeMillerGIS commented 7 years ago

Looking at query layers, they only support Enterprise gdb, so for FGDB, the join approach is best, lets stick with that for now

SteveGrise commented 7 years ago

Completed work on domain mapping to support .lyrx files and other sources.

previnWong commented 7 years ago

Verified. Data Mapper shows both fields from left and right joins.