arcpy Select_analysis where_clause objectid [on hold] The Next CEO of Stack OverflowWhat is the best way to migrate an SDE DatabaseArcpy to copy a layer in the ArcMap TOC, rename the copy, and paste back to TOC?ArcGIS Copy Features tool extremely slow when exporting to ArcSDE?Backup several SDE database connectionsFeature class to Feature class not workingGetting full path of empty sde feature datasets (Children property from arcpy.Describe object won't work))In_memory workspace in geoprocessing servicesWhat are the options for accessing Oracle geodatabase data using full-blown SQL?Copy multiple feature-class schemas to new geodatabaseOptimizing combining multiple feature classes into one via arcpy

How to Reset Passwords on Multiple Websites Easily?

When airplanes disconnect from a tanker during air to air refueling, why do they bank so sharply to the right?

Customer Requests (Sometimes) Drive Me Bonkers!

Implement the Thanos sorting algorithm

Is it my responsibility to learn a new technology in my own time my employer wants to implement?

What does this shorthand mean?

Why didn't Theresa May consult with Parliament before negotiating a deal with the EU?

Anatomically Correct Strange Women In Ponds Distributing Swords

How do we know the LHC results are robust?

Why is there a PLL in CPU?

What does "Its cash flow is deeply negative" mean?

How do I construct this japanese bowl?

If the heap is initialized for security, then why is the stack uninitialized?

Which organization defines CJK Unified Ideographs?

What's the point of interval inversion?

Why were Madagascar and New Zealand discovered so late?

Need some help with wall behind rangetop

How to get regions to plot as graphics

How did people program for Consoles with multiple CPUs?

How do spells that require an ability check vs. the caster's spell save DC work?

Can a caster that cast Polymorph on themselves stop concentrating at any point even if their Int is low?

Rotate a column

How to use tikz in fbox?

Grabbing quick drinks



arcpy Select_analysis where_clause objectid [on hold]



The Next CEO of Stack OverflowWhat is the best way to migrate an SDE DatabaseArcpy to copy a layer in the ArcMap TOC, rename the copy, and paste back to TOC?ArcGIS Copy Features tool extremely slow when exporting to ArcSDE?Backup several SDE database connectionsFeature class to Feature class not workingGetting full path of empty sde feature datasets (Children property from arcpy.Describe object won't work))In_memory workspace in geoprocessing servicesWhat are the options for accessing Oracle geodatabase data using full-blown SQL?Copy multiple feature-class schemas to new geodatabaseOptimizing combining multiple feature classes into one via arcpy










1















Trying to copy features from sde to fgdb but only when the objectid is below a certain number.



outpath = r'C:UsersCHOKDesktopSDE Conversion ProjectTEST.gdb'
query = '"objectid" < ' + "'121'"
for featureclass in dataset:
if featureclass == 'Contour_10m':
output = outpath + os.sep + featureclass
arcpy.Select_analysis(featureclass, output, query)


The code executes but only the schema of the sde is copied in the new feature class created in the gdb and no data with objectid<121 that I expected would be copied over is present.



Any ideas on what the issue is?










share|improve this question







New contributor




user139485 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











put on hold as off-topic by Vince, BERA, Kadir Şahbaz, Erik, Jochen Schwarze 16 hours ago


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "This problem cannot or can no longer be reproduced. Changes to the system or to the asker's circumstances may have rendered the question obsolete, or the question does not include a procedure to enable potential answerers to reproduce the same symptoms. Such questions are off-topic as they are unlikely to help future readers, but editing them to include more details can lead to re-opening." – Vince, BERA, Kadir Şahbaz, Erik, Jochen Schwarze
If this question can be reworded to fit the rules in the help center, please edit the question.
















  • You're testing objectid (Long Integer) with a string, query = 'objectid < 121' will do the job. Better still query = ' < 121'.format(arcpy.Describe(featureclass).OIDFieldName) to get the name of the OID field, Objectid for geodatabases, FID for shapefiles - makes the code more flexible. Also output = os.path.join(outpath,featureclass) instead of simple concatenation is good practice, it automatically inserts os.sep between the strings.

    – Michael Stimson
    yesterday












  • Thanks Michael, it worked fine :)

    – user139485
    yesterday
















1















Trying to copy features from sde to fgdb but only when the objectid is below a certain number.



outpath = r'C:UsersCHOKDesktopSDE Conversion ProjectTEST.gdb'
query = '"objectid" < ' + "'121'"
for featureclass in dataset:
if featureclass == 'Contour_10m':
output = outpath + os.sep + featureclass
arcpy.Select_analysis(featureclass, output, query)


The code executes but only the schema of the sde is copied in the new feature class created in the gdb and no data with objectid<121 that I expected would be copied over is present.



Any ideas on what the issue is?










share|improve this question







New contributor




user139485 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











put on hold as off-topic by Vince, BERA, Kadir Şahbaz, Erik, Jochen Schwarze 16 hours ago


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "This problem cannot or can no longer be reproduced. Changes to the system or to the asker's circumstances may have rendered the question obsolete, or the question does not include a procedure to enable potential answerers to reproduce the same symptoms. Such questions are off-topic as they are unlikely to help future readers, but editing them to include more details can lead to re-opening." – Vince, BERA, Kadir Şahbaz, Erik, Jochen Schwarze
If this question can be reworded to fit the rules in the help center, please edit the question.
















  • You're testing objectid (Long Integer) with a string, query = 'objectid < 121' will do the job. Better still query = ' < 121'.format(arcpy.Describe(featureclass).OIDFieldName) to get the name of the OID field, Objectid for geodatabases, FID for shapefiles - makes the code more flexible. Also output = os.path.join(outpath,featureclass) instead of simple concatenation is good practice, it automatically inserts os.sep between the strings.

    – Michael Stimson
    yesterday












  • Thanks Michael, it worked fine :)

    – user139485
    yesterday














