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

Add support for m & z values #223

Closed
stdavis opened this issue Jan 30, 2018 · 0 comments
Closed

Add support for m & z values #223

stdavis opened this issue Jan 30, 2018 · 0 comments
Assignees

Comments

@stdavis
Copy link
Member

stdavis commented Jan 30, 2018

Steps to reproduce

  1. Create a pallet that points to a source feature class that has m- or z-values enabled. SGID10.TRANSPORTATION.UDOTRoutes_LRS is an example of m-values. The roadkill pallet uses this layer.
  2. forklift lift

Expected behavior

The destination feature class should have the m- and/or z-values preserved.

Actual behavior

The m- and z-values are gone. For example, here is SGID10.TRANSPORTATION.UDOTRoutes_LRS:
image

and here is C:\MapData\transportation.gdb\UDOTRoutes_LRS
image

Research

We use arcpy.management.CreateFeatureclass(..) when we create the destination feature class:

arcpy.CreateFeatureclass_management(crate.destination_workspace,

The docs show has_m and has_z parameters in addition to supporting arcpy.env.outputMFlag. I would have guessed that the default would be to keep whatever the template feature class has but maybe not. I think that setting has_m and haz_z to SAME_AS_TEMPLATE should solve the problem. I'll test it and see.

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

1 participant