Skip to main content
added 277 characters in body
Source Link
Zizouz212
  • 6.8k
  • 5
  • 38
  • 76

You need to look at what the license of your API will be.

You need to look at what the license of your API will be.

Looking at the ArcGIS Copyright Information page...

...No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or by any information storage or retrieval system, except as expressly permitted in writing by ESRI...

Therefore, using the api and allowing open source freedoms, such as reproduction and distribution is asking for trouble.

Looking at the ArcGIS Copyright Information page..I misunderstood.

...No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or by any information storage or retrieval system, except as expressly permitted in writing by ESRI...

Therefore, using It seems like the api and allowing open source freedomslibrary in question is actually ArcPy, such as reproduction and distribution is asking for troublenot ArcGIS.


Therefore, to answer your question, you need to look at the nature of your "referenced libraries". You need to look at their copyright/licensing terms, analyze them, and determine how they will impact the goals of your project. For example, can I still fork, share it and the like. You can have specific terms and conditions, such as copyleft (also known as ShareAlike), or make it as permissive as possible (Such as this license). In the end, you will know your work is Open Source, if it meets their definition:

  1. Free Redistribution
  2. Source Code
  3. Derived Works
  4. Integrity of The Author's Source Code
  5. No Discrimination Against Persons or Groups
  6. No Discrimination Against Fields of Endeavour
  7. Distribution of License
  8. License Must Not Be Specific to a Product
  9. License Must Not Restrict Other Software
  10. License Must Be Technology-Neutral

You need to look at what the license of your API will be.

Looking at the ArcGIS Copyright Information page...

...No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or by any information storage or retrieval system, except as expressly permitted in writing by ESRI...

Therefore, using the api and allowing open source freedoms, such as reproduction and distribution is asking for trouble.


Therefore, to answer your question, you need to look at the nature of your "referenced libraries". You need to look at their copyright/licensing terms, analyze them, and determine how they will impact the goals of your project. In the end, you will know your work is Open Source, if it meets their definition:

  1. Free Redistribution
  2. Source Code
  3. Derived Works
  4. Integrity of The Author's Source Code
  5. No Discrimination Against Persons or Groups
  6. No Discrimination Against Fields of Endeavour
  7. Distribution of License
  8. License Must Not Be Specific to a Product
  9. License Must Not Restrict Other Software
  10. License Must Be Technology-Neutral

You need to look at what the license of your API will be.

Looking at the ArcGIS Copyright Information page...

...No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or by any information storage or retrieval system, except as expressly permitted in writing by ESRI...

Therefore, using the api and allowing open source freedoms, such as reproduction and distribution is asking for trouble.

I misunderstood. It seems like the library in question is actually ArcPy, and not ArcGIS.


Therefore, to answer your question, you need to look at the nature of your "referenced libraries". You need to look at their copyright/licensing terms, analyze them, and determine how they will impact the goals of your project. For example, can I still fork, share it and the like. You can have specific terms and conditions, such as copyleft (also known as ShareAlike), or make it as permissive as possible (Such as this license). In the end, you will know your work is Open Source, if it meets their definition:

  1. Free Redistribution
  2. Source Code
  3. Derived Works
  4. Integrity of The Author's Source Code
  5. No Discrimination Against Persons or Groups
  6. No Discrimination Against Fields of Endeavour
  7. Distribution of License
  8. License Must Not Be Specific to a Product
  9. License Must Not Restrict Other Software
  10. License Must Be Technology-Neutral
Source Link
Zizouz212
  • 6.8k
  • 5
  • 38
  • 76

You need to look at what the license of your API will be.

Looking at the ArcGIS Copyright Information page...

...No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or by any information storage or retrieval system, except as expressly permitted in writing by ESRI...

Therefore, using the api and allowing open source freedoms, such as reproduction and distribution is asking for trouble.


Therefore, to answer your question, you need to look at the nature of your "referenced libraries". You need to look at their copyright/licensing terms, analyze them, and determine how they will impact the goals of your project. In the end, you will know your work is Open Source, if it meets their definition:

  1. Free Redistribution
  2. Source Code
  3. Derived Works
  4. Integrity of The Author's Source Code
  5. No Discrimination Against Persons or Groups
  6. No Discrimination Against Fields of Endeavour
  7. Distribution of License
  8. License Must Not Be Specific to a Product
  9. License Must Not Restrict Other Software
  10. License Must Be Technology-Neutral