1












1








1








Trying to copy features from sde to fgdb but only when the objectid is below a certain number.



outpath = r'C:UsersCHOKDesktopSDE Conversion ProjectTEST.gdb'
query = '"objectid" < ' + "'121'"
for featureclass in dataset:
if featureclass == 'Contour_10m':
output = outpath + os.sep + featureclass
arcpy.Select_analysis(featureclass, output, query)


The code executes but only the schema of the sde is copied in the new feature class created in the gdb and no data with objectid<121 that I expected would be copied over is present.



Any ideas on what the issue is?










share|improve this question







New contributor




user139485 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












Trying to copy features from sde to fgdb but only when the objectid is below a certain number.



outpath = r'C:UsersCHOKDesktopSDE Conversion ProjectTEST.gdb'
query = '"objectid" < ' + "'121'"
for featureclass in dataset:
if featureclass == 'Contour_10m':
output = outpath + os.sep + featureclass
arcpy.Select_analysis(featureclass, output, query)


The code executes but only the schema of the sde is copied in the new feature class created in the gdb and no data with objectid<121 that I expected would be copied over is present.



Any ideas on what the issue is?







arcpy enterprise-geodatabase file-geodatabase






share|improve this question







New contributor




user139485 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




user139485 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




user139485 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked yesterday









user139485user139485

61




61




New contributor




user139485 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





user139485 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






user139485 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




put on hold as off-topic by Vince, BERA, Kadir Şahbaz, Erik, Jochen Schwarze 16 hours ago


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "This problem cannot or can no longer be reproduced. Changes to the system or to the asker's circumstances may have rendered the question obsolete, or the question does not include a procedure to enable potential answerers to reproduce the same symptoms. Such questions are off-topic as they are unlikely to help future readers, but editing them to include more details can lead to re-opening." – Vince, BERA, Kadir Şahbaz, Erik, Jochen Schwarze
If this question can be reworded to fit the rules in the help center, please edit the question.







