Source to Target Mapping GP tools need option to generate Lyrx files for layer in the TOC

[MikeMillerGIS]

This dialog needs to generate a Lyrx file for a feature layer in the TOC

add check box here

[MikeMillerGIS]

If box is not checked, we should warn the user that the layer properties are not be used, such as definition query

[JRosenfeldIntern]

@MikeMillerGIS Why not just make a layer file on the back end and don't expose an option? If it's a feature layer from the TOC, automatically create a layer file (doesn't necessarily have to be in a place the user can see).

I don't really see a case where someone wouldn't want definition queries to be respected or why they wouldn't want that quick intermediate step to be done.

[JRosenfeldIntern]

I have a new idea for this one.

Why don't we create a folder along with the xml file? The folder is named the name of the xml file and it contains the xml file along with source and target layer files. No matter the input, a new layer file is made for source and target pointing to its respective data.

It would look like this

This would

• Solve the feature layer definition query issue
• Make it easier for users to find and monitor their data and changes made to it
• Makes the GPTools only have to handle one data format: lyrx
• Allows for, in the future, Data Assistant to have a good place to store other viable or relevant files.

Thoughts? @MikeMillerGIS @ChrisBuscaglia

[pLeBlanc93]

+1 from me. This doesn't break backwards compatibility and meshes in well with the concept of a DA "workspace".

The only instance where you wouldn't get a source/target lyrx file is if you're using tables. Which is fine.

[MikeMillerGIS]

+5

Sent from my Verizon Wireless 4G LTE DROID