put on hold as off-topic by Vince, BERA, Kadir Şahbaz, Erik, Jochen Schwarze 16 hours ago


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "This problem cannot or can no longer be reproduced. Changes to the system or to the asker's circumstances may have rendered the question obsolete, or the question does not include a procedure to enable potential answerers to reproduce the same symptoms. Such questions are off-topic as they are unlikely to help future readers, but editing them to include more details can lead to re-opening." – Vince, BERA, Kadir Şahbaz, Erik, Jochen Schwarze
If this question can be reworded to fit the rules in the help center, please edit the question.












  • You're testing objectid (Long Integer) with a string, query = 'objectid < 121' will do the job. Better still query = ' < 121'.format(arcpy.Describe(featureclass).OIDFieldName) to get the name of the OID field, Objectid for geodatabases, FID for shapefiles - makes the code more flexible. Also output = os.path.join(outpath,featureclass) instead of simple concatenation is good practice, it automatically inserts os.sep between the strings.

    – Michael Stimson
    yesterday












  • Thanks Michael, it worked fine :)

    – user139485
    yesterday


















  • You're testing objectid (Long Integer) with a string, query = 'objectid < 121' will do the job. Better still query = ' < 121'.format(arcpy.Describe(featureclass).OIDFieldName) to get the name of the OID field, Objectid for geodatabases, FID for shapefiles - makes the code more flexible. Also output = os.path.join(outpath,featureclass) instead of simple concatenation is good practice, it automatically inserts os.sep between the strings.

    – Michael Stimson
    yesterday












  • Thanks Michael, it worked fine :)

    – user139485
    yesterday

















You're testing objectid (Long Integer) with a string, query = 'objectid < 121' will do the job. Better still query = ' < 121'.format(arcpy.Describe(featureclass).OIDFieldName) to get the name of the OID field, Objectid for geodatabases, FID for shapefiles - makes the code more flexible. Also output = os.path.join(outpath,featureclass) instead of simple concatenation is good practice, it automatically inserts os.sep between the strings.

– Michael Stimson
yesterday






You're testing objectid (Long Integer) with a string, query = 'objectid < 121' will do the job. Better still query = ' < 121'.format(arcpy.Describe(featureclass).OIDFieldName) to get the name of the OID field, Objectid for geodatabases, FID for shapefiles - makes the code more flexible. Also output = os.path.join(outpath,featureclass) instead of simple concatenation is good practice, it automatically inserts os.sep between the strings.

– Michael Stimson
yesterday














Thanks Michael, it worked fine :)

– user139485
yesterday






Thanks Michael, it worked fine :)

– user139485
yesterday











1 Answer
1






active

oldest

votes


















0














In your selection query you are expressing 121 as a string '121', as your objectid field is a long integer type the less than operator < doesn't work with a mismatched data type. To fix up your code in the easiest way:



query = '"objectid" < 121'
for featureclass in dataset:
if featureclass == 'Contour_10m':
output = os.path.join(outpath,featureclass)
arcpy.Select_analysis(featureclass, output, query)


However, to make the code more flexible:



for featureclass in dataset:
if featureclass == 'Contour_10m':
query = ' < 121'.format(arcpy.Describe(featureclass).OIDFieldName)
output = os.path.join(outpath,featureclass)
arcpy.Select_analysis(featureclass, output, query)


Using the Describe statement to find the table property OIDFieldName will ensure that the code works for all data types that have an OID (most but not all do).



Describe is extremely useful to access properties about all different types of data; on the help page there are a number of different data type properties, any given dataset may, and usually do, have properties from multiple types.. in this instance arcpy.Describe(featureclass) has dataset, feature class and table properties in addition to the default any kind of data properties.






share|improve this answer





























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    In your selection query you are expressing 121 as a string '121', as your objectid field is a long integer type the less than operator < doesn't work with a mismatched data type. To fix up your code in the easiest way:



    query = '"objectid" < 121'
    for featureclass in dataset:
    if featureclass == 'Contour_10m':
    output = os.path.join(outpath,featureclass)
    arcpy.Select_analysis(featureclass, output, query)


    However, to make the code more flexible:



    for featureclass in dataset:
    if featureclass == 'Contour_10m':
    query = ' < 121'.format(arcpy.Describe(featureclass).OIDFieldName)
    output = os.path.join(outpath,featureclass)
    arcpy.Select_analysis(featureclass, output, query)


    Using the Describe statement to find the table property OIDFieldName will ensure that the code works for all data types that have an OID (most but not all do).



    Describe is extremely useful to access properties about all different types of data; on the help page there are a number of different data type properties, any given dataset may, and usually do, have properties from multiple types.. in this instance arcpy.Describe(featureclass) has dataset, feature class and table properties in addition to the default any kind of data properties.






    share|improve this answer



























      0














      In your selection query you are expressing 121 as a string '121', as your objectid field is a long integer type the less than operator < doesn't work with a mismatched data type. To fix up your code in the easiest way:



      query = '"objectid" < 121'
      for featureclass in dataset:
      if featureclass == 'Contour_10m':
      output = os.path.join(outpath,featureclass)
      arcpy.Select_analysis(featureclass, output, query)


      However, to make the code more flexible:



      for featureclass in dataset:
      if featureclass == 'Contour_10m':
      query = ' < 121'.format(arcpy.Describe(featureclass).OIDFieldName)
      output = os.path.join(outpath,featureclass)
      arcpy.Select_analysis(featureclass, output, query)


      Using the Describe statement to find the table property OIDFieldName will ensure that the code works for all data types that have an OID (most but not all do).



      Describe is extremely useful to access properties about all different types of data; on the help page there are a number of different data type properties, any given dataset may, and usually do, have properties from multiple types.. in this instance arcpy.Describe(featureclass) has dataset, feature class and table properties in addition to the default any kind of data properties.






      share|improve this answer

























        0












        0








        0







        In your selection query you are expressing 121 as a string '121', as your objectid field is a long integer type the less than operator < doesn't work with a mismatched data type. To fix up your code in the easiest way:



        query = '"objectid" < 121'
        for featureclass in dataset:
        if featureclass == 'Contour_10m':
        output = os.path.join(outpath,featureclass)
        arcpy.Select_analysis(featureclass, output, query)


        However, to make the code more flexible:



        for featureclass in dataset:
        if featureclass == 'Contour_10m':
        query = ' < 121'.format(arcpy.Describe(featureclass).OIDFieldName)
        output = os.path.join(outpath,featureclass)
        arcpy.Select_analysis(featureclass, output, query)


        Using the Describe statement to find the table property OIDFieldName will ensure that the code works for all data types that have an OID (most but not all do).



        Describe is extremely useful to access properties about all different types of data; on the help page there are a number of different data type properties, any given dataset may, and usually do, have properties from multiple types.. in this instance arcpy.Describe(featureclass) has dataset, feature class and table properties in addition to the default any kind of data properties.






        share|improve this answer













        In your selection query you are expressing 121 as a string '121', as your objectid field is a long integer type the less than operator < doesn't work with a mismatched data type. To fix up your code in the easiest way:



        query = '"objectid" < 121'
        for featureclass in dataset:
        if featureclass == 'Contour_10m':
        output = os.path.join(outpath,featureclass)
        arcpy.Select_analysis(featureclass, output, query)


        However, to make the code more flexible:



        for featureclass in dataset:
        if featureclass == 'Contour_10m':
        query = ' < 121'.format(arcpy.Describe(featureclass).OIDFieldName)
        output = os.path.join(outpath,featureclass)
        arcpy.Select_analysis(featureclass, output, query)


        Using the Describe statement to find the table property OIDFieldName will ensure that the code works for all data types that have an OID (most but not all do).



        Describe is extremely useful to access properties about all different types of data; on the help page there are a number of different data type properties, any given dataset may, and usually do, have properties from multiple types.. in this instance arcpy.Describe(featureclass) has dataset, feature class and table properties in addition to the default any kind of data properties.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered yesterday









        Michael StimsonMichael Stimson

        21.7k22460




        21.7k22460













            Popular posts from this blog

            រឿង រ៉ូមេអូ និង ហ្ស៊ុយលីយេ សង្ខេបរឿង តួអង្គ បញ្ជីណែនាំ

            QGIS export composer to PDF scale the map [closed] Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Print Composer QGIS 2.6, how to export image?QGIS 2.8.1 print composer won't export all OpenCycleMap base layer tilesSave Print/Map QGIS composer view as PNG/PDF using Python (without changing anything in visible layout)?Export QGIS Print Composer PDF with searchable text labelsQGIS Print Composer does not change from landscape to portrait orientation?How can I avoid map size and scale changes in print composer?Fuzzy PDF export in QGIS running on macSierra OSExport the legend into its 100% size using Print ComposerScale-dependent rendering in QGIS PDF output

            PDF-ში გადმოწერა სანავიგაციო მენიუproject page